WO2024066898A1 - 一种数据包丢弃的方法及相关设备 - Google Patents

一种数据包丢弃的方法及相关设备 Download PDF

Info

Publication number
WO2024066898A1
WO2024066898A1 PCT/CN2023/116090 CN2023116090W WO2024066898A1 WO 2024066898 A1 WO2024066898 A1 WO 2024066898A1 CN 2023116090 W CN2023116090 W CN 2023116090W WO 2024066898 A1 WO2024066898 A1 WO 2024066898A1
Authority
WO
WIPO (PCT)
Prior art keywords
data unit
unit set
protocol data
packet
packet loss
Prior art date
Application number
PCT/CN2023/116090
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 WO2024066898A1 publication Critical patent/WO2024066898A1/zh

Links

Classifications

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

Definitions

  • the present application relates to the field of data processing, and in particular to a method for discarding data packets and related equipment.
  • Extended reality (XR) technology refers to the combination of display and virtuality through computers to create a virtual environment for human-computer interaction, including virtual reality (VR), augmented reality (AR), mixed reality (MR), and cloud games (CG).
  • the services involved in XR technology are usually audio or video. Therefore, in the XR scenario, the data streams exchanged between the user equipment (user equipment, the sending device) and the network device are usually audio data streams or video data streams.
  • the data unit (such as a frame or a video slice) exchanged between the sending device and the network device may include multiple Internet Protocol (IP) packets, and an IP packet will include at least one protocol data unit set (PDU). Therefore, in the video service, the data unit transmitted between the sending device and the network device can actually be regarded as a PDU set (protocol data unit set) including multiple PDUs.
  • IP Internet Protocol
  • PDU protocol data unit set
  • An embodiment of the present application provides a method and related equipment for discarding data packets. By judging whether to perform packet discard processing on the protocol data unit set or the data packets included therein based on at least one of the packet loss number, packet loss timer, attribute information, and dependency relationship corresponding to the protocol data unit set, the method can avoid the continued transmission of useless data and save air interface resources.
  • a method for discarding a data packet which is applied to a sending end, and the method comprises:
  • the judgment basis adopted by the preset judgment method includes at least one of the number of packet losses corresponding to the protocol data unit set, the packet loss timer of the protocol data unit set, the first attribute information corresponding to the protocol data unit set, the second attribute information corresponding to the data packet, and the dependency relationship between the protocol data unit set and other protocol data unit sets; the attribute information is associated with whether to allow discarding or not to allow discarding, and the protocol data unit set includes one or more of the data packets;
  • the protocol data unit set or the data packet included in the protocol data unit set is discarded.
  • a data packet may include a PDU data packet or an SDU data packet, but the present application does not limit this.
  • a protocol data unit set may, for example, refer to a set of multiple data packets, which may include one or more data packets. Exemplarily, a protocol data unit set may correspond to a PDU set, but is not limited thereto.
  • discarding the protocol data unit set or the data packet may include: discarding the data packets in the protocol data unit set that have not been discarded.
  • the data packets that have not been discarded may refer to data packets that have been received but not discarded by the sender; or, may refer to data packets in the protocol data unit set that have not been received, that is, if it is determined that the data packets in the protocol data unit set need to be discarded, the data packets in the protocol data unit set may be directly discarded after being received.
  • allowing to discard means that a set of protocol data units or data packets can be discarded without causing packet loss processing for the set of protocol data units or data packets in the set of protocol data units.
  • Not allowing to discard means that a set of protocol data units or data packets cannot be discarded, and if discarded, it will cause packet loss processing for the set of protocol data units or data packets in the set of protocol data units.
  • the association of attribute information with whether to allow discarding or not to allow discarding means that a data packet or a set of protocol data units having the attribute information belongs to a type of data packet or a set of protocol data units that are allowed to be discarded; or a data packet or a set of protocol data units having the attribute information belongs to a type of data packet or a set of protocol data units that are not allowed to be discarded.
  • a set of high priority data packets or protocol data units belongs to a set of data packets or protocol data units that are not allowed to be discarded, and if discarding occurs, the corresponding set of protocol data units or other data packets in the set of protocol data units need to be discarded.
  • the sending end may be a user equipment, but is not limited thereto.
  • determining whether to discard a protocol data unit set or a data packet included in the protocol data unit set according to a preset judgment method may also refer to determining whether a protocol data unit set or a data packet included in the protocol data unit set meets a discarding condition according to a preset judgment method, and when the discarding condition is met, discarding the protocol data unit set or the data packet included in the protocol data unit set.
  • the number of packet losses or the discarded data packets corresponding to the packet loss counter count in the judgment basis refer to data packets discarded by other means.
  • the other means here refer to the means other than the data packet discarding method provided in the embodiment of the present application, such as: data packets discarded due to network status, communication status, etc.; or data packets discarded due to discard timer timeout; or data packets discarded after the transmission of data packets or protocol data unit sets is completed, etc.
  • the embodiments of the present application do not limit this.
  • the data packets discarded in the protocol data unit set mentioned in the present application can refer to the above explanation, and no special explanation will be given later.
  • this method by judging whether to perform packet loss processing on the protocol data packet unit set based on at least one of the packet loss number, packet loss timer, attribute information, and dependency relationship corresponding to the protocol data packet unit set, this method can avoid the continued transmission of useless data and save air interface resources.
  • the first attribute information includes at least one of a sequence number corresponding to the protocol data unit set, a total number of the data packets included in the protocol data unit set, an importance level of the protocol data unit set, a priority of the protocol data unit set, and a dependency relationship of the protocol data unit set;
  • the second attribute information includes at least one of a data packet sequence number corresponding to the data packet, a position of the data packet in the protocol data unit set, an importance level of the data packet, and a priority level of the data packet.
  • the second attribute information of the data packet may further include a discard type corresponding to the data packet, and the discard type may include allowing discard or not allowing discard.
  • the method when the judgment basis adopted by the preset judgment method is the number of packet losses corresponding to the protocol data unit set, the method specifically includes:
  • the protocol data unit set or the data packet is discarded.
  • the packet loss threshold refers to the maximum number threshold of packets that can be discarded in a protocol data unit set. When it is determined that the number of packet losses in a protocol data unit set reaches or exceeds the packet loss threshold, the packets in the protocol data unit set can be directly discarded.
  • the packet loss threshold is configured in a confirmation mode.
  • the confirmation mode includes receiving indication information fed back by the receiving end after transmitting a data packet, and the indication information indicates whether the data packet is successfully transmitted or needs to be retransmitted.
  • the confirmation mode includes an AM mode or a HARQ transmission mode or an SN status report, which is not limited in this application.
  • the number of packet losses obtained does not include data packets discarded due to successful transmission, or the number of packet losses obtained only includes data packets discarded due to discard timer expiration.
  • the data packets in the protocol data unit set can be directly discarded. For example, assuming that the packet loss threshold is 10, if the number of packet losses of the protocol data unit set reaches 10, that is, the number of packet losses is equal to the packet loss threshold, the data packets in the protocol data unit set can be directly discarded.
  • the data packets in the protocol data unit set can be directly discarded. For example, assuming that the packet loss threshold is 10, if the number of packet losses of the protocol data unit set increases from 10 to 11, that is, the number of packet losses is greater than the packet loss threshold, the data packets in the protocol data unit set can be directly discarded.
  • obtaining the packet loss threshold corresponding to the protocol data unit set specifically includes:
  • the receiving end may be used to receive the data packet.
  • the packet loss threshold pre-configured by the transmitting end itself may be a statically configured packet loss threshold; the packet loss threshold sent by a high-level layer of the transmitting end may be a dynamically configured packet loss threshold.
  • the high layer may refer to an application layer or a transport layer.
  • the method when the packet loss threshold is configured by the transmitting end itself, the method further includes:
  • the packet loss threshold is configured at the granularity of a protocol layer entity; or,
  • the packet loss threshold is configured with a data radio bearer (DRB) as a granularity; or,
  • DRB data radio bearer
  • the packet loss threshold is configured based on the protocol data unit set as the granularity; or,
  • the packet loss threshold is configured based on the granularity of the type of the protocol data unit set, wherein the type of the protocol data unit set is at least one of the priority of the protocol data unit set, the importance level of the protocol data unit set, and the sequence number of the protocol data unit set.
  • configuring the packet loss threshold with the protocol layer entity as the granularity may refer to configuring the packet loss threshold with each protocol layer entity as the object, that is, configuring different packet loss thresholds for different protocol layer entities. For example, for the PDCP layer entity, one PDCP protocol layer entity is configured with 9 as the packet loss threshold, and another PDCP protocol layer entity is configured with 10 as the packet loss threshold.
  • Configuring the packet loss threshold with the data radio bearer DRB as the granularity may refer to configuring the packet loss threshold with each DRB as the object, that is, different packet loss thresholds may be configured for different DRBs.
  • Configuring the packet loss threshold with the protocol data unit set as the granularity may refer to configuring the packet loss threshold with each protocol data unit set as the object, and different protocol data unit sets may correspond to different packet loss thresholds.
  • Configuring the packet loss threshold with the type of the protocol data unit set as the granularity may refer to configuring the packet loss threshold with the type of each protocol data unit set as the object, and different types of protocol data unit sets may correspond to different packet loss thresholds.
  • the method when the judgment basis adopted by the preset judgment method is the number of packet losses corresponding to the protocol data unit set, the method specifically includes:
  • the protocol data unit set or the data packet is discarded.
  • Discarding the data packet may specifically refer to discarding the data packet in the protocol data unit set.
  • the packet loss ratio is a ratio of the number of packet losses in a protocol data unit set to the total number of data packets included in the protocol data unit set.
  • obtaining a packet loss ratio threshold corresponding to the protocol data unit set specifically includes:
  • the data packet received by the receiving end may refer to a data packet in a protocol data unit set transmitted by the receiving end.
  • the packet loss ratio threshold pre-configured by the transmitting end itself may be a statically configured packet loss ratio threshold; the packet loss threshold sent by a high-level layer of the transmitting end may be a dynamically configured packet loss ratio threshold.
  • the packet loss ratio threshold pre-configured by the transmitting end itself may refer to the packet loss ratio threshold configured when the transmitting end is powered on.
  • the high layer may refer to an application layer or a transport layer.
  • the method when the packet loss ratio threshold is configured by the transmitting end itself, the method further includes:
  • the packet loss ratio threshold is configured at the granularity of the protocol layer entity.
  • the packet loss ratio threshold is configured with DRB as the granularity; or,
  • the packet loss ratio threshold is configured based on the protocol data unit set as the granularity; or,
  • the packet loss ratio threshold is configured based on the granularity of the type of the protocol data unit set, wherein the type of the protocol data unit set is at least one of the priority of the protocol data unit set, the importance level of the protocol data unit set, and the sequence number of the protocol data unit set.
  • configuring the packet loss ratio threshold with the protocol layer entity as the granularity may refer to configuring the packet loss ratio threshold with each protocol layer as the object, that is, configuring different packet loss ratio thresholds for different protocol layer entities. For example, for the PDCP layer entity, one PDCP protocol layer entity is configured with 20% as the packet loss ratio threshold, and another PDCP protocol layer entity is configured with 10% as the packet loss ratio threshold.
  • Configuring the packet loss ratio threshold with the data radio bearer DRB as the granularity may refer to configuring the packet loss ratio threshold with each DRB as the object, that is, different packet loss ratio thresholds may be configured for different DRBs.
  • Configuring the packet loss ratio threshold with the protocol data unit set as the granularity may refer to configuring the packet loss ratio threshold with each protocol data unit set as the object, and different write data unit sets may correspond to different packet loss ratio thresholds.
  • Configuring the packet loss ratio threshold with the type of the protocol data unit set as the granularity may refer to configuring the packet loss ratio threshold with the type of each protocol data unit set as the object, and different types of protocol data unit sets may correspond to different packet loss ratio thresholds.
  • obtaining the number of packet losses corresponding to the protocol data unit set specifically includes:
  • the packet loss counter is used to count the number of the data packets discarded in the protocol data unit set
  • the number of packet losses corresponding to the protocol data unit set is obtained according to the count value of the packet loss counter.
  • the method when the packet loss counter counts the number of the data packets discarded in the protocol data unit set, the method further includes:
  • the packet loss counter does not count the data packets that are successfully transmitted and discarded.
  • successfully transmitted and discarded data packets may refer to data packets that are discarded in the cache after the sending end receives a message from the receiving end indicating that a certain data packet has been successfully transmitted.
  • the method further includes:
  • the packet loss counter is released or cleared
  • the packet loss counter is released or cleared
  • the packet loss counter is released or cleared;
  • the packet loss counter is released or cleared; or
  • the packet loss counter is released or cleared.
  • the transmission completion of the protocol data unit set and/or the data packet may refer to: in confirmation mode, determining that the last data packet (such as End PDU) has been received or determining that all data packets of the protocol data unit set have been received, and all data packets in the protocol data unit set have been transmitted.
  • the transmission completion of all data packets here may include two parts of data packets: (1) the sending end receives a message fed back by the receiving end, thereby determining that the data packet is successfully transmitted; (2) the sending end does not receive a feedback message and the data packet is discarded when the timer (discard timer) corresponding to the data packet times out.
  • non-confirmation mode determining that the last data packet in the protocol data unit set is transmitted to the next layer or determining that all data packets of the protocol data unit set have been received.
  • the method further includes:
  • the packet loss counter is set.
  • setting the packet loss counter means configuring the counter in a mode where there is a data packet confirming successful transmission.
  • the method when the judgment basis adopted by the preset judgment method is the packet loss timer of the protocol data unit set, the method specifically includes:
  • the protocol data unit set or the data packet is discarded; or,
  • the protocol data unit set or the data packet When the packet loss timer times out, if the protocol data unit set or the data packet has not been completely transmitted, the protocol data unit set or the data packet is discarded.
  • the packet loss timer when the first data packet in the protocol data unit set is received, the packet loss timer is started.
  • the first data packet in the protocol data unit set may include: a data packet with a sequence number of 1 in the protocol data unit set, or a STRAT data packet in the protocol data unit set, such as a data packet with a START identifier.
  • the method further includes:
  • the protocol data unit set or the data packet is discarded.
  • the protocol data unit set or the data packet is not completely transmitted, specifically including:
  • the transmitting end When the packet loss timer times out, the transmitting end has the data packet in the protocol data unit set.
  • the protocol data unit set that has not been completely transmitted includes the protocol data unit set that may include: (1) the protocol layer entity did not receive the feedback message sent by the receiving end, and therefore did not discard the relevant data packet, which means that the receiving end may not have received the data packet, that is, the data packet has not been completely transmitted; (2) there are still data packets in the protocol layer entity that have not been transmitted to the next layer, which also means that the data packet has not been completely transmitted; (3) the data packets of the protocol data unit set are cached in the protocol layer entity.
  • obtaining a packet loss timer corresponding to the protocol data unit set specifically includes:
  • the high layer may refer to an application layer or a transport layer.
  • the method further includes:
  • the packet loss timer is released or cleared
  • the packet loss timer When the packet loss timer has not timed out and the transmission of the protocol data unit set and/or data packet is completed, the packet loss timer is released or cleared; or,
  • the packet loss timer When the packet loss timer times out, the packet loss timer is released or cleared.
  • the method when the judgment basis adopted by the preset judgment method is the number of packet losses corresponding to the protocol data unit set and the packet loss timer, the method specifically includes:
  • the protocol data unit set or the data packet is discarded.
  • the protocol data unit set or the data packet is not completely transmitted, specifically including: when the packet loss timer times out, the sending end has the data packet in the protocol data unit set.
  • the protocol data unit set or the data packet is not completely transmitted, specifically including:
  • the transmitting end stores the data packet in the protocol data unit set.
  • the method when the judgment basis adopted by the preset judgment method is the first attribute information corresponding to the protocol data unit set and/or the second attribute information corresponding to the data packet, the method specifically includes:
  • the protocol data unit set with the first attribute information is discarded, the protocol data unit set or the data packet is discarded; or,
  • the protocol data unit set or the data packet is discarded.
  • the method further includes:
  • Acquire seventh configuration information sent by a receiving end wherein the seventh configuration information is used to indicate the first attribute information corresponding to the protocol data unit set and/or the second attribute information corresponding to the data packet, and the receiving end is used to receive the data packet; or,
  • Receive eighth configuration information sent by the core network where the eighth configuration information is used to indicate the first attribute information corresponding to the protocol data unit set and/or the second attribute information corresponding to the data packet.
  • the method when the judgment basis adopted by the preset judgment method is the dependency relationship between the protocol data unit set and other protocol data unit sets, the method specifically includes:
  • the first protocol data unit set has a dependency relationship with at least one second protocol data unit set
  • the first protocol data unit set or the data packet included in the first protocol data unit set is discarded.
  • obtaining at least one second protocol data unit set having a dependency relationship with the first protocol data unit set specifically includes:
  • Receive tenth configuration information sent by the core network where the tenth configuration information is used to indicate a dependency identifier; wherein the dependency identifier is used to indicate other protocol data unit sets that are mutually dependent on the protocol data unit set.
  • the method further includes:
  • the protocol data unit set or the data packet of the triggering protocol layer is discarded.
  • discarding the protocol data unit set or the data packet included in the protocol data unit set specifically includes:
  • the protocol layer of the sending end device determines to discard the protocol data unit set or the data packet included in the protocol data unit set according to a preset judgment method, the protocol data unit set or the data packet is discarded.
  • the method further includes:
  • the protocol layer entity of the sending device determines to discard the protocol data unit set or the data packet, if the data packet of the protocol data unit set has been transmitted to the next layer corresponding to the protocol layer, the protocol layer entity sends a notification message to the protocol layer entity of the next layer, and the notification message is used to instruct the protocol layer entity of the next layer to discard the data packet.
  • a method for discarding a data packet which is applied to a sending end, and the method includes:
  • the protocol data unit set of the triggering protocol layer or a data packet in the protocol data unit set is discarded, and the protocol data unit set includes at least one of the data packets.
  • triggering the protocol data unit set of the protocol layer or discarding a data packet in the protocol data unit set may refer to triggering a packet loss processing function of the protocol layer.
  • the protocol layer may execute the method in any implementation of the first aspect.
  • a method for discarding a data packet which is applied to a sending end, and the method includes:
  • a method for discarding a data packet which is applied to a receiving end, and the method includes:
  • the configuration information is sent to the sending end, so that the sending end determines whether to discard the protocol data unit set or the data packet included in the protocol data unit set according to a preset judgment method based on at least one item in the configuration information; the configuration information includes at least one item of the packet loss threshold, the packet loss ratio threshold, the packet loss timer, the first attribute information corresponding to the protocol data unit set, the second attribute information corresponding to the data packet, and a dependency identifier.
  • the method further includes:
  • the configuration information is configured at the granularity of a protocol layer entity; or,
  • the configuration information is configured with DRB as the granularity; or,
  • the configuration information is configured with the protocol data unit set as the granularity; or,
  • the configuration information is configured with the type of the protocol data unit set as the granularity, wherein the type of the protocol data unit set is at least one of the priority of the protocol data unit set, the importance level of the protocol data unit set, and the sequence number of the protocol data unit set.
  • the data structure of the configuration information is a sequence structure.
  • a transmitting end device including:
  • processors one or more processors
  • the one or more memories store one or more computer programs, and the one or more computer programs include instructions.
  • the terminal device executes the method described in any one of the implementation methods of the first to third aspects above.
  • a communication system comprising a transmitting device and a receiving device, wherein the transmitting device is used to execute a method as described in any implementation manner in the first to third aspects above, and the receiving device is used to execute a method as described in any implementation manner in the fourth aspect above.
  • a computer-readable storage medium stores computer-executable program instructions, and when the computer-executable program instructions are executed on a computer, the computer executes a method as described in any one of the implementation methods of the first to fourth aspects above.
  • a computer program product comprising a computer program code, and when the computer program code is run on a computer, the computer is caused to execute the method as described in any one of the implementation modes of the first to fourth aspects above.
  • FIG1 is a schematic diagram of the structure of a protocol data unit set provided in an embodiment of the present application.
  • FIG2A is a schematic diagram of a system architecture applicable to a method for discarding data packets provided in an embodiment of the present application.
  • FIG2B is a schematic diagram of the structure of a transmitting end device 100 provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of a protocol data unit set transmission process provided in an embodiment of the present application.
  • FIG4 is a schematic flowchart of a method for discarding data packets provided in an embodiment of the present application.
  • FIG5 is a schematic flowchart of another method for discarding data packets provided in an embodiment of the present application.
  • FIG6 is a schematic flowchart of another method for discarding data packets provided in an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another method for discarding data packets provided in an embodiment of the present application.
  • FIG8 is a schematic flowchart of another method for discarding data packets provided in an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of another method for discarding data packets provided in an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a triggering flow of discard processing in a method for discarding data packets provided in an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another method for discarding data packets provided in an embodiment of the present application.
  • first and second are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, it is defined that the “first” and “second” features may explicitly or implicitly include one or more of the features.
  • references to "one embodiment” or “some embodiments” etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application.
  • the phrases “in one embodiment”, “in some embodiments”, “in some other embodiments”, “in some other embodiments”, etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean “one or more but not all embodiments", unless otherwise specifically emphasized in other ways.
  • the terms “including”, “comprising”, “having” and their variations all mean “including but not limited to”, unless otherwise specifically emphasized in other ways.
  • a protocol data unit set can be used as a data unit in the data transmission process.
  • a protocol data unit set consists of one or more data packets, each of which can carry a payload that constitutes an information unit.
  • the application layer at the receiving end can obtain a complete information unit based on the payload carried by all PDUs in a protocol data unit set, such as information corresponding to a video frame or a picture frame.
  • the data unit may include frames and video slices. Among them, a frame can be understood as a carrier of transmitted data, and a video slice can be understood as a specific type of data unit in a video service.
  • a protocol data unit set can correspond to a frame; from the perspective of the type of transmitted data, in some cases, in a video service, the data carried by a protocol data unit set can correspond to a video slice.
  • the application layer at the receiving end needs to receive all the data packets in the protocol data unit set to obtain a complete information unit. Discarding one or more data packets may cause the receiving end to be unable to obtain the entire information unit. However, in some cases, the application layer at the receiving end can also calculate the discarded part of the data based on the acquired PDU data through certain algorithms, so that even if some (such as a small number or less important) PDUs are discarded, the application layer at the receiving end can still recover all or part of the information unit.
  • a PDU set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level (e.g. a frame or video slice for XRM Services, as used in TR 26.926[27]).
  • all PDUs in a PDU set are needed by the application layer to use the corresponding unit of information.
  • the application layer can still recover parts all or of the information unit, when some PDUs are missing.
  • the above definition shows that in some implementations, the application layer needs to receive all PDUs in the PDU set to obtain the information unit; in another implementation, when some PDUs are discarded, the application layer can still recover all or part of the information unit.
  • SA defines a variety of attribute information about protocol data unit sets and/or data packets, including, for example: the sequence number of the protocol data unit set, the total number of data packets included in the protocol data unit set, the importance level of the protocol data unit set, the priority of the protocol data unit set, the dependency/dependency relationship of the protocol data unit set; the sequence number of the data packet in the protocol data unit set, the position of the data packet in the protocol data unit set (such as the start data packet/end data packet, etc.), the importance level of the data packet, the priority of the data packet, etc.
  • PDU set sequence number PDU Sequence number, SN
  • Start/End PDU of the PDU set PDU sequence number in a PDU set
  • PDU sequence number in a PDU set PDU SN within a PDU set
  • Number of PDUs within a PDU set (5) PDU set importance; (6) PDU set dependency.
  • the above attribute information may be configured by the receiving end, or may be configured by the sending end itself, such as by the application layer, transport layer or high layer of the sending end, or by the core network.
  • the importance level of a data packet may mean that each PDU in the same protocol data unit set may have different importance levels.
  • the importance of the first data packet (i.e., the start data packet) in the protocol data unit set is higher than the importance of the last data packet (i.e., the last or end data packet).
  • the dependency of a protocol data unit set may mean that some protocol data unit sets may depend on other protocol data unit sets.
  • the dependency of the protocol data unit set may be expressed as whether a video slice has use value depends on whether the previous video slice is successfully received.
  • the dependency of the protocol data unit set may be expressed as two video slices belong to the same frame, and the frame can only be correctly decoded after all the video slices in a frame are successfully decoded. In this case, only when the previous video slice (protocol data unit set) is successfully transmitted, the transmission of the next video slice (protocol data unit set) is meaningful.
  • SA also defines related QoS requirements, including: (1) protocol data unit set delay budget, for example, for PDU set, it can be expressed as PDU set Delay Budget (PSDB); (2) protocol data unit set error rate, for example, for PDU set, it can be expressed as PDU set Error Rate (PSER).
  • PSDB PDU set Delay Budget
  • PSER PDU set Error Rate
  • the protocol data unit set can be understood as a new transmission form for transmitting XR data streams (or other types of video/audio data streams).
  • the reason for proposing the protocol data unit set is mainly based on the following two reasons:
  • the XR data stream may include different types of frames. Since different types of frames have different corresponding importance, there may be frames of different importance in an XR data stream (such as I frames, P frames, and B frames). Based on the current protocol, an XR data stream is transmitted in a QoS stream, and the current QoS processing is based on the QoS stream, so frames of different importance transmitted in a QoS stream may be subjected to the same QoS processing. But in fact, frames with lower importance may not require the same QoS processing as frames with higher importance. In view of this, it is necessary to propose a more fine-grained data stream transmission method to transmit frames of different importance separately.
  • a data unit (such as a frame or video slice) that needs to be transmitted by the application layer or transport layer usually includes multiple IP data packets, and an IP data packet may include at least one data packet (such as a PDU). Therefore, when transmitting a video frame, multiple data packets are actually transmitted.
  • a protocol data unit set can be used as a data unit, which can specifically correspond to a frame or a video slice.
  • a protocol data unit set includes multiple data packets, each of which has a sequence number (such as PDU SN) that is different from other data packets.
  • the payloads carried by the multiple data packets can constitute information units (such as a video frame, a picture, etc.).
  • Different protocol data unit sets can be set with different importance levels.
  • a protocol data unit set with a high importance level can be used to transmit frames of high importance
  • a protocol data unit set with a low importance level can be used to transmit frames of low importance, thereby realizing the separate transmission of frames of different importance so that these frames can be processed differently later.
  • the structure of a protocol data unit set can be shown in Figure 1, and the PDU set includes 8 PDUs, that is, the number of PDUs within a PDU set (Number of PDUs within a PDU set) is 8, and the PDU sequence numbers (PDU SN) of these 8 PDUs can be recorded as: PDU SN1, PDU SN2, ..., PDU SN8. It should be understood that the number of PDUs included in the protocol data unit set shown in Figure 1 and the representation of the PDU sequence number are only examples, and the embodiments of the present application are not limited to this.
  • the protocol data unit set as a whole or some data packets in the protocol data unit set may be discarded.
  • Different packet loss situations may have different effects on the application layer of the receiving end to obtain information units. For example, it can be divided into the following situations:
  • Scenario 1 If one or more protocol data unit sets are discarded during the transmission process, the application layer at the receiving end cannot obtain the information units carried by the protocol data unit sets.
  • Scenario 2 If some data packets in a protocol data unit set are discarded during the transmission process, and the application layer at the receiving end cannot obtain the information units carried by the protocol data unit set through the remaining data packets, then the remaining data packets in the protocol data unit set are no longer of use value and lose their function.
  • Scenario 3 If a small number of packets or packets with a lower importance level in the protocol data unit set are discarded during the transmission process, but the application layer at the receiving end can calculate the data content carried by the discarded packets based on other PDUs received in the protocol data unit set, then discarding the packets will not affect the application layer's acquisition of the information units carried by the protocol data unit set. However, if the number of discarded PDUs reaches a certain number, or the importance level of the discarded packets is relatively high, the application layer at the receiving end still cannot obtain the information units carried by the protocol data unit set.
  • the discarded data packets mentioned in the above three situations and similar situations below may refer to data packets discarded by other means.
  • the other means here refer to the methods other than the data packet discarding method provided in the embodiments of the present application, such as: data packets discarded due to network status, communication status, etc.; or data packets discarded due to discard timer timeout; or data packets discarded after the transmission of data packets or protocol data unit sets is completed, etc.
  • the embodiments of the present application do not limit this.
  • the data packets discarded in the protocol data unit set mentioned in this application can refer to the above explanation, and no special explanation will be given later.
  • the present application provides a method for discarding data packets.
  • whether to discard the remaining data packets or protocol data unit sets is calculated based on information about the number of lost packets, time information about the arrival of data packets, and dependencies between protocol data unit sets.
  • the method can avoid the transmission of invalid data packets or protocol data unit sets for the protocol data unit set or data packet, thereby saving air interface resources.
  • the method for discarding data packets provided in the embodiment of the present application can be applied to the scene of audio stream data, video stream data or picture data transmission between the sender and the receiver under audio, video, picture and other services, such as XR scene, etc.
  • the method for discarding data packets provided in the embodiment of the present application can be applied to various types of communication systems, such as the fifth generation ( 5th Generation, 5G) mobile communication system, such as the new radio (new radio, NR) system.
  • 5G fifth generation
  • NR new radio
  • universal mobile telecommunications system universal mobile telecommunications system
  • UMTS wireless local area network
  • WLAN wireless local area network
  • Wi-Fi wireless fidelity
  • wired system vehicle to everything (vehical to everything, V2X) communication system
  • device-to-device device-to-device, D2D
  • fourth generation 4th generation, 4G
  • satellite communication system satellite communication system
  • future communication systems such as the sixth generation ( 6th Generation, 6G) mobile communication system, etc.
  • 6G sixth generation
  • FIG. 2A is a schematic diagram of a system architecture 10 applicable to a method for discarding data packets provided in an embodiment of the present application.
  • the system architecture includes a transmitting device 100 and a receiving device 200 (or a transmitting end and a receiving end).
  • the transmitting end device 100 can be used as a transmitting end of data packet transmission
  • the receiving end device 200 can be used as a receiving end of data packet transmission.
  • the discarding process can be mainly performed by the transmitting end.
  • the transmitting device 100 can be various types of electronic devices, such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, cloud gaming (CG) devices, mixed reality (MR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), and other devices with audio/video and communication functions.
  • electronic devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, cloud gaming (CG) devices, mixed reality (MR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), and other devices with audio/video and communication functions.
  • AR augmented reality
  • VR virtual reality
  • CG cloud gaming
  • MR mixed reality
  • laptop computers laptop computers
  • UPC ultra-mobile personal computers
  • PDA personal digital assistants
  • the embodiments of the present application do not limit the types of transmitting devices.
  • the receiving device 200 may be a network device/core network device, for example, an access device for the transmitting device 100 to access the wireless communication system by wireless means.
  • the receiving device 200 may be an entity on the network side for transmitting or receiving signals, such as a base station.
  • the base station may broadly cover various names as follows, or be replaced with the following names, such as: Node B (NodeB), evolved NodeB (evolved NodeB, eNB), next generation NodeB (next generation NodeB, gNB), relay station, access point, transmission point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP), master station MeNB, auxiliary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), radio head (RRH), central unit (CU), distribution unit (DU), positioning node, etc.
  • NodeB Node B
  • eNB evolved NodeB
  • next generation NodeB next generation NodeB
  • relay station access point
  • transmission point transmission point
  • TRP transmitting and receiving point
  • TRP transmitting point
  • TP transmitting point
  • the base station may be a macro base station, a micro base station, a relay node, a donor node, or the like.
  • the base station may also be used for a communication module, a modem, or a chip disposed in the aforementioned device or apparatus.
  • the base station may also be a mobile switching center and a device that performs the base station function in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • FIG2B it is a schematic diagram of the structure of a transmitting end device 100 provided in an embodiment of the present application.
  • the sending device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.
  • SIM subscriber identification module
  • the transmitting end device 100 may include more or fewer components than those shown in the figure, or combine certain components, or split certain components, or arrange the components differently.
  • the illustrated components may be implemented in hardware, software, or a combination of software and hardware.
  • the interface connection relationship between the modules illustrated in the embodiments of the present application is a schematic illustration and does not constitute a structural limitation on the transmitting end device 100.
  • the transmitting end device 100 may also adopt an interface connection method different from that in the above-mentioned embodiments, or a combination of multiple interface connection methods.
  • the processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc.
  • AP application processor
  • GPU graphics processor
  • ISP image signal processor
  • controller a memory
  • video codec a digital signal processor
  • DSP digital signal processor
  • NPU neural-network processing unit
  • Different processing units may be independent devices or integrated in one or more processors.
  • the controller may be the nerve center and command center of the transmitting device 100.
  • the controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.
  • the processor 110 may also be provided with a memory for storing instructions and data.
  • the memory in the processor 110 is a cache memory.
  • the memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.
  • the charging management module 140 is used to receive charging input from the charger.
  • the power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110.
  • the power management module 141 receives input from the battery 142 and/or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160.
  • the power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc.
  • the power management module 141 can also be set in the processor 110.
  • the power management module 141 and the charging management module 140 can also be set in the same device.
  • the wireless communication function of the transmitting device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.
  • Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.
  • Each antenna in the transmitting end device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas.
  • antenna 1 can be reused as a diversity antenna for a wireless local area network.
  • the antenna can be used in combination with a tuning switch.
  • the mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G etc. applied on the transmitting end device 100 .
  • the wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) and the like applied to the transmitting device 100.
  • WLAN wireless local area networks
  • BT Bluetooth
  • GNSS global navigation satellite system
  • FM frequency modulation
  • NFC near field communication
  • IR infrared
  • the wireless communication module 160 can be one or more devices integrating at least one communication processing module.
  • the wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110.
  • the wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the signal, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.
  • the antenna 1 of the transmitting device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the transmitting device 100 can communicate with the network and other devices through wireless communication technology.
  • the wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technology.
  • the GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and/or a satellite based augmentation system (SBAS).
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • BDS Beidou navigation satellite system
  • QZSS quasi-zenith satellite system
  • SBAS satellite based augmentation system
  • the transmitting end device 100 implements the display function through the GPU, the display screen 194, and the application processor, etc.
  • the display screen 194 is used to display images, videos, etc.
  • the external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the sending end device 100.
  • the external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.
  • the internal memory 121 can be used to store computer executable program codes, and the executable program codes include instructions.
  • the internal memory 121 may include a program storage area and a data storage area.
  • the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the data storage area may store data created during the use of the sending end device 100 (such as audio data, a phone book, etc.).
  • the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device. Flash memory devices, universal flash storage (UFS), etc.
  • the processor 110 executes various functional applications and data processing of the sending end device 100 by running instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.
  • the transmitting device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor.
  • FIG3 a schematic diagram of a protocol data unit set transmission process provided in an embodiment of the present application is provided.
  • the process of transmitting a data packet in a protocol data unit set at the transmitting end may involve the following layers: service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, radio link control protocol (RLC) layer and medium access control (MAC) layer.
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control protocol
  • MAC medium access control
  • the protocol data unit set data packet mentioned in the embodiment of the present application can be an SDU data packet or a PDU data packet.
  • the effective load carried by the SDU data packet and the PDU data packet can be the same, and the relationship between the two can be understood as follows: in the protocol layer, the PDU of this layer is the lower layer SDU, and the SDU of this layer is the upper layer PDU.
  • the process of transmitting a data packet of a protocol data unit set by the transmitting end may include: the SDAP layer obtains the IP data packet transmitted by its upper layer (application layer or transport layer), performs radio bearer (RB) processing on the basis of the IP data packet, and generates a data packet including a header and a physical part SDAP SDU (i.e., payload), and the data packet may be marked as an SDAP PDU data packet. Afterwards, the SDAP layer transmits the SDAP PDU data packet to the PDCP layer.
  • the SDAP layer obtains the IP data packet transmitted by its upper layer (application layer or transport layer), performs radio bearer (RB) processing on the basis of the IP data packet, and generates a data packet including a header and a physical part SDAP SDU (i.e., payload), and the data packet may be marked as an SDAP PDU data packet.
  • the SDAP layer transmits the SDAP PDU data packet to the PDCP layer.
  • the PDCP layer After the PDCP layer obtains the SDAP PDU data packet, it processes the data packet according to the PDCP protocol, and generates a data packet including a header H and a physical part PDCP PDU, and the data packet may be marked as a PDCP PDU data packet. Afterwards, the PDCP layer further transmits the PDCP PDU data packet to the PLC layer.
  • the RLC layer After the RLC layer obtains the PDCP PDU data packet, it processes the PDCP PDU data packet according to the RLC protocol, and generates a data packet including a header H and a physical part RLC PDU, and the data packet may be marked as an RLC PDU data packet. Afterwards, the RLC layer further transmits the RLC PDU data packet to the MAC layer.
  • the MAC layer After the MAC layer obtains the RLC PDU data packet, it processes the RLC PDU data packet according to the MAC protocol to generate a data packet including a header H and a physical part MAC PDU. This data packet can be marked as a MAC PDU data packet.
  • the MAC layer can obtain multiple MAC PDU data packets corresponding to a data unit. Based on these MAC PDU data packets, the MAC can finally obtain a MAC PDU transport block including multiple data packets. After that, the MAC layer can transmit the generated MAC PDU transport block to the receiving end through air interface resources.
  • the receiving end can parse the protocol data unit according to the reverse process of generating the protocol data unit, so that the application layer of the receiving end can obtain the data carried by all PDUs in the protocol data unit set based on the parsed result, and then obtain the information unit according to the payload carried by all PDUs.
  • the specific method and process of parsing the data in the protocol data unit set by the receiving end can be set according to the relevant protocol or actual needs, and the embodiments of the present application are not limited to this.
  • the method of parsing the protocol data unit set by the network device described in the embodiment of Figure 3 of the present application is only an example.
  • the application layer of the receiving end can also obtain the data carried by the PDU in other ways, and the embodiment of the present application does not limit this.
  • the specific method and processing content of the SDAP layer, PDCP layer, RLC layer and MAC layer processing the data packet can refer to the provisions in the relevant protocol, and the embodiment of the present application will not be described in detail.
  • the protocol data unit set or the data packets included therein will be discarded; if it is determined not to discard the protocol data unit set or the data packets included therein (that is, the judgment result is not discarded), then even if there is a discard phenomenon of the protocol data unit set, the protocol data unit set and the data packets included in the protocol data unit set will not be discarded.
  • the present application may have multiple judgment methods for judging whether a protocol data unit set or a data packet needs to be discarded. For example, the judgment may be made based on the following judgment basis: the number of data packets discarded in the protocol data unit set, the packet loss timer of the protocol data unit set, the first attribute information corresponding to the protocol data unit set, the second attribute information corresponding to the data packet, the dependency relationship between the protocol data unit set and other protocol data unit sets, wherein the attribute information is associated with whether the discard is allowed or not.
  • the specific judgment process and discard process of each judgment method will be described in detail below and will not be described in detail here.
  • an operation of discarding the protocol data unit set or the data packet included in the protocol data unit set may also be performed in the protocol layer.
  • the protocol layer here may specifically be any one of the SDAP layer, the PDCP layer, the RLC layer, or the MAC layer, which is not limited in the embodiments of the present application.
  • the protocol layer In order to realize the judgment of whether to discard the protocol data unit set or the data packet included in the protocol data unit set, the protocol layer needs to perceive which protocol data unit set (or sub-QoS flow) the data packet in the protocol layer belongs to.
  • the above-mentioned perception purpose can be achieved by: the protocol layer obtains the attribute information of the data packet from the high layer, and then determines which protocol data unit set the data packet in the protocol layer belongs to based on the attribute information.
  • the high layer here can include the application layer or the transport layer.
  • the attribute information here can include the information defined by SA for the protocol data unit set, such as: the sequence number of the protocol data unit set, the start data packet and the end data packet in the protocol data unit set, the sequence number of each data packet in the protocol data unit set, the importance level of the data packet, the priority of the data packet, the total number of data packets in the protocol data unit set, the importance level of the protocol data unit set, the priority of the protocol data unit set, the dependency of the protocol data unit set, etc.
  • the protocol layer can also obtain QoS requirement information from the high layer, such as: the delay budget of the protocol data unit set, the fault tolerance rate of the protocol data unit set, etc.
  • the QoS requirement information can be the requirement information corresponding to the QoS flow for transmitting the protocol data unit set.
  • the protocol layer may obtain the above attribute information in a variety of ways, such as: Mode 1, the upper layer of the protocol layer may carry the above attribute information in a data packet and transmit it to the protocol layer; Mode 2, the upper layer of the protocol layer may transmit the data packet corresponding to the above attribute information to the protocol layer when or after transmitting the data packet.
  • Mode 1 the upper layer of the protocol layer may carry the above attribute information in a data packet and transmit it to the protocol layer
  • Mode 2 the upper layer of the protocol layer may transmit the data packet corresponding to the above attribute information to the protocol layer when or after transmitting the data packet.
  • This application does not limit the specific way in which the protocol layer obtains the above attribute information.
  • the protocol layer can be any one of the SDAP layer, the PDCP layer, the RLC layer or the MAC layer, the manner in which the protocol layer obtains the protocol data unit set attribute information can be divided into the following types:
  • the upper layer of the SDAP layer (such as the application layer or the transport layer or the upper protocol layer of the SDAP layer, which is not limited in this application) can indicate the above-mentioned attribute information corresponding to the protocol data unit set and/or the data packet to the SDAP layer.
  • the SDAP layer After the SDAP layer obtains the attribute information of the protocol data unit set and/or the data packet, it can encapsulate the attribute information in the SDAP PDU or notify the next protocol layer.
  • the SDAP layer or the protocol layer above the PDCP layer can indicate the above attribute information corresponding to the protocol data unit set and/or data packet to the PDCP layer.
  • the PDCP layer After the PDCP layer obtains the attribute information of the protocol data unit set and/or data packet, it can encapsulate the attribute information in the PDCP PDU or notify the next protocol layer.
  • the PDCP layer can instruct the RLC layer to receive the above-mentioned attribute information corresponding to the protocol data unit set and/or data packet. After the RLC layer obtains the attribute information of the protocol data unit set, it can encapsulate the attribute information in the RLC PDU or notify the next protocol layer.
  • the method for discarding data packets can judge the discarding condition from one or more aspects of the number of packet losses corresponding to the protocol data unit set, the packet loss timer of the protocol data unit set, the first attribute information corresponding to the protocol data unit set, the second attribute information corresponding to the data packet, and the dependency relationship between the protocol data unit set and other protocol data unit sets.
  • the specific judgment methods can be divided into the following:
  • Judgment method 1 determining whether to discard the protocol data unit set or the data packets included therein according to the number of lost packets of the protocol data unit set.
  • Judgment method 2 determining whether to discard the protocol data unit set or the data packets included therein according to the packet loss ratio of the protocol data unit set.
  • Judgment method 3 determining whether to discard the protocol data unit set or the data packets included therein according to whether the packet loss timer set for the protocol data unit set times out.
  • Judgment method 4 comprehensively determine whether to discard the protocol data unit set or the data packets included therein according to the number of packet losses for the protocol data unit set and the corresponding packet loss timer of the protocol data unit set.
  • Judgment method 5 Determine whether to discard the protocol data unit set or the data packets included therein according to whether the data packet with specific attribute information in the protocol data unit set is discarded, and the specific attribute information is associated with not allowing discarding.
  • Judgment method 6 for a protocol data unit set with dependency (or dependency relationship), determine whether to discard the protocol data unit set or the data packets included therein according to whether the associated protocol data unit set is lost or the number of lost packets.
  • the transmitting end is a user equipment (UE) and the receiving end is a network device.
  • UE user equipment
  • FIG. 4 is a schematic flow chart of a method for discarding a data packet provided in an embodiment of the present application.
  • the method for determining whether a packet is lost in the process may correspond to the above-mentioned determination method 1, that is, determining whether to discard the protocol data unit set or the data packets included therein according to the number of packet losses of the protocol data unit set.
  • the process may include the following steps:
  • the network device sends a packet loss threshold to the UE.
  • the network device sending the packet loss threshold to the UE can also be understood as the network device configuring the packet loss threshold to the UE.
  • the packet loss threshold is used to indicate the maximum threshold of the number of data packets that the protocol data unit set can allow to be discarded.
  • the maximum threshold of the number of data packets that the protocol data unit set can allow to be discarded here means that when the number of discarded data packets in the protocol data unit set is less than the threshold, it may not affect the network device application layer to obtain the information unit carried by the protocol data unit set. For example, the number of discarded data packets is small, and the network device can calculate the content carried by the discarded data packets based on the content of the data packets that have not been discarded, thereby obtaining the complete information unit. When the number of discarded data packets in the protocol data unit set is greater than or equal to the threshold, the network device may not be able to obtain the complete information unit based on the payload carried by the remaining data packets.
  • the embodiment of Figure 4 of the present application shows the process of configuring the packet loss threshold by the network device, but in actual applications, the packet loss threshold can also be configured by the higher layer of the UE (such as the application layer or the transport layer), or it can also be configured by the core network device, and the embodiment of the present application does not limit this.
  • the configuration granularity of the packet loss threshold is to configure each data radio bearer (DRB) separately, that is, the configuration granularity is per DRB, that is, the DRB configuration includes the packet loss threshold, and different DRBs may correspond to different packet loss thresholds; or, the configuration granularity of the packet loss threshold is to configure each protocol layer entity, that is, the protocol layer entity configuration includes the packet loss threshold, and different types of protocol layer entities (such as SDAP, PDCP, RLC, etc.) may correspond to different packet loss thresholds; or, the configuration granularity of the packet loss threshold is to configure each protocol data unit set separately, for example, the configuration granularity is per protocol data unit set, that is, the protocol data unit set configuration includes the packet loss threshold, and different protocol data unit sets may correspond to different packet loss thresholds; or, the configuration granularity of the packet loss threshold is to configure each type of protocol data unit set separately, that is, the protocol data unit set type configuration includes the packet loss threshold, and different types of protocol data unit
  • DRB
  • the type of the protocol data unit set mentioned above may be the importance level of the protocol data unit set, the priority of the protocol data unit set, and the sequence number of the protocol data unit set, which is not limited in the embodiments of the present application.
  • the packet loss thresholds corresponding to the protocol data unit set or the protocol data unit set type respectively can be a sequence structure.
  • the data type of the packet loss threshold configured by the network device may be an enumeration type or an integer type.
  • the network device can configure the packet loss threshold through radio resource control (RRC) signaling, MAC control element (MAC Control Element, MAC CE), and downlink control information (DCI).
  • RRC radio resource control
  • MAC Control Element MAC Control Element
  • DCI downlink control information
  • the packet loss threshold configured by the network device may be included in the data radio bearer (DRB) or protocol layer entity configuration.
  • DRB data radio bearer
  • the UE may determine the maximum number of data packets allowed to be discarded by the current protocol data unit set based on the packet loss threshold sent by the network device. In some embodiments, the UE may determine the number of packet losses of the current protocol data unit set based on the count value in the packet loss counter, and when the number of packet losses reaches the packet loss threshold, the protocol data unit set is discarded.
  • the process may include: the UE may maintain a packet loss counter for the current protocol data unit set, and when the protocol data unit set discards a data packet, the count value of the packet loss counter is increased by 1; when the count value of the packet loss counter is equal to the packet loss threshold or equal to (packet loss threshold + 1), the UE may discard the protocol data unit set or the data packets included therein. When the protocol data unit set has been transmitted and the count value of the packet loss counter corresponding to the protocol data unit set has not reached the packet loss threshold, the protocol data unit set is not discarded.
  • discarding the protocol data unit set or the data packets included therein may refer to discarding the data packets in the protocol data unit set that are not discarded.
  • the above-mentioned discarding of the data packets that are not discarded in the protocol data unit set may include two types: (1) refers to the client (such as the protocol layer of the client) discarding the data packets in the protocol data unit set that have been received; (2) the client (such as the protocol layer of the client) discards the data packets in the protocol data unit set that have not been received, that is, once it is determined that the protocol data unit set needs to be discarded, then when the data packets after the protocol data unit set are received, they can be directly discarded.
  • the UE when the count value of the packet loss counter reaches the packet loss threshold, the UE can release the count value in the packet loss counter, or clear the count value in the packet loss counter.
  • the UE can also release the count value in the packet loss counter, or clear the count value in the packet loss counter.
  • the packet loss counter will not count the data packets that are discarded after successful transmission.
  • Method 1 based on whether the last data packet in the protocol data unit set has been received or transmitted to the next layer, if so, determining that the transmission is complete; Method 2, based on the received data packet belonging to the protocol data unit set, determining whether the last data packet in the protocol data unit set has been received and all data packets in the protocol data unit set have been transmitted, where all data packets include data packets that have been successfully transmitted and actively discarded after receiving a feedback message from a network device, and data packets that have been discarded according to a discard timer, or all data packets include data packets that have been successfully transmitted and actively discarded after receiving a feedback message from a network device, and data packets that have been transmitted to the next layer.
  • the packet loss counter is configured in confirmation mode.
  • the confirmation mode includes receiving an indication message (or status report) fed back by the receiving end after transmitting the data packet, and the indication message indicates whether the data packet is successfully transmitted or needs to be retransmitted.
  • the confirmation mode includes an AM mode or a HARQ transmission mode or an SN status report, which is not limited in this application.
  • the discarding process corresponding to the above judgment method 1 is further introduced with examples.
  • the PDCP entity of the UE after the PDCP entity of the UE receives the PDCP SDU, it can determine that the PDU set to which the PDCP SDU belongs is PDU set 1 according to the PDU set sequence number (assuming it is 1) corresponding to the PDCP SDU, and can determine that the PDCP SDU is the first data packet of PDU set 1 according to the PDU SN (assuming it is 1) corresponding to the PDCP SDU. Afterwards, the UE starts the discard timer corresponding to the PDCP SDU.
  • the PDCP entity of the subsequent UE will continue to receive other PDCP SDUs of the PDU set 1, and the PDCP entity will start the corresponding discard timer (discard timer) for each PDCP SDU.
  • the discard timer here can be set for the UE to receive the status report fed back by the network device for the data packet, or it can be set for the time when the UE discards the data packet it caches.
  • the network device when the network device receives the data packet (that is, the data packet is successfully transmitted to the network device), the network device will feedback the status report (or feedback message) corresponding to the data packet to the UE, informing the UE that the data packet has been successfully transmitted; after the UE obtains the information, it will discard the cached data packet. If the UE discards the corresponding data packet when the discard timer (discard timer) times out, it means that the data packet has not been successfully transmitted.
  • the PDCP SDU if the PDCP receives a status report corresponding to the PDCP SDU and indicates that the PDCP SDU is successfully transmitted, the PDCP SDU is discarded; in this case, the packet loss occurs after the data packet is successfully transmitted, and thus the packet loss will not be counted by the packet loss counter. In other words, the counter in the embodiment of the present application will count the packet loss in the case of unsuccessful transmission.
  • the PDCP SDU is discarded. It can be explained that when the discard timer times out, the PDCP entity does not receive a status report fed back by the network device for the PDCP SDU, then the PDCP entity can determine that the PDCP SDU is discarded in the case of unsuccessful transmission. Based on this, if the PDCP SDU is discarded because its corresponding discard timer times out, in another case, if the protocol introduces other packet discarding methods and the method does not include discarding due to successful transmission of the packet, then the method generates a discarded packet, and the packet loss counter counts, and the count value increases by 1.
  • the discarding process may include: 1) discarding the data packet of the PDU set 1 that has been received and not discarded; 2) for the subsequently received data packet, judging whether it belongs to the data packet of the PDU set 1, if it belongs to the data packet of the PDU set 1, then discarding the data packet.
  • the UE can release or clear the packet loss counter.
  • the method for discarding data packets when packet loss occurs during the transmission of a protocol data unit set, whether it is necessary to transmit the remaining data packets or protocol data unit sets is calculated based on information on the number of lost packets, time information on the arrival of data packets, and dependencies between protocol data unit sets. If there is no need to continue transmitting, the protocol data unit set or data packet is discarded. This method can avoid the transmission of invalid data packets or protocol data unit sets, thereby saving air interface resources.
  • FIG. 5 is a schematic flow chart of another method for discarding data packets provided in an embodiment of the present application.
  • the method for determining whether a packet is lost in the process may correspond to the above-mentioned determination method 2, that is, determining whether to discard the protocol data unit set or the data packets included therein according to the packet loss ratio of the protocol data unit set.
  • the process may include the following steps:
  • S501 The network device sends a packet loss ratio threshold to the UE.
  • the network device sending the packet loss ratio threshold to the UE can also be understood as the network device configuring the packet loss ratio threshold to the UE.
  • the packet loss ratio threshold is used to indicate the maximum ratio of data packets that can be discarded in the protocol data unit set.
  • the maximum ratio of data packets that can be discarded in the protocol data unit set mentioned here means that when the ratio of the number of discarded data packets in the protocol data unit set to the total number of data packets in the protocol data unit set is less than the packet loss ratio threshold, it may not affect the network device application layer to obtain the information unit carried by the protocol data unit set. For example, the number of discarded data packets is small, and the network device can calculate the content carried by the discarded data packets based on the content of the data packets that have not been discarded, thereby obtaining the complete information unit.
  • the network device may not be able to obtain the complete information unit based on the payload carried by the remaining data packets.
  • the embodiment of Figure 5 of the present application shows the process of configuring the packet loss ratio threshold by the network device, but in actual applications, the packet loss ratio threshold can also be configured by the higher layer of the UE (such as the application layer or the transport layer), or it can also be configured by the core network, and the embodiment of the present application does not limit this.
  • the configuration granularity of the packet loss ratio threshold is to configure each data radio bearer (DRB) separately, that is, the configuration granularity is per DRB, that is, the DRB configuration includes the packet loss ratio threshold, and different DRBs may correspond to different packet loss ratio thresholds; or, the configuration granularity of the packet loss ratio threshold is to configure each protocol layer entity, that is, the protocol layer entity configuration includes the packet loss ratio threshold, and different types of protocol layer entities (such as SDAP, PDCP, RLC, etc.) may correspond to different packet loss ratio thresholds; or, the configuration granularity of the packet loss ratio threshold is to configure each protocol data unit set separately, that is, the configuration granularity is per protocol data unit set, that is, the protocol data unit set configuration includes the packet loss ratio threshold, and different protocol data unit sets may correspond to different packet loss ratio thresholds; or, the configuration granularity of the packet loss ratio threshold is to configure each type of protocol data unit set separately, that is, the protocol data unit set type configuration includes the packet
  • the type of the protocol data unit set mentioned above may be the importance level of the data unit set, the priority of the protocol data unit set, the sequence number of the protocol data unit set, etc. This embodiment of the present application does not limit this.
  • the network device can configure the packet loss threshold through RRC signaling, MAC CE, and DCI.
  • the packet loss ratio threshold configured by the network device may be included in the data radio bearer (DRB) or protocol layer entity configuration.
  • DRB data radio bearer
  • S502 Obtain a packet loss ratio corresponding to a protocol data unit set, and when the packet loss ratio of the protocol data unit set reaches or exceeds a packet loss ratio threshold, discard the protocol data unit set or data packets included therein.
  • the UE may determine a packet loss ratio threshold corresponding to the current protocol data unit set according to a packet loss threshold sent by a network device.
  • the UE may determine the number of packet losses of the current protocol data unit set according to the count value in the packet loss counter, and determine the packet loss ratio according to the ratio of the number of packet losses to the total number of data packets in the protocol data unit set. When the packet loss ratio reaches or exceeds the packet loss ratio threshold, the protocol data unit set or the data packets included therein are discarded.
  • the process may include: the UE may maintain a packet loss counter for the current protocol data unit set. When the UE determines that the protocol data unit set discards a data packet, the count value of the packet loss counter is increased by 1, and the packet loss ratio of the protocol data unit set is obtained; as the number of packet losses increases, the packet loss ratio also increases.
  • the UE may discard the data packets in the protocol data unit set that have not been discarded.
  • the protocol data unit set has been transmitted and the packet loss ratio corresponding to the protocol data unit set has not reached the packet loss ratio threshold, the protocol data unit set will not be discarded.
  • the data packets that are not discarded in the protocol data unit set that can be discarded by the UE mentioned above may include: (1) data packets in the protocol data unit set that have been received by the protocol layer; (2) data packets in the protocol data unit set that have not been received by the protocol layer, that is, once it is determined that the protocol data unit set needs to be discarded, the protocol layer can directly discard the data packets after receiving the protocol data unit set.
  • the UE may release the count value in the packet loss counter, or clear the count value in the packet loss counter.
  • the UE may also release the count value in the packet loss counter, or clear the count value in the packet loss counter.
  • the packet loss counter will not count the data packets that are discarded after successful transmission.
  • Method 1 based on whether the last data packet in the protocol data unit set has been received or transmitted to the next layer, if so, determining that the transmission is complete; Method 2, based on the received data packet belonging to the protocol data unit set, determining whether the last data packet in the protocol data unit set has been received and all data packets in the protocol data unit set have been transmitted, where all data packets include data packets that have been successfully transmitted and actively abandoned after receiving feedback from the network device, and data packets that have been discarded according to the discard timer, or all data packets include data packets that have been successfully transmitted and actively discarded after the protocol layer receives feedback from the network device, and data packets that have been transmitted to the next layer.
  • the discarding process corresponding to the above judgment method 2 is further introduced with examples.
  • the UE's PDCP entity can determine that the PDU set to which the PDCP SDU belongs is PDU set 1 according to the PDU set sequence number (assuming it is 1) corresponding to the PDCP SDU, and can determine that the PDCP SDU is the first data packet of PDU set 1 according to the PDU SN (assuming it is 1) corresponding to the PDCP SDU. Afterwards, the UE starts the discard timer corresponding to the PDCP SDU and maintains the packet loss counter for the PDU set 1. Subsequently, the UE's PDCP entity will continue to receive other PDCP SDUs of the PDU set 1, and the PDCP entity will start the corresponding discard timer for each PDCP SDU.
  • the discard timer here can be used to time the UE to receive the status report of the data packet feedback from the network device, or can be used to time the time for the UE to discard the cached data packet.
  • the network device When the network device receives the data packet (that is, the data packet is successfully transmitted to the network device), the network device will feedback the status report (or feedback message) corresponding to the data packet to the UE, informing the UE that the data packet has been successfully transmitted; after the UE obtains the information, it will discard the cached data packet. If the UE discards the corresponding data packet when the discard timer times out, it means that the data packet has not been successfully transmitted.
  • the PDCP SDU if the PDCP receives a status report corresponding to the PDCP SDU and indicates that the PDCP SDU is successfully transmitted, the PDCP SDU is discarded; in this case, the packet loss occurs after the data packet is successfully transmitted, and thus the packet loss will not be counted by the packet loss counter. In other words, the counter in the embodiment of the present application will count the packet loss in the case of unsuccessful transmission.
  • the PDCP SDU is discarded. It can be explained that when the discard timer times out, the PDCP does not receive a status report fed back by the network device for the PDCP SDU, then the PDCP entity can determine that the PDCP SDU is discarded in the case of unsuccessful transmission. Based on this, if the PDCP SDU is discarded because its corresponding discard timer times out, in another case, if the protocol introduces other data packet discarding methods and the method does not include discarding due to successful data packet transmission, then the method generates a discarded data packet, and the packet loss counter counts, and the count value increases by 1.
  • the discarding process may include: 1) discarding the data packets of the PDU set 1 that have been received and not yet discarded; 2) for the subsequently received data packets, judging whether they belong to the data packets of the PDU set 1, and if they belong to the data packets of the PDU set 1, discarding the data packets.
  • the UE may release or clear the packet loss counter.
  • the UE may first determine whether at least one data packet of the protocol data unit set has been successfully received. Only after determining that one or more data packets in the protocol data unit set have been successfully received by the UE, will the UE configure the packet loss counter. Alternatively, before configuring the packet loss counter, the UE may first determine whether at least one data packet of the protocol data unit set has been successfully transmitted to the network device (such as determining whether a feedback message of successful data packet transmission sent by the network device has been received). Only after determining that one or more data packets in the protocol data unit set have been successfully transmitted to the network device, will the UE configure the packet loss counter.
  • the method for discarding data packets when packet loss occurs during the transmission of a protocol data unit set, whether it is necessary to transmit the remaining data packets or protocol data unit sets is calculated based on information on the number of lost packets, time information on the arrival of data packets, and dependencies between protocol data unit sets. If there is no need to continue transmitting, the protocol data unit set or data packet is discarded. This method can avoid the transmission of invalid data packets or protocol data unit sets, thereby saving air interface resources.
  • FIG. 6 is a schematic flow chart of another method for discarding data packets provided in an embodiment of the present application.
  • the method for determining whether a packet is lost in the process may correspond to the above-mentioned determination method 3, that is, determining whether to discard the protocol data unit set or the data packets included therein according to whether the packet loss timer set for the protocol data unit set has timed out.
  • the process may include the following steps:
  • the network device sends a packet loss timer to the UE.
  • the network device sending the packet loss timer to the UE can also be understood as the network device configuring the packet loss timer to the UE.
  • the packet loss timer is used to indicate the packet loss time of the protocol data unit set.
  • the packet loss time can be understood as the allowable transmission time of the protocol data unit set.
  • the embodiment of Figure 6 of the present application shows the process of configuring the packet loss timer by the network device, but in actual applications, the packet loss timer can also be configured by the higher layer of the UE (such as the application layer or the transport layer), or it can also be configured by the core network. The embodiment of the present application does not limit this.
  • the configuration granularity of the packet loss timer is configured for each data radio bearer (DRB), that is, the configuration granularity is per DRB, that is, the DRB configuration includes a packet loss timer, and different DRBs may correspond to different packet loss timers; or, the configuration granularity of the packet loss timer is configured for each protocol layer entity, that is, the protocol layer entity configuration includes a packet loss timer, and different types of protocol layer entities (such as SDAP, PDCP, RLC, etc.) may correspond to different packet loss timers; or, the configuration granularity of the packet loss timer is configured for each protocol data unit set, that is, the configuration granularity is per protocol data unit set, that is, the protocol data unit set configuration includes a packet loss timer, and different protocol data unit sets may correspond to different packet loss timers; or, the configuration granularity of the packet loss timer is configured for each type of protocol data unit set, that is, the protocol data unit set type configuration includes a packet
  • the network device can configure the packet loss timer through RRC signaling, MAC CE, and DCI.
  • a packet loss timer configured by a network device may be included in a data radio bearer (DRB) or a protocol layer entity configuration.
  • DRB data radio bearer
  • the method of determining that the received data packet is the first data packet in the protocol data unit set may include: after receiving the data packet, judging whether the data packet is the starting data packet of the protocol data unit set, and if so, indicating that the data packet is the first data packet in the protocol data unit set. Alternatively, after receiving the data packet, judging whether the data packet sequence number corresponding to the data packet is the first data packet in the protocol data unit set. Alternatively, after the protocol layer entity receives the data packet, it judges that it has not received a data packet of the protocol data unit set before, then the data packet is the first data packet in the protocol data unit set. This application is not limited.
  • the manner of determining that the data packet of the protocol data unit set has not been completely transmitted may include the following:
  • Method 1 based on whether the last data packet in the protocol data unit set has been received or transmitted to the next layer, if so, determining that the transmission is complete; Method 2, based on the received data packet belonging to the protocol data unit set, determining whether the last data packet in the protocol data unit set has been received and all data packets in the protocol data unit set have been completely transmitted, all of which include data packets that have been actively discarded after receiving a feedback message from a network device and data packets that have been discarded according to a discard timer, or all of which include data packets that have been successfully transmitted and actively discarded after the protocol layer receives a feedback message from a network device, and data packets that have been transmitted to the next layer.
  • packet loss timer and discard timer in the embodiments of the present application are two different concepts and need to be distinguished and understood.
  • the packet loss timer may be stopped, or the packet loss timer may be released, or the packet loss timer may be cleared.
  • the protocol data unit set may be discarded.
  • discarding a protocol data unit set may specifically refer to discarding the data packets in the protocol data unit set that have not been discarded.
  • the data packets in the protocol data unit set that have not been discarded may include: (1) data packets in the protocol data unit set that have been received by the client (such as the client's protocol layer); (2) data packets in the protocol data unit set that have not been received by the client, that is, once it is determined that the protocol data unit set needs to be discarded, the client (such as the client's protocol layer) may directly discard the data packets after receiving the protocol data unit set.
  • the discard processing process corresponding to the above-mentioned method 3 for determining whether a packet is lost is further introduced by way of example.
  • the PDCP entity of the UE can determine that the protocol data unit set to which the PDCP SDU belongs is protocol data unit set 1 according to the protocol data unit set sequence number (assuming it is 1) corresponding to the PDCP SDU, and can determine that the protocol data unit set to which the PDCP SDU belongs is protocol data unit set 1 according to the PDU SN (assuming it is 1) corresponding to the PDCP SDU.
  • the PDCP SDU is determined to be the first data packet of protocol data unit set 1. After that, the UE starts the discard timer corresponding to the PDCP SDU, and at the same time starts the corresponding packet loss timer for the protocol data unit set 1. The PDCP entity of the UE will continue to receive other PDCP SDUs of the protocol data unit set 1, and the PDCP entity will also start the corresponding discard timer for each PDCP SDU.
  • the protocol data unit set 1 if the packet loss timer times out and there are data packets of the protocol data unit set 1 that have not been discarded at the PDCP layer, the protocol data unit set 1 is discarded and the data packets in the protocol data unit set 1 that have not been discarded are directly discarded.
  • the packet loss timer is stopped. In the mode of data packet non-confirmation, if all data packets of the protocol data unit set 1 have been transmitted (transmitted to the next layer or discarded), the packet loss timer is stopped.
  • the method for discarding data packets when packet loss occurs during the transmission of a protocol data unit set, whether it is necessary to transmit the remaining data packets or protocol data unit sets is calculated based on information on the number of lost packets, time information on the arrival of data packets, and dependencies between protocol data unit sets. If there is no need to continue transmitting, the protocol data unit set is discarded. This method can avoid the transmission of invalid data packets or protocol data unit sets, thereby saving air interface resources.
  • FIG. 7 is a schematic flow chart of another method for discarding data packets provided in an embodiment of the present application.
  • the method for determining whether a packet is lost in the process may correspond to the above-mentioned determination method 4, that is, whether to discard the protocol data unit set or the data packets included therein is determined comprehensively based on the number of packet losses for the protocol data unit set and the corresponding packet loss timer of the protocol data unit set.
  • the process may include the following steps:
  • the network device sends a packet loss threshold and a packet loss timer to a UE.
  • the network device sending the packet loss threshold and packet loss timer to the UE can also be understood as the network device configuring the packet loss threshold and packet loss timer to the UE.
  • the meanings of the packet loss threshold and the packet loss timer can be referred to the introduction in the embodiment of FIG. 4 and the embodiment of FIG. 6 above, and will not be repeated here.
  • the embodiment of Figure 7 of the present application shows the process of configuring the packet loss threshold by the network device, but in actual applications, the packet loss threshold can also be configured by the higher layer of the UE (such as the application layer or the transport layer), or it can also be configured by the core network device, and the embodiment of the present application does not limit this.
  • the configuration granularity of the packet loss threshold and the packet loss timer can be found in the description of the embodiments of FIG. 4 and FIG. 6 above, and will not be described in detail here.
  • the way in which the network device sends the packet loss threshold and the packet loss timer to the UE can be respectively referred to the introduction in the above-mentioned embodiments of Figure 4 and Figure 6, and will not be repeated here.
  • the UE will simultaneously use a packet loss counter to count whether the number of packet losses in the protocol data unit set reaches the packet loss threshold, and use a packet loss timer to count whether the data packet of the protocol data unit set is transmitted within the timing time. These two methods are used to comprehensively determine whether to discard the protocol data unit set.
  • the protocol data unit set or the data packets included therein may be discarded.
  • the protocol data unit set or the data packets included therein may be discarded. That is, only at least one of the two discard conditions needs to be met to discard the protocol data unit set.
  • the protocol data unit set or the data packets included therein are discarded. If the count value counted by the packet loss counter reaches or exceeds the packet loss threshold, but the packet loss timer does not time out, the protocol data unit set or the data packets included therein are also discarded. If the count value counted by the packet loss counter reaches the packet loss threshold and the packet loss timer times out, the protocol data unit set or the data packets included therein are also discarded. It should be understood that the discard processing in the embodiments of the present application may refer to discarding the protocol data unit set or the data packets included therein.
  • an exemplary process may include the following: (1) determining the packet loss threshold and packet loss timer of the PDU set.
  • the data packets of the PDU set may be directly discarded; or when the packet loss timer times out, the data packets of the PDU set that have not been discarded are discarded; (2) after receiving the first data packet of the PDU set, starting the packet loss timer; the method for determining the first data packet includes receiving the first data packet in the PDU set. art PDU (data packet that identifies the start), or the first data packet belonging to the PDU set is received; (3) During the time when the packet loss timer is turned on, a packet loss counter is maintained for the PDU set.
  • the packet loss counter is increased by 1.
  • the packet loss threshold the timer has not expired
  • the data packets of the PDU set that have not been discarded can be directly discarded
  • the packet loss timer expires, but the packet loss counter has not exceeded the packet loss threshold
  • the data packets of the PDU set that have not been discarded are discarded; (5)
  • the PDU set is discarded; or both conditions must be met at the same time, the PDU set is discarded.
  • the embodiment of Figure 7 only takes the example of determining whether to discard the protocol data unit set or the data packets included therein based on the packet loss timer and the packet loss threshold. In other embodiments, it can also be determined whether to discard the protocol data unit set or the data packets included therein based on the packet loss timer and the packet loss ratio threshold, or it can be determined whether to discard the protocol data unit set or the data packets included therein by a combination of the other two judgment bases.
  • the embodiments of the present application are not limited to this.
  • the method for discarding data packets when packet loss occurs during the transmission of a protocol data unit set, whether it is necessary to transmit the remaining data packets or protocol data unit sets is calculated based on information on the number of lost packets, time information on the arrival of data packets, and dependencies between protocol data unit sets. If there is no need to continue transmitting, the protocol data unit set is discarded. This method can avoid the transmission of invalid data packets or protocol data unit sets, thereby saving air interface resources.
  • FIG. 8 is a schematic flow chart of another method for discarding data packets provided in an embodiment of the present application.
  • the method for determining whether a packet is lost in the process may correspond to the above-mentioned determination method 5, that is, whether to discard the protocol data unit set or the data packets included therein according to whether a data packet with specific attribute information in the protocol data unit set is discarded, and the specific attribute is associated with not allowing discarding.
  • the process may include the following steps:
  • the network device sends first attribute information of a protocol data unit set and/or second attribute information corresponding to a data packet to a UE.
  • the first attribute information is associated with allowing discarding or not allowing discarding
  • the second attribute information is associated with allowing discarding or not allowing discarding.
  • the network device sends the first attribute information of the protocol data unit set to the UE, and/or the second attribute information corresponding to the data packet, which can also be understood as the network device configuring the first attribute information of the protocol data unit set and/or the second attribute information corresponding to the data packet to the UE.
  • the network device may configure a protocol data unit set and/or a data packet with attribute information associated with allowable discard in a variety of ways, including: (1) the network device may set the protocol data unit set and/or the data packet according to the priority and importance of the protocol data unit set and/or the data packet, such as associating a higher priority or a higher importance with not allowing discard, that is, setting a data packet with a higher priority or a higher importance as a protocol data unit set and/or a data packet that is not allowed to be discarded; (2) the network device may also set the data packet according to the position of the data packet in the protocol data unit set, such as associating a strat PDU with not allowing discard, that is, setting a data packet as a strat PDU as a data packet that is not allowed to be discarded; (3) the network device may also set the protocol data unit set and/or the data packet according to the sequence number of the protocol data unit set and/or the data packet, such as associating a PDU SN of 1
  • packets in the protocol data unit set that are not configured to be discarded can be considered as packets that are not allowed to be discarded.
  • the network device configures PDUs in the protocol data unit set whose PDU SNs are a to b (a and b are both integers greater than or equal to 1, and b is greater than a) as discardable packets, then other PDUs in the protocol data unit set whose PDU SNs are not any of the sequence numbers from a to b can be considered as packets that are not allowed to be discarded.
  • the embodiment of Figure 8 of the present application shows the process of configuring the packet loss threshold by the network device, but in actual applications, the packet loss threshold can also be configured by the higher layer of the UE (such as the application layer or the transport layer), or it can also be configured by the core network, and the embodiment of the present application does not limit this.
  • the protocol data unit set can be discarded.
  • the UE can determine which non-discardable data packets are based on all PDUs included in the protocol data unit set, and then when the UE detects that one or more non-discardable data packets are discarded, the protocol data unit set can be discarded.
  • the EU obtains non-discardable data packets sent by a network device, when the UE detects that one or more non-discardable data packets are discarded, the protocol data unit set can be directly discarded.
  • the manner in which the UE discards the protocol data unit set can refer to the relevant introduction in the embodiments of Figures 4 to 6 above, and will not be repeated here.
  • the method for discarding data packets when packet loss occurs during the transmission of a protocol data unit set, whether it is necessary to transmit the remaining data packets or protocol data unit sets is calculated based on information on the number of lost packets, time information on the arrival of data packets, and dependencies between protocol data unit sets. If there is no need to continue transmitting, the protocol data unit set is discarded. This method can avoid the transmission of invalid data packets or protocol data unit sets, thereby saving air interface resources.
  • FIG. 9 is a schematic flow chart of another method for discarding data packets provided in an embodiment of the present application.
  • the method for determining whether a packet is lost in the process may correspond to the above-mentioned determination method 6, that is, for a set of dependent protocol data units, whether to discard the set of protocol data units or the data packets included therein is determined based on whether the associated set of protocol data units is lost or the number of lost packets.
  • the process may include the following steps:
  • a network device sends a dependency identifier of a first protocol data unit set to a UE.
  • the protocol data unit set that the first protocol data unit set depends on is recorded as the second protocol data unit set.
  • the network device sending the dependency identifier of the first protocol data unit set to the UE can also be understood as the network device configuring the dependency identifier of the first protocol data unit set to the UE.
  • the dependency relationship here can also be described as dependency, and two or more protocol data unit sets with a dependency relationship can have the same dependency identifier, and the dependency identifier is used to indicate other protocol data unit sets that are mutually dependent on the protocol data unit set.
  • the first protocol data unit set and the second protocol data unit set here are only distinguished from each other, and the first and second do not represent the order or quantity of the protocol data unit sets.
  • the dependency between the first protocol data unit set and the second protocol data unit set can be understood as: the application or role of the first protocol data unit set depends on the successful transmission of the second protocol data unit set.
  • the first protocol data unit set When the second protocol data unit set is successfully transmitted, the first protocol data unit set is necessary to be transmitted; and if the second protocol data unit set is not successfully transmitted, the first protocol data unit set is no longer valuable to be used even if it is successfully transmitted.
  • the application of P frames needs to be implemented on the basis of I frame data, that is, only when I frames are successfully transmitted, P frames are necessary to be transmitted. If I frames are not successfully transmitted, there is no need for P frames to continue to be transmitted.
  • the first protocol data unit set may depend on one or more second protocol data unit sets.
  • the first protocol data unit set depends on more than one second protocol data unit set, if any second protocol data unit set is discarded, there is no need to continue transmitting the first protocol data unit set, and the first protocol data unit set may be discarded.
  • a network device may configure dependencies between protocol data unit sets, such as: (1) configuring dependency identification (ID) for dependent protocol data unit sets, and configuring protocol data unit sets with the same dependency ID to be mutually dependent; (2) configuring an identification of a protocol data unit set (such as a first protocol data unit set) on which it depends (such as a second protocol data unit set), such as carrying the ID of the second protocol data unit set in the first protocol data unit set; (3) configuring the number of protocol data unit sets with dependencies that are allowed to be discarded.
  • ID dependency identification
  • a protocol data unit set such as a first protocol data unit set
  • second protocol data unit set such as carrying the ID of the second protocol data unit set in the first protocol data unit set
  • configuring the number of protocol data unit sets with dependencies that are allowed to be discarded can be configured in the protocol data unit set at the same time, or can be configured in the protocol data unit set partially. The embodiments of the present application do not limit this.
  • the UE may determine that the first protocol data unit set has a dependency relationship with the second protocol data unit set based on the dependency relationship (such as a dependency identifier) of the received first protocol data unit set, and then determine whether to discard the first protocol data unit set based on the dependency relationship.
  • the dependency relationship such as a dependency identifier
  • the UE may determine whether to discard the first protocol data unit set based on the dependency relationship in a variety of ways, such as: (1) When the UE determines that the second protocol data unit set has been discarded (the determination method can be referred to the above related embodiments), based on the dependency identifier of the second protocol data unit set, the subsequent first protocol data unit set with the corresponding dependency identifier is discarded. (2) When the UE receives the first protocol data unit set, it determines that the first protocol data unit set depends on the second protocol data unit set based on its corresponding dependency identifier. If it is determined that the second protocol data unit set has been discarded, the first protocol data unit set is discarded. (3) Based on the dependency identifier of the first protocol data unit set, it is determined whether the number of packet loss of the protocol data unit set with the same dependency identifier has exceeded a preset threshold. If exceeded, the first protocol data unit set is discarded.
  • the manner in which the UE discards the protocol data unit set can refer to the relevant introduction in the embodiments of Figures 4 to 6 above, and will not be repeated here.
  • the method for discarding data packets when packet loss occurs during the transmission of a protocol data unit set, whether it is necessary to transmit the remaining data packets or protocol data unit sets is calculated based on information on the number of lost packets, time information on the arrival of data packets, and dependencies between protocol data unit sets. If there is no need to continue transmitting, the protocol data unit set is discarded. This method can avoid the transmission of invalid data packets or protocol data unit sets, thereby saving air interface resources.
  • the protocol layer (such as the PDCP layer) discards a certain protocol data unit set
  • the protocol layer needs to notify the lower layer to also discard the data packets of the protocol data unit set. For example, after the PDCP layer discards the protocol data unit set, it notifies the RLC layer to discard the data packets related to the protocol data unit set cached by the RLC layer.
  • RLC can notify the MAC layer of the attribute information of the protocol data unit set (such as the sequence number of the protocol data unit set, the sequence number of the PDU in the protocol data unit set, the start PDU/end PDU in the protocol data unit set, etc.), and can notify the MAC layer that if the data packets related to the protocol data unit set have not been transmitted on the air interface, then there is no need to schedule the protocol data unit set, or there is no need to wait for the scheduling resources corresponding to the protocol data unit set.
  • the MAC can determine whether the protocol data unit set has been transmitted on the air interface. If the protocol data unit set has not been transmitted on the air interface, the MAC will no longer wait for the scheduling resources corresponding to the protocol data unit set, or will no longer schedule the protocol data unit set.
  • the MAC layer may not discard the relevant data packets. For example, when the protocol data unit set in the MAC layer has been transmitted over the air interface, the protocol data unit set is no longer discarded.
  • the discard processing flow shown in the embodiments of Figures 4 to 9 above is only a schematic example. In actual application, the discard processing flow may also include more or fewer steps, and the embodiments of the present application are not limited to this.
  • FIG10 a schematic diagram of the triggering process of discarding processing in a method for discarding a data packet provided in an embodiment of the present application is provided.
  • the process may include the following steps:
  • a network device sends discard indication information of a protocol data unit set to a sending end device.
  • the network device here sends the discard indication information of the protocol data unit set to the UE can also be understood as the network device configures the discard indication information of the protocol data unit set to the UE.
  • the discard indication information of the protocol data unit set configured by the network device its corresponding data structure can be an enumeration type or a Boolean type.
  • the enumeration content can be true, for example, it can be expressed as: PDUsetDiscard ENUMERATED ⁇ true ⁇ .
  • the embodiment of the present application does not limit the specific data structure of the discard indication information.
  • the discard indication information may be carried in a variety of messages sent by the network device to the sending end device, or may be sent to the sending end device as a separate message. This embodiment of the present application does not limit this.
  • the sending end device receives discard indication information of a protocol data unit set or a data packet, triggering discard of the protocol data unit set or the data packet.
  • the transmitting end device when it receives the discard indication information, it can start the service of discarding the protocol data unit set in response to the discard indication information.
  • the protocol layer can be triggered to discard the protocol data unit set.
  • the method of determining whether the protocol data unit set meets the discard processing conditions and the process of discarding the protocol data unit set can refer to the relevant introduction above, which will not be repeated here.
  • the method for discarding data packets when packet loss occurs during the transmission of a protocol data unit set, whether it is necessary to transmit the remaining data packets or protocol data unit sets is calculated based on information on the number of lost packets, time information on the arrival of data packets, and dependencies between protocol data unit sets. If there is no need to continue transmitting, the protocol data unit set is discarded. This method can avoid the transmission of invalid data packets or protocol data unit sets, thereby saving air interface resources.
  • discard processing flow shown in the embodiment of Figure 10 above is only an illustrative example. In actual application, the discard processing flow may also include other more or fewer steps, and the embodiment of the present application is not limited to this.
  • FIG11 a schematic flow chart of a method for discarding a data packet provided in an embodiment of the present application is provided.
  • the execution subject of the process may be a sending end device, and specifically may include the following steps:
  • the judgment basis adopted by the preset judgment method includes the number of packet losses corresponding to the protocol data unit set, the packet loss timer of the protocol data unit set, the first attribute information corresponding to the protocol data unit set, the second attribute information corresponding to the data packet, and at least one of the dependencies between the protocol data unit set and other protocol data unit sets; the attribute information is associated with whether to allow discarding or not, and the protocol data unit set includes one or more of the data packets.
  • the data packet may include a PDU data packet or an SDU data packet, but this application is not limited to this.
  • discarding the protocol data unit set or the data included in the protocol data unit set may include: discarding the data packets in the protocol data unit set that have not been discarded.
  • the data packets that have not been discarded may refer to data packets that have been received but not discarded by the sender; or, may refer to data packets in the protocol data unit set that have not been received, that is, if it is determined that the data packets in the protocol data unit set need to be discarded, the data packets in the protocol data unit set may be directly discarded after being received.
  • the protocol data unit set may correspond to a PDU set, but is not limited to this.
  • allowing to discard means that a set of protocol data units or data packets can be discarded, which will not cause the set of protocol data units or data packets in the set of protocol data units to be discarded.
  • Not allowing to discard means that a set of protocol data units or data packets are not allowed to be discarded, and if discarded, it will cause the set of protocol data units or data packets in the set of protocol data units to be discarded.
  • the association of attribute information with allowing discarding or not allowing discarding means that the data packet or protocol data unit set with the attribute information belongs to the type of data packet or protocol data unit set that is allowed to be discarded; or the data packet or protocol data unit set with the attribute information belongs to the type of data packet or protocol data unit set that is not allowed to be discarded. For example, if the high priority attribute is associated with not allowing discarding, then the high priority data packet protocol data unit set belongs to the data packet or protocol data unit set that is not allowed to be discarded. If discarding occurs, it needs to be discarded, and the corresponding protocol data unit set or other data packets in the protocol data unit set will be discarded.
  • the transmitting end may be a user equipment, but is not limited thereto.
  • determining whether to discard a protocol data unit set or a data packet included in the protocol data unit set according to a preset judgment method may also mean determining whether a protocol data unit set or a data packet included in the protocol data unit set meets a discarding condition according to a preset judgment method, and discarding the protocol data unit set or the data packet included in the protocol data unit set when the discarding condition is met.
  • the first attribute information includes at least one of the sequence number corresponding to the protocol data unit set, the total number of the data packets included in the protocol data unit set, the importance level of the protocol data unit set, the priority of the protocol data unit set, and the dependency relationship of the protocol data unit set;
  • the second attribute information includes at least one of the data packet sequence number corresponding to the data packet, the position of the data packet in the protocol data unit set, the importance level of the data packet, and the priority of the data packet.
  • the method specifically includes: obtaining the packet loss threshold corresponding to the protocol data unit set; obtaining the number of packet losses corresponding to the protocol data unit set; if the number of packet losses reaches or exceeds the packet loss threshold, discarding the protocol data unit set or the data packet.
  • obtaining the packet loss threshold corresponding to the protocol data unit set specifically includes: receiving first configuration information sent by a receiving end, the first configuration information is used to indicate the packet loss threshold, and the receiving end is used to receive the data packet; or, obtaining the packet loss threshold pre-configured by the sending end itself; or, receiving the packet loss threshold sent by the high layer of the sending end through the protocol layer of the sending end itself; or, receiving second configuration information sent by a core network, the second configuration information is used to indicate the packet loss threshold.
  • the packet loss ratio threshold pre-configured by the transmitting end itself may be a statically configured packet loss ratio threshold; the packet loss threshold sent by the transmitting end high layer may be a dynamically configured packet loss ratio threshold.
  • the method further includes: configuring the packet loss threshold with a protocol layer entity as the granularity; or, configuring the packet loss threshold with a data radio bearer DRB as the granularity; or, configuring the packet loss threshold with a protocol data unit set as the granularity; or, configuring the packet loss threshold with a type of the protocol data unit set as the granularity, wherein the type of the protocol data unit set is at least one of the priority of the protocol data unit set, the importance level of the protocol data unit set, and the sequence number of the protocol data unit set.
  • the method specifically includes: obtaining a packet loss ratio threshold corresponding to the protocol data unit set; obtaining the number of packet losses corresponding to the protocol data unit set; obtaining the packet loss ratio corresponding to the protocol data unit set based on the ratio of the number of packet losses to the total number of the data packets included in the protocol data unit set; if the packet loss ratio reaches or exceeds the packet loss ratio threshold, discarding the protocol data unit set or the data packet.
  • the obtaining of the packet loss ratio threshold corresponding to the protocol data unit set specifically includes: receiving third configuration information sent by a receiving end, the third configuration information being used to indicate the packet loss ratio threshold, and the receiving end being used to receive the data packet; or, obtaining the packet loss ratio threshold pre-configured by the sending end itself; or, receiving the packet loss ratio threshold sent by the high layer of the sending end through the protocol layer of the sending end itself; or, receiving fourth configuration information sent by a core network, the fourth configuration information being used to indicate the packet loss ratio threshold.
  • the method when the packet loss ratio threshold is configured by the sending end itself, the method also includes: configuring the packet loss ratio threshold with the protocol layer entity as the granularity; or, configuring the packet loss ratio threshold with the DRB as the granularity; or, configuring the packet loss ratio threshold with the protocol data unit set as the granularity; or, configuring the packet loss ratio threshold with the type of the protocol data unit set as the granularity, wherein the type of the protocol data unit set is at least one of the priority of the protocol data unit set, the importance level of the protocol data unit set, and the sequence number of the protocol data unit set.
  • the obtaining of the number of packet losses corresponding to the protocol data unit set specifically includes: setting a packet loss counter, the packet loss counter being used to count the number of the data packets discarded in the protocol data unit set; adding 1 to the count value of the packet loss counter each time a data packet in the protocol data unit set is discarded; and obtaining the number of packet losses corresponding to the protocol data unit set according to the count value of the packet loss counter.
  • the method further includes: the packet loss counter does not count the data packets that are successfully transmitted and discarded.
  • the method further includes: when the protocol data unit set or the data packet is discarded, releasing or clearing the packet loss counter; or, when the number of packet losses corresponding to the protocol data unit set does not reach or exceed the packet loss threshold, and the transmission of the protocol data unit set and/or the data packet is completed, releasing or clearing the packet loss counter; or, when the ratio of the number of packet losses corresponding to the protocol data unit set to the total number of data packets included in the protocol data unit set does not reach or exceed the packet loss ratio threshold, and the transmission of the protocol data unit set and/or the data packet is completed, releasing or clearing the packet loss counter; or, when the ratio of the count value of the counter to the total number of data packets included in the protocol data unit set reaches or exceeds the corresponding packet loss ratio threshold, releasing or clearing the packet loss counter; or, when the count value of the counter reaches or exceeds the packet loss threshold, releasing or clearing the packet loss counter.
  • the method further includes: when the data packet is successfully transmitted, setting the packet loss counter.
  • the method specifically includes: obtaining the packet loss timer corresponding to the protocol data unit set; when the packet loss timer times out, discarding the protocol data unit set or the data packet; or, when the packet loss timer times out, if the protocol data unit set or the data packet has not been transmitted, discarding the protocol data unit set or the data packet.
  • the method further includes: when the first data packet in the protocol data unit set is received, starting the packet loss timer.
  • the method further includes: when the transmission time of the protocol data unit set exceeds the packet loss timing time of the packet loss timer, discarding the protocol data unit set or the data packet.
  • obtaining the packet loss timer corresponding to the protocol data unit set specifically includes: receiving the fifth configuration information sent by the receiving end, the fifth configuration information is used to indicate the packet loss timer, and the receiving end is used to receive the data packet; or, obtaining the packet loss timer pre-configured by the sending end itself; or, receiving the packet loss timer sent by the high layer of the sending end through the protocol layer of the sending end itself; or, receiving the sixth configuration information sent by the core network, and the sixth configuration information is used to indicate the packet loss timer.
  • the method also includes: when the protocol data unit set or the data packet is discarded, the packet loss timer is released or cleared; or, when the packet loss timer has not timed out and the transmission of the protocol data unit set and/or data packet is completed, the packet loss timer is released or cleared; or, when the packet loss timer times out, the packet loss timer is released or cleared.
  • the method specifically includes: obtaining the packet loss threshold corresponding to the protocol data unit set and the packet loss timer corresponding to the protocol data unit set; obtaining the number of packet losses corresponding to the protocol data unit set; if the number of packet losses exceeds the packet loss threshold, and/or if the packet loss timer times out, the protocol data unit set or the data packet is not transmitted, discarding the protocol data unit set or the data packet; or, if the number of packet losses exceeds the packet loss threshold, and/or if the packet loss timer times out, discarding the protocol data unit set or the data packet.
  • the protocol data unit set or the data packet is not completely transmitted, which specifically includes: the sending end has the data packet in the protocol data unit set.
  • the method specifically includes: when the first attribute information corresponding to the protocol data unit set is associated with the not allowed discard, if the protocol data unit set with the first attribute information is discarded, then the protocol data unit set or the data packet is discarded; or, when the second attribute information corresponding to the data packet is associated with the not allowed discard, if the data packet with the second attribute information is discarded, then the protocol data unit set or the data packet is discarded.
  • the method also includes: obtaining the seventh configuration information sent by the receiving end, the seventh configuration information is used to indicate the first attribute information corresponding to the protocol data unit set, and/or the second attribute information corresponding to the data packet, and the receiving end is used to receive the data packet; or, obtaining the first attribute information corresponding to the protocol data unit set pre-configured by the sending end itself, and/or the second attribute information corresponding to the data packet; or, receiving the first attribute information corresponding to the protocol data unit set sent by the high layer of the sending end through the protocol layer of the sending end itself, and/or the second attribute information corresponding to the data packet; or, receiving the eighth configuration information sent by the core network, the eighth configuration information is used to indicate the first attribute information corresponding to the protocol data unit set, and/or the second attribute information corresponding to the data packet.
  • the method specifically includes: obtaining a first protocol data unit set and having a dependency relationship with at least one second protocol data unit set; based on the dependency relationship, if the second protocol data unit set is obtained and discarded, discarding the first protocol data unit set or the data packet included in the first protocol data unit set; or, based on the dependency relationship, if the number of the second protocol data unit sets that are discarded reaches a preset threshold, discarding the first protocol data unit set or the data packet included in the first protocol data unit set.
  • the acquisition of at least one second protocol data unit set having a dependency relationship with the first protocol data unit set specifically includes: receiving ninth configuration information sent by a receiving end, the ninth configuration information being used to indicate a dependency identifier, the receiving end being used to receive the data packet transmitted by the sending end; or, acquiring a dependency identifier pre-configured by the sending end itself; or, receiving a dependency identifier sent by a high-level layer of the sending end through the protocol layer of the sending end itself; or, receiving the tenth configuration information sent by a core network, the tenth configuration information being used to indicate a dependency identifier; wherein the dependency identifier is used to indicate other protocol data unit sets that are mutually dependent on the protocol data unit set.
  • the method also includes: receiving packet loss indication information sent by the receiving end or the high layer of the sending end, the packet loss indication information is used to instruct the sending end to trigger the discarding of a set of protocol data units or the discarding of the data packet; triggering the discarding of the set of protocol data units or the discarding of the data packet at the protocol layer.
  • the protocol data unit set or the data packet included in the protocol data unit set is discarded, specifically including: if the protocol layer of the sending end device determines according to a preset judgment method to discard a protocol data unit set or a data packet included in the protocol data unit set, then the protocol data unit set or the data packet is discarded.
  • the method also includes: when the protocol layer entity of the sending device determines to discard the protocol data unit set or the data packet, if the data packet of the protocol data unit set has been transmitted to the next layer corresponding to the protocol layer, then the protocol layer entity sends a notification message to the protocol layer entity of the next layer, and the notification message is used to instruct the protocol layer entity of the next layer to discard the data packet.
  • an embodiment of the present application also provides a method for discarding data packets, which is applied to a receiving end, and the method includes: sending the configuration information to the sending end, so that the sending end determines whether to discard the protocol data unit set or the data packet included in the protocol data unit set according to a preset judgment method based on at least one item in the configuration information; the configuration information includes a packet loss threshold, a packet loss ratio threshold, a packet loss timer, the first attribute information corresponding to the protocol data unit set, the second attribute information corresponding to the data packet, and at least one of a dependency identifier.
  • the method also includes: configuring the configuration information with a protocol layer entity as the granularity; or, configuring the configuration information with a DRB as the granularity; or, configuring the configuration information with a protocol data unit set as the granularity; or, configuring the configuration information with a type of the protocol data unit set as the granularity, wherein the type of the protocol data unit set is at least one of the priority of the protocol data unit set, the importance level of the protocol data unit set, and the sequence number of the protocol data unit set.
  • the data structure of the configuration information is a sequence structure.
  • an embodiment of the present application also provides a method for discarding data packets, which is applied to a sending end, and the method includes: receiving packet loss indication information sent by the receiving end, and the packet loss indication information is used to indicate that the sending end triggers the discarding of a protocol data unit set or the discarding of the data packet; triggering the discarding of the protocol data unit set of the protocol layer or the data packet in the protocol data unit set, and the protocol data unit set includes at least one of the data packets.
  • an embodiment of the present application also provides a method for discarding data packets, which is applied to a sending end, and the method includes: receiving packet loss indication information sent by the receiving end, and the packet loss indication information is used to instruct the sending end to trigger the discarding of a set of protocol data units or the discarding of the data packet; triggering the protocol layer to execute the method for discarding data packets as described in any of the above embodiments.
  • an embodiment of the present application also provides a sending end device, including one or more processors; one or more memories; the one or more memories store one or more computer programs, and the one or more computer programs include instructions.
  • the sending end device executes one or more steps in any of the above methods.
  • an embodiment of the present application also provides a communication system, including a sending end device and a receiving end device, wherein the sending end device is used to execute one or more steps in any one of the above methods, and the receiving end is used to receive the data packet in the protocol data unit set transmitted by the sending end.
  • an embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable program instructions.
  • the computer-executable program instructions When executed on a computer, the computer or processor executes one or more steps in any of the above methods.
  • an embodiment of the present application also provides a computer program product comprising instructions, wherein the computer program product includes computer program code.
  • the computer program code runs on a computer, the computer or processor executes one or more steps in any of the above methods.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium.
  • the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive (SSD)), etc.
  • the processes can be completed by a computer program to instruct the relevant hardware, and the program can be stored in a computer-readable storage medium.
  • the program When the program is executed, it can include the processes of the above-mentioned method embodiments.
  • the aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请提供了一种数据包丢弃的方法及相关设备，属于数据处理领域。该方法包括：按照预设的判断方式判断是否丢弃协议数据单元集合或者协议数据单元集合包括的数据包，判断方式采用的判断依据包括协议数据单元集合的丢包数量、协议数据单元集合的丢包定时器、协议数据单元集合对应的第一属性信息、数据包对应的第二属性信息、协议数据单元集合与其他协议数据单元集合之间的依赖关系中至少一项；属性信息与允许丢弃或不允许丢弃关联，协议数据单元集合包括至少一个数据包；若按照该判断方式判断丢弃协议数据单元集合或数据包，则丢弃协议数据单元集合或数据包。该方法能够避免对无作用数据的继续传输，节省空口资源。

Description

一种数据包丢弃的方法及相关设备
本申请要求于2022年09月26日提交国家知识产权局、申请号为202211176858.4、申请名称为“一种数据包丢弃的方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及数据处理领域，尤其涉及一种数据包丢弃的方法及相关设备。
背景技术
扩展现实(extended reality，XR)技术是指通过计算机将显示与虚拟相结合，打造一个可人机交互的虚拟环境，包括虚拟现实(virtual reality，VR)、增强现实(augmented reality，AR)、混合现实(mixed reality，MR)以及云游戏(cloud game，CG)等。XR技术涉及的业务通常为音频或者视频，因而在XR场景下，用户设备(user equipment，发送端设备)和网络设备之间交互的数据流通常为音频数据流或者视频数据流。以视频业务为例，发送端设备和网络设备之间交互的数据单元(如一个帧或者视频切片)可能会包括多个网际互连协议(Internet Protocol，IP)数据包，而一个IP数据包又会包括至少一个协议数据单元集合(protocol data unit，PDU)。因此，在视频业务中，发送端设备和网络设备之间传输的数据单元实际上可以视为包括多个PDU的PDU集合(协议数据单元集合)。
在实际的数据单元传输过程中，由于多种因素的影响，不可避免地会产生丢包问题。对于以协议数据单元集合形式来传输的数据单元来说，如果在丢弃了一个或多个协议数据单元集合，或者丢弃了协议数据单元集合中的某些PDU，那么接收端就无法得到该协议数据单元集合携带的完整信息单元，此时即使获取了剩余的其他协议数据单元集合，也可能仍然无法得到完整的信息。因而，在一些协议数据单元集合发生了丢包的情形下，如果接收端坚持接收所有的协议数据单元集合，不仅无法得到完整信息，还会导致用于传输其他协议数据单元集合的资源被白白浪费。
发明内容
本申请实施例提供了一种数据包丢弃的方法及相关设备，通过基于协议数据包单元集对应的丢包数量、丢包定时器、属性信息、依赖关系中的至少一项，判断是否对该协议数据单元集合或其包括的数据包进行丢包处理，该方法能够避免对无作用数据的继续传输，节省空口资源。
第一方面，提供了一种数据包丢弃的方法，应用于发送端，所述方法包括：
按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，所述预设的判断方式采用的判断依据包括所述协议数据单元集合对应的丢包数量、所述协议数据单元集合的丢包定时器、所述协议数据单元集合对应的第一属性信息、所述数据包对应的第二属性信息、所述协议数据单元集合与其他协议数据单元集合之间的依赖关系中的至少一项；所述属性信息与允许丢弃或者不允许丢弃关联，所述协议数据单元集合包括一个或多个所述数据包；
若按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，则丢弃所述协议数据单元集合或者所述数据包。
在一种实现方式中，数据包可以包括PDU数据包或者SDU数据包，但本申请对此不作限定。协议数据单元集合例如可以指多个数据包的集合，可以包括一个或多个数据包。示例性的，协议数据单元集合可以对应于PDU set，但并不仅限于此。
在一种实现方式中，这里的丢弃协议数据单元集合或者所述数据包，可以包括：丢弃所述协议数据单元集合中未丢弃的数据包。其中，这里未丢弃的数据包可以指发送端已经接收到但还未丢弃的数据包；或者，可以指还未接收到的该协议数据单元集合中的数据包，也就是说，如果确定该协议数据单元集合的数据包需要丢弃之后，则接收到该协议数据单元集合的数据包之后可直接进行丢弃。
在一种实现方式中，允许丢弃是指协议数据单元集合或者数据包可以允许丢弃，不会导致对该协议数据单元集合或者该协议数据单元集合中的数据包进行丢包处理。不允许丢弃是指协议数据单元集合或者数据包不允许丢弃，如果丢弃则会导致对该协议数据单元集合或者该协议数据单元集合中的数据包进行丢包处理。
在一种实现方式中，属性信息与允许丢弃或者不允许丢弃关联是指，具有该属性信息的数据包或协议数据单元集合属于允许丢弃的数据包或协议数据单元集合的类型；或者具有该属性信息的数据包或协议数据单元集合属于不允许丢弃的数据包或协议数据单元集合的类型。比如，高优先级属性与不允许丢弃关联，那么优先级高的数据包协议数据单元集合则属于不允许丢弃的数据包或协议数据单元集合，如果发生丢弃，则需要对相应的协议数据单元集合或协议数据单元集合中的其它数据包进行丢弃。
在一种实现方式中，发送端可以是用户设备，但并不仅限于此。
在一种实现方式中，按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包也可以指，按照预设的判断方式判断协议数据单元集合或者所述协议数据单元集合包括的数据包是否满足丢弃条件，当满足该丢弃条件时，则丢弃所述协议数据单元集合或者所述协议数据单元集合包括的数据包。
值得注意的是，在本申请中，判断依据中的丢包数量或者丢包计数器计数所对应的丢弃的数据包是指通过其他方式丢弃的数据包，这里的其它方式是指本申请实施例提供的数据包丢弃方法之外的方式，比如包括：由于网络状态、通信状态等原因导致丢弃的数据包；或者，由于discard timer超时导致丢弃的数据包；或者，数据包或协议数据单元集合传输完成后，丢弃的数据包等等。本申请实施例对此不作限定。本申请中所说的协议数据单元集合中丢弃的数据包均可以参考前述解释，后续不再进行特别说明。
根据本实现方式提供的方法，通过基于协议数据包单元集对应的丢包数量、丢包定时器、属性信息、依赖关系中的至少一项，判断是否对该协议数据包单元集合进行丢包处理，该方法能够避免对无作用数据的继续传输，节省空口资源。
结合第一方面，在第一方面的某些实现方式中，所述第一属性信息包括所述协议数据单元集合对应的序列号、所述协议数据单元集合包括的所述数据包的总数量、所述协议数据单元集合的重要性等级、所述协议数据单元集合的优先级、所述协议数据单元集合的依赖关系中的至少一项；
所述第二属性信息包括所述数据包对应的数据包序列号、所述数据包在所述协议数据单元集合中的位置、所述数据包的重要性等级、所述数据包的优先级中的至少一项。
在一种实现方式中，数据包的第二属性信息还可以包括数据包对应的丢弃类型，该丢弃类型可以包括允许丢弃或不允许丢弃。
结合第一方面，在第一方面的某些实现方式中，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量时，所述方法具体包括：
获取所述协议数据单元集合对应的丢包门限；
获取所述协议数据单元集合对应的所述丢包数量；
若所述丢包数量达到或超过所述丢包门限，则丢弃所述协议数据单元集合或者所述数据包。
在一种实现方式中，丢包门限是指协议数据单元集合可以丢弃的数据包的最大数量门限。当确定协议数据单元集合的丢包数量达到或超过丢包门限时，则该协议数据单元集合中的数据包可以直接丢弃。
在一种实现方式中，丢包门限会在确认模式下进行配置。确认模式包括在传输数据包之后会接收到接收端反馈的指示信息，该指示信息指示该数据包是否传输成功或者是否需要重传，确认模式包括AM模式或者HARQ传输模式或者SN状态报告，本申请不做限定。
在一种实现方式中，丢包数量的获取不包括由于成功传输而丢弃的数据包，或者，丢包数量的获取仅包括由discard timer超时而丢弃的数据包。
在一种实现方式中，当确定协议数据单元集合的丢包数量达到丢包门限时，则该协议数据单元集合中的数据包可以直接丢弃，例如为：假设丢包门限为10，如果该协议数据单元集合的丢包数量达到10，也即丢包数量与丢包门限相等时，则该协议数据单元集合中的数据包可以直接丢弃。
在一种实现方式中，当确定协议数据单元集合的丢包数量超过丢包门限时，则该协议数据单元集合中的数据包可以直接丢弃，例如为：假设丢包门限为10，如果该协议数据单元集合的丢包数量从10增加为11，也即丢包数量大于丢包门限时，则该协议数据单元集合中的数据包可以直接丢弃。
结合第一方面，在第一方面的某些实现方式中，所述获取所述协议数据单元集合对应的丢包门限，具体包括：
接收接收端发送的第一配置信息，所述第一配置信息用于指示所述丢包门限，所述接收端用于接收所述数据包；或者，
获取所述发送端自身预先配置的所述丢包门限；或者，
通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包门限；或者，
接收核心网发送的第二配置信息，所述第二配置信息用于指示所述丢包门限。
其中，接收端可以用于接收所述数据包。
在一种实现方式中，发送端自身预先配置的所述丢包门限，可以是静态配置的丢包门限；发送端高层发送的所述丢包门限，可以是动态配置的丢包门限。
在一种实现方式中，高层可以指应用层或者传输层。
结合第一方面，在第一方面的某些实现方式中，当由所述发送端自身配置所述丢包门限时，所述方法还包括：
以协议层实体为粒度配置所述丢包门限；或者，
以数据无线承载DRB为粒度配置所述丢包门限；或者，
以所述协议数据单元集合为粒度配置所述丢包门限；或者，
以所述协议数据单元集合的类型为粒度配置所述丢包门限，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中的至少一项。
在一种实现方式中，以协议层实体为粒度配置所述丢包门限，可以指以每个协议层实体作为对象，配置丢包门限，也即对不同协议层实体配置不同的丢包门限，比如对于PDCP层实体，一个PDCP协议层实体配置9作为丢包门限，另一个PDCP协议层实体配置10作为丢包门限。以数据无线承载DRB为粒度配置所述丢包门限，可以指以每个DRB作为对象，配置丢包门限，也即可以对不同的DRB配置不同的丢包门限。以所述协议数据单元集合为粒度配置所述丢包门限，可以指以每个协议数据单元集合作为对象，配置丢包门限，不同协议数据单元集合可以对应不同的丢包门限。以所述协议数据单元集合的类型为粒度配置所述丢包门限，可以指以每个协议数据单元集合的类型作为对象，配置丢包门限，不同协议数据单元集合的类型可以对应不同的丢包门限。
结合第一方面，在第一方面的某些实现方式中，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量时，所述方法具体包括：
获取所述协议数据单元集合对应的丢包比例门限；
获取所述协议数据单元集合对应的所述丢包数量；
根据所述丢包数量与所述协议数据单元集合包括的所述数据包的总数量的比值获取所述协议数据单元集合对应的丢包比例；
若所述丢包比例达到或超过所述丢包比例门限，则丢弃所述协议数据单元集合或者所述数据包。
其中，丢弃所述数据包具体可以指丢弃所述协议数据单元集合中的数据包。
在一种实现方式中，丢包比例为协议数据单元集合中的丢包数量与该协议数据单元集合包括的数据包总数量的比值。
结合第一方面，在第一方面的某些实现方式中，所述获取所述协议数据单元集合对应的丢包比例门限，具体包括：
接收接收端发送的第三配置信息，所述第三配置信息用于指示所述丢包比例门限，所述接收端用于接收所述数据包；或者，
获取所述发送端自身预先配置的所述丢包比例门限；或者，
通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包比例门限；或者，
接收核心网发送的第四配置信息，所述第四配置信息用于指示所述丢包比例门限。
其中，接收端接收的数据包可以指接收的发送端传输的协议数据单元集合中的数据包。
在一种实现方式中，发送端自身预先配置的所述丢包比例门限，可以是静态配置的丢包比例门限；发送端高层发送的所述丢包门限，可以是动态配置的丢包比例门限。
在一种实现方式中，发送端自身预先配置的丢包比例门限，可以指发送端开机时配置的丢包比例门限。
在一种实现方式中，高层可以指应用层或者传输层。
结合第一方面，在第一方面的某些实现方式中，当由所述发送端自身配置所述丢包比例门限时，所述方法还包括：
以协议层实体为粒度配置所述丢包比例门限；或者，
以DRB为粒度配置所述丢包比例门限；或者，
以所述协议数据单元集合为粒度配置所述丢包比例门限；或者，
以所述协议数据单元集合的类型为粒度配置所述丢包比例门限，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中至少一项。
在一种实现方式中，以协议层实体为粒度配置所述丢包比例门限，可以指以每个协议层作为对象，配置丢包比例门限，也即对不同协议层实体配置不同的丢包比例门限，比如对于PDCP层实体，一个PDCP协议层实体配置20％作为丢包比例门限，另一个PDCP协议层实体配置10％作为丢包比例门限。以数据无线承载DRB为粒度配置所述丢包比例门限，可以指以每个DRB作为对象，配置丢包比例门限，也即可以对不同的DRB配置不同的丢包比例门限。以所述协议数据单元集合为粒度配置所述丢包比例门限，可以指以每个协议数据单元集合作为对象，配置丢包比例门限，不同写数据单元集合可以对应不同的丢包比例门限。以所述协议数据单元集合的类型为粒度配置所述丢包比例门限，可以指以每个协议数据单元集合的类型作为对象，配置丢包比例门限，不同协议数据单元集合的类型可以对应不同的丢包比例门限。
结合第一方面，在第一方面的某些实现方式中，所述获取所述协议数据单元集合对应的所述丢包数量，具体包括：
设置丢包计数器，所述丢包计数器用于对所述协议数据单元集合中丢弃的所述数据包的数量进行计数；
每获取一个所述协议数据单元集合中的所述数据包丢弃，所述丢包计数器的计数值加1；
根据所述丢包计数器的计数值获取所述协议数据单元集合对应的所述丢包数量。
结合第一方面，在第一方面的某些实现方式中，当所述丢包计数器对所述协议数据单元集合中丢弃的所述数据包的数量进行计数时，所述方法还包括：
所述丢包计数器对成功传输的且丢弃的所述数据包不进行计数。
应理解，成功传输的且丢弃的数据包，可以指发送端接收到接收端反馈的某数据包传输成功的消息后，在缓存中将其进行丢弃的数据包。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
当丢弃所述协议数据单元集合或者所述数据包时，对所述丢包计数器进行释放或清零；或者，
当所述协议数据单元集合对应的丢包数量未达到或者未超过所述丢包门限，且所述协议数据单元集合和/或所述数据包传输完成时，对所述丢包计数器进行释放或清零；或者，
当所述协议数据单元集合对应的丢包数量与所述协议数据单元集合包括的数据包的总数量的比值未达到或者未超过所述丢包比例门限，且所述协议数据单元集合和/或所述数据包传输完成时，对所述丢包计数器进行释放或清零；或者，
当所述计数器的计数值与所述协议数据单元集合包括的所述数据包的总数量的比值达到或超过对应的所述丢包比例门限时，对所述丢包计数器进行释放或清零；或者，
当所述计数器的计数值达到或超过所述丢包门限时，对所述丢包计数器进行释放或清零。
在一种实现方式中，所述协议数据单元集合和/或所述数据包传输完成可以指：在确认模式下，确定已经接收到最后一个数据包(如End PDU)或者确定已经接收到该协议数据单元集合的全部数据包，并且该协议数据单元集合中的数据包已经全部传输完成，这里的数据包全部传输完成可以包括两部分数据包：(1)发送端接收到接收端反馈的消息，从而确定成功传输的数据包；(2)发送端没有接收到反馈消息，且在数据包对应的定时器(discard timer)超时时丢弃的数据包。在无确认模式下，确定该协议数据单元集合中最后一个数据包传输至下一层或者确定已经接收到该协议数据单元集合的全部数据包。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
当存在所述数据包传输成功时，设置所述丢包计数器。
在一种实现方式中，当存在所述数据包传输成功时，设置所述丢包计数器是指，在有数据包确认传输成功的模式下配置计数器。
结合第一方面，在第一方面的某些实现方式中，当所述预设的判断方式采用的判断依据为所述协议数据单元集合的丢包定时器时，所述方法具体包括：
获取所述协议数据单元集合对应的丢包定时器；
当所述丢包定时器超时时，则丢弃所述协议数据单元集合或者所述数据包；或者，
当所述丢包定时器超时时，若所述协议数据单元集合或所述数据包未传输完成，则丢弃所述协议数据单元集合或者所述数据包。
结合第一方面，在第一方面的某些实现方式中，当接收到所述协议数据单元集合中的第一个所述数据包时，开启所述丢包定时器。
在一种实现方式中，所述协议数据单元集合中的第一个数据包可以包括：所述协议数据单元集合中的序列号为1的数据包，或者所述协议数据单元集合中的STRAT数据包，如具有START标识的数据包。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
当所述协议数据单元集合的传输时间超过所述丢包定时器的丢包定时时间时，则丢弃所述协议数据单元集合或者所述数据包。
结合第一方面，在第一方面的某些实现方式中，所述协议数据单元集合或数据包未传输完成，具体包括：
当所述丢包定时器超时时，所述发送端存在所述协议数据单元集合中的所述数据包。
应理解，这里的所说的发送端存在数据包是指发送端协议层缓存有所述数据包。
在一种实现方式中，所述协议数据单元集合未传输完成包括所述协议数据单元集合可以包括：(1)协议层实体未接收到接收端发送的反馈消息，因而未将相关数据包丢弃，意味着接收端可能没有接收到该数据包，也即数据包未传输完成；(2)协议层实体中还存在未传输至下一层的数据包，此时也说明数据包未传输完成；(3)协议层实体中缓存着所述协议数据单元集合的数据包。
结合第一方面，在第一方面的某些实现方式中，所述获取所述协议数据单元集合对应的丢包定时器，具体包括：
接收接收端发送的第五配置信息，所述第五配置信息用于指示所述丢包定时器，所述接收端用于接收所述数据包；或者，
获取所述发送端自身预先配置的所述丢包定时器；或者，
通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包定时器；或者，
接收核心网发送的第六配置信息，所述第六配置信息用于指示所述丢包定时器。
在一种实现方式中，高层可以指应用层或者传输层。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
当丢弃所述协议数据单元集合或者所述数据包时，对所述丢包定时器进行释放或清零；或者，
当所述丢包定时器未超时，且所述协议数据单元集合和/或数据包传输完成时，对所述丢包定时器进行释放或清零；或者，
当所述丢包定时器超时时，对所述丢包定时器进行释放或清零。
结合第一方面，在第一方面的某些实现方式中，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量和所述丢包定时器时，所述方法具体包括：
获取所述协议数据单元集合对应的丢包门限，以及所述协议数据单元集合对应的丢包定时器；
获取所述协议数据单元集合对应的所述丢包数量；
若所述丢包数量超过丢包门限，和/或若所述丢包定时器超时时，所述协议数据单元集合或者所述数据包未传输完成，则丢弃所述协议数据单元集合或者所述数据包；或者，
若所述丢包数量超过丢包门限，和/或若所述丢包定时器超时时，则丢弃所述协议数据单元集合或者所述数据包。
在一种实现方式中，所述协议数据单元集合或所述数据包未传输完成，具体包括：当所述丢包定时器超时时，所述发送端存在所述协议数据单元集合中的所述数据包。
结合第一方面，在第一方面的某些实现方式中，所述协议数据单元集合或所述数据包未传输完成，具体包括：
所述发送端存在所述协议数据单元集合中的所述数据包。
结合第一方面，在第一方面的某些实现方式中，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的第一属性信息和/或所述数据包对应的第二属性信息时，所述方法具体包括：
当所述协议数据单元集合对应的第一属性信息与所述不允许丢弃关联时，若具有所述第一属性信息的所述协议数据单元集合丢弃，则丢弃所述协议数据单元集合或者所述数据包；或者，
当所述数据包对应的第二属性信息与所述不允许丢弃关联时，若具有所述第二属性信息的所述数据包丢弃，则丢弃所述协议数据单元集合或者所述数据包。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
获取接收端发送的第七配置信息，所述第七配置信息用于指示所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息，所述接收端用于接收所述数据包；或者，
获取所述发送端自身预先配置的所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息；或者，
通过所述发送端自身的协议层接收所述发送端高层发送的所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息；或者，
接收核心网发送的第八配置信息，所述第八配置信息用于指示所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息。
结合第一方面，在第一方面的某些实现方式中，当所述预设的判断方式采用的判断依据为所述协议数据单元集合与其他协议数据单元集合之间的依赖关系时，所述方法具体包括：
获取第一协议数据单元集合与至少一个第二协议数据单元集合具有依赖关系；
基于所述依赖关系，若获取所述第二协议数据单元集合发生丢弃，则丢弃所述第一协议数据单元集合或者所述第一协议数据单元集合包括的所述数据包；或者，
基于所述依赖关系，若获取发生丢弃的所述第二协议数据单元集合的数量达到预设阈值，则丢弃所述第一协议数据单元集合或者所述第一协议数据单元集合包括的所述数据包。
结合第一方面，在第一方面的某些实现方式中，所述获取与第一协议数据单元集合具有依赖关系的至少一个第二协议数据单元集合，具体包括：
接收接收端发送的第九配置信息，所述第九配置信息用于指示依赖关系标识，所述接收端用于接收所述发送端传输的所述数据包；或者，
获取所述发送端自身预先配置的依赖关系标识；或者，
通过所述发送端自身的协议层接收所述发送端高层发送的依赖关系标识；或者，
接收核心网发送的第十配置信息，所述第十配置信息用于指示依赖关系标识；其中，所述依赖关系标识用于指示与所述协议数据单元集合相互依赖的其他所述协议数据单元集合。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
接收所述接收端或者所述发送端高层发送的丢包指示信息，所述丢包指示信息用于指示所述发送端触发协议数据单元集合的丢弃或者所述数据包的丢弃；
触发协议层的所述协议数据单元集合丢弃或者所述数据包丢弃。
结合第一方面，在第一方面的某些实现方式中，所述若按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，则丢弃所述协议数据单元集合或者所述协议数据单元集合包括的数据包，具体包括：
若所述发送端设备的协议层按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包时，则丢弃所述协议数据单元集合或者所述数据包。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
当所述发送端设备的协议层实体判断丢弃协议数据单元集合或者所述数据包时，如果所述协议数据单元集合的所述数据包已经被传输至所述协议层对应的下一层，则所述协议层实体向所述下一层的协议层实体发送通知消息，所述通知消息用于指示所述下一层的协议层实体丢弃所述数据包。
第二方面，提供了一种数据包丢弃的方法，应用于发送端，所述方法包括：
接收所述接收端或者所述发送端高层发送的丢包指示信息，所述丢包指示信息用于指示协议数据单元集合的丢弃或者所述数据包的丢弃；
触发协议层的所述协议数据单元集合或者所述协议数据单元集合中数据包丢弃，所述协议数据单元集合包括至少一个所述数据包。
在一种实现方式中，触发协议层的所述协议数据单元集合或者所述协议数据单元集合中数据包丢弃，可以指触发协议层的丢包处理功能。在该触发下，协议层可以执行如第一方面中任一实现方式中的方法。
第三方面，提供了一种数据包丢弃的方法，应用于发送端，所述方法包括：
接收所述接收端发送的丢包指示信息，所述丢包指示信息用于指示协议数据单元集合的丢弃或者所述数据包的丢弃；
触发协议层执行如上述第一方面中任一实现方式所述的数据包丢弃的方法。
第四方面，提供了一种数据包丢弃的方法，应用于接收端，所述方法包括：
向发送端发送所述配置信息，使得所述发送端依据所述配置信息中的至少一项，按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包；所述配置信息包括丢包门限、丢包比例门限、丢包定时器、协议数据单元集合对应的所述第一属性信息、数据包对应的第二属性信息、依赖关系标识中的至少一项。
结合第四方面，在第四方面的某些实现方式中，所述方法还包括：
以协议层实体为粒度配置所述配置信息；或者，
以DRB为粒度配置所述配置信息；或者，
以所述协议数据单元集合为粒度配置所述配置信息；或者，
以所述协议数据单元集合的类型为粒度配置所述配置信息，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中至少一项。
结合第四方面，在第四方面的某些实现方式中，所述配置信息的数据结构为序列结构。
第五方面，提供了一种发送端设备，包括：
一个或多个处理器；
一个或多个存储器；
所述一个或多个存储器存储有一个或多个计算机程序，所述一个或多个计算机程序包括指令，当所述指令被所述一个或多个处理器执行时，使得所述终端设备执行如上述第一方面至第三方面中任一实现方式所述的方法。
第六方面，提供了一种通信系统，包括发送端设备和接收端设备，所述发送端设备用于执行如上述第一方面至第三方面中任一实现方式所述的方法，所述接收端用于执行如上述第四方面中任一实现方式所述的方法。
第七方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机可执行程序指令，所述计算机可执行程序指令在被计算机上运行时，使所述计算机执行如上述第一方面至第四方面中任一实现方式所述的方法。
第八方面，提供了一种计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使所述计算机执行如上述第一方面至第四方面中任一实现方式所述的方法。
附图说明
图1为本申请实施例提供的一种协议数据单元集合的结构示意图。
图2A为本申请实施例提供的一种数据包丢弃的方法适用的系统架构的结构示意图。
图2B为本申请实施例提供的一种发送端设备100的结构示意图。
图3为本申请实施例提供的一种协议数据单元集合传输过程的示意图。
图4为本申请实施例提供的一种数据包丢弃的方法的示意性流程图。
图5为本申请实施例提供的另一种数据包丢弃的方法的示意性流程图。
图6为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。
图7为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。
图8为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。
图9为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。
图10为本申请实施例提供的一种数据包丢弃的方法中丢弃处理的触发流程示意图。
图11为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。
具体实施方式
需要说明的是，本申请实施例的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。在本申请实施例的描述中，除非另有说明，“/”表示或的意思，例如，A/B可以表示A或B；本文中的“和/或”仅仅是一种描述关联障碍物的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，在本申请实施例的描述中，除非另有说明，“多个”是指两个或多于两个，“至少一个”、“一个或多个”是指一个、两个或两个以上。
以下，术语“第一”、“第二”仅用于描述目的，而不能理解为指示或暗示相对重要性或者隐含指明所指示的技术特征的数量。由此，限定有“第一”、“第二”特征可以明示或者隐含地包括一个或者更多个该特征。
在本说明书中描述的参考“一个实施例”或“一些实施例”等意味着在本申请的一个或多个实施例中包括结合该实施例描述的特定特征、结构或特点。由此，在本说明书中的不同之处出现的语句“在一个实施例中”、“在一些实施例中”、“在其它一些实施例中”、“在另外一些实施例中”等不是必然都参考相同的实施例，而是意味着“一个或多个但不是所有的实施例”，除非是以其它方式另外特别强调。术语“包括”、“包含”、“具有”及它们的变形都意味着“包括但不限于”，除非是以其它方式另外特别强调。
为了便于理解本申请提供的数据包丢弃的方法，首先对下文实施例可能涉及的概念或者属于进行介绍。
1、协议数据单元集合
根据SA的定义，协议数据单元集合可以作为数据传输过程中的一个数据单元，一个协议数据单元集合由一个或者多个数据包组成，每个数据包都可以携带组成一个信息单元的有效载荷，接收端的应用层可以基于一个协议数据单元集合中所有PDU承载的有效载荷获取一个完整的信息单元，例如一个视频帧或者图片帧对应的信息。在本申请实施例中，数据单元可以包括帧和视频切片。其中，帧可以理解为传输数据的载体，视频切片可以理解为一种视频业务中特定类型的数据单元。从传输数据的载体的角度来看，在一些情形下，一个协议数据单元集合可以对应一个帧；从传输数据的类型的角度来看，在一些情形下，在视频业务中，一个协议数据单元集合承载的数据可以对应一个视频切片。
通常来说，接收端的应用层需要接收在协议数据单元集合内的所有数据包才能得到一个完整的信息单元，丢弃一个或者多个数据包可能都会导致接收端无法获得整个信息单元。然而，在一些情形下，接收端的应用层也可以通过某些算法根据已获取的PDU的数据计算丢弃部分的数据，这样即使丢弃了一些(如少量或者重要性较低的)PDU，接收端的应用层仍然可以恢复所有或者部分信息单元。
SA提出了PDU set的概念，定义如下：
PDU set:A PDU set is composed of one or more PDUs carrying the payload of one unit of information generated at the application level(e.g.a frame or video slice for XRM Services,as used in TR 26.926[27]).In some implementations all PDUs in a PDU set are needed by the application layer to use the corresponding unit of information.In other implementations,the application layer can still recover parts all or of the information unit,when some PDUs are missing.也即，一个PDU set由一个或者多个PDU组成，这些PDU携带了应用层产生的一个信息单元的有效载荷，例如一个帧或者视频切片。以上定义中说明，在一些实现中，应用层需要接收在PDU set内所有的PDU才能得到该信息单元；另一种实现，在丢弃了一些PDU的情况下，应用层仍然可以恢复所有或者部分信息单元。
2、协议数据单元集合的属性信息
SA中定义了多种关于协议数据单元集合和/或数据包的属性信息，例如包括：协议数据单元集合的序列号、协议数据单元集合包括的数据包的总数量、协议数据单元集合的重要性等级、协议数据单元集合的优先级、协议数据单元集合的依赖性/依赖关系；数据包在协议数据单元集合中的序列号、数据包在协议数据单元集合中的位置(如开始数据包/结束数据包等)、数据包的重要性等级、数据包的优先级等等。
比如，以协议数据单元集合是PDU set为例，其对应的属性信息例如可以表示为：(1)PUD set序列号(PDU Sequence number，SN)；(2)PDU set中的开始PDU/结束PDU(Start/End PDU of the PDU set)；(3)PDU set中的PDU序列号(PDU SN within a PDU set)；(4)PDU set中的PDU数量(Number of PDUs within a PDU set)；(5)PDU set重要性(PDU set importance)；(6)PDU set的依赖性/依赖关系(PDU set dependency)。
其中，上述属性信息可以由接收端来配置，或者可以由发送端自身配置，如由发送端的应用层或者传输层或者高层来配置，或者由核心网进行配置。
示例性的，数据包的重要性等级可以指位于同一个协议数据单元集合中的各个PDU可以具有不同的重要性等级。通常来说，协议数据单元集合内的第一个数据包(也即开始数据包)的重要性会高于最后一个数据包(也即最后或结束数据包)的重要性。
示例性的，协议数据单元集合的依赖性可以指一些协议数据单元集合可能依赖于其他协议数据单元集合。比如，当一个协议数据单元集合对应一个视频切片时，协议数据单元集合的依赖性可以表现为一个视频切片是否具有使用价值需要依赖于前一个视频切片是否被成功接收。再比如，当一个协议数据单元集合对应一个视频切片时，协议数据单元集合的依赖性可以表现为两个视频切片属于同一个帧，一个帧内所有的视频切片解码成功之后才能正确解码该帧，这种情况下只有前一个视频切片(协议数据单元集合)传输成功，后一个视频切片(协议数据单元集合)的传输才有意义。
此外，SA还定义了相关的QoS需求，包括：(1)协议数据单元集合延时预算，例如对于PDU set来说，可以表示为PDU set Delay Budget(PSDB)；(2)协议数据单元集合错误率，例如对于PDU set来说，可以表示为PDU set Error Rate(PSER)。
结合上文中的介绍，协议数据单元集合可以理解为用于传输XR数据流(或其他类型的视频/音频数据流)的新的传输形式。在目前已存在可以通过QoS流传输XR数据流的基础上，之所以再提出协议数据单元集合，主要基于以下两个方面的原因：
方面一：在当前的XR课题讨论中，XR数据流可能包括不同类型的帧，由于不同类型的帧对应的重要性也不同，因而一个XR数据流中可能存在不同重要性的帧(如I帧、P帧、B帧)。基于当前协议，一个XR数据流在一个QoS流中进行传输，而当前QoS处理是基于QoS流进行的，那么一个QoS流传输的不同重要性的帧可能会被进行同样的QoS处理。但实际上，重要程度较低的帧，可能并不需要和重要程度较高的帧进行相同的QoS处理。有鉴于此，就需要提出一种更细粒度的数据流传输方式，将不同重要性的帧分开传输。
方面二：对于视频流业务来说，应用层或者传输层需要传输的一个数据单元(如一个帧或者视频切片)通常会包括多个IP数据包，而一个IP数据包可能包括至少一个数据包(如PDU)。因而，在传输一个视频帧时，实际上传输的是多个数据包。
因而，综合第二方面介绍的数据单元的特点以及第一方面中的需求，SA提出了协议数据单元集合的概念。一个协议数据单元集合可作为一个数据单元，其可以具体对应一个帧或者一个视频切片。一个协议数据单元集合包括多个数据包，每个数据包都有区别于其他数据包的序列号(如PDU SN)，该多个数据包承载的有效载荷可以组成信息单元(如一个视频帧、一张图片等)。不同的协议数据单元集合可以设置不同的重要性等级，重要性等级高的协议数据单元集合例如可以用于传输重要性高的帧，重要等级低的协议数据单元集合例如可以用于传输重要性较低的帧，从而实现将重要性不同的帧分开传输，以便后续对这些帧进行有区别的处理。
举例来说，以协议数据单元集合是PDU set，且数据包为PDU作为示例，一种协议数据单元集合的结构可以如图1所示，该PDU set包括8个PDU，也即PDU set中的PDU数量(Number of PDUs within a PDU set)为8，并且这8个PDU的PDU序列号(PDU SN)例如可以分别记为：PDU SN1，PDU SN2，……，PDU SN8。应理解，图1所示的协议数据单元集合包括的PDU的数量以及PDU序列号的表示方式仅为示例，本申请实施例对此不作限定。
结合背景技术中的介绍，在传输过程中，由于网络状态或其他因素的影响，协议数据单元集合作为一个整体或者协议数据单元集合中的部分数据包都可能会丢弃。不同的丢包情况可能对接收端的应用层获取信息单元的影响也不同。比如可以分为以下几种情形：
情形一：如果在传输过程中，丢弃了一个或多个协议数据单元集合，那么接收端的应用层就无法得到该协议数据单元集合携带的信息单元。
情形二：如果在传输过程中，丢弃了协议数据单元集合中的部分数据包，且接收端的应用层无法通过剩余的数据包得到该协议数据单元集合携带的信息单元，那么该协议数据单元集合内剩余的数据包就不再具有使用价值，失去作用。
情形三：如果在传输过程中，丢弃了协议数据单元集合中的少量或者重要性等级较低的数据包，但接收端的应用层能够根据接收到的该协议数据单元集合中的其他PDU计算出丢弃数据包携带的数据内容，那么丢弃数据包不会影响应用层获得该协议数据单元集合携带的信息单元。但是如果当丢弃的PDU达到一定数量，或者丢弃的数据包重要性等级比较高时，接收端的应用层仍然无法得到该协议数据单元集合携带的信息单元。
需要说明的是，上述三种情形中以及下文类似情形下所说的丢弃的数据包可以指通过其他方式丢弃的数据包，这里的其它方式是指本申请实施例提供的数据包丢弃方法之外的方式，比如包括：由于网络状态、通信状态等原因导致丢弃的数据包；或者，由于discard timer超时导致丢弃的数据包；或者，数据包或协议数据单元集合传输完成后，丢弃的数据包等等。本申请实施例对此不作限定。本申请中所说的协议数据单元集合中丢弃的数据包均可以参考前述解释，后续不再进行特别说明。
根据上述列举的示例性情形可以得出，如果丢弃了一个或者多个协议数据单元集合内的数据包，或者丢弃了存在依赖性的多个协议数据单元集合中的一个或多个协议数据单元集合，就可能导致整个协议数据单元集合或者多个协议数据单元集合传输失败。此时，如果继续传输剩余的数据包或者协议数据单元集合，仅会导致资源浪费，而并不会对获取信息单元提供帮助。
有鉴于此，本申请提供了一种数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否丢弃剩余的数据包或者协议数据单元集合，并且在判断结果为丢弃协议数据单元集合或数据包时，对协议数据单元集合或数据包，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
本申请实施例提供的数据包丢弃的方法可以应用于在音频、视频、图片等业务下发送端与接收端之间进行音频流数据、视频流数据或图片数据传输的场景中，比如XR场景等。本申请实施例提供的数据包丢弃的方法可以应用于多种类型的通信系统中，比如，第五代(5th Generation，5G)移动通信系统，如新空口(new radio，NR)系统。此外，也可以应用于通用移动通信系统(universal mobile telecommunications system，UMTS)、无线局域网(wireless local area network，WLAN)、无线保真(wireless fidelity，Wi-Fi)系统、有线系统、车到任意物体(vehical to everything，V2X)通信系统、设备间(device-to-deveice，D2D)通信系统、第四代(4th generation，4G)移动通信系统、卫星通信系统，以及未来的通信系统，如第六代(6th Generation，6G)移动通信系统等。本申请实施例对此不作限定。
示例性的，如图2A所示，为本申请实施例提供的一种数据包丢弃的方法适用的系统架构10的结构示意图。该系统架构包括发送端设备100和接收端设备200(或称发送端和接收端)。
在一些实施例中，发送端设备100可以作为数据包传输的发送端，接收端设备200可以作为数据包传输的接收端。在本申请实施例提供的数据包丢弃的方法中，丢弃处理流程可以主要由发送端来执行。
在一些实施例中，发送端设备100可以多种类型的电子设备，比如手机、平板电脑、可穿戴设备、车载设备、增强现实(argumented reality，AR)/虚拟现实(virtual reality，VR)设备、云游戏(cloud gaming，CG)设备、混合现实(mixed reality，MR)设备、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、个人数字助理(personal digital assistant，PDA)等具有音频/视频，以及通信功能的设备。本申请实施例对发送端设备的具备类型不作限定。
在一些实施例中，接收端设备200可以是网络设备/核心网设备，例如为发送端设备100通过无线方式接入到该无线通信系统中的接入设备。接收端设备200可以是网络侧的一种用于发射或接收信号的实体，如基站。基站可以广义地覆盖如下中的各种名称，或与如下名称进行替换，比如：节点B(NodeB)、演进型基站(evolved NodeB，eNB)、下一代基站(next generation NodeB，gNB)、中继站、接入点、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、主站MeNB、辅站SeNB、多制式无线(MSR)节点、家庭基站、网络控制器、接入节点、接入点(AP)、传输节点、收发节点、基带单元(BBU)、射频拉远单元(RRU)、有源天线单元(AAU)、射频头(RRH)、中心单元(CU)、分布单元(DU)、定位节点等。基站可以是宏基站、微基站、中继节点、施主节点或者类似物。基站还可以用于设置于前述设备或者装置内的通信模块、调制解调器或者芯片。基站还可以是移动交换中心以及设备到设备(D2D)、车辆外联(V2X)、机器到机器(M2M)通信中承担基站功能的设备等。本申请实施例对网络设备所采用的具体技术和具体设备形态不作限定。
以下结合附图，对本申请实施例提供的数据包丢弃的方法中涉及的协议数据单元集合的传输过程进行介绍。
示例性的，如图2B所示，为本申请实施例提供的一种发送端设备100的结构示意图。
发送端设备100可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。
可以理解的是，本申请实施例示意的结构并不构成对发送端设备100的具体限定。在本申请另一些实施例中，发送端设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。另外，本申请实施例示意的各模块间的接口连接关系，指示示意性说明，并不构成对发送端设备100的结构限定。在本申请的另一些实施例中，发送端设备100也可以采用与上述实施例不同的接口连接方式，或多种接口连接方式的组合。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，存储器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是发送端设备100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
充电管理模块140用于从充电器接收充电输入。电源管理模块141用于连接电池142，充电管理模块140与处理器110。电源管理模块141接收电池142和/或充电管理模块140的输入，为处理器110，内部存储器121，外部存储器，显示屏194，摄像头193，和无线通信模块160等供电。电源管理模块141还可以用于监测电池容量，电池循环次数，电池健康状态(漏电，阻抗)等参数。在其他一些实施例中，电源管理模块141也可以设置于处理器110中。在另一些实施例中，电源管理模块141和充电管理模块140也可以设置于同一个器件中。
发送端设备100的无线通信功能可以通过天线1，天线2，移动通信模块150，无线通信模块160，调制解调处理器以及基带处理器等实现。
天线1和天线2用于发射和接收电磁波信号。发送端设备100中的每个天线可用于覆盖单个或多个通信频带。不同的天线还可以复用，以提高天线的利用率。例如：可以将天线1复用为无线局域网的分集天线。在另外一些实施例中，天线可以和调谐开关结合使用。
移动通信模块150可以提供应用在发送端设备100上的包括2G/3G/4G/5G等无线通信的解决方案。
无线通信模块160可以提供应用在发送端设备100上的包括无线局域网(wireless local area networks，WLAN)(如无线保真(wireless fidelity，Wi-Fi)网络)，蓝牙(bl发送端设备tooth，BT)，全球导航卫星系统(global navigation satellite system，GNSS)，调频(freq发送端设备ncy modulation，FM)，近距离无线通信技术(near field communication，NFC)，红外技术(infrared，IR)等无线通信的解决方案。无线通信模块160可以是集成至少一个通信处理模块的一个或多个器件。无线通信模块160经由天线2接收电磁波，将电磁波信号调频以及滤波处理，将处理后的信号发送到处理器110。无线通信模块160还可以从处理器110接收待发送的信号，对其进行调频，放大，经天线2转为电磁波辐射出去。
在一些实施例中，发送端设备100的天线1和移动通信模块150耦合，天线2和无线通信模块160耦合，使得发送端设备100可以通过无线通信技术与网络以及其他设备通信。所述无线通信技术可以包括全球移动通讯系统(global system for mobile communications，GSM)，通用分组无线服务(general packet radio service，GPRS)，码分多址接入(code division multiple access，CDMA)，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，长期演进(long term evolution，LTE)，BT，GNSS，WLAN，NFC，FM，和/或IR技术等。所述GNSS可以包括全球卫星定位系统(global positioning system，GPS)，全球导航卫星系统(global navigation satellite system，GLONASS)，北斗卫星导航系统(beidou navigation satellite system，BDS)，准天顶卫星系统(quasi-zenith satellite system，QZSS)和/或星基增强系统(satellite based augmentation systems，SBAS)。
发送端设备100通过GPU，显示屏194，以及应用处理器等实现显示功能。显示屏194用于显示图像，视频等。
外部存储器接口120可以用于连接外部存储卡，例如Micro SD卡，实现扩展发送端设备100的存储能力。外部存储卡通过外部存储器接口120与处理器110通信，实现数据存储功能。例如将音乐，视频等文件保存在外部存储卡中。
内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如声音播放功能，图像播放功能等)等。存储数据区可存储发送端设备100使用过程中所创建的数据(比如音频数据、电话本等)。此外，内部存储器121可以包括高速随机存取村呼气，还可以包括非易失性存储器，例如至少一个磁盘存储器件。闪存器件，通用闪存存储器(universal flash storage，UFS)等。处理器110通过运行存储在内部存储器121的指令，和/或存储在设置于处理器中的存储器的指令，执行发送端设备100的各种功能应用以及数据处理。
发送端设备100可以通过音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，以及应用处理器等实现音频功能。例如音乐播放，录音等。
示例性的，如图3所示，为本申请实施例提供的一种协议数据单元集合传输过程的示意图。
在一些实施例中，发送端传输协议数据单元集合中数据包的过程可以涉及以下几个层：服务数据适配协议(service data adaptation protocol，SDAP)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、无线链路层控制协议(radio link control，RLC)层和媒体接入控制层(medium access control，MAC)。但应理解，在实际应用中，发送端传输协议数据单元集合中数据包的过程所涉及的层并不仅限于前述介绍的几种。
需要说明的是，本申请实施例中所说的协议数据单元集合数据包可以是SDU数据包或者PDU数据包。SDU数据包和PDU数据包所承载的有效载荷可以是相同的，两者之间的关系可以理解为，在协议层中，本层的PDU为下层SDU，本层的SDU为上层的PDU。
在一些实施例中，发送端传输协议数据单元集合的数据包的过程可以包括：SDAP层获取其上层(应用层或者传输层)传输的IP数据包，在IP数据包的基础上进行无线承载(radio bearer，RB)处理，并生成包括头部(header)和实体部分SDAP SDU(即有效载荷)的数据包，该数据包可以被标记为SDAP PDU数据包。之后，SDAP层将SDAP PDU数据包传输至PDCP层。PDCP层获取SDAP PDU数据包之后，根据PDCP协议对数据包进行处理，生成包括头部H和实体部分PDCP PDU的数据包，该数据包可以被标记为PDCP PDU数据包。之后，PDCP层级将PDCP PDU数据包进一步传输至PLC层。RLC层获取PDCP PDU数据包之后，根据RLC协议对该PDCP PDU数据包进行处理，生成包括头部H和实体部分RLC PDU的数据包，该数据包可以被标记为RLC PDU数据包。之后，RLC层级将RLC PDU数据包进一步传输至MAC层。MAC层获取RLC PDU数据包之后，根据MAC协议对该RLC PDU数据包进行处理，生成包括头部H和实体部分MAC PDU的数据包，该数据包可以被标记为MAC PDU数据包。
按照上述过程，MAC层可以获得一个数据单元对应的多个MAC PDU数据包，基于这些MAC PDU数据包，MAC最终可以获取包括多个数据包的MAC PDU传输块(MAC PDU transport block)。之后，MAC层可以通过空口资源将生成的MAC PDU传输块传输至接收端。
在一些实施例中，接收端接收到协议数据单元之后，例如可以按照生成协议数据单元的逆过程对该协议数据单元进行解析，使接收端的应用层能够基于解析后的结果获取协议数据单元集合中所有PDU承载的数据，然后根据该所有PDU承载的有效载荷获取信息单元。其中，接收端对协议数据单元集合中的数据进行解析的具体方式以及过程可以根据相关协议或者实际需求进行设置，本申请实施例对此不作限定。
需要说明的是，本申请的图3实施例介绍的网络设备解析协议数据单元集合的方式仅为一种示例，在实际应用中，接收端的应用层还可以通过其他方式获取PDU承载的数据，本申请实施例对此不作限定。此外，在上述图3实施例介绍的协议数据单元集合生成过程中，SDAP层、PDCP层、RLC层和MAC层对数据包进行处理的具体方式和处理内容可以参见相关协议中的规定，本申请实施例对此不再详述。
值得注意的是，在本申请实施例提供的数据包丢弃的方法中，在对协议数据单元集合或者PDU执行丢弃处理之前，可以首先根据一种或多种判断方式判断是否丢弃协议数据单元集合或协议数据单元集合包括的数据包，如果判断丢弃协议数据单元集合或者其包括的数据包(也即判断结果为丢弃)，那么才会丢弃协议数据单元集合或协议数据单元集合包括的数据包；如果判断不丢弃协议数据单元集合或者其包括的数据包(也即判断结果为不丢弃)，那么即使存在协议数据单元集合的丢弃现象，也不会丢弃协议数据单元集合和协议数据单元集合包括的数据包。
在一些实施例中，本申请用于判断协议数据单元集合或数据包是否需要丢弃的判断方式可以有多种，例如，可以根据以下判断依据进行判断：协议数据单元集合中丢弃的数据包的数量、协议数据单元集合的丢包定时器、协议数据单元集合对应的第一属性信息、数据包对应的第二属性信息、协议数据单元集合与其他协议数据单元集合之间的依赖关系，其中，属性信息与允许丢弃或者不允许丢弃关联。关于每种判断方式的具体判断过程及丢弃过程，将在下文进行详细介绍，此处暂不详述。
在一些实施例中，当判断丢弃协议数据单元集合或协议数据单元集合包括的数据包时，也可以在协议层中执行丢弃协议数据单元集合或协议数据单元集合包括的数据包的操作。示例性的，这里的协议层具体可以是SDAP层、PDCP层、RLC层或者MAC层中的任一个，本申请实施例对此不作限定。
为了实现对是否丢弃协议数据单元集合或协议数据单元集合包括的数据包的判断，协议层需要感知该协议层中的数据包是哪一个协议数据单元集合(或称子QoS流)中的。示例性的，实现上述感知目的方式可以包括：协议层从高层获取数据包的属性信息，然后根据这些属性信息确定该协议层中的数据包属于哪一协议数据单元集合。其中，这里的高层可以包括应用层或者传输层。这里的属性信息可以包括SA针对协议数据单元集合定义的信息，比如：协议数据单元集合序列号、协议数据单元集合中的开始数据包和结束数据包、协议数据单元集合中每个数据包的序列号、数据包的重要性等级、数据包的优先级、协议数据单元集合中数据包的总数量、协议数据单元集合的重要性等级、协议数据单元集合的优先级、协议数据单元集合的依赖关系等等。此外，协议层还可以从高层获取QoS需求信息，比如：协议数据单元集合的时延预算、协议数据单元集合的容错率等。其中，该QoS需求信息可以是用于传输协议数据单元集合的QoS流对应的需求信息。
在一些实施例中，协议层获取上述属性信息的方式可以有多种，比如：方式1、协议层的上层可以将上述属性信息携带在数据包中传输至该协议层；方式2、协议层的上层可以在传输数据包时或者之后，将数据包对应上述属性信息传输至该协议层。本申请对协议层获取上述属性信息的具体方式不做限定。
考虑到在本申请中，协议层可以是SDAP层、PDCP层、RLC层或者MAC层中的任一个，那么协议层获取协议数据单元集合属性信息的方式可以分为以下几种：
1、如果是SDAP层进行感知，那么可以由SDAP层的上层(如应用层或者传输层或者SDAP层的上一层协议层，本本申请对此不做限定)指示该SDAP层关于协议数据单元集合和/或数据包对应的上述属性信息。SDAP层获取协议数据单元集合和/或数据包的属性信息后，可以把这些属性信息封装在SDAP PDU中或者通知给下一层协议层。
2、如果是PDCP层进行感知，那么可以由SDAP层或者PDCP层的上一层协议层指示该PDCP层关于协议数据单元集合和/或数据包对应的上述属性信息。PDCP层获取协议数据单元集合和/或数据包的属性信息后，可以把这些属性信息封装在PDCP PDU或者通知给下一层协议层。
3、如果是RLC层进行感知，那么可以由PDCP层指示该RLC层接收关于协议数据单元集合和/或数据包对应的上述属性信息。RLC层获取协议数据单元集合的属性信息后，可以把这些属性信息封装在RLC PDU或者通知给下一层协议层。
以下结合具体示例，对通过不同判断方式确定协议数据单元集合或数据包是否需要丢弃的过程进行的介绍。为了便于理解，下文以本申请实施例提供的数据包丢弃的方法在协议层的PDAC层进行作为示例。
示例性的，本申请实施例提供的数据包丢弃的方法，可以从协议数据单元集合对应的丢包数量、协议数据单元集合的丢包定时器、协议数据单元集合对应的第一属性信息、数据包对应的第二属性信息、协议数据单元集合与其他协议数据单元集合之间的依赖关系中的一个或多个方面进行丢弃条件的判断。示例性的，具体可以分为以下几种判断方式：
判断方式1：根据协议数据单元集合的丢包数量确定是否丢弃该协议数据单元集合或其包括的数据包。
判断方式2：根据协议数据单元集合的丢包比例确定是否丢弃该协议数据单元集合或其包括的数据包。
判断方式3：根据针对协议数据单元集合设置的丢包定时器是否超时确定是否丢弃该协议数据单元集合或其包括的数据包。
判断方式4：根据针对协议数据单元集合的丢包数量以及该协议数据单元集合的对应的丢包定时器综合确定是否丢弃该协议数据单元集合或其包括的数据包。
判断方式5：根据协议数据单元集合中具有特定属性信息的数据包是否丢弃，确定是否丢弃该协议数据单元集合或其包括的数据包，该特定属性信息与不允许丢弃关联。
判断方式6：对存在依赖性(或称依赖关系)的协议数据单元集合，根据关联的协议数据单元集合是否丢包或丢包数量确定是否丢弃该协议数据单元集合或其包括的数据包。
为了便于理解，下文实施例以发送端是用户设备(user equipment，UE)、接收端是网络设备为例进行介绍。
示例性的，请参见图4，为本申请实施例提供的一种数据包丢弃的方法的示意性流程图。该流程中用于判断是否丢包的方式可以对应于上述判断方式1，也即根据协议数据单元集合的丢包数量确定是否丢弃该协议数据单元集合或其包括的数据包。该流程可以包括以下步骤：
S401，网络设备向UE发送丢包门限。
其中，这里的网络设备向UE发送丢包门限也可以理解为，网络设备向UE配置丢包门限。
其中，该丢包门限用于指示协议数据单元集合可允许丢弃的数据包数量的最大门限。这里所说的协议数据单元集合可允许丢弃的数据包数量的最大门限是指，当该协议数据单元集合中丢弃的数据包的数量小于该门限时，可能不会影响网络设备应用层获取该协议数据单元集合承载的信息单元，例如丢弃的数据包数量较少，网络设备可以基于没有丢弃的数据包的内容计算获取丢弃的数据包承载的内容，从而获取完整的信息单元。而当该协议数据单元集合中丢弃的数据包的数量大于或者等于该门限时，网络设备可能就无法基于剩余的数据包承载的有效载荷获取完整的信息单元。
需要说明的是，对于判断方式1，本申请图4实施例给出了由网络设备配置丢包门限的过程，但在实际应用中，该丢包门限还可以由UE的高层(如应用层或者传输层)进行配置，或者还可以由核心网设备进行配置，本申请实施例对此不作限定。
在一些实施例中，该丢包门限的配置粒度为针对每个数据无线承载(data radio bearer，DRB)分别进行配置，也即配置粒度为per DRB，也即DRB配置中包括丢包门限，不同的DRB可能会对应不同的丢包门限；或者，该丢包门限的配置粒度为针对每个协议层实体进行配置，即协议层实体配置中包括丢包门限，不同类型的协议层实体(如SDAP、PDCP、RLC等)可能会对应不同的丢包门限；或者，该丢包门限的配置粒度为针对每个协议数据单元集合分别进行配置，例如配置粒度为per协议数据单元集合，即协议数据单元集合配置中包括丢包门限，不同的协议数据单元集合可能会对应不同的丢包门限；或者，该丢包门限的配置粒度为针对每个协议数据单元集合的类型分别进行配置，即协议数据单元集合类型配置中包括丢包门限，不同类型的协议数据单元集合可能会对应不同的丢包门限。本申请实施例对丢包门限的配置粒度不作具体限定。
需要说明的是，上文所说的协议数据单元集合的类型可以为协议数据单元集合的重要性等级、协议数据单元集合的优先级、协议数据单元集合序列号。本申请实施例对此不作限定。
在一些实施例中，如果以per协议数据单元集合或者per协议数据单元集合的类型作为丢包门限的配置粒度，那么协议数据单元集合或者协议数据单元集合的类型分别对应的丢包门限可以是序列结构。
在一些实施例中，网络设备配置的丢包门限的数据类型可以是枚举型或者整数型。
在一些实施例中，网络设备可以通过无线资源控制(Radio Resource Control，RRC)信令，MAC控制元素(MAC Control Element，MAC CE)，下行控制信息(downlink control information，DCI)配置丢包门限。
在一些实施例中，网络设备配置的丢包门限可以包括在数据无线承载(data radio bearer，DRB)或者协议层实体配置中。
S402，获取协议数据单元集合中数据包的丢包数量，当该协议数据单元集合的数据包丢包数量达到或超过丢包门限后，丢弃该协议数据单元集合或其包括的数据包。
在一些实施例中，UE可以根据网络设备发送的丢包门限，确定当前协议数据单元集合允许丢弃的数据包的最大数量。在一些实施例中，UE可以根据丢包计数器中的计数值确定当前协议数据单元集合的丢包数量，当丢包数量达到丢包门限时，对该协议数据单元集合进行丢弃处理。示例性的，该过程可以包括：UE可以为当前协议数据单元集合维护一个丢包计数器，当该协议数据单元集合丢弃一个数据包时，该丢包计数器的计数值加1；当该丢包计数器的计数值等于丢包门限或等于(丢包门限+1)时，UE可以丢弃该协议数据单元集合或其包括的数据包。当该协议数据单元集合已经传输完成且该协议数据单元集合对应的丢包计数器的计数值未达到丢包门限，则不对该协议数据单元集合进行丢弃处理。
需要说明的是，丢弃该协议数据单元集合或其包括的数据包可以指丢弃协议数据单元集合中未丢弃的数据包。
其中，上文所说丢弃协议数据单元集合中未丢弃的数据包可以包括两种：(1)是指客户端(如客户端的协议层)丢弃已经接收到的该协议数据单元集合中的数据包；(2)客户端(如客户端的协议层)丢弃还未接收到的该协议数据单元集合中的数据包，也就是说，一旦确定需要对该协议数据单元集合进行丢弃处理，那么在接收到该协议数据单元集合之后的数据包时，可以直接进行丢弃。在一些实施例中，当丢包计数器的计数值达到丢包门限时，UE可以释放丢包计数器中的计数值，或者对丢包计数器中的计数值进行清零。当协议数据单元集合已经传输完成且该协议数据单元集合对应的丢包计数器的计数值未达到丢包门限时，UE也可以释放丢包计数器中的计数值，或者对丢包计数器中的计数值进行清零。
在一些实施例中，对于已经被成功传输至网络设备的数据包(如UE接收到针对该数据包反馈的状态报告，指示该数据包已经被成功传输)，如果将其丢弃，由于该情况的丢包不会影响网络设备对信息单元的获取，因而不将丢包计入丢包计数器。也就是说，丢包计数器不会对成功传输之后进行丢弃的数据包进行计数。
在一些实施例中，判断协议数据单元集合是否已经传输完成的方式可以包括多种，比如：方式1，根据该协议数据单元集合内最后一个数据包是否已经接收或者已经传输至下一层，若是，则确定传输完成；方式2，根据接收到的属于该协议数据单元集合的数据包，判断是否已经接收到该协议数据单元集合内最后一个数据包且该协议数据单元集合内的所有数据包已经全部传输完成，该所有数据包包括接收到网络设备反馈消息后主动丢弃已经传输成功的数据包，以及已经按照discard timer丢弃的数据包，或者该所有数据包包括接收网络设备反馈消息后主动丢弃已经传输成功的数据包，以及传输至下一层的数据包。
在一些实施例中，需要说明的是，丢包计数器会在确认模式下进行配置。确认模式包括在传输数据包之后会接收到接收端反馈的指示信息(或状态报告)，该指示信息指示该数据包是否传输成功或者是否需要重传，确认模式包括AM模式或者HARQ传输模式或者SN状态报告，本申请不做限定。
以实体是PDCP实体、协议数据单元集合为PDU set为例，对上述判断方式1所对应的丢弃的过程进行进一步举例介绍。
示例性的，对于AM DRB来说，UE的PDCP实体接收到PDCP SDU之后，可以根据该PDCP SDU对应的PDU set序列号(假设为1)确定该PDCP SDU所属的PDU set为PDU set 1，并且可以根据该PDCP SDU对应的PDU SN(假设为1)确定该PDCP SDU为PDU set 1的第一个数据包。之后，UE开启PDCP SDU对应的丢弃定时器
(discard timer)，同时为该PDU set 1维护丢包计数器。后续UE的PDCP实体会继续接收该PDU set 1的其他PDCP SDU，PDCP实体会为每一个PDCP SDU开启对应的丢弃定时器(discard timer)。
需要说明的是，这里的丢弃定时器(discard timer)可以针对UE接收网络设备针对数据包反馈的状态报告进行定时，或者可以针对UE对其缓存的数据包进行丢弃的时间进行定时。其中，当网络设备接收到数据包(也即数据包成功传输至网络设备)时，网络设备会向UE反馈该数据包对应的状态报告(或称反馈消息)，告知UE该数据包已经传输成功；UE获取到该信息之后，会将其缓存的该数据包丢弃。如果在丢弃定时器(discard timer)超时时，UE会丢弃对应的数据包，那么意味着该数据包未被成功传输完成。
在一些实施例中，如果PDCP接收到针对该PDCP SDU对应的状态报告并指示该PDCP SDU成功传输，则丢弃该PDCP SDU；这种情况下，丢包是在数据包成功传输之后进行的，因而该丢包不会被丢包计数器计入计数值。也就是说，本申请实施例的计数器会对未成功传输情形下的丢包进行统计。
在一些实施例中，如果PDCP SDU对应的discard timer超时时，则丢弃该PDCP SDU。可以说明的是，PDCP在discard timer超时时，没有接收到网络设备针对该PDCP SDU反馈的状态报告，则PDCP实体可以确定该PDCP SDU在未成功传输的情形下丢弃，基于此，如果PDCP SDU因为其对应的discard timer超时而进行丢弃，另一种情况如果协议引入其他的数据包丢弃方法并且该方法不包括因为数据包成功传输而进行丢弃，则该方法产生丢弃数据包，则丢包计数器进行计数，计数值加1。当PDCP实体为该PDU set 1维护的丢包计数器超过了丢包门限，则认为该PDU set 1的数据包需要进行丢弃处理，其中，该丢弃处理可以包括：1)对于已经接收到并且还未丢弃的PDU set 1的数据包进行丢弃；2)后续接收到的数据包，判断其是否属于PDU set 1的数据包，如果属于PDU set 1的数据包，则丢弃该数据包。而在另一些实施例中，如果该PDU set 1的数据包已经传输完成并且丢弃的数据包并未超过丢包门限，则UE可以释放或者清零该丢包计数器。
根据本申请提供的数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否有必要对剩余的数据包或者协议数据单元集合进行传输，在没有必要继续传输的情况下，对协议数据单元集合或者数据包进行丢弃，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
示例性的，请参见图5，为本申请实施例提供的另一种数据包丢弃的方法的示意性流程图。该流程中用于判断是否丢包的方式可以对应于上述判断方式2，也即根据协议数据单元集合的丢包比例确定是否丢弃该协议数据单元集合或其包括的数据包。该流程可以包括以下步骤：
S501，网络设备向UE发送丢包比例门限。
其中，这里的网络设备向UE发送丢包比例门限也可以理解为，网络设备向UE配置丢包比例门限。
其中，该丢包比例门限用于指示协议数据单元集合可允许丢弃数据包的最大比例。这里所说的协议数据单元集合可允许丢弃数据包的最大比例是指，当该协议数据单元集合中丢弃的数据包的数量占该协议数据单元集合中数据包总数量的比例小于丢包比例门限时，可能不会影响网络设备应用层获取该协议数据单元集合承载的信息单元，例如丢弃的数据包数量较少，网络设备可以基于没有丢弃的数据包的内容计算获取丢弃的数据包承载的内容，从而获取完整的信息单元。而当该协议数据单元集合中丢弃的数据包的数量占该协议数据单元集合中数据包总数量的比例大于或等于丢包比例门限时，网络设备可能无法基于剩余的数据包承载的有效载荷获取完整的信息单元。
需要说明的是，对于判断方式2，本申请图5实施例给出了由网络设备配置丢包比例门限的过程，但在实际应用中，该丢包比例门限还可以由UE的高层(如应用层或者传输层)进行配置，或者还可以由核心网进行配置，本申请实施例对此不作限定。
在一些实施例中，该丢包比例门限的配置粒度为针对每个数据无线承载(data radio bearer，DRB)分别进行配置，也即配置粒度为per DRB，也即DRB配置中包括丢包比例门限，不同的DRB可能会对应不同的丢包比例门限；或者，该丢包比例门限的配置粒度为针对每个协议层实体进行配置，即协议层实体配置中包括丢包比例门限，不同类型的协议层实体(如SDAP、PDCP、RLC等)可能会对应不同的丢包比例门限；或者，该丢包比例门限的配置粒度为针对每个协议数据单元集合分别进行配置，也即配置粒度为per协议数据单元集合，即协议数据单元集合配置中包括丢包比例门限，不同的协议数据单元集合可能会对应不同的丢包比例门限；或者，该丢包比例门限的配置粒度为针对每个协议数据单元集合的类型分别进行配置，即协议数据单元集合类型配置中包括丢包比例门限，不同类型的协议数据单元集合可能会对应不同的丢包比例门限。本申请实施例对丢包比例门限的配置粒度不作具体限定。
需要说明的是，上文所说的协议数据单元集合的类型可以为数据单元集合的重要性等级、协议数据单元集合的优先级、协议数据单元集合序列号等。本申请实施例对此不作限定。
在一些实施例中，网络设备可以通过RRC信令，MAC CE，DCI配置丢包门限。
在一些实施例中，网络设备配置的丢包比例门限可以包括在数据无线承载(data radio bearer，DRB)或者协议层实体配置中。
S502，获取协议数据单元集合对应的丢包比例，当该协议数据单元集合的丢包比例达到或超过丢包比例门限后，丢弃该协议数据单元集合或其包括的数据包。
在一些实施例中，UE可以根据网络设备发送的丢包门限，确定当前协议数据单元集合对应的丢包比例门限。
在一些实施例中，UE可以根据丢包计数器中的计数值确定当前协议数据单元集合的丢包数量，并根据丢包数量和该协议数据单元集合中数据包的总数量的比值确定丢包比例，当丢包比例达到或超过丢包比例门限时，则丢弃该协议数据单元集合或其包括的数据包。示例性的，该过程可以包括：UE可以为当前协议数据单元集合维护一个丢包计数器，当UE确定该协议数据单元集合丢弃一个数据包时，该丢包计数器的计数值加1，并获取该协议数据单元集合的丢包比例；随着丢包数量增加，丢包比例也会增加，当丢包比例等于或大于丢包比例门限时，UE可以丢弃该协议数据单元集合中未丢弃的数据包。当该协议数据单元集合已经传输完成且该协议数据单元集合对应的丢包比例未达到丢包比例门限，则不对该协议数据单元集合进行丢弃处理。
其中，上文所说的UE可以丢弃的协议数据单元集合中未丢弃的数据包可以包括：(1)是指协议层已经接收到的该协议数据单元集合中的数据包；(2)协议层还未接收到的该协议数据单元集合中的数据包，也就是说，一旦确定需要对该协议数据单元集合进行丢弃处理，那么协议层在接收到该协议数据单元集合之后的数据包时，可以直接进行丢弃。
在一些实施例中，当丢包比例达到丢包比例门限时，UE可以释放丢包计数器中的计数值，或者对丢包计数器中的计数值进行清零。当协议数据单元集合已经传输完成且该协议数据单元集合对应的丢包比例未达到丢包比例门限时，UE也可以释放丢包计数器中的计数值，或者对丢包计数器中的计数值进行清零。
在一些实施例中，对于已经被成功传输至网络设备的数据包(如UE接收到针对该数据包反馈的状态报告，指示该数据包已经被成功传输)，如果协议层将其主动丢弃，那么由于该情况的丢包不会影响网络设备对信息单元的获取，因而不将丢包计入丢包计数器。也就是说，丢包计数器不会对成功传输之后进行丢弃的数据包进行计数。
在一些实施例中，判断协议数据单元集合是否已经传输完成的方式可以包括多种，比如：方式1，根据该协议数据单元集合内最后一个数据包是否已经接收或者已经传输到下一层，若是，则确定传输完成；方式2，根据接收到的属于该协议数据单元集合的数据包，判断是否已经接收到该协议数据单元集合内最后一个数据包且该协议数据单元集合内的所有数据包已经传输完成，该所有数据包包括接收到网络设备反馈消息后主动放弃已经传输成功的数据包，以及已经按照discard timer丢弃的数据包，或者该所有数据包包括协议层接收网络设备反馈消息后主动丢弃已经传输成功的数据包，以及传输至下一层的数据包。
以实体是PDCP实体、协议数据单元集合为PDU set为例，对上述判断方式2所对应的丢弃的过程进行进一步举例介绍。
示例性的，对于AM DRB来说，UE的PDCP实体接收到PDCP SDU之后，可以根据该PDCP SDU对应的PDU set序列号(假设为1)确定该PDCP SDU所属的PDU set为PDU set 1，并且可以根据该PDCP SDU对应的PDU SN(假设为1)确定该PDCP SDU为PDU set 1的第一个数据包。之后，UE开启PDCP SDU对应的丢弃定时器(discard timer)，同时为该PDU set 1维护丢包计数器。后续UE的PDCP实体会继续接收该PDU set 1的其他PDCP SDU，PDCP实体会为每一个PDCP SDU开启对应的丢弃定时器(discard timer)。
需要说明的是，这里的discard timer可以针对UE接收网络设备针对数据包反馈的状态报告进行定时，或者可以针对UE对其缓存的数据包进行丢弃的时间进行定时。其中，当网络设备接收到数据包(也即数据包成功传输至网络设备)时，网络设备会向UE反馈该数据包对应的状态报告(或称反馈消息)，告知UE该数据包已经传输成功；UE获取到该信息之后，会将其缓存的该数据包丢弃。如果在discard timer超时时，UE会丢弃对应的数据包，那么意味着该数据包未被成功传输完成。
在一些实施例中，如果PDCP接收到针对该PDCP SDU对应的状态报告并指示该PDCP SDU成功传输，则丢弃该PDCP SDU；这种情况下，丢包是在数据包成功传输之后进行的，因而该丢包不会被丢包计数器计入计数值。也就是说，本申请实施例的计数器会对未成功传输情形下的丢包进行统计。
在一些实施例中，如果PDCP SDU对应的discard timer超时时，则丢弃该PDCP SDU。可以说明的是，PDCP在discard timer超时时，没有接收到网络设备针对该PDCP SDU反馈的状态报告，则PDCP实体可以确定该PDCP SDU在未成功传输的情形下丢弃，基于此，如果PDCP SDU因为其对应的discard timer超时而进行丢弃，另一种情况如果协议引入其他的数据包丢弃方法并且该方法不包括因为数据包成功传输而进行丢弃，则该方法产生丢弃数据包，则丢包计数器进行计数，计数值加1。当PDCP实体为该PDU set 1维护的丢包计数器的计数值与PDU set包括的PDCP SDU总数量的比值超过了对应的丢包比例门限，则认为需要丢弃该PDU set 1的数据包，其中，该丢弃处理可以包括：1)对于已经接收到并且还未丢弃的PDU set 1的数据包进行丢弃；2)后续接收到的数据包，判断其是否属于PDU set 1的数据包，如果属于PDU set 1的数据包，则丢弃该数据包。而在另一些实施例中，如果该PDU set 1的数据包已经传输完成，并且对应的丢包数量与PDU set包括的PDCP SDU总数量的比值并未超过丢包门限，则UE可以释放或者清零该丢包计数器。
需要说明的是，UE在配置丢包计数器之前，可以首先判断是否已经成功接收到协议数据单元集合的至少一个数据包，当确定该协议数据单元集合中存在一个或多个数据包被UE成功接收之后，UE才会对该丢包计数器进行配置。或者，UE在配置丢包计数器之前，可以首先判断是否已经成功将协议数据单元集合的至少一个数据包传输至网络设备(如判断是否接收到了网络设备发送的数据包传输成功的反馈消息)，当确定该协议数据单元集合中存在一个或多个数据包已被成功传输至网络设备之后，UE才会对该丢包计数器进行配置。
根据本申请提供的数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否有必要对剩余的数据包或者协议数据单元集合进行传输，在没有必要继续传输的情况下，对协议数据单元集合或者数据包进行丢弃，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
示例性的，请参见图6，为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。该流程中用于判断是否丢包的方式可以对应于上述判断方式3，也即根据针对协议数据单元集合设置的丢包定时器是否超时确定是否丢弃该协议数据单元集合或其包括的数据包。该流程可以包括以下步骤：
S601，网络设备向UE发送丢包定时器。
其中，这里的网络设备向UE发送丢包定时器也可以理解为，网络设备向UE配置丢包定时器。
其中，该丢包定时器用于指示协议数据单元集合的丢包时间，一种实现方式，丢包时间可以理解为协议数据单元集合可允许的传输时间。
需要说明的是，对于判断是否丢包的方式3，本申请图6实施例给出了由网络设备配置丢包定时器的过程，但在实际应用中，该丢包定时器还可以由UE的高层(如应用层或者传输层)进行配置，或者还可以由核心网进行配置，本申请实施例对此不作限定。
在一些实施例中，该丢包定时器的配置粒度为针对每个数据无线承载(data radio bearer，DRB)分别进行配置，也即配置粒度为per DRB，也即DRB配置中包括丢包定时器，不同的DRB可能会对应不同的丢包定时器；或者，该丢包定时器的配置粒度为针对每个协议层实体进行配置，即协议层实体配置中包括丢包定时器，不同类型的协议层实体(如SDAP、PDCP、RLC等)可能会对应不同的丢包定时器；或者，该丢包定时器的配置粒度为针对每个协议数据单元集合分别进行配置，也即配置粒度为per协议数据单元集合，即协议数据单元集合配置中包括丢包定时器，不同的协议数据单元集合可能会对应不同的丢包定时器；或者，该丢包定时器的配置粒度为针对每个协议数据单元集合的类型分别进行配置，即协议数据单元集合类型配置中包括丢包定时器，不同类型的协议数据单元集合可能会对应不同的丢包定时器。本申请实施例对丢包定时器的配置粒度不作具体限定。
在一些实施例中，网络设备可以通过RRC信令，MAC CE，DCI配置丢包定时器。
在一些实施例中，网络设备配置的丢包定时器可以包括在数据无线承载(data radio bearer，DRB)或者协议层实体配置中。
S602，当接收到协议数据单元集合的第一个数据包时，开启丢包定时器；当丢包定时器超时，且协议数据单元集合的数据包还未传输完成时，或者丢包定时器超时，丢弃该协议数据单元集合或其包括的数据包。
在一些实施例中，当接收到协议数据单元集合的第一个数据包时，开启丢包定时器。其中，确定其接收到的数据包为协议数据单元集合中第一个数据包的方式可以包括：接收到数据包后，判断该数据包是否为协议数据单元集合的开始数据包，若是，则表示该数据包为协议数据单元集合中的第一个数据包。或者，接收到数据包后，判断该数据包对应的数据包序列号是否为协议数据单元集合中的第一个数据包。或者，协议层实体接收到数据包后，判断之前并未接收过该协议数据单元集合的数据包，则该数据包为协议数据单元集合中的第一个数据包。本申请不做限制。
在一些实施例中，当丢包定时器超时，且协议数据单元集合的数据包还未传输完成时，丢弃该协议数据单元集合或其包括的数据包。或者，在另一些实施例中，也可以当丢包定时器超时，就丢弃该协议数据单元集合或其包括的数据包。其中，确定协议数据单元集合的数据包还未传输完成的方式可以包括以下几种：
在一些实施例中，判断协议数据单元集合是否已经传输完成的方式可以包括多种，比如：方式1，根据该协议数据单元集合内最后一个数据包是否已经接收或者已经传输至下一层，若是，则确定传输完成；方式2，根据接收到的属于该协议数据单元集合的数据包，判断是否已经接收到该协议数据单元集合内最后一个数据包且该协议数据单元集合内的所有数据包已经全部传输完成，该所有数据包包括接收到网络设备反馈消息后主动丢弃已经传输成功的数据包，以及已经按照discard timer丢弃的数据包，或者该所有数据包包括协议层接收网络设备反馈消息后主动丢弃已经传输成功的数据包，以及传输至下一层的数据包。
值得注意的时，本申请实施例中的丢包计时器和丢弃计时器(discard timer)为两个不同的概念，需区分理解。
在一些实施例中，如果在丢包定时器未超时时，协议数据单元集合的数据包传输完成，那么可以停止该丢包定时器，或者可以释放该丢包定时器，又或者可以对该丢包定时器进行清零。
在一些实施例中，如果在丢包定时器超时，那么可以对该协议数据单元集合进行丢弃处理。
在一些实施例中，协议数据单元集合进行丢弃处理具体可以指，丢弃该协议数据单元集合中未被丢弃的数据包。其中，协议数据单元集合中未被丢弃的数据包可以包括：(1)是指客户端(如客户端的协议层)已经接收到的该协议数据单元集合中的数据包；(2)客户端还未接收到的该协议数据单元集合中的数据包，也就是说，一旦确定需要对该协议数据单元集合进行丢弃处理，那么客户端(如客户端的协议层)在接收到该协议数据单元集合之后的数据包时，可以直接进行丢弃。
以PDCP实体为例，对上述用于判断是否丢包的方式3所对应的丢弃处理的过程进行进一步举例介绍。
示例性的，UE的PDCP实体接收到PDCP SDU之后，可以根据该PDCP SDU对应的协议数据单元集合序列号(假设为1)确定该PDCP SDU所属的协议数据单元集合为协议数据单元集合1，并且可以根据该PDCP SDU对应的PDU SN(假设为1)
确定该PDCP SDU为协议数据单元集合1的第一个数据包。之后，UE开启PDCP SDU对应的丢弃定时器(discard timer)，同时针对该协议数据单元集合1开启对应的丢包定时器。后续UE的PDCP实体会继续接收该协议数据单元集合1的其他PDCP SDU，PDCP实体也会为每一个PDCP SDU开启对应的丢弃定时器(discard timer)。
在一些实施例中，如果丢包定时器超时，且PDCP层存在该协议数据单元集合1的数据包未被丢弃，则对该协议数据单元集合1进行丢弃处理，直接丢弃该协议数据单元集合1中未丢弃的数据包。
在一些实施例中，在数据包确认传输的模式下(也即网络设备收到数据包后会向UE反馈)，如果协议数据单元集合1的所有数据包已经传输完成(包括PDCP实体已经丢弃的数据包或者成功传输的数据包)，则停止丢包定时器。在数据包无确认的模式下，如果协议数据单元集合1的所有数据包已经传输完成(传输至下一层或者丢弃)，则停止丢包定时器。
根据本申请提供的数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否有必要对剩余的数据包或者协议数据单元集合进行传输，在没有必要继续传输的情况下，对协议数据单元集合进行丢弃处理，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
示例性的，请参见图7，为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。该流程中用于判断是否丢包的方式可以对应于上述判断方式4，也即根据针对协议数据单元集合的丢包数量以及该协议数据单元集合的对应的丢包定时器综合确定是否丢弃该协议数据单元集合或其包括的数据包。该流程可以包括以下步骤：
S701，网络设备向UE发送丢包门限和丢包定时器。
其中，这里的网络设备向UE发送丢包门限和丢包定时器也可以理解为，网络设备向UE配置丢包门限和丢包定时器。其中，丢包门限和丢包定时器分别表示的含义可以参见上文图4实施例和图6实施例中的介绍，此处不再赘述。
需要说明的是，对于判断是否丢包的方式4，本申请图7实施例给出了由网络设备配置丢包门限的过程，但在实际应用中，该丢包门限还可以由UE的高层(如应用层或者传输层)进行配置，或者还可以由核心网设备进行配置，本申请实施例对此不作限定。
其中，该丢包门限和丢包定时器的配置粒度可以参见上文图4实施例和图6实施例中的介绍，此处不再赘述。
其中，网络设备向UE发送丢包门限和丢包定时器的方式，可以分别参见上文图4实施例和图6实施例中的介绍，此处不再赘述。
S702，当丢包定时器超时，且协议数据单元集合或数据包还未传输完成时；和/或，当该协议数据单元集合的丢包数量达到或超过丢包门限时，丢弃该协议数据单元集合或其包括的数据包。
需要说明的是，本申请实施例与上述图4实施例和图6实施例最主要的区别在于，UE会同时使用丢包计数器来统计协议数据单元集合中的丢包数量是否达到丢包门限，以及使用丢包计时器来统计在定时时间内协议数据单元集合的数据包是否传输完成这两种方式综合确定是否对协议数据单元集合进行丢弃处理。
在一些实施例中，当确定协议数据单元集合中的丢包数量达到或超过丢包门限，和/或确定丢包定时器超时时协议数据单元集合的数据包未传输完成，则可以丢弃该协议数据单元集合或其包括的数据包。或者，当确定协议数据单元集合中的丢包数量达到或超过丢包门限，和/或丢包定时器超时时，则可以丢弃该协议数据单元集合或其包括的数据包。也就是说，两个丢弃条件只需满足至少一个即可对协议数据单元集合进行丢弃处理。具体地，如果丢包定时器超时，但丢包计数器统计的计数值未达到丢包门限，则丢弃协议数据单元集合或其包括的数据包。如果丢包计数器统计的计数值达到或超过了丢包门限，但丢包定时器未超时，则也丢弃协议数据单元集合或其包括的数据包。如果丢包计数器统计的计数值达到了丢包门限，同时丢包定时器超时，则也丢弃协议数据单元集合或其包括的数据包。应理解，本申请实施例中的丢弃处理可以指丢弃该协议数据单元集合或其包括的数据包。
作为一个示例，以协议数据单元集合是PDU set，数据包是PDU为例，在该判断方式4对应的数据包丢弃的方法中，一种示例性的过程可以包括以下几种：(1)确定PDU set的丢包门限和丢包定时器，当PDU set的数据包丢弃数量(也即PDU set的丢包数量)达到(或超过)丢包门限后，则该PDU set的数据包可直接丢弃；或者当丢包定时器超时，则丢弃该PDU set还未丢弃的数据包；(2)当接收到该PDU set的第一个数据包之后，开启该丢包定时器；第一个数据包的确定方式包括接收到该PDU set内的start PDU(标识开始的数据包)，或者接收到属于该PDU set的第一个数据包；(3)在丢包定时器开启时间内，为PDU set维护一个丢包计数器，当该PDU set的一个数据包丢弃之后，该丢包计数器加1，当该丢包计数器超过丢包门限之后(定时器并未超时)，可直接丢弃该PDU set的还未丢弃的数据包；(4)当丢包定时器超时，但是丢包计数器并未超过丢包门限，丢弃该PDU set还未丢弃的数据包；(5)按照所述，当两个条件满足其中一个条件时，丢弃PDU set；或者必须同时满足两个条件，丢弃PDU set。
其中，关于本申请实施例实现的详细过程，如丢包门限的配置方式、丢包定时器的开启方式、丢弃处理的方式等等，可以参见上文图4实施例和图6实施例中的相关介绍，此处不再对此进行赘述。
需要说明的是，图7实施例仅以根据丢包定时器和丢包门限判断是否丢弃该协议数据单元集合或其包括的数据包为例，在另一些实施例中，还可以根据丢包定时器和丢包比例门限判断是否丢弃该协议数据单元集合或其包括的数据包，或者通过其它两种判断依据的组合来判断是否丢弃该协议数据单元集合或其包括的数据包，本申请实施例对此不作限定。
根据本申请提供的数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否有必要对剩余的数据包或者协议数据单元集合进行传输，在没有必要继续传输的情况下，对协议数据单元集合进行丢弃处理，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
示例性的，请参见图8，为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。该流程中用于判断是否丢包的方式可以对应于上述判断方式5，也即根据协议数据单元集合中具有特定属性信息的数据包是否丢弃，确定是否丢弃该协议数据单元集合或其包括的数据包，该特定属性与不允许丢弃关联。该流程可以包括以下步骤：
S801，网络设备向UE发送协议数据单元集合的第一属性信息，和/或者数据包对应的第二属性信息。
其中，第一属性信息与允许丢弃或不允许丢弃关联，第二属性信息与允许丢弃或不允许丢弃关联。这里的网络设备向UE发送协议数据单元集合的第一属性信息，和/或者数据包对应的第二属性信息也可以理解为，网络设备向UE配置协议数据单元集合的第一属性信息，和/或者数据包对应的第二属性信息。
在一些实施例中，网络设备配置协议数据单元集合和/或数据包具有与允许丢弃关联的属性信息的数据包的方式可以有多种，包括：(1)网络设备可以根据协议数据单元集合和/或数据包的优先级、重要性进行设置，比如将优先级较高或者重要性较高与不允许丢弃关联，也即将优先级较高或者重要性较高的数据包设置为不允许丢弃的协议数据单元集合和/或数据包；(2)网络设备还可以根据数据包在协议数据单元集合中的位置进行设置，比如将strat PDU与不允许丢弃关联，也即设置作为strat PDU的数据包为不允许丢弃的数据包；(3)网络设备还可以根据协议数据单元集合和/或数据包的序列号进行设置，比如将PDU SN为1～m(m为大于1的整数)与不允许丢弃关联，也即PDU SN为1～m的数据包设置为不允许丢弃的数据包，等等。类似地，网络设备也可以根据协议数据单元集合和/或数据包的优先级、重要性、序列号等设置协议数据单元集合中允许丢弃的协议数据单元集合和/或数据包。
可选地，当网络设备配置的是协议数据单元集合内允许丢弃的数据包时，那么协议数据单元集合中未被配置为允许丢弃的数据包可以被视为是不允许丢弃的数据包。比如，网络设备将协议数据单元集合中PDU SN为a至b(a和b均为大于或等于1的整数，且b大于a)的PDU配置为可丢弃的数据包，那么该协议数据单元集合中PDU SN不为a至b中任一序列号的其它PDU均可以被视为是不允许丢弃的数据包。
需要说明的是，对于判断方式5，本申请图8实施例给出了由网络设备配置丢包门限的过程，但在实际应用中，该丢包门限还可以由UE的高层(如应用层或者传输层)进行配置，或者还可以由核心网进行配置，本申请实施例对此不作限定。
S802，当UE确定协议数据单元集合内具有与不允许丢弃关联的属性信息的数据包发生丢弃之后，丢弃协议数据单元集合或其包括的数据包。
在一些实施例中，如果UE获取的为网络设备发送的可丢弃的数据包，那么当UE检测到某一个或多个不属于这些可丢弃的数据包发生丢弃，则可以对该协议数据单元集合进行丢弃处理。或者，如果UE获取的为网络设备发送的可丢弃的数据包，UE可以基于协议数据单元集合包括的所有PDU确定不可丢弃的数据包是哪些，然后当UE检测到某一个或多个不可丢弃的数据包发生丢弃时，则可以对该协议数据单元集合进行丢弃处理。再或者，如果EU获取的为网络设备发送的不可丢弃的数据包，则当UE检测到某一个或多个不可丢弃的数据包发生丢弃时，可以直接对该协议数据单元集合进行丢弃处理。
其中，UE对协议数据单元集合进行丢弃处理的方式可以参见上文图4实施例至图6实施例中的相关介绍，此处不再赘述。
根据本申请提供的数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否有必要对剩余的数据包或者协议数据单元集合进行传输，在没有必要继续传输的情况下，对协议数据单元集合进行丢弃处理，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
示例性的，请参见图9，为本申请实施例提供的又一种数据包丢弃的方法的示意性流程图。该流程中用于判断是否丢包的方式可以对应于上述判断方式6，也即对存在依赖性的协议数据单元集合，根据关联的协议数据单元集合是否丢包或丢包数量确定是否丢弃该协议数据单元集合或其包括的数据包。该流程可以包括以下步骤：
S901，网络设备向UE发送第一协议数据单元集合的依赖性标识。
其中，被该第一协议数据单元集合依赖的协议数据单元集合被记为第二协议数据单元集合。这里的网络设备向UE发送第一协议数据单元集合的依赖性标识也可以理解为，网络设备向UE配置第一协议数据单元集合的依赖性标识。
其中，这里的依赖关系也可以描述为依赖性，具有依赖关系的两个或多个协议数据单元集合可以具有相同的依赖关系标识，该所述依赖关系标识用于指示与所述协议数据单元集合相互依赖的其他所述协议数据单元集合。这里的第一协议数据单元集合和第二协议数据单元集合仅为互相区分，其中的第一、第二并不代表协议数据单元集合的顺序或者数量。具体地，第一协议数据单元集合和第二协议数据单元集合之间的依赖性可以理解为：第一协议数据单元集合的应用或作用依赖于第二协议数据单元集合的成功传输，当第二协议数据单元集合被成功传输时，第一协议数据单元集合才有传输的必要；而如果第二协议数据单元集合未被成功传输，则第一协议数据单元集合即使被成功传输，也不再具备被使用的价值。比如，以I帧和P帧为例，P帧的应用需要在I帧数据的基础上实现，也就是说，只有I帧被成功传输，P帧才有传输的必要，如果I帧未被成功传输，则P帧也没有继续被传输的必要。
可选地，第一协议数据单元集合依赖的第二协议数据单元集合可以有一个或者多个。当第一协议数据单元集合依赖的第二协议数据单元集合有多个时，任一个第二协议数据单元集合丢弃，则该第一协议数据单元集合都没有继续传输的必要，可以对该第一协议数据单元集合进行丢弃处理。
在一些实施例中，网络设备配置协议数据单元集合之间依赖性的方式可以有多种，比如包括：(1)对具有依赖性的协议数据单元集合配置依赖性标识(identification，ID)，配置有相同依赖性ID的协议数据单元集合相互依赖；(2)对某一协议数据单元集合(如第一协议数据单元集合)配置它依赖的协议数据单元集合(如第二协议数据单元集合)的标识，如在第一协议数据单元集合中携带第二协议数据单元集合的ID；(3)配置具有依赖关系的协议数据单元集合允许丢弃的数量。应理解，前述介绍的三种依赖性配置方式可以被同时配置于协议数据单元集合中，或者可以被部分地配置于协议数据单元集合中。本申请实施例对此不做限定。
S902，当UE确定第二协议数据单元集合发生丢包之后，对该第一协议数据单元集合进行丢弃处理。
在一些实施例中，UE可以根据接收到的第一协议数据单元集合的依赖关系(如依赖性标识)，确定该第一协议数据单元集合与第二协议数据单元集合之间具有依赖关系。之后，可以根据该依赖关系确定是否对第一协议数据单元集合进行丢弃处理。
示例性的，UE根据该依赖关系确定是否对第一协议数据单元集合进行丢弃处理的方式可以由多种，比如包括：(1)当UE确定第二协议数据单元集合已经丢弃(确定方式可以参见上文相关实施例)时，根据该第二协议数据单元集合的依赖性标识，对后续具有相依赖性标识的第一协议数据单元集合进行丢弃处理。(2)当UE接收到第一协议数据单元集合时，基于其对应的依赖性标识确定该第一协议数据单元集合依赖的是第二协议数据单元集合，如果确定该第二协议数据单元集合已经丢弃时，则对该第一协议数据单元集合进行丢弃处理。(3)基于第一协议数据单元集合的依赖性标识，判断与其具有相同依赖性标识的协议数据单元集合的丢包数量是否已经超过预设的门限，如果超过，则对该第一协议数据单元集合进行丢弃处理。
其中，UE对协议数据单元集合进行丢弃处理的方式可以参见上文图4实施例至图6实施例中的相关介绍，此处不再赘述。
根据本申请提供的数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否有必要对剩余的数据包或者协议数据单元集合进行传输，在没有必要继续传输的情况下，对协议数据单元集合进行丢弃处理，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
需要说明的是，当协议层(比如PDCP层)对某一协议数据单元集合进行丢弃处理之后，该协议层需要通知底层也对该协议数据单元集合的数据包进行丢弃。比如，PDCP层对协议数据单元集合进行丢弃处理之后，通知RLC层将该RLC层缓存的与该协议数据单元集合相关的数据包进行丢弃。
然而，在一些实施例中，如果该协议数据单元集合的数据包已经被RLC传输到下一层(MAC层)，那么RLC可以向MAC层通知该协议数据单元集合的属性信息(如协议数据单元集合的序列号、协议数据单元集合中PDU的序列号、协议数据单元集合中的开始PDU/结束PDU等等)，并且可以通知MAC层如果该协议数据单元集合相关的数据包还未在空口传输，那么无需对协议数据单元集合进行调度，或者无需等待该协议数据单元集合对应的调度资源。MAC可以响应于RLC层的通知，判断该协议数据单元集合是否已在空口传输，如果该协议数据单元集合还未在空口传输，则该MAC不再等待该协议数据单元集合对应的调度资源，或者不再对该协议数据单元集合进行调度。
在另一些实施例中，如果该协议数据单元集合的数据包已经被RLC传输到下一层(MAC层)，MAC层也可以不对相关的数据包执行丢弃。比如，在MAC层中的协议数据单元集合已经进行了空口传输时，则不再对该协议数据单元集合进行丢弃处理。
需要说明的是，上文图4至图9实施例所示的丢弃处理流程仅为示意性举例，在实际应用时，该丢弃处理流程还可以包括其他更多或更少的步骤，本申请实施例对此不作限定。
以下结合附图，对触发对协议数据单元集合进行丢弃处理的过程进行介绍。示例性的，如图10所示，为本申请实施例提供的一种数据包丢弃的方法中丢弃处理的触发流程示意图。该流程可以包括以下步骤：
S1001，网络设备向发送端设备发送协议数据单元集合的丢弃指示信息。
其中，这里的网络设备向UE发送协议数据单元集合的丢弃指示信息也可以理解为，网络设备向UE配置协议数据单元集合的丢弃指示信息。示例性的，网络设备配置的协议数据单元集合的丢弃指示信息，其对应的数据结构可以是枚举型或者布尔型。其中，枚举内容可以为true，比如可以表示为：PDUsetDiscard ENUMERATED{true}。但本申请实施例对丢弃指示信息的具体数据结构不做限定。
示例性的，该丢弃指示信息可以承载在网络设备向发送端设备发送的多种消息中，或者，也可以作为一个单独的消息发送至发送端设备。本申请实施例对此不作限定。
S1002，发送端设备接收协议数据单元集合或数据包的丢弃指示信息，触发协议数据单元集合或数据包的丢弃。
在一些实施例中，当发送端设备接收到丢弃指示信息时，可以响应于该丢弃指示信息，开启对协议数据单元集合进行丢弃处理的业务。当在协议数据单元集合传输过程中，确定该协议数据单元集合满足丢弃处理的条件时，可以触发协议层对该协议数据单元集合进行丢弃处理。其中，判断协议数据单元集合是否满足丢弃处理条件的方式以及对协议数据单元集合进行丢弃处理的过程，可以分别参见上文中的相关介绍，此处不再赘述。
根据本申请提供的数据包丢弃的方法，通过当在协议数据单元集合传输过程中发生丢包时，根据丢包的数量信息、数据包到达的时间信息和协议数据单元集合之间的依赖性等计算是否有必要对剩余的数据包或者协议数据单元集合进行传输，在没有必要继续传输的情况下，对协议数据单元集合进行丢弃处理，该方法能够避免对无效数据包或者协议数据单元集合的传输，从而节省空口资源。
需要说明的是，上文图10实施例所示的丢弃处理流程仅为示意性举例，在实际应用时，该丢弃处理流程还可以包括其他更多或更少的步骤，本申请实施例对此不作限定。
示例性的，如图11所示，为本申请实施例提供的一种数据包丢弃的方法的示意性流程图。该流程的执行主体可以是发送端设备，具体可以包括以下步骤：
S1101，按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，所述预设的判断方式采用的判断依据包括所述协议数据单元集合对应的丢包数量、所述协议数据单元集合的丢包定时器、所述协议数据单元集合对应的第一属性信息、所述数据包对应的第二属性信息、所述协议数据单元集合与其他协议数据单元集合之间的依赖关系中的至少一项；所述属性信息与允许丢弃或者不允许丢弃关联，所述协议数据单元集合包括一个或多个所述数据包。
在一种实现方式中，数据包可以包括PDU数据包或者SDU数据包，但本申请对此不作限定。
在一种实现方式中，这里的丢弃协议数据单元集合或者所述协议数据单元集合包括的数据，可以包括：丢弃所述协议数据单元集合中未丢弃的数据包。其中，这里未丢弃的数据包可以指发送端已经接收到但还未丢弃的数据包；或者，可以指还未接收到的该协议数据单元集合中的数据包，也就是说，如果确定该协议数据单元集合的数据包需要丢弃之后，则接收到该协议数据单元集合的数据包之后可直接进行丢弃。
在一些实施例中，协议数据单元集合可以对应于PDU set，但并不仅限于此。
在一些实施例中，允许丢弃是指协议数据单元集合或者数据包可以允许丢弃，不会导致对该协议数据单元集合或者该协议数据单元集合中的数据包进行丢弃处理。不允许丢弃是指协议数据单元集合或者数据包不允许丢弃，如果丢弃则会导致对该协议数据单元集合或者该协议数据单元集合中的数据包进行丢弃处理。
在一些实施例中，属性信息与允许丢弃或者不允许丢弃关联是指，具有该属性信息的数据包或协议数据单元集合属于允许丢弃的数据包或协议数据单元集合的类型；或者具有该属性信息的数据包或协议数据单元集合属于不允许丢弃的数据包或协议数据单元集合的类型。比如，高优先级属性与不允许丢弃关联，那么优先级高的数据包协议数据单元集合则属于不允许丢弃的数据包或协议数据单元集合，如果发生丢弃，则需要丢弃，会对相应的协议数据单元集合或协议数据单元集合中的其它数据包进行丢弃。
在一些实施例中，发送端可以是用户设备，但并不仅限于此。
在一些实施例中，按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包也可以指，按照预设的判断方式判断协议数据单元集合或者所述协议数据单元集合包括的数据包是否满足丢弃条件，当满足该丢弃条件时，则丢弃所述协议数据单元集合或者所述协议数据单元集合包括的数据包。
S1102，若按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述第一属性信息包括所述协议数据单元集合对应的序列号、所述协议数据单元集合包括的所述数据包的总数量、所述协议数据单元集合的重要性等级、所述协议数据单元集合的优先级、所述协议数据单元集合的依赖关系中的至少一项；所述第二属性信息包括所述数据包对应的数据包序列号、所述数据包在所述协议数据单元集合中的位置、所述数据包的重要性等级、所述数据包的优先级中的至少一项。
作为一个实施例，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量时，所述方法具体包括：获取所述协议数据单元集合对应的丢包门限；获取所述协议数据单元集合对应的所述丢包数量；若所述丢包数量达到或超过所述丢包门限，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述获取所述协议数据单元集合对应的丢包门限，具体包括：接收接收端发送的第一配置信息，所述第一配置信息用于指示所述丢包门限，所述接收端用于接收所述数据包；或者，获取所述发送端自身预先配置的所述丢包门限；或者，通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包门限；或者，接收核心网发送的第二配置信息，所述第二配置信息用于指示所述丢包门限。
其中，在一种实现方式中，发送端自身预先配置的所述丢包比例门限，可以是静态配置的丢包比例门限；发送端高层发送的所述丢包门限，可以是动态配置的丢包比例门限。
作为一个实施例，当由所述发送端自身配置所述丢包门限时，所述方法还包括：以协议层实体为粒度配置所述丢包门限；或者，以数据无线承载DRB为粒度配置所述丢包门限；或者，以所述协议数据单元集合为粒度配置所述丢包门限；或者，以所述协议数据单元集合的类型为粒度配置所述丢包门限，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中的至少一项。
作为一个实施例，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量时，所述方法具体包括：获取所述协议数据单元集合对应的丢包比例门限；获取所述协议数据单元集合对应的所述丢包数量；根据所述丢包数量与所述协议数据单元集合包括的所述数据包的总数量的比值获取所述协议数据单元集合对应的丢包比例；若所述丢包比例达到或超过所述丢包比例门限，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述获取所述协议数据单元集合对应的丢包比例门限，具体包括：接收接收端发送的第三配置信息，所述第三配置信息用于指示所述丢包比例门限，所述接收端用于接收所述数据包；或者，获取所述发送端自身预先配置的所述丢包比例门限；或者，通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包比例门限；或者，接收核心网发送的第四配置信息，所述第四配置信息用于指示所述丢包比例门限。
作为一个实施例，当由所述发送端自身配置所述丢包比例门限时，所述方法还包括：以协议层实体为粒度配置所述丢包比例门限；或者，以DRB为粒度配置所述丢包比例门限；或者，以所述协议数据单元集合为粒度配置所述丢包比例门限；或者，以所述协议数据单元集合的类型为粒度配置所述丢包比例门限，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中至少一项。
作为一个实施例，所述获取所述协议数据单元集合对应的所述丢包数量，具体包括：设置丢包计数器，所述丢包计数器用于对所述协议数据单元集合中丢弃的所述数据包的数量进行计数；每获取一个所述协议数据单元集合中的所述数据包丢弃，所述丢包计数器的计数值加1；根据所述丢包计数器的计数值获取所述协议数据单元集合对应的所述丢包数量。
作为一个实施例，当所述丢包计数器对所述协议数据单元集合中丢弃的所述数据包的数量进行计数时，所述方法还包括：所述丢包计数器对成功传输的且丢弃的所述数据包不进行计数。
作为一个实施例，所述方法还包括：当丢弃所述协议数据单元集合或者所述数据包时，对所述丢包计数器进行释放或清零；或者，当所述协议数据单元集合对应的丢包数量未达到或者未超过所述丢包门限，且所述协议数据单元集合和/或所述数据包传输完成时，对所述丢包计数器进行释放或清零；或者，当所述协议数据单元集合对应的丢包数量与所述协议数据单元集合包括的数据包的总数量的比值未达到或者未超过所述丢包比例门限，且所述协议数据单元集合和/或所述数据包传输完成时，对所述丢包计数器进行释放或清零；或者，当所述计数器的计数值与所述协议数据单元集合包括的所述数据包的总数量的比值达到或超过对应的所述丢包比例门限时，对所述丢包计数器进行释放或清零；或者，当所述计数器的计数值达到或超过所述丢包门限时，对所述丢包计数器进行释放或清零。
作为一个实施例，所述方法还包括：当存在所述数据包传输成功时，设置所述丢包计数器。
作为一个实施例，当所述预设的判断方式采用的判断依据为所述协议数据单元集合的丢包定时器时，所述方法具体包括：获取所述协议数据单元集合对应的丢包定时器；当所述丢包定时器超时时，则丢弃所述协议数据单元集合或者所述数据包；或者，当所述丢包定时器超时时，若所述协议数据单元集合或所述数据包未传输完成，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述方法还包括：当接收到所述协议数据单元集合中的第一个所述数据包时，开启所述丢包定时器。
作为一个实施例，所述方法还包括：当所述协议数据单元集合的传输时间超过所述丢包定时器的丢包定时时间时，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述获取所述协议数据单元集合对应的丢包定时器，具体包括：接收接收端发送的第五配置信息，所述第五配置信息用于指示所述丢包定时器，所述接收端用于接收所述数据包；或者，获取所述发送端自身预先配置的所述丢包定时器；或者，通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包定时器；或者，接收核心网发送的第六配置信息，所述第六配置信息用于指示所述丢包定时器。
作为一个实施例，所述方法还包括：当丢弃所述协议数据单元集合或者所述数据包时，对所述丢包定时器进行释放或清零；或者，当所述丢包定时器未超时，且所述协议数据单元集合和/或数据包传输完成时，对所述丢包定时器进行释放或清零；或者，当所述丢包定时器超时时，对所述丢包定时器进行释放或清零。
作为一个实施例，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量和所述丢包定时器时，所述方法具体包括：获取所述协议数据单元集合对应的丢包门限，以及所述协议数据单元集合对应的丢包定时器；获取所述协议数据单元集合对应的所述丢包数量；若所述丢包数量超过丢包门限，和/或若所述丢包定时器超时时，所述协议数据单元集合或者所述数据包未传输完成，则丢弃所述协议数据单元集合或者所述数据包；或者，若所述丢包数量超过丢包门限，和/或若所述丢包定时器超时时，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述协议数据单元集合或所述数据包未传输完成，具体包括：所述发送端存在所述协议数据单元集合中的所述数据包。
作为一个实施例，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的第一属性信息和/或所述数据包对应的第二属性信息时，所述方法具体包括：当所述协议数据单元集合对应的第一属性信息与所述不允许丢弃关联时，若具有所述第一属性信息的所述协议数据单元集合丢弃，则丢弃所述协议数据单元集合或者所述数据包；或者，当所述数据包对应的第二属性信息与所述不允许丢弃关联时，若具有所述第二属性信息的所述数据包丢弃，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述方法还包括：获取接收端发送的第七配置信息，所述第七配置信息用于指示所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息，所述接收端用于接收所述数据包；或者，获取所述发送端自身预先配置的所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息；或者，通过所述发送端自身的协议层接收所述发送端高层发送的所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息；或者，接收核心网发送的第八配置信息，所述第八配置信息用于指示所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息。
作为一个实施例，当所述预设的判断方式采用的判断依据为所述协议数据单元集合与其他协议数据单元集合之间的依赖关系时，所述方法具体包括：获取第一协议数据单元集合与至少一个第二协议数据单元集合具有依赖关系；基于所述依赖关系，若获取所述第二协议数据单元集合发生丢弃，则丢弃所述第一协议数据单元集合或者所述第一协议数据单元集合包括的所述数据包；或者，基于所述依赖关系，若获取发生丢弃的所述第二协议数据单元集合的数量达到预设阈值，则丢弃所述第一协议数据单元集合或者所述第一协议数据单元集合包括的所述数据包。
作为一个实施例，所述获取与第一协议数据单元集合具有依赖关系的至少一个第二协议数据单元集合，具体包括：接收接收端发送的第九配置信息，所述第九配置信息用于指示依赖关系标识，所述接收端用于接收所述发送端传输的所述数据包；或者，获取所述发送端自身预先配置的依赖关系标识；或者，通过所述发送端自身的协议层接收所述发送端高层发送的依赖关系标识；或者，接收核心网发送的第十配置信息，所述第十配置信息用于指示依赖关系标识；其中，所述依赖关系标识用于指示与所述协议数据单元集合相互依赖的其他所述协议数据单元集合。
作为一个实施例，所述方法还包括：接收所述接收端或者所述发送端高层发送的丢包指示信息，所述丢包指示信息用于指示所述发送端触发协议数据单元集合的丢弃或者所述数据包的丢弃；触发协议层的所述协议数据单元集合丢弃或者所述数据包丢弃。
作为一个实施例，所述若按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，则丢弃所述协议数据单元集合或者所述协议数据单元集合包括的数据包，具体包括：若所述发送端设备的协议层按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包时，则丢弃所述协议数据单元集合或者所述数据包。
作为一个实施例，所述方法还包括：当所述发送端设备的协议层实体判断丢弃协议数据单元集合或者所述数据包时，如果所述协议数据单元集合的所述数据包已经被传输至所述协议层对应的下一层，则所述协议层实体向所述下一层的协议层实体发送通知消息，所述通知消息用于指示所述下一层的协议层实体丢弃所述数据包。
基于同样的技术构思，本申请实施例还提供了一种数据包丢弃的方法，应用于接收端，所述方法包括：向发送端发送所述配置信息，使得所述发送端依据所述配置信息中的至少一项，按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包；所述配置信息包括丢包门限、丢包比例门限、丢包定时器、协议数据单元集合对应的所述第一属性信息、数据包对应的第二属性信息、依赖关系标识中的至少一项。
作为一个示例，所述方法还包括：以协议层实体为粒度配置所述配置信息；或者，以DRB为粒度配置所述配置信息；或者，以所述协议数据单元集合为粒度配置所述配置信息；或者，以所述协议数据单元集合的类型为粒度配置所述配置信息，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中至少一项。
作为一个示例，所述配置信息的数据结构为序列结构。
基于同样的技术构思，本申请实施例还提供了一种数据包丢弃的方法，应用于发送端，所述方法包括：接收所述接收端发送的丢包指示信息，所述丢包指示信息用于指示所述发送端触发协议数据单元集合的丢弃或者所述数据包的丢弃；触发协议层的所述协议数据单元集合或者所述协议数据单元集合中数据包丢弃，所述协议数据单元集合包括至少一个所述数据包。
基于同样的技术构思，本申请实施例还提供了一种数据包丢弃的方法，应用于发送端，所述方法包括：接收所述接收端发送的丢包指示信息，所述丢包指示信息用于指示所述发送端触发协议数据单元集合的丢弃或者所述数据包的丢弃；触发协议层执行如上述任一实施例所述的数据包丢弃的方法。
基于同样的技术构思，本申请实施例还提供了一种发送端设备，包括一个或多个处理器；一个或多个存储器；所述一个或多个存储器存储有一个或多个计算机程序，所述一个或多个计算机程序包括指令，当所述指令被所述一个或多个处理器执行时，使得发送端设备执行上述任一个方法中的一个或多个步骤。
基于同样的技术构思，本申请实施例还提供了一种通信系统，包括发送端设备和接收端设备，所述发送端设备用于执行上述任一个方法中的一个或多个步骤，所述接收端用于接收所述发送端传输的所述协议数据单元集合中的所述数据包。
基于同样的技术构思，本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机可执行程序指令，所述计算机可执行程序指令在被计算机上运行时，使得计算机或处理器执行上述任一个方法中的一个或多个步骤。
基于同样的技术构思，本申请实施例还提供了一种包含指令的计算机程序产品，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机或处理器执行上述任一个方法中的一个或多个步骤。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其它可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来指令相关的硬件完成，该程序可存储于计算机可读取存储介质中，该程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：ROM或随机存储记忆体RAM、磁碟或者光盘等各种可存储程序代码的介质。
以上所述，仅为本申请实施例的具体实施方式，但本申请实施例的保护范围并不局限于此，任何在本申请实施例揭露的技术范围内的变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应以所述权利要求的保护范围为准。

Claims (35)

  1. 一种数据包丢弃的方法，其特征在于，应用于发送端，所述方法包括：
    按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，所述预设的判断方式采用的判断依据包括所述协议数据单元集合对应的丢包数量、所述协议数据单元集合的丢包定时器、所述协议数据单元集合对应的第一属性信息、所述数据包对应的第二属性信息、所述协议数据单元集合与其他协议数据单元集合之间的依赖关系中的至少一项；所述属性信息与允许丢弃或者不允许丢弃关联，所述协议数据单元集合包括一个或多个所述数据包；
    若按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，则丢弃所述协议数据单元集合或者所述数据包。
  2. 根据权利要求1所述的方法，其特征在于，所述第一属性信息包括所述协议数据单元集合对应的序列号、所述协议数据单元集合包括的所述数据包的总数量、所述协议数据单元集合的重要性等级、所述协议数据单元集合的优先级、所述协议数据单元集合的依赖关系中的至少一项；
    所述第二属性信息包括所述数据包对应的数据包序列号、所述数据包在所述协议数据单元集合中的位置、所述数据包的重要性等级、所述数据包的优先级中的至少一项。
  3. 根据权利要求1所述的方法，其特征在于，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量时，所述方法具体包括：
    获取所述协议数据单元集合对应的丢包门限；
    获取所述协议数据单元集合对应的所述丢包数量；
    若所述丢包数量达到或超过所述丢包门限，则丢弃所述协议数据单元集合或者所述数据包。
  4. 根据权利要求3所述的方法，其特征在于，所述获取所述协议数据单元集合对应的丢包门限，具体包括：
    接收接收端发送的第一配置信息，所述第一配置信息用于指示所述丢包门限，所述接收端用于接收所述数据包；或者，
    获取所述发送端自身预先配置的所述丢包门限；或者，
    通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包门限；或者，
    接收核心网发送的第二配置信息，所述第二配置信息用于指示所述丢包门限。
  5. 根据权利要求3或4所述的方法，其特征在于，当由所述发送端自身配置所述丢包门限时，所述方法还包括：
    以协议层实体为粒度配置所述丢包门限；或者，
    以数据无线承载DRB为粒度配置所述丢包门限；或者，
    以所述协议数据单元集合为粒度配置所述丢包门限；或者，
    以所述协议数据单元集合的类型为粒度配置所述丢包门限，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中的至少一项。
  6. 根据权利要求1所述的方法，其特征在于，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量时，所述方法具体包括：
    获取所述协议数据单元集合对应的丢包比例门限；
    获取所述协议数据单元集合对应的所述丢包数量；
    根据所述丢包数量与所述协议数据单元集合包括的所述数据包的总数量的比值获取所述协议数据单元集合对应的丢包比例；
    若所述丢包比例达到或超过所述丢包比例门限，则丢弃所述协议数据单元集合或者所述数据包。
  7. 根据权利要求6所述的方法，其特征在于，所述获取所述协议数据单元集合对应的丢包比例门限，具体包括：
    接收接收端发送的第三配置信息，所述第三配置信息用于指示所述丢包比例门限，所述接收端用于接收所述数据包；或者，
    获取所述发送端自身预先配置的所述丢包比例门限；或者，
    通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包比例门限；或者，
    接收核心网发送的第四配置信息，所述第四配置信息用于指示所述丢包比例门限。
  8. 根据权利要求6或7所述的方法，其特征在于，当由所述发送端自身配置所述丢包比例门限时，所述方法还包括：
    以协议层实体为粒度配置所述丢包比例门限；或者，
    以DRB为粒度配置所述丢包比例门限；或者，
    以所述协议数据单元集合为粒度配置所述丢包比例门限；或者，
    以所述协议数据单元集合的类型为粒度配置所述丢包比例门限，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中至少一项。
  9. 根据权利要求3-8中任一项所述的方法，其特征在于，所述获取所述协议数据单元集合对应的所述丢包数量，具体包括：
    设置丢包计数器，所述丢包计数器用于对所述协议数据单元集合中丢弃的所述数据包的数量进行计数；
    每获取一个所述协议数据单元集合中的所述数据包丢弃，所述丢包计数器的计数值加1；
    根据所述丢包计数器的计数值获取所述协议数据单元集合对应的所述丢包数量。
  10. 根据权利要求9所述的方法，其特征在于，当所述丢包计数器对所述协议数据单元集合中丢弃的所述数据包的数量进行计数时，所述方法还包括：
    所述丢包计数器对成功传输的且丢弃的所述数据包不进行计数。
  11. 根据权利要求9或10所述的方法，其特征在于，所述方法还包括：
    当丢弃所述协议数据单元集合或者所述数据包时，对所述丢包计数器进行释放或清零；或者，
    当所述协议数据单元集合对应的丢包数量未达到或者未超过所述丢包门限，且所述协议数据单元集合和/或所述数据包传输完成时，对所述丢包计数器进行释放或清零；或者，
    当所述协议数据单元集合对应的丢包数量与所述协议数据单元集合包括的数据包的总数量的比值未达到或者未超过所述丢包比例门限，且所述协议数据单元集合和/或所述数据包传输完成时，对所述丢包计数器进行释放或清零；或者，
    当所述计数器的计数值与所述协议数据单元集合包括的所述数据包的总数量的比值达到或超过对应的所述丢包比例门限时，对所述丢包计数器进行释放或清零；或者，
    当所述计数器的计数值达到或超过所述丢包门限时，对所述丢包计数器进行释放或清零。
  12. 根据权利要求9-11中任一项所述的方法，其特征在于，所述方法还包括：
    当存在所述数据包传输成功时，设置所述丢包计数器。
  13. 根据权利要求1或2所述的方法，其特征在于，当所述预设的判断方式采用的判断依据为所述协议数据单元集合的丢包定时器时，所述方法具体包括：
    获取所述协议数据单元集合对应的丢包定时器；
    当所述丢包定时器超时时，则丢弃所述协议数据单元集合或者所述数据包；或者，
    当所述丢包定时器超时时，若所述协议数据单元集合或所述数据包未传输完成，则丢弃所述协议数据单元集合或者所述数据包。
  14. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    当接收到所述协议数据单元集合中的第一个所述数据包时，开启所述丢包定时器。
  15. 根据权利要求13或14所述的方法，其特征在于，所述方法还包括：
    当所述协议数据单元集合的传输时间超过所述丢包定时器的丢包定时时间时，则丢弃所述协议数据单元集合或者所述数据包。
  16. 根据权利要求13-15中任一项所述的方法，其特征在于，所述获取所述协议数据单元集合对应的丢包定时器，具体包括：
    接收接收端发送的第五配置信息，所述第五配置信息用于指示所述丢包定时器，所述接收端用于接收所述数据包；或者，
    获取所述发送端自身预先配置的所述丢包定时器；或者，
    通过所述发送端自身的协议层接收所述发送端高层发送的所述丢包定时器；或者，
    接收核心网发送的第六配置信息，所述第六配置信息用于指示所述丢包定时器。
  17. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    当丢弃所述协议数据单元集合或者所述数据包时，对所述丢包定时器进行释放或清零；或者，
    当所述丢包定时器未超时，且所述协议数据单元集合和/或数据包传输完成时，对所述丢包定时器进行释放或清零；或者，
    当所述丢包定时器超时时，对所述丢包定时器进行释放或清零。
  18. 根据权利要求1或2所述的方法，其特征在于，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的丢包数量和所述丢包定时器时，所述方法具体包括：
    获取所述协议数据单元集合对应的丢包门限，以及所述协议数据单元集合对应的丢包定时器；
    获取所述协议数据单元集合对应的所述丢包数量；
    若所述丢包数量超过丢包门限，和/或若所述丢包定时器超时时，所述协议数据单元集合或者所述数据包未传输完成，则丢弃所述协议数据单元集合或者所述数据包；或者，
    若所述丢包数量超过丢包门限，和/或若所述丢包定时器超时时，则丢弃所述协议数据单元集合或者所述数据包。
  19. 根据权利要求13-18中任一项所述的方法，其特征在于，所述协议数据单元集合或所述数据包未传输完成，具体包括：
    所述发送端存在所述协议数据单元集合中的所述数据包。
  20. 根据权利要求1或2所述的方法，其特征在于，当所述预设的判断方式采用的判断依据为所述协议数据单元集合对应的第一属性信息和/或所述数据包对应的第二属性信息时，所述方法具体包括：
    当所述协议数据单元集合对应的第一属性信息与所述不允许丢弃关联时，若具有所述第一属性信息的所述协议数据单元集合丢弃，则丢弃所述协议数据单元集合或者所述数据包；或者，
    当所述数据包对应的第二属性信息与所述不允许丢弃关联时，若具有所述第二属性信息的所述数据包丢弃，则丢弃所述协议数据单元集合或者所述数据包。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    获取接收端发送的第七配置信息，所述第七配置信息用于指示所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息，所述接收端用于接收所述数据包；或者，
    获取所述发送端自身预先配置的所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息；或者，
    通过所述发送端自身的协议层接收所述发送端高层发送的所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息；或者，
    接收核心网发送的第八配置信息，所述第八配置信息用于指示所述协议数据单元集合对应的所述第一属性信息，和/或所述数据包对应的第二属性信息。
  22. 根据权利要求1或2所述的方法，其特征在于，当所述预设的判断方式采用的判断依据为所述协议数据单元集合与其他协议数据单元集合之间的依赖关系时，所述方法具体包括：
    获取第一协议数据单元集合与至少一个第二协议数据单元集合具有依赖关系；
    基于所述依赖关系，若获取所述第二协议数据单元集合发生丢弃，则丢弃所述第一协议数据单元集合或者所述第一协议数据单元集合包括的所述数据包；或者，
    基于所述依赖关系，若获取发生丢弃的所述第二协议数据单元集合的数量达到预设阈值，则丢弃所述第一协议数据单元集合或者所述第一协议数据单元集合包括的所述数据包。
  23. 根据权利要求22所述的方法，其特征在于，所述获取与第一协议数据单元集合具有依赖关系的至少一个第二协议数据单元集合，具体包括：
    接收接收端发送的第九配置信息，所述第九配置信息用于指示依赖关系标识，所述接收端用于接收所述发送端传输的所述数据包；或者，
    获取所述发送端自身预先配置的依赖关系标识；或者，
    通过所述发送端自身的协议层接收所述发送端高层发送的依赖关系标识；或者，
    接收核心网发送的第十配置信息，所述第十配置信息用于指示依赖关系标识；其中，所述依赖关系标识用于指示与所述协议数据单元集合相互依赖的其他所述协议数据单元集合。
  24. 根据权利要求1-23中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述接收端或者所述发送端高层发送的丢包指示信息，所述丢包指示信息用于指示所述发送端触发协议数据单元集合的丢弃或者所述数据包的丢弃；
    触发协议层的所述协议数据单元集合丢弃或者所述数据包丢弃。
  25. 根据权利要求1-24中任一项所述的方法，其特征在于，所述若按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包，则丢弃所述协议数据单元集合或者所述协议数据单元集合包括的数据包，具体包括：
    若所述发送端设备的协议层按照预设的判断方式判断丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包时，则丢弃所述协议数据单元集合或者所述数据包。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    当所述发送端设备的协议层实体判断丢弃协议数据单元集合或者所述数据包时，如果所述协议数据单元集合的所述数据包已经被传输至所述协议层对应的下一层，则所述协议层实体向所述下一层的协议层实体发送通知消息，所述通知消息用于指示所述下一层的协议层实体丢弃所述数据包。
  27. 一种数据包丢弃的方法，其特征在于，应用于发送端，所述方法包括：
    接收所述接收端或者所述发送端高层发送的丢包指示信息，所述丢包指示信息用于指示协议数据单元集合的丢弃或者所述协议数据单元集合包括的数据包的丢弃；
    触发所述协议数据单元集合丢弃或者所述数据包丢弃，所述协议数据单元集合包括至少一个所述数据包。
  28. 一种数据包丢弃的方法，其特征在于，应用于发送端，所述方法包括：
    接收所述接收端发送的丢包指示信息，所述丢包指示信息用于指示协议数据单元集合的丢弃或者所述协议数据单元集合包括的数据包的丢弃；
    触发协议层执行如权利要求1-26中任一项所述的数据包丢弃的方法。
  29. 一种数据包丢弃的方法，其特征在于，应用于接收端，所述方法包括：
    向发送端发送所述配置信息，使得所述发送端依据所述配置信息中的至少一项，按照预设的判断方式判断是否丢弃协议数据单元集合或者所述协议数据单元集合包括的数据包；所述配置信息包括丢包门限、丢包比例门限、丢包定时器、协议数据单元集合对应的所述第一属性信息、数据包对应的第二属性信息、依赖关系标识中的至少一项。
  30. 根据权利要求29所述的方法，其特征在于，所述方法还包括：
    以协议层实体为粒度配置所述配置信息；或者，
    以DRB为粒度配置所述配置信息；或者，
    以所述协议数据单元集合为粒度配置所述配置信息；或者，
    以所述协议数据单元集合的类型为粒度配置所述配置信息，其中，所述协议数据单元集合的类型为所述协议数据单元集合的优先级、所述协议数据单元集合的重要性等级、所述协议数据单元集合的序列号中至少一项。
  31. 根据权利要求29或30所述的方法，其特征在于，所述配置信息的数据结构为序列结构。
  32. 一种发送端设备，其特征在于，包括：
    一个或多个处理器；
    一个或多个存储器；
    所述一个或多个存储器存储有一个或多个计算机程序，所述一个或多个计算机程序包括指令，当所述指令被所述一个或多个处理器执行时，使得所述发送端设备执行如权利要求1至28中任一项所述的方法。
  33. 一种接收端设备，其特征在于，包括：
    一个或多个处理器；
    一个或多个存储器；
    所述一个或多个存储器存储有一个或多个计算机程序，所述一个或多个计算机程序包括指令，当所述指令被所述一个或多个处理器执行时，使得所述接收端设备执行如权利要求29-30中任一项所述的方法。
  34. 一种通信系统，其特征在于，包括发送端设备和接收端设备，所述发送端设备用于执行如权利要求1至28中任一项所述的方法，所述接收端用于执行如权利要求29-31中任一项所述的方法。
  35. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有计算机可执行程序指令，所述计算机可执行程序指令在被计算机上运行时，使所述计算机执行如权利要求1至31中任一项所述的方法。
PCT/CN2023/116090 2022-09-26 2023-08-31 一种数据包丢弃的方法及相关设备 WO2024066898A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211176858.4 2022-09-26
CN202211176858.4A CN117812637A (zh) 2022-09-26 2022-09-26 一种数据包丢弃的方法及相关设备

Publications (1)

Publication Number Publication Date
WO2024066898A1 true WO2024066898A1 (zh) 2024-04-04

Family

ID=90428639

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/116090 WO2024066898A1 (zh) 2022-09-26 2023-08-31 一种数据包丢弃的方法及相关设备

Country Status (2)

Country Link
CN (1) CN117812637A (zh)
WO (1) WO2024066898A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008133577A1 (en) * 2007-04-27 2008-11-06 Telefonaktiebolaget Lm Ericsson (Publ) Method for selectively discarding data units in a radio communication system
WO2018176480A1 (zh) * 2017-04-01 2018-10-04 华为技术有限公司 数据处理方法和设备
WO2021031019A1 (zh) * 2019-08-16 2021-02-25 Oppo广东移动通信有限公司 数据包的删除方法、设备及存储介质
WO2022081073A1 (en) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Packet transmission and reception in a wireless communication network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008133577A1 (en) * 2007-04-27 2008-11-06 Telefonaktiebolaget Lm Ericsson (Publ) Method for selectively discarding data units in a radio communication system
WO2018176480A1 (zh) * 2017-04-01 2018-10-04 华为技术有限公司 数据处理方法和设备
WO2021031019A1 (zh) * 2019-08-16 2021-02-25 Oppo广东移动通信有限公司 数据包的删除方法、设备及存储介质
WO2022081073A1 (en) * 2020-10-16 2022-04-21 Telefonaktiebolaget Lm Ericsson (Publ) Packet transmission and reception in a wireless communication network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on XR-specific capacity enhancements techniques", 3GPP DRAFT; R1-2203132, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220509 - 20220520, 29 April 2022 (2022-04-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052143950 *

Also Published As

Publication number Publication date
CN117812637A (zh) 2024-04-02

Similar Documents

Publication Publication Date Title
CN107483710B (zh) 在无线通信系统中为终端提供服务的方法和设备
WO2018094872A1 (zh) sidelink资源调度方法、装置和系统
WO2018202037A1 (zh) 传输数据的方法、终端设备和网络设备
CN111818630B (zh) 状态变量维护方法、装置及用户设备
WO2021062797A1 (zh) 配置方法和装置
CN113923712A (zh) 数据处理的方法及装置
WO2022075912A1 (en) Group pdcp discard timer for low-latency services
WO2022000336A1 (zh) 信息传输方法、装置、通信设备及存储介质
EP3982611B1 (en) Data processing method and device, and terminal
WO2020192776A1 (zh) 通信方法和装置
WO2023207846A1 (zh) 通信方法和装置
CN112312588B (zh) 用于传输数据的方法、终端设备和网络设备
WO2024066898A1 (zh) 一种数据包丢弃的方法及相关设备
WO2022151878A1 (zh) 上行资源预申请的方法及相关设备
WO2022063187A1 (zh) 一种通信方法和装置
EP4109986A1 (en) Data transmission method and apparatus, and communication device
CN108886766B (zh) 一种控制信息的传输方法及装置
WO2018103016A1 (zh) 数据处理方法和设备
CN111654360A (zh) 一种非激活态的切换处理方法及通信设备
WO2023066106A1 (zh) 数据丢弃方法、装置、终端及网络侧设备
WO2023226662A1 (zh) 通信方法、通信装置和通信系统
WO2023134410A1 (zh) 通信方法、装置及系统
WO2021190277A1 (zh) 一种上行数据的分流方法及终端
WO2023202164A1 (zh) 通信方法、通信装置和通信系统
WO2023093696A1 (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: 23870138

Country of ref document: EP

Kind code of ref document: A1