Methods, user equipment, and non-transitory computer-readable media for wireless communication

Abstract

The present disclosure relates to truncation of packet data units (PDUs) for uplink transmissions. Some aspects of the present disclosure relate to an apparatus and method for a user equipment (UE) to transmit a portion of a packet data unit (PDU) to a base station. A radio link control (RLC) layer of the UE generates the PDU and a truncation indicator, where the truncation indicator can indicate a set of truncation points for the PDU. A medium access control (MAC) layer determines whether an uplink transmission size based on an uplink grant is less than a first number of bytes included in the PDU. In response to determining that the uplink transmission size is less than the first number of bytes, the MAC layer selects a truncation point from the set of truncation points indicated by the truncation indicator and removes at least a portion of the PDU to generate a truncated PDU having a second number of bytes that is less than the uplink transmission size.

Description

Technical Field

[0001] The aspects described generally relate to wireless communication, including the truncation of packet data units (PDUs) used for uplink transmission in wireless networks. Background Technology

[0002] Various wireless networks exist. The 3rd Generation Partnership Project (3GPP) has developed a new radio access technology called fifth-generation (5G) New Radio (NR). 5G wireless technology is designed to adapt to a variety of use cases categorized as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). Exemplary applications may include industrial wireless sensor networks, video surveillance, or wearable devices.

[0003] In a wireless network, User Equipment (UE) can communicate with the base station in the uplink, and the base station can communicate with the UE in the downlink. Channel conditions between the UE and the base station may deteriorate depending on the circumstances. Improving the performance of communication between the UE and the base station when channel conditions deteriorate can be challenging. Summary of the Invention

[0004] Some aspects of this disclosure relate to apparatus and methods for implementing a mechanism for removing a portion of a Packet Data Unit (PDU) based on an uplink transmit size determined by an uplink license to obtain a truncated PDU. In order for a User Equipment (UE) to transmit information to a base station, an uplink license may be sent from the base station to the UE, wherein the uplink license may indicate resource allocation, such as an uplink transmit size. When channel conditions between the UE and the base station deteriorate, the uplink transmit size may be reduced. Therefore, an effective mechanism may be needed to adjust a large-size PDU to obtain a truncated PDU adapted to the uplink transmit size determined by the uplink license.

[0005] Some aspects of this disclosure relate to a method for wireless communication performed by a UE in a wireless network. The UE may store a protocol stack including at least a Radio Link Control (RLC) layer and a Media Access Control (MAC) layer. The method may include generating a PDU and a truncation indicator from the RLC layer of the UE's protocol stack. The truncation indicator may indicate a set of truncation points for the PDU. An instance of a truncation point in this set of truncation points may indicate a Negative Acknowledgment Sequence Number (NACK-SN).

[0006] The method may further include sending a PDU and a truncation indicator from the RLC layer to the MAC layer of the protocol stack. The MAC layer may determine whether the uplink transmit size based on the uplink license is less than the number of first bytes included in the PDU. The MAC layer may also select a truncation point from the set of truncation points indicated by the truncation indicator in response to determining that the uplink transmit size is less than the number of first bytes. The PDU and truncation indicator may be generated by the RLC layer, and the selection of a truncation point from this set of truncation points may be performed by the MAC layer.

[0007] According to some aspects, the MAC layer may remove at least a portion of the PDU to generate a truncated PDU with a second number of bytes less than or equal to the uplink transmit size. The portion of the PDU to be removed may be determined at least based on a selected truncation point. The selection of the truncation point may include choosing a truncation point from a set of truncation points to obtain a truncated PDU with a size closest to the uplink transmit size among the truncation points in this set of truncation points. The PDU may include an ordered sequence of bytes, and the removed portion may include consecutive bytes at the end of the ordered sequence of bytes.

[0008] According to some aspects, the method may further include updating a portion of the truncated PDU by the MAC layer to generate an updated truncated PDU. Subsequently, the method may include sending the updated truncated PDU from the MAC layer to the RLC layer; and transmitting the updated truncated PDU from the RLC layer to a base station of the wireless network. After the PDU is truncated, a truncated state may be indicated to the RLC layer, which can be used to generate the next RLC state PDU to include the discarded portion of the truncated state PDU and the new state.

[0009] According to some aspects, a truncation indicator may be implemented by a truncation point array, wherein the elements of the array indicate the byte positions in an ordered sequence of bytes of the PDU associated with truncation points. In some embodiments, the truncation indicator may also include a list of truncation information for the elements of the truncation point array. In some embodiments, the truncation indicator may be implemented by a bitmap having a first number of bits, wherein the bits of the bitmap correspond to bytes of the PDU, and the bits may be values ​​0 or 1. In some embodiments, the bitmap may be a first bitmap, and the truncation indicator may also include a second bitmap having a first number of bits, wherein the bits of the second bitmap correspond to bytes of the PDU, and the bits have values ​​0 or 1. A truncation point selected from the set of truncation points may be determined by the first bitmap and the second bitmap. In some embodiments, the truncation indicator may also include a list of truncation information for one or more bits in the bitmap.

[0010] Some aspects of this disclosure relate to a UE, including a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The transceiver is configured to enable wireless communication in a wireless network. The memory stores a protocol stack of the UE, wherein the protocol stack includes at least an RLC layer and a MAC layer. The processor is configured to generate a PDU and a truncation indicator by the RLC layer. The truncation indicator indicates a set of truncation points for the PDU. The processor is also configured to transmit the PDU and the truncation indicator from the RLC layer to the MAC layer; and for the MAC layer to determine whether an uplink transmit size based on an uplink license is less than a first number of bytes included in the PDU. In response to determining that the uplink transmit size is less than the first number of bytes, the processor may further be configured to select a truncation point from the set of truncation points indicated by the truncation indicator; and for the MAC layer to remove at least a portion of the PDU to generate a truncated PDU having a second number of bytes less than the uplink transmit size. The portion of the PDU removed may be determined at least based on the selected truncation point.

[0011] Some aspects of this disclosure relate to a non-transitory computer-readable medium storing instructions. When executed by a processor of a UE, instructions stored in the non-transitory computer-readable medium cause the UE to perform various operations. These operations may include generating a PDU and a truncation indicator by the RLC layer of the UE's protocol stack, wherein the truncation indicator indicates a set of truncation points for the PDU; sending the PDU and the truncation indicator from the RLC layer to the MAC layer of the protocol stack; determining by the MAC layer whether an uplink transmit size based on an uplink license is less than a first number of bytes included in the PDU; selecting a truncation point from the set of truncation points indicated by the truncation indicator in response to determining that the uplink transmit size is less than the first number of bytes; and removing at least a portion of the PDU by the MAC layer to generate a truncated PDU having a second number of bytes less than the uplink transmit size, wherein the portion of the PDU removed is determined at least based on the selected truncation point.

[0012] The content of this invention is provided for illustrative purposes only, to provide an understanding of the subject matter described herein. Therefore, the features described above are merely illustrative and should not be construed as narrowing the scope or substance of the subject matter of this disclosure. Other features, aspects, and advantages of this disclosure will become apparent from the following detailed description, the accompanying drawings, and the claims. Attached Figure Description

[0013] The accompanying drawings, which are incorporated herein and form part of this specification, illustrate the present disclosure and, together with the specification, further serve to explain the principles of the disclosure and enable those skilled in the art to make and use the disclosure.

[0014] Figures 1A to 1BA wireless system according to some aspects of this disclosure is shown, the wireless system including user equipment (UE) configured to remove a portion of a packet data unit (PDU) to generate a truncated PDU for uplink transmission.

[0015] Figure 2 A block diagram of a UE for performing the functions described herein is shown, according to some aspects of this disclosure.

[0016] Figure 3 An exemplary process is shown, performed by a UE according to some aspects of this disclosure, to remove a portion of a PDU to generate a truncated PDU for uplink transmission.

[0017] Figures 4A to 4C Additional exemplary procedures are shown, performed by a UE according to some aspects of this disclosure, to remove a portion of a PDU to generate a truncated PDU for uplink transmission.

[0018] Figures 5A to 5B Additional exemplary procedures are shown, performed by a UE according to some aspects of this disclosure, to remove a portion of a PDU to generate a truncated PDU for uplink transmission.

[0019] Figures 6A to 6B Additional exemplary procedures are shown, performed by a UE according to some aspects of this disclosure, to remove a portion of a PDU to generate a truncated PDU for uplink transmission.

[0020] Figures 7A to 7B Additional exemplary procedures are shown, performed by a UE according to some aspects of this disclosure, to remove a portion of a PDU to generate a truncated PDU for uplink transmission.

[0021] Figure 8 It is an exemplary computer system for implementing some aspects or parts of the disclosure provided herein.

[0022] This disclosure is described with reference to the accompanying drawings. In the drawings, the same reference numerals generally denote the same or similarly functional elements. Additionally, the leftmost numeral of the reference numerals generally appears first in the drawings. Detailed Implementation

[0023] User equipment (UE) can generate Packet Data Units (PDUs) for uplink (UL) transmission to a base station of the wireless network. Based on a resource allocation scheme, the UE can receive an uplink grant from the base station, which may indicate the uplink transmission size. When channel conditions deteriorate between the UE and the base station, due to low downlink (DL) bandwidth, the Radio Link Control (RLC) layer may generate PDUs with large sizes, such as exceeding 8188 octets or more. On the other hand, the UL resource allocation for the UE indicated by the UL grant from the base station may be reduced in response to deteriorated channel conditions. When the allocated UL resources do not meet the requirements for transmitting the large-sized PDU, if the UE is able to transmit at least a portion of the PDU, the transmitted portion of the PDU can reduce the recovery time for uplink transmission when the UE enters an area with improved channel conditions. Exemplary use cases may include when a UE exits an elevator or a network congestion area where channel conditions suddenly improve.

[0024] According to some aspects, in order to transmit a portion of the PDU, the UE may truncate the PDU at the uplink media access control (MAC) layer. In some implementations, the RLC layer may generate the PDU and a truncation indicator, wherein the truncation indicator may indicate a set of truncation points for the PDU. The MAC layer may determine whether the uplink transmit size based on the uplink license is less than the number of first bytes included in the PDU. In response to determining that the uplink transmit size is less than the number of first bytes, the MAC layer may select a truncation point from the set of truncation points indicated by the truncation indicator and remove at least a portion of the PDU to generate a truncated PDU having a second number of bytes less than the uplink transmit size. The portion of the PDU to be removed is determined at least based on the selected truncation point.

[0025] According to some aspects, using a truncation indicator that indicates a set of truncation points for the PDU can provide the MAC layer with the flexibility to select the correct size of the truncated PDU. Not any arbitrary byte of the PDU, the truncation points in the set of truncation points can indicate a negative acknowledgment sequence number (NACK-SN). When the RLC layer generates the PDU, it does not know what uplink transmit size can be granted to the UE. The RLC layer can generate a truncation indicator that includes multiple truncation points for the PDU, allowing the MAC layer to dynamically adjust and select the correct truncation point based on the allocated uplink transmit size. In some implementations, the MAC layer can select a truncation point from the set of truncation points to obtain a truncated PDU with a size closest to the uplink transmit size among the truncation points in the set of truncation points.

[0026] According to some aspects, the PDU and truncation indicator can be generated by the RLC layer, which does not process the PDU in real time. Additionally, the selection of the truncation point from the set of truncation points indicated by the truncation indicator can be performed by the MAC layer. Using a truncation indicator with an appropriate specific implementation, such as an array or bitmap, can reduce the computations performed by the MAC during permitted processing time. Even though the RLC performs additional computations to generate the truncation indicator, the RLC can be considered to have no hard limitations. Overall, the computation of the truncation indicator performed by the RLC can improve the real-time response of the MAC and improve the overall performance of the UE in generating truncated PDUs.

[0027] Depending on several aspects, a PDU can be an RLC downlink state PDU. The implementation described herein is applicable to many different wireless systems, such as LTE or NR wireless systems. In some implementations, the RLC layer can generate a PDU smaller than the most recent uplink license for a particular logical channel to avoid truncation. However, to do this, additional communication between the MAC and RLC is required so that the RLC is aware of the uplink transmit size. Therefore, such a method avoids PDU truncation but may introduce additional latency and additional communication overhead.

[0028] According to some aspects, once a PDU such as an RLC state PDU is truncated, there is no way to send the remainder of the RLC DL state PDU because if the first segment is lost or the segment is delivered out of order, the network may interpret that the UE has received the Acknowledgment Mode (AM) RLC PDU up to the Acknowledgment (ACK) sequence number (SN) mentioned in the RLC DL state PDU segment (for that AM RLC entity). To overcome this problem, the MAC layer can notify the RLC of the truncation offset, and the RLC can update the Receive (RX)_Highest_Status status variable and regenerate a new state PDU using the truncation information. The additional overhead between the MAC and RLC for RLC DL state PDU truncation can be eliminated by tracking the RLC state PDU and its segment allocation sequence number and segment information for each segmented RLC state PDU.

[0029] Figures 1A to 1B A wireless system 100 according to some aspects of this disclosure is illustrated, comprising a UE, such as UE 101, configured to remove a portion of a PDU to generate a truncated PDU for uplink transmission. The wireless system 100 is provided for illustrative purposes only and is not intended to limit the disclosed aspects. The wireless system 100 may include, but is not limited to, UE 101, base station 103, and base station 105, all communicatively coupled to core network 110. UE 101 communicates with base station 103 via channel 121 and with base station 105 via channel 123.

[0030] In some examples, wireless system 100 may include one or more of an NR system, an LTE system, a 5G system, or another wireless system. Other network entities, such as network controllers and relay stations, may be present. Wireless system 100 can support a wide range of use cases, such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), ultra-reliable and low-latency communications (URLLC), and enhanced vehicle-to-everything communications (eV2X).

[0031] Depending on some aspects, base stations 103 and 105 can be fixed or mobile stations. Base stations 103 and 105 may also be referred to by other names, such as Base Transceiver System (BTS), Access Point (AP), Transmit / Receive Point (TRP), Evolved Node B (eNB), Next Generation Node B (gNB), 5G Node B (NB), or some other equivalent term. In some examples, base station 103 can be an eNB, while base station 105 can be a gNB. In some examples, base stations 103 and 105 can be interconnected with each other and / or interconnected to other base stations or network nodes in the network via various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) (not shown).

[0032] Depending on some aspects, UE 101 can be fixed or mobile. UE 101 can be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a desktop computer, a cordless phone, a wireless local loop station, a wireless sensor, a tablet computer, a camera, a video surveillance camera, a gaming device, a netbook, an ultrabook, a medical device or equipment, a biometric sensor or device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry such as a smart ring or smart bracelet), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component, a smart meter, industrial manufacturing equipment, a GPS device, an Internet of Things (IoT) device, a machine-type communication (MTC) device, an evolved or enhanced machine-type communication (eMTC) device, or any other suitable device configured to communicate via a wireless medium. For example, MTC and eMTC devices may include robots, drones, location tags, etc.

[0033] According to some aspects, base stations 103 and 105 are communicatively coupled to core network 110. Base station 103 serves cell 102, and base station 105 serves cell 104 contained within cell 102. In some other embodiments, cell 102 may partially overlap with cell 104. Cells 102 and 104 may be macrocells, picocells, femtocells, and / or another type of cell. In contrast, macrocells can cover relatively large geographic areas, such as a radius of several kilometers, while femtocells can cover relatively small geographic areas, such as a home, and picocells cover areas smaller than those covered by macrocells but larger than those covered by femtocells. For example, cell 102 may be a macrocell, while cell 104 may be a picocell or a femtocell. Alternatively, cell 102 may be a picocell, while cell 104 may be a femtocell. In some examples, the geographic area of ​​the cell may shift depending on the location of the mobile base station.

[0034] According to some aspects, base station 103 may have a downlink transmission 122 including resource allocation, which may include an uplink grant 124 and an uplink transmission size 126. The uplink transmission size 126 may specify the allowed size, for example, the number of bytes, that can be transmitted from UE 101 uplink to base station 103. The uplink transmission size 126 may be determined based on the channel conditions of channel 121 or channel 123.

[0035] Depending on some aspects, UE 101 may store a protocol stack including various protocol layers, such as RLC layer 111, MAC layer 113, and more. UE 101 may receive downlink transmissions 122 and determine the allocated resources for uplink transmissions. RLC layer 111 may generate a PDU 112 and a truncation indicator 114 indicating a set of truncation points for the PDU, and send the PDU 112 and truncation indicator 114 to MAC layer 113.

[0036] Depending on some aspects, there may be many different types of PDUs, such as Acknowledgment Mode Data (AMD) PDUs, Unacknowledgment Mode Data (UMD) PDUs, RLC Data PDUs, RLC Status PDUs, or other PDUs. PDU 112 may include various components. Figure 1BAn exemplary PDU 112 as an RLC status PDU is shown. A status PDU may include a negative acknowledgment sequence number (NACK-SN), a NACK range, and segment offset (SO) fields such as SOstart and SOend. The RLC status PDU payload may begin with the first character following the RLC control PDU header, and it may include an ACK_SN and an E1, zero, or more groups of NACK_SNs, E1, E2, and E3, and may include a pair of SOstart and SOend fields or a NACK range field for each NACK_SN. Further details of RLC status PDUs can be found in various technical standards, such as TS 38.322, TS 36.322, etc., which are known to those skilled in the art.

[0037] Based on the uplink transmit size 126, the MAC layer 113 can determine whether the uplink transmit size 126 is less than the number of bytes included in PDU 112. When the uplink transmit size 126 is less than the number of bytes included in PDU 112, the MAC layer 113 can select a truncation point from the set of truncation points indicated by the truncation indicator 114 and remove at least a portion of PDU 112 to generate a truncated PDU 116 having a second number of bytes less than the uplink transmit size 126. The portion of PDU 112 removed is determined at least based on the selected truncation point. The MAC layer 113 can also update a portion of the truncated PDU 116 to generate an updated truncated PDU 118 and send the updated truncated PDU 118 to the RLC layer 111. The RLC layer 111 can also transmit the updated truncated PDU 118 to the base station 103.

[0038] Figure 2 A block diagram of a UE 101 is illustrated, having an antenna panel 217 including one or more antenna elements, such as antenna element 219 coupled to transceiver 203 and controlled by processor 201. Specifically, transceiver 203 may include radio frequency (RF) circuitry 216, baseband transmitting circuitry 212, and baseband receiving circuitry 214. RF circuitry 216 may include multiple parallel RF chains for performing one or more transmit or receive functions, each RF chain being connected to one or more antenna elements in the antenna panel. Furthermore, processor 201 may be communicatively coupled to memory 211, which is further coupled to transceiver 203.

[0039] In some examples, RF circuitry 216 is used by UE 101 to perform measurements of reference signals and to transmit and receive data in the serving cell. Memory 211 may store PDU 112, truncation indicator 114, truncated PDU 116, and updated truncated PDU 118. Furthermore, memory 211 may include a protocol stack comprising various protocols, such as RLC layer 111, MAC layer 113, and more. Memory 211 may include instructions that, when executed by processor 201, perform functions to remove a portion of PDU 112 to generate truncated PDU 116 for uplink transmission. Alternatively, processor 201 may be "hard-coded" to perform the functions described herein.

[0040] According to some aspects, processor 201 can be configured to perform various operations. For example, processor 201 can be configured to generate PDU 112 and truncation indicator 114. Truncation indicator 114 can indicate a set of truncation points for PDU 112. The truncation point in the set of truncation points can indicate a negative acknowledgment sequence number (NACK-SN). PDU 112 and truncation indicator 114 can be generated by the RLC processing path of RLC layer 111. Processor 201 can be configured to send PDU 112 and truncation indicator 114 from RLC layer 111 to MAC layer 113. Processor 201 can be configured to determine by MAC layer 113 whether the uplink transmit size 126 based on uplink license 124 is less than the number of first bytes included in PDU 112. In response to determining that the uplink transmit size is less than the number of first bytes, processor 201 can be configured to select a truncation point from the set of truncation points indicated by truncation indicator 114. The selection of a truncation point from the set of truncation points may be performed by MAC layer 113. Processor 201 may be configured to remove at least a portion of PDU 112 to produce a truncated PDU 116. The portion of PDU 112 to be removed may be determined at least based on the selected truncation point. PDU 112 may include an ordered sequence of bytes, and the removed portion may include consecutive bytes at the end of the ordered sequence of bytes. The truncated PDU 116 may have a second number of bytes less than the uplink transmit size 126. The truncation point from the set of truncation points indicated by truncation indicator 114 is selected such that the truncated PDU 116 has a size that is closest to the uplink transmit size 126 among the truncation points of PDU 112.

[0041] According to some aspects, processor 201 may be configured to update a portion of truncated PDU 116 to generate an updated truncated PDU 118, and transmit the updated truncated PDU 118 from MAC layer 113 to RLC layer 111. Processor 201 may be configured to transmit the updated truncated PDU 118 from RLC layer 111 to base station 103.

[0042] Depending on some aspects, the truncation indicator 114 can be implemented by an array of truncation points, such as Figures 4A to 4C and Figures 5A to 5B As shown in more detail, the elements of the array indicate the byte positions in the ordered sequence of bytes of PDU 112 that are associated with truncation points. In some embodiments, the truncation indicator 114 may also include a list of truncation information for the elements of the truncation point array.

[0043] According to some aspects, the truncation indicator 114 can be implemented by a bitmap having a first number of bits, wherein the bits of the bitmap correspond to bytes of the PDU, as shown by... Figures 6A to 6B and Figures 7A to 7B As shown in more detail. Each bit of the bitmap can have a value of 0 or a value of 1. In some embodiments, the bitmap may be a first bitmap, and the truncation indicator 114 may also include a second bitmap having a first number of bits, wherein the bits of the second bitmap correspond to bytes of the PDU, as shown by... Figures 7A to 7B As shown in more detail. The truncation point selected from the set of truncation points can be determined by a first bitmap and a second bitmap. In some embodiments, the truncation indicator 114 may also include a list of truncation information for bits with a value of 1 in the bitmap, such as those shown by... Figure 4C , Figure 5B and Figure 6B See in more detail.

[0044] Figure 3 An exemplary procedure 300, performed by a UE according to some aspects of this disclosure, is illustrated to remove a portion of a PDU to generate a truncated PDU for uplink transmission. Method 300 can be performed by UE 101, as... Figure 1A or Figure 2 As shown.

[0045] At 301, the RLC layer of the UE's protocol stack can generate PDUs and truncation indicators, where the truncation indicators indicate a set of truncation points for the PDUs. For example, as shown in Figure 1, the RLC layer 111 of the UE 101's protocol stack can generate PDU 112 and truncation indicators 114, where the truncation indicators 114 indicate a set of truncation points for PDU 112.

[0046] At 302, the RLC layer can send the PDU and truncation indicator to the MAC layer of the protocol stack. For example, RLC layer 111 can send PDU 112 and truncation indicator 114 to MAC layer 113.

[0047] At 303, the MAC layer can compare the uplink transmit size with the PDU size to determine whether the uplink transmit size based on the uplink license is less than the number of first bytes included in the PDU. For example, MAC layer 113 can determine whether the uplink transmit size 126 based on the uplink license 124 is less than the number of first bytes included in the PDU 112.

[0048] At 304, in response to determining that the uplink transmit size is less than the number of first bytes, the MAC layer may select a truncation point from the set of truncation points indicated by the truncation indicator. For example, MAC layer 113 may select a truncation point from the set of truncation points indicated by truncation indicator 114.

[0049] At 305, the MAC layer can remove at least a portion of the PDU to generate a truncated PDU with a second byte number smaller than the uplink transmit size, wherein the portion of the PDU to be removed is determined at least based on a selected truncation point. For example, MAC layer 113 can remove at least a portion of PDU 112 to generate a truncated PDU 116 with a second byte number smaller than the uplink transmit size, wherein the portion of PDU 112 to be removed is determined at least based on a selected truncation point.

[0050] At 306, the MAC layer can update a portion of the truncated PDU to generate an updated truncated PDU. For example, MAC layer 113 can update a portion of the truncated PDU 116 to generate an updated truncated PDU 118. The truncated PDU 116 is obtained by removing a portion of PDU 112, and the truncated PDU 116 is the remainder of PDU 112. The updated truncated PDU 118 is obtained by updating a portion of the truncated PDU 116 (instead of the original PDU 112).

[0051] At 307, the MAC layer can send the updated truncated PDU to the RLC layer. For example, MAC layer 113 can send the updated truncated PDU 118 to RLC layer 111.

[0052] At 308, the RLC layer can transmit the updated truncated PDU to the base station of the wireless network. For example, RLC layer 111 can transmit the updated truncated PDU 118 to base station 103. MAC layer 113 can transmit a truncated RLC status PDU to the RLC and indicate the truncated status, and the RLC will adjust the status variable (RX_Highest_Status).

[0053] Process 300 can be implemented with more details, as Figures 4A to 4C , Figures 5A to 5B , Figures 6A to 6B ,and Figures 7A to 7B The process shown is 400, 500, 600, or 700. In Figures 4A to 4C , Figures 5A to 5B , Figures 6A to 6B ,and Figures 7A to 7B There exists Figure 3 Some additional operations are not shown in the diagram. Similarly, in Figure 3 There are no in Figures 4A to 4C , Figures 5A to 5B , Figures 6A to 6B ,and Figures 7A to 7B Some of the operations shown are illustrated in the diagram. Those skilled in the art can select the operations to be performed for a specific application based on the illustrated procedures.

[0054] Processes 400, 500, 600, or 700 may share many common operations, and they may differ in the details of the specific implementation of the cutoff indicator at the operation used for 301. The operations used for 304, 305, and 306 may also differ depending on the specific implementation of the cutoff indicator at 301. Further details are provided below for the operations performed at 304, 305, and 306, which together form process 310.

[0055] Figures 4A to 4C Additional exemplary procedure 400, performed by UE 101 according to some aspects of this disclosure, is shown to remove a portion of a PDU to generate a truncated PDU for uplink transmission. Procedure 400 may be an example of procedure 300 with more details. In some embodiments, UE 101 may remove a portion of the PDU based on a selected truncation point indicated by a truncation indicator, wherein the truncation indicator is implemented by an array of truncation points or a bitmap. For procedure 400, PDU 112 is an RLC-state PDU, such as... Figure 1B As shown, it includes fields such as NACK-SN, SN, SOstart, SOend, E1, E2, E3, and more. The RLC status PDU can also be called an RLC DL status PDU. Procedure 400 can also be applied to other PDUs.

[0056] Process 400 begins at 401. At 401, the RLC can initiate operations. At 402, the RLC can test whether the conditions are met to construct the RLC state PDU. Afterward, process 400 proceeds to the operations shown in process 300.

[0057] In 301, the RLC layer can generate RLC state PDUs and truncation indicators, where the truncation indicators specify a set of cutoff points for the PDUs. The truncation indicators can be implemented using one or more arrays, one or more bitmaps, one or more lists, or some other data structure. For example... Figure 4B As shown, the truncation indicator can be implemented by a truncation point array, a truncation offset (TO) array, and the elements of the array indicate the byte positions in the ordered sequence of bytes of the PDU that are associated with the truncation point (TP). Figure 4C As shown, in addition to the list of truncation information (TI) for the elements of the truncation point array, truncation indicators can also be implemented by the array. The output of the operation performed at 301 can be provided to the operations performed at 302 and 307.

[0058] At 302, the RLC layer can send the PDU and truncation indicator to the MAC layer. At 303, the MAC layer can compare the uplink transmit size with the PDU size to determine whether the uplink transmit size based on uplink licensing is less than the number of first bytes included in the PDU.

[0059] At 404, in response to determining that the uplink transmit size is less than the first byte number, the MAC layer may select a truncation point from the set of truncation points indicated by the truncation indicator. In some embodiments, the MAC layer may find the closest TO in the TO array that fits the uplink transmit size. The PDU may include an ordered sequence of bytes, and the MAC layer may find the closest TO in the TO array in descending order based on the ordered sequence of bytes in the PDU.

[0060] At 405, the MAC layer may remove at least a portion of the PDU to generate a truncated PDU with a second number of bytes smaller than the uplink transmit size, wherein the portion of the PDU to be removed is determined at least based on a selected truncation point. In some implementations, the MAC layer may read truncation information (TI) corresponding to a TO found in the TO array and generate a truncated PDU.

[0061] At 406, the MAC layer can update a portion of the truncated PDU to generate an updated truncated PDU. Operations implemented at 404, 405, and 406 are described below. Figure 3 The process 310 is shown in the diagram. The operation of process 310 stops at 407, and the result of the operation is passed to the operation at 307.

[0062] At 307, the MAC layer can send the updated truncated PDU to the RLC layer. Then, process 400 continues at the RLC layer. At 408, the RLC layer can determine if the PDU has been truncated. If it is determined that the PDU has been truncated, then at 409, the RLC layer can update the RLC state variables accordingly. The RLC layer can also transmit the updated truncated PDU to the base station of the wireless network. At 411, RLC operation stops.

[0063] like Figure 4B As shown, the RLC provides a TO array 413 for the RLC state PDU 412, where PDU 412 is an implementation of PDU 112. The size of the TO array 413 is determined by multiplying the number of bits required for the maximum RLC state PDU size by the number of TO entries. In some examples, the RLC state PDU size is 9000 bytes, where each byte can have a 15-bit address. The TO array size can be 15 times the number of TO entries in bits, where each entry in the TO array is a binary address of a byte in the PDU. For each valid cutoff point in the RLC state PDU 412, the RLC can add a TO entry in the TO array 413. For example, a TO entry can be added after each 'N'NACK SN block based on the RLC state PDU 412. The TO array 413 has three entries corresponding to octet 3, octet 6, and octet 14. The TO array 413 helps the MAC layer find the valid cutoff points set by the RLC.

[0064] In some implementations, when using TO array 413 to implement the truncation indicator, no changes are required from the RLC. The truncation point is determined in the RLC by the "N" NACK SN block. Alternatively, additional computation in the MAC can be used to determine the valid NACK_SN to update the ACK_SN in the first 3 octets of the RLC state PDU. A fixed number of truncation points are determined by the RLC based on the RLC DL state PDU size.

[0065] like Figure 4C As shown, the RLC provides a TO array 413. Additionally, the RLC provides a truncation information (TI) array, which includes the ACK-SN value and an E1 bit offset for modification from the current TP. The TI array includes elements 414, 415, and 416, corresponding to three entries in the TO array 413.

[0066] In some implementations, the TO array 413 can be implemented in memory accessible by the MAC layer, and the TI array can be stored in a Double Data Rate (DDR) Synchronous Dynamic Random Access Memory (SDRAM) device. In some implementations, for an additional TI array including the ACK_SN and the E1 bit offset to be updated, a small change from the RLC is required. The RLC determines the cutoff point and TI, and the MAC layer does not require any additional processing to find the cutoff point and NACK SN for updating the ACK SN.

[0067] Figures 5A to 5B An additional exemplary procedure 500, performed by UE 101 according to some aspects of this disclosure, is shown to remove a portion of the PDU to generate a truncated PDU for uplink transmission. Procedure 500 may be an example of procedure 300 with more details.

[0068] In some implementations, UE 101 may remove a portion of the PDU based on a selected truncation point indicated by a truncation indicator, wherein the truncation indicator is implemented by a byte offset (BO) array used to indicate the truncation point. Figure 5A As shown, the RLS state PDU 512 can have 53 octets. A byte offset (BO) array 513 can be used to represent a set of truncation points. As shown, the BO array 513 can contain three elements, corresponding to three truncation points at octet 6, octet 24, and octet 45. The elements of the BO array 513 can include E2, E3, and NSN bits. The truncation of the RLS state PDU 512 can be fully processed by the MAC layer using the E2, E3, and NSN bits.

[0069] In some implementation schemes, such as Figure 5B As shown, process 500 can also describe Figure 4A The process 310 is implemented by operations performed at 514, 515, 516, 504 and 505, which are described in detail below.

[0070] At 514, the MAC layer finds the nearest byte offset (BO) in the BO array adapted to the UL transmit size. At 515, the MAC layer reads three pairs of E2, E3, and NSN bits. At 516, the MAC layer tests whether the NSN bit is set. If the NSN bit is not set, the MAC layer can loop back to the operation at 514. If the NSN bit is set, at 517, the MAC layer finds the precise cutoff point from the new NACK-SN block adapted to the UL transmit size. In some examples, at SOend, the MAC layer updates the E3 and E1 bits of the current NACK SN block and updates ACK_SN with the NACK SN or the subsequent new NACK SN. At the NACK range, the MAC layer updates the E1 bit of the current NACK SN block and updates ACK_SN with the subsequent new NACK SN. At the new NACK SN block, the MAC layer updates the E1 bit of the previous NACK SN block and updates ACK_SN with the current NACK SN. In 518, the MAC layer can generate truncated PDUs, such as RLC_STATUS_PDU TRUNCATED.

[0071] Figures 6A to 6B An additional exemplary procedure 600, performed by UE 101 according to some aspects of this disclosure, is shown to remove a portion of the PDU to generate a truncated PDU for uplink transmission. Procedure 500 may be an example of procedure 300 with more details.

[0072] In some implementation schemes, such as Figure 6A As shown, UE 101 can remove a portion of PDU 612 based on a selected truncation point indicated by a truncation indicator, where the truncation indicator is implemented by a truncation point (TP) bitmap 613. The RLC provides a bitmap 613 with a size equal to the RLC state PDU 612 in bits. For example, when the RLC state PDU size is 9000 bytes, bitmap 613 has a size of 1125 bytes. TP bitmap 613 helps the MAC layer find a valid TP determined by the RLC. Bitmap 613 also includes a truncation information (TI) array with one or more elements, where each element corresponds to a bit set to the value 1. For example, TI array element 614 corresponds to bit position 3 with a value of 1, TI array element 615 corresponds to bit position 6 with a value of 1, and TI array element 616 corresponds to bit position 14 with a value of 1. Array elements 613, 614 and 615 may include the ACK_SN value for modification from the current truncation point, the values ​​of the E1, E2 and E3 bit offsets, and optional byte offsets for MAC layer truncation of RLC state PDUs.

[0073] In some implementation schemes, such as Figure 6B As shown, process 600 can also describe Figure 4A The process 310 is implemented through the operations performed at 604, 605, 615 and 606 as described below.

[0074] At 604, the MAC layer finds the nearest truncation point at the nearest bit set in the TP bitmap adapted to the UL transmit size. At 605, the MAC layer reads the TI corresponding to the TP bit set in the bitmap. The additional BO field in the TI determines the exact TP of the RLC status PDU. At 606, the MAC layer generates a truncated PDU, for example, RLC_STATUS_PDU TRUNCATED. At 607, the MAC layer updates ACK_SN, E1, E2, and E3 with the corresponding byte and bit offset.

[0075] In the implementation, only limited processing is performed at the MAC layer to truncate the RLC state PDU to find a lower truncation point from the licensed size allocated to the RLC state PDU. The MAC layer can also modify the RLC state PDU from truncation information such as ACK_SN, E1, E2, and E3 at the corresponding byte and bit offsets.

[0076] Figures 7A to 7B An additional exemplary procedure 700, performed by UE 101 according to some aspects of this disclosure, is shown to remove a portion of the PDU to generate a truncated PDU for uplink transmission. Procedure 700 may be an example of procedure 300 with more details.

[0077] In some implementation schemes, such as Figure 7A As shown, UE 101 can remove a portion of PDU 712 based on a selected truncation point indicated by a truncation indicator, where the truncation indicator is implemented by bitmaps 713 and 714. RLC provides bitmaps 713 and 714 with dimensions equal to the RLC state PDU 712 in bits. Bitmap 713 is an E1 bitmap. For each E1 bit set in the octet of the RLC state PDU, it can be configured as follows: Figure 7A The corresponding bits in bitmap 713 are shown. Bitmap 714 is an NSN bitmap. For each new NACK_SN encoded in the octet of the RLC state PDU, the corresponding bit in the NSN bitmap can be set to 1. For example, for consecutive NACK_SNs in RLC state PDU 712, the bit can be set to 1. Both bitmap 713 and bitmap 714 can be generated by RLC and stored in MAC layer accessible memory.

[0078] In some implementation schemes, such as Figure 7B As shown, process 700 may also describe process 310 implemented by the operations performed at 711, 712, 713, 714, 715, 716 and 717 as described below.

[0079] At 711, the MAC layer finds the closest bit set in the E1 bitmap. At 712, the MAC layer tests whether the corresponding new NACK SN bit is set in the NSN bitmap. If the test result is negative, at 713, the MAC layer finds the closest bit set in the NSN bitmap. At 714, the MAC layer finds the truncation point at the new NACK_SN block. At 715, the MAC layer can jump to the previous E1 octet in the RLC status PDU via the E1 bitmap and set the E1 bit to 0. At 716, the MAC layer reads NACK_SN and updates ACK_SN. At 717, the MAC layer generates RLC_STATUS_PDU TRUNCATED.

[0080] One or more computer systems, such as Figure 8 The computer system 800 shown implements these aspects. The computer system 800 can be any computer capable of performing the functions described herein, such as... Figure 1A and Figure 2 The UE 101, base station 103, or base station 105 are shown. The computer system 800 includes one or more processors (also referred to as a central processing unit or CPU), such as processor 804. Processor 804 is connected to communication infrastructure 806 (e.g., a bus). The computer system 800 also includes user input / output devices 803, such as a monitor, keyboard, pointing device, etc., that communicate with the communication infrastructure 806 via user input / output interface 802. The computer system 800 also includes main memory or primary memory 808, such as random access memory (RAM). Main memory 808 may include one or more levels of cache. Main memory 808 stores control logic (e.g., computer software) and / or data.

[0081] The computer system 800 may also include one or more auxiliary storage devices or memories 810. Auxiliary storage 810 may include, for example, a hard disk drive 812 and / or a removable storage device or drive 814. The removable storage drive 814 may be a floppy disk drive, a magnetic tape drive, an optical disk drive, an optical storage device, a magnetic tape backup device, and / or any other storage device / drive.

[0082] Removable storage drive 814 can interact with removable storage unit 818. Removable storage unit 818 includes a computer-usable or readable storage device on which computer software (control logic components) and / or data are stored. Removable storage unit 818 can be a floppy disk, magnetic tape, optical disc, DVD, optical storage disk, and / or any other computer data storage device. Removable storage drive 814 reads from and / or writes to removable storage unit 818 in a well-known manner.

[0083] According to some aspects, auxiliary storage 810 may include other means, tools, or other methods for allowing computer programs and / or other instructions and / or data to be accessed by computer system 800. Such means, tools, or other methods may include, for example, removable storage unit 822 and interface 820. Examples of removable storage unit 822 and interface 820 may include program boxes and box interfaces (such as those found in video game devices), removable memory chips (such as EPROM or PROM) and associated sockets, memory sticks and USB ports, memory cards and associated memory card slots, and / or any other removable storage unit and associated interface.

[0084] In some examples, main memory 808, removable storage unit 818, and removable storage unit 822 can store instructions that, when executed by processor 804, cause processor 804 to perform actions targeting the UE or base station (e.g., such as...). Figure 1A and Figure 2 The operation of UE 101, base station 103, or base station 105 shown. In some examples, the operation includes... Figure 3 , Figures 4A to 4C , Figures 5A to 5B , Figures 6A to 6B as well as Figures 7A to 7B The operations illustrated and described in the example.

[0085] Computer system 800 may also include a communication or network interface 824. Communication interface 824 enables computer system 800 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referred to by reference numeral 828). For example, communication interface 824 may allow computer system 800 to communicate with remote device 828 via communication path 826, which may be wired and / or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic and / or data may be transmitted to and from computer system 800 via communication path 826. Operation of communication interface 824 may be performed by a wireless controller and / or a cellular controller. The cellular controller may be a separate controller to manage communications according to different wireless communication technologies. The operations in the foregoing aspects can be implemented in various configurations and architectures. Therefore, some or all of the operations in the foregoing aspects may be performed in hardware, software, or both. In some aspects, tangible, non-transitory devices or articles of art include tangible, non-transitory computer-usable or readable media on which control logic components (software) are stored, also referred to herein as computer program products or program storage devices. This includes, but is not limited to, computer system 800, main memory 808, secondary memory 810, and removable storage units 818 and 822, and tangible articles embodying any combination thereof. Such control logic, when executed by one or more data processing devices (such as computer system 800), causes such data processing devices to operate as described herein.

[0086] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the art how to use [other methods]. Figure 8 Other data processing devices, computer systems, and / or computer architectures besides those shown may be used to make and use aspects of this disclosure. In particular, aspects may operate in conjunction with software, hardware, and / or operating system implementations other than those described herein.

[0087] It should be understood that the Detailed Description section, rather than the Summary and Abstract section, is intended to be used to interpret the claims. The Summary and Abstract section may set forth one or more, but not all, exemplary aspects of this disclosure as contemplated by the inventors, and is therefore not intended to limit this disclosure or the appended claims in any way.

[0088] Although this disclosure has been described herein with reference to exemplary aspects of exemplary fields and applications, it should be understood that this disclosure is not limited thereto. Other aspects and modifications are possible and are within the scope and spirit of this disclosure. For example, and without limiting the generality of this paragraph, the aspects are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. Furthermore, the aspects (whether explicitly described herein or not) have significant utility for fields and applications beyond those illustrated herein.

[0089] The aspects have been described here using functional building blocks that illustrate specific implementations of functions and their relationships. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries can be defined as long as the specified functions and relationships (or their equivalents) are performed appropriately. Furthermore, alternative aspects may perform functional blocks, steps, operations, methods, etc., in a different order than that described herein.

[0090] References to “an implementation,” “implementation,” “exemplary implementation,” or similar phrases herein indicate that the described implementation may include specific feature structures, structures, or characteristics, but each implementation may not necessarily include such feature structures, structures, or characteristics. Furthermore, such terminology does not necessarily refer to the same implementation. Additionally, when a specific feature, structure, or characteristic is described in connection with an implementation, whether or not it is explicitly mentioned or described herein, the integration of such feature, structure, or characteristic into other aspects is within the knowledge of a person skilled in the art.

[0091] The breadth and scope of this disclosure should not be limited by any of the foregoing exemplary aspects, but should be defined solely by the following claims and their equivalents.

[0092] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, such entities should implement and adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and / or use change. Personal information from users should be collected for the entity's lawful and reasonable purposes and not shared or sold outside of these lawful uses. Furthermore, such collection / sharing should only occur upon receipt of the user's informed consent. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to such personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party evaluations to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including specific considerations regarding jurisdiction. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Transfer and Accountability Act (HIPAA); while in other countries, health data may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

Claims

1. A method for wireless communication performed by a user equipment (UE) in a wireless network, the method comprising: The Radio Link Control (RLC) layer of the UE's protocol stack generates Packet Data Units (PDUs) and truncation indicators, wherein the truncation indicators indicate a set of truncation points for the PDUs generated by the RLC layer of the UE, wherein the truncation indicators are implemented as a data structure including a bitmap or array, the bitmap or array being different from the PDU, and the bitmap or array having a length determined based on the number of bytes in the PDU, and the elements of the bitmap or array indicating the byte positions within the bytes of the PDU associated with the truncation points; The RLC layer sends the PDU and the truncation indicator to the Media Access Control (MAC) layer of the protocol stack; The MAC layer determines whether the uplink transmit size based on the uplink license is less than the number of the first bytes included in the PDU; In response to determining that the uplink transmit size is less than the first byte number, a truncation point is selected from the set of truncation points indicated by the truncation indicator; and At least a portion of the PDU is removed by the MAC layer to generate a truncated PDU with a second number of bytes smaller than the uplink transmit size, wherein the portion of the PDU to be removed is determined at least based on the selected truncation point.

2. The method according to claim 1, further comprising: The MAC layer updates a portion of the truncated PDU to generate an updated truncated PDU; The updated truncated PDU is sent from the MAC layer to the RLC layer; The updated truncated PDU is transmitted from the RLC layer to the base station of the wireless network; and The RLC layer forms the next RLC state PDU for transmission to the base station.

3. The method of claim 1, wherein the cutoff point in the set of cutoff points indicates a negative acknowledgment sequence number (NACK-SN) block.

4. The method of claim 1, wherein selecting the cutoff point comprises selecting the cutoff point from the set of cutoff points to obtain the truncated PDU having a size closest to the uplink transmit size among the set of cutoff points of the PDU.

5. The method of claim 1, wherein the PDU comprises an ordered sequence of bytes, and the portion of the PDU to be removed comprises consecutive bytes at the end of the ordered sequence of bytes.

6. The method of claim 5, wherein the data structure is implemented by an array of truncation points, and the elements of the array indicate the byte positions in the ordered sequence of bytes associated with the truncation points.

7. The method of claim 6, wherein the data structure further comprises a list of truncation information for the elements of the array of the truncation points.

8. The method of claim 5, wherein the data structure is implemented by a bitmap having a first number of bits, wherein the bits of the bitmap correspond to bytes of the PDU, and the bits have a value of 0 or a value of 1.

9. The method of claim 8, wherein the bitmap is a first bitmap, and the data structure further comprises a second bitmap having the first number of bits, wherein the bits of the second bitmap correspond to bytes of the PDU, the bits having a value of 0 or a value of 1, and wherein the truncation point selected from the set of truncation points is determined by the first bitmap and the second bitmap.

10. The method of claim 8, wherein the data structure further comprises a list of truncation information for bits with value 1 in the bitmap.

11. The method of claim 1, wherein the PDU and the truncation indicator are generated by the RLC layer, and the selection of the truncation point in the set of truncation points is performed by the MAC layer.

12. A user equipment (UE) for wireless communication, comprising: A transceiver configured to enable wireless communication in a wireless network; The memory stores the protocol stack of the UE, wherein the protocol stack includes at least a radio link control (RLC) layer and a media access control (MAC) layer; as well as A processor, communicatively coupled to the transceiver and the memory, and configured to: The RLC layer generates Packet Data Units (PDUs) and truncation indicators, wherein the truncation indicators indicate a set of truncation points for the PDUs generated by the RLC layer of the UE, wherein the truncation indicators are implemented as a data structure including a bitmap or array, the bitmap or array being different from the PDU, and the bitmap or array having a length determined based on the number of bytes in the PDU, and the elements of the bitmap or array indicating the byte positions within the bytes of the PDU associated with the truncation points; The RLC layer sends the PDU and the truncation indicator to the MAC layer; The MAC layer determines whether the uplink transmit size based on the uplink license is less than the number of the first bytes included in the PDU; In response to determining that the uplink transmit size is less than the first byte number, a truncation point is selected from the set of truncation points indicated by the truncation indicator; and At least a portion of the PDU is removed by the MAC layer to generate a truncated PDU with a second number of bytes smaller than the uplink transmit size, wherein the portion of the PDU to be removed is determined at least based on the selected truncation point.

13. The UE of claim 12, wherein the processor is further configured to: The MAC layer updates a portion of the truncated PDU to generate an updated truncated PDU; The updated truncated PDU is sent from the MAC layer to the RLC layer; and The updated truncated PDU is transmitted from the RLC layer to the base station of the wireless network.

14. The UE of claim 12, wherein the processor is further configured to select one of the set of cutoff points to obtain the truncated PDU having a size closest to the uplink transmit size among the set of cutoff points of the PDU.

15. The UE of claim 12, wherein the PDU comprises an ordered sequence of bytes, and the portion of the PDU that is removed comprises consecutive bytes at the end of the ordered sequence of bytes.

16. The UE of claim 15, wherein the data structure is implemented by an array of truncation points, and the elements of the array indicate the byte positions in the ordered sequence of bytes associated with the truncation points.

17. The UE of claim 15, wherein the data structure is implemented by a bitmap having a first number of bits, wherein the bits of the bitmap correspond to bytes of the PDU, and the bits have a value of 0 or a value of 1.

18. The UE of claim 12, wherein the PDU and the truncation indicator are generated by the RLC layer, and the selection of the truncation point in the set of truncation points is performed by the MAC layer.

19. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a user equipment (UE), cause the UE to perform operations, the operations including: The Radio Link Control (RLC) layer of the UE's protocol stack generates Packet Data Units (PDUs) and truncation indicators, wherein the truncation indicators indicate a set of truncation points for the PDUs generated by the RLC layer of the UE, wherein the truncation indicators are implemented as a data structure including a bitmap or array, the bitmap or array being different from the PDU, and the bitmap or array having a length determined based on the number of bytes in the PDU, and the elements of the bitmap or array indicating the byte positions within the bytes of the PDU associated with the truncation points; The RLC layer sends the PDU and the truncation indicator to the Media Access Control (MAC) layer of the protocol stack; The MAC layer determines whether the uplink transmit size based on the uplink license is less than the number of the first bytes included in the PDU; In response to determining that the uplink transmit size is less than the first byte number, a truncation point is selected from the set of truncation points indicated by the truncation indicator; and At least a portion of the PDU is removed by the MAC layer to generate a truncated PDU with a second number of bytes smaller than the uplink transmit size, wherein the portion of the PDU to be removed is determined at least based on the selected truncation point.

20. The non-transitory computer-readable medium of claim 19, further comprising: The MAC layer updates a portion of the truncated PDU to generate an updated truncated PDU; The updated truncated PDU is sent from the MAC layer to the RLC layer; and The updated truncated PDU is transmitted from the RLC layer to the base station of the wireless network.

Images