Methods and apparatus for handling data unit transmission problems

Abstract

This disclosure describes methods, systems, and apparatus for handling data unit transmission problems. One method includes a first communication node determining that at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) has been discarded; and the first communication node sending a first message indicating that at least one PDCP PDU has been discarded to a second communication node, such that the second communication node is configured to ignore at least one discarded PDCP PDU when performing PDCP reordering. Another method includes the second communication node receiving a first message indicating that at least one PDCP PDU has been discarded from the first communication node; and the second communication node determining that at least one discarded PDCP PDU will be ignored when performing PDCP reordering.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication. In particular, this disclosure relates to methods and apparatus for addressing data unit transmission problems. Background Technology

[0002] Wireless communication technology is propelling the world towards an increasingly connected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to base stations). Next-generation networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the requirements of various industries and users.

[0003] In some wireless communication systems, when data units (e.g., radio link control (RLC) protocol data units (PDUs)) are lost or delayed, the receiving RLC entity may wait for the lost or delayed PDU, which in some cases can lead to transmission delays or other problems, resulting in poor transmission rates and poor performance.

[0004] This disclosure describes various embodiments for handling data unit transmission problems, solving at least one of the difficulties / problems discussed in this disclosure, thereby improving the efficiency of data unit transmission and enhancing telecommunications performance. Summary of the Invention

[0005] This document relates to methods, systems, and apparatus for wireless communication, and more specifically, for addressing data unit transmission problems, which facilitates the efficient utilization of data transmission resources, improves the efficiency of telecommunications resource utilization, and / or enhances the performance of wireless communication.

[0006] In one embodiment, this disclosure describes a method for wireless communication. The method includes a first communication node determining that at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) has been discarded; and the first communication node sending a first message to a second communication node indicating that at least one PDCP PDU has been discarded, such that the second communication node is configured to ignore at least one discarded PDCP PDU when performing PDCP reordering.

[0007] In another embodiment, this disclosure describes another method for wireless communication. The method includes a second communication node receiving from a first communication node a first message indicating that at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) has been discarded; and the second communication node determining that at least one discarded PDCP PDU should be ignored when performing PDCP reordering.

[0008] In some other embodiments, an apparatus for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to perform the methods described above.

[0009] In some other embodiments, a device for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, it is configured to perform the methods described above.

[0010] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above. The computer-readable medium may be a non-transitory computer-readable medium.

[0011] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0012] Figure 1A An example of a wireless communication system is shown.

[0013] Figure 1B A schematic diagram of one embodiment of this disclosure is shown.

[0014] Figure 2 An example of a network node is shown.

[0015] Figure 3 An example of a user device is shown.

[0016] Figure 4A A flowchart of a method for wireless communication is shown.

[0017] Figure 4B A flowchart of another method for wireless communication is shown.

[0018] Figure 5A Exemplary embodiments of this disclosure are shown.

[0019] Figure 5B Another exemplary embodiment of this disclosure is shown.

[0020] Figure 5C Another exemplary embodiment of this disclosure is shown.

[0021] Figure 5D Another exemplary embodiment of this disclosure is shown.

[0022] Figure 6 Another exemplary embodiment of this disclosure is shown.

[0023] Figure 7AAnother exemplary embodiment of this disclosure is shown.

[0024] Figure 7B Another exemplary embodiment of this disclosure is shown.

[0025] Figure 8A Another exemplary embodiment of this disclosure is shown.

[0026] Figure 8B Another exemplary embodiment of this disclosure is shown.

[0027] Figure 8C Another exemplary embodiment of this disclosure is shown.

[0028] Figure 8D Another exemplary embodiment of this disclosure is shown.

[0029] Figure 9 Another exemplary embodiment of this disclosure is shown.

[0030] Figure 10 Another exemplary embodiment of this disclosure is shown. Detailed Implementation

[0031] This disclosure will now be described in detail below with reference to the accompanying drawings, which form part of this disclosure and illustrate specific examples of embodiments by way of illustration. However, it should be noted that this disclosure may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0032] Throughout the specification and claims, terms may have meanings beyond their explicitly stated meanings, implied or suggested in the context. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. It is intended, for example, that the claimed subject matter includes all or part of exemplary embodiments or combinations of embodiments.

[0033] Generally, terms can be understood, at least in part, from their usage in context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings that can depend, at least in part, on the context in which they are used. Typically, “or,” if used with an associative list such as A, B, or C, is intended to mean A, B, and C, used here in an inclusive sense, and A, B, or C, used here in an exclusive sense. Additionally, terms such as “one or more” or “at least one” as used herein, depending at least in part on the context, can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, and characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can again be understood to convey either a singular or a plural usage, depending at least in part on the context. Furthermore, the terms “based on” or “determined by” can be understood not necessarily to convey a set of exclusive factors, and can instead allow for additional factors that are not necessarily explicitly described, again depending at least in part on the context.

[0034] This disclosure describes methods and apparatus for handling data unit transmission problems.

[0035] Next-generation (NG) mobile communication systems are propelling the world towards an increasingly connected and networked society. High-speed and low-latency wireless communication relies on efficient network resource management and allocation between user equipment and wireless access network nodes (including but not limited to wireless base stations). NG networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the requirements of various industries and users.

[0036] The fourth-generation mobile communication technology (4G) Long-Term Evolution (LTE) or LTE-Advance (LTE-A), the fifth-generation mobile communication technology (5G), and the further sixth-generation mobile communication technology (6G) are facing increasing demands and challenges / problems.

[0037] In some wireless communication systems, when a data unit (e.g., a Radio Link Control (RLC) Protocol Data Unit (PDU)) is lost or delayed, the receiving RLC entity may wait for the lost or delayed PDU to reassemble the RLC service data unit (SDU). In some cases, this can lead to RLC SDU transmission delays or RLC SDU hang-ups, resulting in poor transmission rates and poor performance.

[0038] In some implementations, when a Packet Data Convergence Protocol (PDCP) PDU is dropped, the receiving PDCP entity may wait for one or more dropped PDUs to be reordered for PDCP, which may result in PDCP sequence number (SN) gaps, causing PDCP SDU transmission delays or PDCP SDU hangs, as well as poor transmission rates and poor performance.

[0039] In some implementations, according to current specifications, user equipment (UE) may not transmit / receive data during the duration of the measurement gap. However, for latency-sensitive services, when uplink (UL) data bursts arrive at the UE or downlink (DL) data bursts arrive at the radio access network (RAN) (e.g., gNB) during the measurement gap period, data may not be transmitted immediately, affecting data transmission latency. In some implementations, the measurement gap may impact UE throughput.

[0040] This disclosure describes various embodiments for handling data unit transmission problems, solving at least one of the difficulties / problems discussed above, particularly for latency-critical user data transmission, improving latency-sensitive service performance, improving the efficiency of data unit transmission, and / or improving telecommunications performance.

[0041] Figure 1A A wireless communication system 100 is illustrated, comprising a wireless network node (or wireless communication node) 118 and one or more user equipments (UEs) (or wireless communication nodes or wireless communication devices) 110. The wireless network node 118 may include a network base station, which may be a nodeB (NB, e.g., gNB) in a mobile telecommunications context. Each UE may wirelessly communicate with the wireless network node via one or more radio channels 115 for downlink / uplink communication. For example, a first UE 110 may wirelessly communicate with the wireless network node 118 via a channel including multiple radio channels for a certain period of time. The network base station 118 may send higher-layer signaling to the UE 110. The higher-layer signaling may include configuration information for communication between the UE and the base station. In one embodiment, the higher-layer signaling may include a radio resource control (RRC) message.

[0042] like Figure 1BAs shown, the first communication node 150 can communicate with the second communication node 170, and in some cases, it needs to send data units (160) to the second communication node. The first communication node may include one of the following: a base station, a RAN node, an NG-RAN node, a functional node in the core network (CN), or a UE; and / or the second communication node may include one of the following: a base station, a RAN node, an NG-RAN node, a functional node in the core network (CN), or a UE.

[0043] The first communication node 150 may include a Packet Data Convergence Protocol (PDCP) layer 151, which may be referred to as the PDCP entity of the first communication node. PDCP 151 may communicate with a Radio Link Control (RLC) layer 153, which may be referred to as the RLC entity of the first communication node. RLC 153 may communicate with a Medium Access Control (MAC) layer 155, which may be referred to as the MAC entity of the first communication node.

[0044] The second communication node 170 may include a Packet Data Convergence Protocol (PDCP) layer 171, which may be referred to as the PDCP entity of the second communication node. PDCP 171 may communicate with a Radio Link Control (RLC) layer 173, which may be referred to as the RLC entity of the second communication node. RLC 173 may communicate with a Media Access Control (MAC) layer 175, which may be referred to as the MAC entity of the second communication node.

[0045] refer to Figure 1B Data unit transmission 160 can be performed wirelessly from PDCP 151, RLC 153, and MAC 155 of the first node 150 to MAC 175, RLC 173, and PDCP 171 of the second node 170. In some embodiments, the PDCP entity at the first node is referred to as the first PDCP entity, and the PDCP entity at the second node is referred to as the second PDCP entity.

[0046] Figure 2 An example of an electronic device 200 implementing a network base station is shown. The example electronic device 200 may include radio transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with a UE and / or other base stations. The electronic device 200 may also include network interface circuitry 209 for enabling the base station to communicate with other base stations and / or the core network, such as optical or wired interconnects, Ethernet, and / or other data transmission media / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 for communication with an operator or similar personnel.

[0047] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include one or more processors 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured to perform functions of one or more network nodes in processor 124. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.

[0048] Figure 3 An example of an electronic device implementing terminal device 300 (e.g., user equipment (UE)) is shown. UE 300 may be a mobile device, such as a smartphone or a mobile communication module installed in a vehicle. UE 300 may include a communication interface 302, system circuitry 304, input / output interfaces (I / O) 306, display circuitry 308, and storage device 309. The display circuitry may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. System circuitry 304 may be implemented, for example, using one or more systems on a chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System circuitry 304 may be part of an implementation of any desired functionality in UE 300. In this regard, system circuitry 304 may include logic that facilitates, for example, decoding and playing music and video, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (for example, an internet connection); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include a microphone, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0049] refer to Figure 3The communication interface 302 may include radio frequency (RF) transmit (Tx) and receive (Rx) circuitry 316, which processes the transmission and reception of signals via one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver, including modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaping table, an analog-to-digital converter (ADC), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. The transmitted and received signals may conform to any of various formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, communication interface 302 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High-Speed ​​Packet Access (HSPA)+, 4G / LTE, 5G standards, and / or 6G standards. However, the techniques described below are applicable to other wireless communication technologies, whether originating from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.

[0050] refer to Figure 3 System circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to perform the desired functions of UE 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that UE 300 can send or has received via communication interface 302. In various embodiments, system power for UE 300 may be supplied by power storage devices such as batteries or transformers.

[0051] This disclosure describes various embodiments for handling the problem of data unit transmission, which may be partially or wholly derived from the above. Figures 2 to 3The network base stations and / or user equipment described herein are implemented. Various embodiments in this disclosure can achieve efficient utilization of transmission resources in telecommunications systems, which can improve overall communication efficiency and / or enhance latency performance of communication traffic.

[0052] refer to Figure 4A This disclosure describes various embodiments of a method 400 for wireless communication. Method 400 may include some or all of the following: step 410, where a first communication node determines that at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) has been discarded; and / or step 420, where the first communication node sends a first message to a second communication node indicating that at least one PDCP PDU has been discarded, such that the second communication node is configured to ignore at least one discarded PDCP PDU when performing PDCP reordering.

[0053] refer to Figure 4B This disclosure describes various embodiments of a method 450 for wireless communication. Method 450 may include some or all of the following steps: step 460, whereby a second communication node receives from a first communication node a first message indicating that at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) has been discarded; and / or step 470, whereby the second communication node determines that at least one discarded PDCP PDU should be ignored when performing PDCP reordering.

[0054] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the first communication node includes a first user equipment (UE) or a first base station; and / or the second communication node includes a second UE or a second base station.

[0055] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, in response to at least one discarded PDCP PDU not being submitted to the lower layer of the first communication node, the first communication node encodes the first sequence number (SN) of the subsequent PDCP PDU following at least one discarded PDCP PDU after the second SN of the latest PDCP PDU being transmitted, without generating a PDCP SN gap.

[0056] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the first message includes a control PDU for PDCP PDU discard notification; and / or the first communication node causes the transmission of the control PDU to the second communication node to take precedence over the transmission of the PDCP data PDU and the RLC data PDU.

[0057] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the first communication node prioritizes the transmission of control PDUs to the second communication node by: the PDCP entity of the first communication node transmitting PDCP control PDUs to the radio link control (RLC) entity of the first communication node with a higher priority than transmitting PDCP data PDUs; the RLC entity of the first communication node prioritizing the transmission of PDCP control PDUs over at least one RLC data PDU; and / or the media access control (MAC) entity of the first communication node prioritizing the transmission of PDCP control PDUs.

[0058] In some implementations, in addition to some, all, or any combination of other implementations / embodiments described in this disclosure, controlling the PDU includes: a first lost or discarded count (FMC), which indicates the count value of a first lost PDCP SDU within a reordering window; and / or the number of lost or discarded SDUs, which indicates the number of lost or discarded PDCP SDUs having a continuous count starting from and including the FMC.

[0059] In some embodiments, as an adjunct to, or in whole or in any combination of, other embodiments / exemplifications described herein, controlling the PDU includes: a number of FMCs; a plurality of first lost or discarded counts (FMCs), each FMC indicating the count value of a first lost or discarded PDCP SDU within a reordering window; and / or a plurality of lost SDUs, each indicating the number of lost or discarded PDCP SDUs having a consecutive count starting from and including the corresponding FMC. In some embodiments, FMC may refer to a first lost count; and / or FMC may also refer to a first discarded count (FDC), a first discarded count (LDC), the SN of the first discarded PDCP PDU, the SN of the last discarded PDCP PDU, etc.

[0060] In some implementations, in addition to some, all, or any combination of other implementations / embodiments described in this disclosure, controlling the PDU includes: a first lost or discarded PDCP SN indicating the SN of the first lost PDCP PDU; and / or a number of lost or discarded PDUs indicating the number of lost PDCP PDUs having consecutive PDCP SNs starting from and including the first lost or discarded PDCP SN.

[0061] In some implementations, as an adjunct to other implementations / embodiments described herein, the control PDU includes: a first loss or discard count (FMC) indicating the count value of a first lost or discarded PDCP SDU within a reordering window; a bitmap indicating whether each of one or more PDCP SDUs is lost, correctly received by the PDCP entity of a second communication node, or discarded by the PDCP entity of a first communication node; and / or, in response to the number of lost, correctly received, or discarded SDUs not being an integer multiple of an octet, the bitmap includes a number of valid bits indicating the number of valid bits in the last octet of the bitmap.

[0062] In some implementations, the first message may include a portion, all, or any combination of other implementations / embodiments described herein, including PDCP data PDUs for PDCP PDU discard or loss notification.

[0063] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the PDCP data PDU includes: a bit indicating that at least one PDC PDU with a SN less than the indicated PDCP SN is discarded or lost, and the PDCP entity of the second communication node is configured to ignore discarded or lost PDCP PDUs with a SN less than the indicated PDCP-SN when performing PDCP reordering; and / or a PDCP SN having 12 or 18 bits for discarding or losing PDCP PDUs.

[0064] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the first communication node and the second communication node respectively include a first UE and a second base station; the first communication node sends a second message for capability indication to the second communication node; and / or the first communication node receives a third message for activation indication from the second communication node, wherein: the capability indication indicates the support capability of a control PDU for PDCP PDU drop notification or a PDCP data PDU for PDCP PDU drop or loss notification, and / or the activation indication indicates the activation of a control PDU for PDCP PDU drop notification or a PDCP data PDU for PDCP PDU drop or loss notification.

[0065] In some implementations, in addition to some, all, or any combination of other implementations / embodiments described in this disclosure, the second message includes a Radio Resource Control (RRC) message; and / or the third message includes a downlink RRC message.

[0066] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the RLC entity of the first communication node sends a control PDU to the RLC entity of the second communication node for information on at least one lost or discarded RLC PDU; and / or the RLC entity of the second communication node determines that no RLC status PDU is generated for NACK_SN transmission.

[0067] In some implementations, in addition to some, all, or any combination of other implementations / embodiments described in this disclosure, controlling the PDU includes: a first lost or discarded RLC SN having 12 bits or 18 bits; and / or the number of lost or discarded PDUs indicating that RLC PDUs with SNs from N to (N+M-1) have been lost or discarded, where: N is the first lost or discarded RLC SN, and M is the number of lost or discarded PDUs.

[0068] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the RLC entity of the second communication node detects a lost RLC PDU; and / or the RLC entity of the second communication node immediately triggers the transmission of an RLC status PDU to the first communication node for retransmission of the lost RLC PDU.

[0069] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the RLC entity of the second communication node detects the loss of an RLC PDU; and / or the RLC entity of the second communication node starts a timer; in response to the lost RLC PDU being received before the timer expires, the RLC entity of the second communication node stops the timer; and / or in response to the lost RLC PDU not being received when the timer expires, the RLC entity of the second communication node immediately triggers the transmission of an RLC status PDU to the first communication node for retransmission of the lost RLC PDU.

[0070] In some implementations, in addition to some, all, or any combination of other implementations / embodiments described in this disclosure, the timer includes one of a disable timer or a suspend timer to disable the transmission of RLC status PDUs for a predefined duration in order to wait for a lost RLC PDU.

[0071] In some embodiments, as additional to some, all, or any combination of other embodiments / exemplifications described in this disclosure, the RLC entity of the second communication node detects a lost RLC PDU when the following conditions are met: the lost RLC PDU has not yet been received, and / or a subsequent RLC PDU has been received. In some embodiments, a control PDU for RLC PDU discard notification has not yet been received to indicate that the lost RLC PDU has been discarded.

[0072] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the RLC entity of the second communication node detects a lost RLC PDU when the following conditions are met: the lost RLC PDU has not yet been received, and / or the elapsed time when a subsequent RLC PDU has been received is greater than a time threshold.

[0073] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the RLC entity of the second communication node makes the transmission of RLC status PDUs take precedence over the transmission of RLC data PDUs.

[0074] In some implementations, in part, all, or any combination of other implementations / embodiments described herein, the first communication node and the second communication node respectively include a first UE and a second base station; the first communication node sends a fourth message for capability indication to the second communication node; and / or the first communication node receives a fifth message for activation indication from the second communication node, wherein: the capability indication indicates support capability of a control PDU for information of at least one lost or discarded RLC PDU, and / or the activation indication indicates that once the loss of an RLC PDU is detected, an RLC control PDU for PLC PDU discard notification is activated and / or an RLC control PDU transmission is triggered.

[0075] In some implementations, in response to any of the following: receiving an activation indication (e.g., for a UE acting as a receiving communication node) indicating that an RLC control PDU for PLC PDU drop notification and / or triggering RLC control PDU transmission is activated upon detection of RLC PDU loss, or determining (e.g., for a gNB acting as a receiving communication node) that an RLC control PDU for PLC PDU drop notification and / or triggering RLC control PDU transmission is activated upon detection of RLCPDU loss, the RLC entity stops retransmitting RLC PDUs and does not indicate to the upper layer that the maximum number of retransmissions has been reached, and / or does not trigger RRC release or RRC re-establishment when the number of RLC PDU retransmissions reaches the maximum RLC PDU retransmission threshold. In some implementations, the RLC entity may stop retransmitting RLC PDUs and continue transmitting and / or receiving other RLC PDUs when the number of RLC PDU retransmissions reaches the maximum RLC PDU retransmission threshold.

[0076] This disclosure describes various exemplary embodiments for handling data unit transmission problems. These embodiments are illustrative only and do not constitute limitations. Any steps and / or operations in one or more identical embodiments / implementations of this disclosure may be combined or arranged in any number or order as needed. Two or more steps and / or operations may be performed in parallel. The embodiments and implementations in this disclosure may be used individually or in any combination in any order. Furthermore, each of the methods (or embodiments) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits).

[0077] Implementation Set

[0078] This disclosure describes various embodiments for handling data unit transmission problems, particularly those related to PDCP control of PDU priority. In some implementations, when the transmitting side of the PDCP entity discards a PDU or a set of at least one PDU (i.e., a PDU set), at least one of the following methods can be used to avoid PDCP SDU transmission delays and / or PDCP SDU hang-ups.

[0079] In one approach (Approach 1), when a subsequent PDCP PDU (e.g., one or more PDUs following a discarded PDCP PDU or a set of PDUs) has not yet been submitted to the lower layer of the PDCP entity, the transport side of the PDCP entity may not generate a PDCP SN gap when discarding the PDCP PDU. For example, the SN of the subsequent PDCP PDU is encoded after the SN of the latest PDCP PDU that was transmitted and not discarded, as if the discarded PDCP PDU or set of PDUs did not exist.

[0080] In another method (method 2), when at least one of the subsequent PDCP PDUs (e.g., one or more PDUs after a discarded PDCP PDU or a set of PDUs) has been submitted to the lower layer, the transport side generates a control PDU for PDCP PDU discard notification to notify the receiving PDCP entity of the SN of one or more discarded PDUs or a set of one or more PDUs, so that the receiving PDCP entity can ignore the SN of one or more PDUs or a set of one or more PDUs when performing PDCP reordering.

[0081] In some implementations, for a control PDU for PDCP PDU discard notification to be transmitted to the receiving PDCP entity, the transmitting sides of the PDCP entity and RLC entity can prioritize the transmission of the control PDU for PDCP PDU discard notification over the PDCP data PDU and RLC data PDU. When a control PDU for PDCP PDU discard notification is generated, the transmitting side of the PDCP entity can submit it to the transmitting side of the RLC entity, and / or an indication for the control PDU for PDCP PDU discard notification can also be provided to the transmitting side of the RLC entity. Upon receiving a control PDU for PDCP PDU discard notification, the transmitting side of the RLC entity places it at the very beginning of the RLC queue header (headmost), or places it in a queue separate from the RLC data PDU queue, so that the transmitting side of the RLC entity can prioritize the transmission of the control PDU for PDCP PDU discard notification over the RLC data PDU.

[0082] In some implementations, during the logical channel priority sorting process, when a control PDU for PDCP PDU drop notification is available, the MAC entity may first allocate resources to the control PDU for PDCP PDU drop notification, and allocate remaining resources to other PDUs based on physical block resource (PBR), elapsed time, and / or remaining time.

[0083] For another method (method 3), when one or more PDCP PDUs have been discarded and / or lost, an indicator is included in the next or subsequent PDCP data PDU to indicate that a PDCP PDU has been discarded and / or lost, and to indicate that the PDCP SN gap before the current PDCP SN should be ignored for subsequent PDCP PDU reordering.

[0084] In some implementations, the control PDU for PDCP PDU discard notification can be one of the following configurations.

[0085] For one configuration (control PDU configuration 1), a PDCP PDU drop notification is indicated to the receiving PDCP entity based on a first lost PDCP count (CN) (FMC) (or a first lost PDCP SN) and the number of lost SDUs (or the number of lost PDUs). The FMC may indicate the first lost count, which is the count value of the first lost PDCP SDU within the reordering window. The number of lost SDUs may indicate the number of lost PDCP SDUs with consecutive counts starting from and including the FMC. The first lost PDCP SN may indicate the SN of the first lost PDCP PDU. The number of lost PDUs may indicate the number of lost PDCP PDUs (with consecutive PDCP SNs starting from and including the first lost PDCP SN).

[0086] Figure 5A An example of a control PDU for PDCP PDU drop notification is shown, which includes an FMC 502 and a lost SDU count field 504 to indicate that an SDU with a count from FMC to (FMC + (lost SDU count - 1)) has been lost / dropped.

[0087] In some implementations, a value of the PDU type or an R bit is used to indicate that the PDU is used for PDCPPDU discard notification.

[0088] Figure 5B Another example of a control PDU for PDCP PDU drop notification is shown. It includes a number of FMCs (522), multiple FMCs (524), and multiple lost SDU count fields (526) to indicate that SDUs with multiple count segments have been lost / dropped. For the first group, there are SDUs with counts from FMC1 to FMC1+ (number of lost SDUs 1-1); for the second group, there are SDUs with counts from FMC2 to FMC2+ (number of lost SDUs 2-1); ...; for the Nth group, there are SDUs with counts from FMC1 to FMC1+ (number of lost SDUs 1-1); ... N To FMC N + (Number of lost SDUs)N The SDU count of -1) is lost, where N is determined by the quantity field 522 of the FMC.

[0089] Figure 5C Another example of a control PDU for PDCP PDU discard notification is shown, including a first lost PDCP SN 542 (with an 18-bit PDCP SN) and a lost PDU count field 544 to indicate that a PDCP PDU with a SN from the first lost PDCP SN to the first lost PDCP SN + (lost PDU count - 1) has been lost / discarded.

[0090] Figure 5D Another example of a control PDU for PDCP PDU discard notification is shown, including a first lost PDCP SN 562 (with a 12-bit PDCP SN) and a lost PDU count field 564 to indicate that a PDCP PDU with an SN from the first lost PDCP SN to the first lost PDCP SN + (lost PDU count - 1) has been lost / discarded.

[0091] In some implementations, a PDCP PDU drop notification is given to the receiving PDCP entity based on some or all of the following: at least one FMC, at least one Bitmap i and Bitmap N At least one significant bit. The FMC can indicate the first loss count, which is the count value of the first lost PDCP SDU within the reordering window. The bitmap can indicate which SDUs were lost / discarded and which SDUs were correctly received in the receiving PDCP entity. Bitmap N The number of significant bits can indicate the number of significant bits in the last eight bytes of the bitmap, and the number of significant bits of the bitmap can be used in cases where the number of lost or correctly received SDUs in the receiving PDCP entity is not an integer multiple of eight bytes, where eight bytes represent 8 bits.

[0092] In some implementations, the position of the m-th bit in the bitmap is m, meaning the position of the first bit in the bitmap is 1. Furthermore, the bit values ​​in the bitmap are indicated as follows: when the bit value is 0, it has COUNT = (FMC + bit position) modulo 2. 32 The PDCP SDU is lost; when the bit value is 1, it has COUNT = (FMC + bit position) modulo 2. 32 The PDCP SDU was received correctly.

[0093] Figure 6Another example of a control PDU used for PDCP PDU discard notification is shown. The number of valid bits in the bitmap (610) indicates the number of valid bits in the last eight bytes of the bitmap (bitmap). N 612), which is used when the number of SDUs lost or correctly received in the receiving PDCP entity is not an integer multiple of octet bytes (e.g., 8 bits).

[0094] In some implementations, a bit in the PDCP data PDU is used to indicate PDUs that were not correctly received by the receiving PDCP entity before the current PDCP SN (e.g., were discarded or lost), and to indicate that the receiving PDCP entity should ignore them when performing PDCP reordering.

[0095] Figure 7A The diagram illustrates an example where the “Mis” bit 710 in a PDCP data PDU with an 18-bit PDCP SN 720 indicates that some PDUs have been discarded or lost. The “Mis” bit is a missing PDU indicator. When the Mis bit is set to 1, it indicates that a PDU prior to the PDCP SN (included in the PDU) was not properly received by the receiving PDCP entity (e.g., it has been discarded or lost), and that the receiving PDCP entity should ignore them when performing PDCP reordering.

[0096] Figure 7B Another example is shown where the Mis bit 740 in a PDCP data PDU with a 12-bit PDCP SN 750 indicates that some PDUs have been discarded or lost. The Mis bit is an indication of a lost PDU. When the Mis bit is set to 1, it indicates that a PDU that was not properly received by the receiving PDCP entity before the PDCP SN (included in the PDU) (e.g., it has been discarded or lost), and that the receiving PDCP entity should ignore them when performing PDCP reordering.

[0097] In some implementations, before the control PDU for PDCP PDU drop notification or the data PDU including the Mis bit is sent, the UE may send a capability to the gNB to indicate support for the control PDU for PDCP PDU drop notification or the data PDU including the Mis bit as described above. Upon receiving the capability indicating support for the control PDU for PDCP PDU drop notification or the data PDU including the Mis bit, the gNB may send an indication to the UE to activate the use of the control PDU for PDCP PDU drop notification or the data PDU including the Mis bit.

[0098] In some implementations, the control PDU or data PDU including the Mis bit described above can only be sent when the use of the control PDU for PDCP PDU discard notification or the data PDU including the Mis bit is activated.

[0099] In some implementations, the capability to indicate support for a control PDU or a data PDU including the Mis bit for PDCP PDU drop notification can be sent via an RRC message (e.g., UECapabilityInformation). In a DL RRC message within RRCResume, RRCSetup, RRCReestablishment, or RRCReconfiguration (e.g., in a PDCP-Config IE), an indication that the UE is activating the use of a control PDU or a data PDU including the Mis bit for PDCP PDU drop notification can be sent.

[0100] Implementation Set

[0101] This disclosure describes various embodiments for handling data unit transmission problems, particularly those related to RLC control PDU priority.

[0102] In some implementations, when an RLC PDU containing an RLC SDU segment is discarded or lost, the receiving RLC entity may wait for the discarded or lost PDU to be reassembled into an RLC SDU, and only the reassembled RLC SDU can be delivered to the upper layer; when an RLC PDU containing an RLC SDU is discarded or lost, the receiving RLC entity may wait for one or more discarded or lost PDUs to be delivered to the upper layer.

[0103] In some implementations of RLC acknowledge mode (AM), an RLC status PDU can be triggered for retransmission when an RLC PDU is discarded or lost; however, in some cases, the current RLC status PDU may not be triggered as needed. For example, when an RLC PDU is intentionally / deliberately discarded by the transmitting RLC entity (e.g., due to congestion), an RLC status PDU and retransmission are not necessary. When an RLC PDU is lost (e.g., due to poor radio conditions), an RLC status PDU and retransmission are necessary, but the current RLC status PDU cannot be triggered in a timely manner enough to delay critical services (e.g., polling bits or t-reassembly timers are too slow).

[0104] In some implementations of the RLC non-acknowledge mode (UM), when an RLC PDU containing an RLC SDU segment is discarded or lost, the receiving RLC entity may also wait for one or more discarded or lost PDUs to be reassembled into an RLC SDU, and only the reassembled RLC SDU can be delivered to the upper layer.

[0105] At least one of the following methods can be used so that RLC SDUs can be delivered to the upper layer as quickly as possible and unnecessary RLC state SDUs can be avoided.

[0106] In one method (Method 1), when an RLC SDU is discarded by the transmitting RLC entity: the transmitting RLC entity informs the transmitting PDCP entity of the discarded RLC SDU information (e.g., discarded PDCP PDU information). The transmitting PDCP entity may notify the receiving PDCP entity of the discarded PDCP PDU information to avoid PDCP reordering stalls caused by PDU loss.

[0107] For another method (method 2), when the RLC PDU is discarded by the transmitting RLC entity: in RLC AM mode, the transmitting RLC entity notifies the receiving RLC entity of the discarded RLC PDU information (e.g., discarded RLC SDU information or discarded RLCPDU segment information); and the receiving RLC entity may not generate an RLC status PDU for NACK_SN transmission.

[0108] In some implementations, the discarded RLC PDU information can be obtained from, for example... Figure 8A , Figure 8B , Figure 8C and Figure 8D One of the control PDUs shown is being transmitted.

[0109] Figure 8A An example of a control PDU for RLC PDU discard notification is shown, including a first lost RLC SN 810 (with an 18-bit RLC SN) and a lost PDU count field 820 to indicate that an RLC PDU with a SN from the first lost RLC SN to the first lost RLC SN + (lost PDU count - 1) has been discarded.

[0110] Figure 8BAnother example of a control PDU for RLC PDU discard notification is shown, including a first lost RLC SN 850 (with a 12-bit RLC SN) and a lost PDU count field 860 to indicate that an RLC PDU with a SN from the first lost RLC SN to the first lost RLC SN + (lost PDU count - 1) has been discarded.

[0111] Figure 8C Another example of a control PDU for RLC PDU drop notification is shown, including at least one first lost RLC SN 871 (with 12 bits of RLC SN) and at least a set of E1 bits 873, E2 bits 874, and E3 bits 875, and a possible pair of SOstart bits 876 and SOend bits 877 for each first lost RLC SN, or a lost RLC PDU range field 878. The SOstart field (together with the SOend field) indicates a portion of the RLC SDU whose SN = the first lost RLC SN has been dropped by the transmitting side of the RLC entity or detected as lost by the receiving side of the AM RLC entity. When E3 is 0, the SOend field (together with the SOstart field) indicates a portion of the RLC SDU of the first lost RLC SN (e.g., specifically, the SOend field indicates the position of the last byte of the portion of the RLC SDU within the bytes of the original RLC SDU), which has been discarded by the transmitting side of the RLC entity or detected as lost by the receiving side of the AM RLC entity. In some implementations, specifically, the SOstart field indicates the position of the first byte of the portion of the RLC SDU within the bytes of the original RLC SDU, and the SOend field indicates the position of the last byte of the portion of the RLC SDU within the bytes of the original RLC SDU. In some implementations, the extension bit 1 (E1) field indicates whether a set of first lost RLC SNs, E1, E2, and E3 follows. The extension bit 1 (E2) field indicates whether a set of SOstart and SOend follows. The E3 field indicates whether information about a continuous sequence of RLC SDUs that have not yet been received (e.g., the range field of lost RLC PDUs) follows.

[0112] Figure 8D Another example of a control PDU for RLC PDU drop notification is shown, including a first lost RLC SN 891 (with an 18-bit RLC SN), where the meanings of the fields are as follows: Figure 8C The meanings are the same, except for the difference in RLC SN length.

[0113] For another method (method 3) in RLC AM mode, when the receiving RLC entity detects the loss of an RLC PDU (e.g., an RLC SDU or RLCSDU segment), it immediately triggers an RLC status PDU to trigger the retransmission of the lost RLC PDU.

[0114] In some implementations, whether RLC PDU loss can trigger an RLC state PDU depends on the activation indication. An RLC PDU loss can only trigger an RLC state PDU if the activation indication is that RLC PDU loss can trigger an RLC state PDU. The activation indication is configured by the gNB, each logical channel (e.g., in the LogicalChannelConfig IE), each RLC entity (e.g., in the RLC-Config or RLC-BearerConfig IE), or each PDCP entity (e.g., in the PDCP-Config IE) in DLRRC messages (e.g., in RRCResume, RRCSetup, RRCReestablishment, or RRCReconfiguration).

[0115] In some implementations, the UE can report an indication that supports the ability to report RLC status PDUs triggered by RLC PDU loss before the activation indication is configured.

[0116] For another method (Method 4) in RLC AM mode, when the receiving RLC entity detects the loss of an RLC PDU (e.g., an RLC SDU or RLCSDU segment), it starts a timer to wait for the lost RLC PDU (e.g., a disable timer or suspend timer used by the receiving side of the AM RLC entity to disable the transmission of the status PDU for the duration of the wait for the lost RLCSDU when the RLC PDU loss is detected). The timer stops when the lost RLC PDU has been received while it is running. When the timer expires (e.g., no lost RLC PDU was received during the timer period), the RLC status PDU or... Figure 8A , Figure 8B , Figure 8C or Figure 8D The RLC control PDU shown is triggered for retransmission of the lost RLC PDU.

[0117] In some implementations, the timer is configured by the gNB, each logical channel (e.g., in LogicalChannelConfigIE), each RLC entity (e.g., in RLC-Config or RLC-BearerConfigIE), or each PDCP entity (e.g., in PDCP-ConfigIE) in DL RRC messages (e.g., in RRCResume, RRCSetup, RRCReestablishment, or RRCReconfiguration).

[0118] In some implementations, the UE can report an indication of support for RLC status PDU reporting triggered by RLC PDU loss before the timer is configured.

[0119] In some implementations, one difference between method 3 and method 4 is that method 4 has a timer for waiting for a lost RLC PDU; and both methods (3) and (4) include receiving RLC entities that can detect the loss of RLC PDUs based on one of the following methods.

[0120] In one approach, when an RLC PDU (e.g., a first RLC PDU) has not yet been received, a subsequent RLC PDU (e.g., a second RLC PDU) has been received, and no control PDU for RLC PDU discard notification indicating that the RLC PDU (e.g., the first RLC PDU) has been discarded, the receiving RLC entity can determine that the RLC PDU (e.g., the first RLC PDU) is lost / missing. For example, when an RLC PDU with sequence number (SN) = x has not yet been received, and an RLC PDU with SN = x + n has been received (n is a positive integer), the receiving RLC entity can determine that the RLC PDU with SN = x has been lost / missing. When an RLC PDU with SN = x and segment offset (SO) = y has not yet been received, and an RLC PDU with SN = x and SO = y + n has been received (n is a positive integer), the receiving RLC entity can determine that the RLC PDU with SN = x and SO = y has been lost / missing (e.g., the RLC SDU segment has been lost).

[0121] In another approach, when an RLC PDU (e.g., the second RLC PDU) is received, and the elapsed time is greater than a time threshold, and a previous RLC PDU (e.g., the first RLC PDU) has not yet been received, and no control PDU for RLC PDU discard notification is received to indicate that the RLC PDU (e.g., the first RLC PDU) has been discarded, the receiving RLC entity can determine that the RLC PDU (e.g., the first RLC PDU) has been lost / discarded, where “previous RLC PDU” means an RLC PDU with a smaller SN and / or the same SN but a smaller SO.

[0122] Implementation Set

[0123] This disclosure describes various embodiments for activating and / or deactivating measurement gaps. In some implementations, a measurement gap is a period of time during which the network configures a UE to perform one or more neighbor cell reference signal received power (RSRP) and / or reference signal received quality (RSRQ) measurements. During a measurement gap, the UE cannot perform user data transmission and / or reception, which can increase latency or reduce UE throughput.

[0124] In some implementations, the UE may be in good radio coverage and one or more neighbor cell measurements are not required, which can be reported from the UE to the gNB via MeasurementReport messages (e.g., via events A1 and A2). In other implementations, the UE may be geostationary and one or more neighbor cell measurements can be relaxed, which can be sent from the UE to the gNB via UEAssistanceInformation messages (e.g., via rrm-MeasRelaxationFulfilment indication). Given that radio coverage and / or the UE's geostationary state may change (e.g., the UE is in intermittent geostationary conditions), measurement gaps need to be dynamically activated or deactivated, and whether a measurement gap is activated or deactivated should be coordinated between the UE and the gNB. For example, based on information sent from the UE (e.g., event A1 report, event A2 report, or rrm-MeasRelaxationFulfilment indication), the gNB can send an activation or deactivation indication via DCI or MAC CE to activate or deactivate a measurement gap for one or more neighboring cell measurements; when only one measurement gap mode is configured, an activation or deactivation indication is in the DCI or MAC CE; and / or when multiple measurement gap modes are configured, one of the following methods can be used.

[0125] One approach includes a single activation or deactivation indicator in the DCI or MAC CE to activate or deactivate all measurement gap modes. Another approach includes an activation or deactivation indicator for each measurement gap ID in the DCI or MAC CE to indicate which measurement gap is activated or deactivated.

[0126] In some implementations, a fixed-size MAC CE with zero bits can be used when only one activation or deactivation indication is used in the MAC CE to activate or deactivate (all) measurement gap modes. For example, only the MAC subheader is used, one (e)LCID is defined to activate (all) measurement gap modes, and another (e)LCID is defined to deactivate (all) measurement gap modes.

[0127] When the MAC CE (Activation or Deactivation Indicator for Each Measurement Gap ID) is used to activate or deactivate (all) measurement gap modes, the MAC CE can be defined with a fixed size of 8 bits, such as... Figure 9 As shown.

[0128] Figure 9 An example of the activation or deactivation indication MAC CE for each measurement gap ID is shown, where a GapIdi field of 0 indicates that the measurement gap mode for measurement GAP ID=1 is not activated; a GapIdi field of 1 indicates that the measurement gap mode for measurement GAP ID=1 is activated.

[0129] Implementation Set

[0130] This disclosure describes various embodiments with a new formula for measurement gaps. In some embodiments, to avoid overlap between measurement gaps and XR data bursts (e.g., C-DRX on-time duration), a non-integer measurement gap period (e.g., a measurement gap repetition period (MGRP) with a non-integer value) is configured, and the measurement timing is determined based on one of the following formulas. When a non-integer MGRP value is configured or an indication to use the new gap formula is given (e.g., providing the hsfn-LSB or gap-TimeReferenceSFN below in the RRC (re)configuration), the first subframe of each gap occurs at the system frame number (SFN) and subframe that satisfy the following conditions.

[0131] For a formula (Formula 1), FLOOR[(GAP_SFN_COUNTER × 1024 + SFN) mod T] = FLOOR( gapOffset / 10); and subframe = gapOffset mod 10; where T = MGRP / 10.

[0132] For another formula (Formula 2), floor([(GAP_SFN_COUNTER × 10240) + (SFN ×10) + number of subframes] modulo(MGRP)) = floor(gapOffset modulo(MGRP)).

[0133] Here, gapOffset is the gap offset of the gap pattern with the MGRP indicated in the mgrp field. It is used to determine the start timing of each gap, and the value of gapOffset ranges from 0 to MGRP-1, an integer. MGRP is a non-integer, and the unit is milliseconds (ms). GAP_SFN_COUNTER is used to handle SFN wraparound issues. It is set to 0 in the HSFN containing the first transmission of RRC (re)configuration with a non-integer measurement gap configuration, or set to 1 in the next H-SFN after the first transmission of RRC (re)configuration message with a non-integer measurement gap configuration (e.g., the RRC (re)configuration message is sent in the H-SFN but received by the UE in the next H-SFN), and incremented by 1 in the first subframe where the SFN changes to 0.

[0134] In some implementations, the HSFN where the first transmission of the RRC (re)configuration resides can be determined by one of the following methods.

[0135] For one method (Alt 1), the RRC (re)configuration includes an hsfn-LSB indication to indicate the LSB of the H-SFN in the first transmission of the RRC (re)configuration message, which includes a non-integer measurement gap configuration. In the H-SFN indicated by the hsfn-LSB, GAP_SFN_COUNTER is set to 0.

[0136] For another approach (Alt 2), RRC (re)configuration may include a gap-TimeReferenceSFN with values ​​(reference SFN=0, reference SFN=512) to indicate the nearest SFN with the indicated number before receiving the RRC (re)configuration. When gap-TimeReferenceSFN is set to SFN=512 and RRC (re)configuration is received at an SFN between 0 and 511, this means that RRC (re)configuration was received in the next H-SFN after the H-SFN of the first transmission of the RRC (re)configuration message, and GAP_SFN_COUNTER is set to 1 when the UE receives the RRC (re)configuration message; otherwise, this means that RRC (re)configuration was received in the H-SFN of the first transmission of the RRC (re)configuration message, and GAP_SFN_COUNTER is set to 0. In some implementations, this mechanism is based on the assumption that the transmission delay of the RRC (re)configuration message will not exceed 5120ms.

[0137] In some implementations, a UE capability report indicates whether a non-integer measurement gap period and / or measurement gap enhancement are necessary. The network can only configure a non-integer measurement gap period (e.g., non-integer MGRP) to the UE if the UE supports it. With only the non-integer measurement gap period (e.g., non-integer MGRP) configured, the UE performs measurements based on the configured non-integer measurement gap period and at least one determined measurement GAP from the equation above. The UE capability report also indicates whether the non-integer measurement gap period can be included in an RRC message, such as UECapabilityInformation. Figure 10 An example of the process is shown.

[0138] This disclosure describes methods, apparatus, and computer-readable media for wireless communication. This disclosure solves the difficult problem of handling data unit transmission. The methods, apparatus, and computer-readable media described in this disclosure can improve the performance of wireless communication, thereby increasing efficiency and overall performance. The methods, apparatus, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.

[0139] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above. A computer-readable medium may be referred to as a non-transitory computer-readable medium (CRM) that stores data for a long period, such as a flash drive or compact disk (CD), or for a short period in the presence of power, such as a memory device or random access memory (RAM). In some embodiments, computer-readable instructions may be included in software embodied in one or more tangible, non-transitory computer-readable media. Such a non-transitory computer-readable medium may be associated with a user-accessible mass storage device and certain short-duration storage devices with non-transitory characteristics, such as internal mass storage or ROM. Software implementing various embodiments of this disclosure may be stored in such a device and executed by a processor (or processing circuitry). Depending on specific needs, a computer-readable medium may include one or more memory devices or chips. Software can cause processors (including CPUs, GPUs, FPGAs, and the like) to perform specific processes or specific parts of specific processes described herein, including defining data structures stored in RAM and modifying such data structures according to software-defined processes.

[0140] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable with this solution should be included or included in any single implementation thereof. Rather, references to features and advantages are to be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, throughout this specification, discussions of features and advantages, and similar language, may, but do not necessarily, refer to the same embodiments.

[0141] Furthermore, the features, advantages, and characteristics described in this solution can be combined in one or more embodiments in any suitable manner, and for non-limiting examples, a portion from one or more embodiments can be combined with another portion of other embodiments. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more of a particular feature or advantage of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments, which may not be present in all embodiments of this solution.

Claims

1. A method for wireless communication, comprising: The first communication node determines that at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) has been discarded; and The first communication node sends a first message to the second communication node indicating that at least one PDCP PDU has been discarded, such that the second communication node is configured to ignore at least one discarded PDCP PDU when performing PDCP reordering.

2. A method for wireless communication, comprising: The second communication node receives from the first communication node a first message indicating that at least one Packet Data Convergence Protocol (PDCP) Protocol Data Unit (PDU) has been discarded; and The second communication node determines that at least one discarded PDCP PDU should be ignored when performing PDCP reordering.

3. The method according to any one of claims 1 to 2, wherein: The first communication node includes a first user equipment (UE) or a first base station; and The second communication node includes a second UE or a second base station.

4. The method according to any one of claims 1 to 3, wherein: In response to the fact that at least one discarded PDCP PDU is not submitted to the lower layer of the first communication node, the first communication node encodes the first sequence number (SN) of the subsequent PDCP PDU after the at least one discarded PDCP PDU after the second SN of the latest PDCP PDU being transmitted, without generating a PDCP SN gap.

5. The method according to any one of claims 1 to 3, wherein: The first message includes a control PDU for PDCP PDU discard notification; and The first communication node prioritizes the transmission of the control PDU to the second communication node over the transmission of PDCP data PDU and RLC data PDU.

6. The method according to claim 5, wherein, The first communication node prioritizes the transmission of the control PDU to the second communication node, including: The PDCP entity of the first communication node transmits the PDCP control PDU to the radio link control (RLC) entity of the first communication node with a higher priority than the transmission of the PDCP data PDU; The RLC entity of the first communication node makes the transmission of the PDCP control PDU take precedence over at least one RLC data PDU; and The Media Access Control (MAC) entity of the first communication node enables PDCP to prioritize PDU transmission.

7. The method according to any one of claims 5 to 6, wherein, The control PDU includes: First Loss or Discard Count (FMC), which indicates the count value of the first lost PDCP SDU within the reordering window; and The number of lost or discarded SDUs indicates the number of lost or discarded PDCP SDUs with a continuous count starting from and including the FMC.

8. The method according to any one of claims 5 to 6, wherein, The control PDU includes: The number of the first lost or discarded count (FMC), Multiple FMCs, each FMC indicating the count value of the first lost or discarded PDCP SDU within the reordering window; and The number of multiple lost SDUs, each indicating the number of lost or discarded PDCP SDUs with a consecutive count starting from and including the corresponding FMC.

9. The method according to any one of claims 5 to 6, wherein, The control PDU includes: The first lost or discarded PDCP SN, which indicates the SN of the first lost PDCP PDU; and The number of lost or discarded PDUs, indicating the number of lost PDCP PDUs having consecutive PDCP SNs starting from and including the first lost or discarded PDCP SN.

10. The method according to any one of claims 5 to 6, wherein, The control PDU includes: First Loss or Discard Count (FMC) indicates the count value of the first lost or discarded PDCP SDU within the reordering window; A bitmap indicating whether each of one or more PDCP SDUs is lost, correctly received by the PDCP entity of the second communication node, or discarded by the PDCP entity of the first communication node; and In response to the number of SDUs that are lost, correctly received, or discarded not being an integer multiple of eight bytes, the number of valid bits in the bitmap is included, indicating the number of valid bits in the last eight bytes of the bitmap.

11. The method according to any one of claims 1 to 3, wherein: The first message includes PDCP data PDU for PDCP PDU discard or loss notification.

12. The method according to claim 11, wherein, The PDCP data PDU includes: A bit indicating that at least one PDCP PDU with a SN less than the indicated PDCP SN has been discarded or lost, and the PDCP entity of the second communication node is configured to ignore discarded or lost PDCP PDUs with a SN less than the indicated PDCP-SN when performing PDCP reordering; and PDCP SN, which has 12 or 18 bits for the discarded or lost PDCP PDU.

13. The method according to any one of claims 1 to 12, wherein: The first communication node and the second communication node respectively include the first UE and the second base station; The first communication node sends a second message for capability indication to the second communication node; and The first communication node receives a third message from the second communication node for an activation indication. in: The capability indicator specifies the supported capabilities of control PDUs for PDCP PDU drop notifications or PDCP data PDUs for PDCP PDU drop or loss notifications. The activation instruction specifies the activation of a control PDU for PDCP PDU discard notification or a PDCP data PDU for PDCP PDU discard or loss notification.

14. The method of claim 13, wherein: The second message includes a Radio Resource Control (RRC) message; and The third message includes a downlink RRC message.

15. The method according to any one of claims 1 to 14, wherein: The RLC entity of the first communication node sends a control PDU to the RLC entity of the second communication node for information on at least one lost or discarded RLC PDU; and The RLC entity of the second communication node determines that it does not generate an RLC status PDU for NACK_SN transmission.

16. The method according to claim 15, wherein, The control PDU includes: The first lost or discarded RLC SN, which has 12 or 18 bits; and The number of lost or discarded PDUs, indicating the number of RLC PDUs (SN) from N to (N+M-1) that have been lost or discarded. Where: N is the first lost or discarded RLC SN, and M is the number of lost or discarded PDUs.

17. The method according to any one of claims 1 to 14, wherein: The RLC entity of the second communication node detected the lost RLC PDU; and The RLC entity of the second communication node immediately triggers the transmission of an RLC status PDU to the first communication node for the retransmission of the lost RLC PDU.

18. The method according to any one of claims 1 to 14, wherein: The RLC entity of the second communication node detected the loss of the RLC PDU; and The RLC entity of the second communication node starts a timer; In response to the receipt of an RLC PDU lost before the timer expires, the RLC entity of the second communication node stops the timer; and In response to the loss of the RLC PDU not being received when the timer expires, the RLC entity of the second communication node immediately triggers the transmission of an RLC status PDU to the first communication node for retransmission of the loss of the RLC PDU.

19. The method of claim 18, wherein: The timer includes one of a disable timer or a suspend timer to disable the transmission of RLC status PDUs for a predefined duration in order to wait for the lost RLC PDU.

20. The method according to any one of claims 17 to 19, wherein: The RLC entity of the second communication node detects a lost RLC PDU when the following conditions are met: The lost RLC PDU has not yet been received, and The subsequent RLC PDU has been received.

21. The method according to any one of claims 17 to 19, wherein: The RLC entity of the second communication node detects a lost RLC PDU when the following conditions are met: The lost RLC PDU has not yet been received, and When a subsequent RLC PDU has been received, the elapsed time exceeds the time threshold.

22. The method according to any one of claims 18, wherein: The RLC entity of the second communication node prioritizes the transmission of the RLC status PDU over the transmission of the RLC data PDU.

23. The method according to any one of claims 15 to 22, wherein: The first communication node and the second communication node respectively include the first UE and the second base station; The first communication node sends a fourth message for capability indication to the second communication node; and The first communication node receives a fifth message from the second communication node for an activation indication. in: The capability indicator specifies the support capability of the control PDU for information of at least one lost or discarded RLC PDU, and The activation instruction specifies that once the loss of an RLC PDU is detected, the RLC control PDU for PLC PDU discard notification is activated and / or the RLC control PDU transmission is triggered.

24. The method according to claim 23, wherein: Respond to any of the following: Receive the activation instruction, which specifies that once the loss of an RLC PDU is detected, activate the RLC control PDU for PLC PDU discard notification and / or trigger RLC control PDU transmission, or Once an RLC PDU loss is detected, the RLC control PDU for PLC PDU discard notification is activated and / or an RLC control PDU transmission is triggered. The RLC entity stops retransmitting the RLC PDU and does not indicate to the upper layer that the maximum number of retransmissions has been reached, and / or When the number of RLC PDU retransmissions reaches the maximum RLC PDU retransmission threshold, RRC release or RRC re-establishment will not be triggered.

25. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method of any one of claims 1 to 24.

26. A non-transitory computer program product comprising computer-readable program medium code stored thereon, the computer-readable program medium code, when executed by a processor, causing the processor to perform the method of any one of claims 1 to 24.

Images