Determining data transmission preemption
By determining data transmission preemption and managing hybrid automatic repeat request processes, the method addresses the issue of data transmission in wireless communications by identifying and handling overlapping uplink grants and hybrid automatic repeat processes, ensuring efficient and efficient data transmission.
Patent Information
- Application Number
- CN202411226703.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-09-23
- Filing Date
- 2020-09-17
- Publication Date
- 2024-12-06
AI Technical Summary
Data transmission contention occurs in wireless communication networks, leading to issues with data preemption and inefficient handling of hybrid automatic repeat request processes.
Methods and apparatuses determine data transmission preemption by identifying when a first data transmission is preempted by a second data transmission, and in response, do not generate a transport block for the first uplink grant and flush the associated hybrid automatic repeat request buffer.
This approach effectively manages data transmission preemption, ensuring efficient use of resources and preventing data loss by handling overlapping uplink grants and hybrid automatic repeat request processes.
Smart Images

Figure CN119094090A_ABST
Abstract
Description
[0001] This application is a divisional application of an application which entered the Chinese national phase on March 10, 2022, with PCT application number PCT / IB2020 / 058647, international application date September 17, 2020, Chinese application number 202080063943.2, and invention name “Determining Data Transmission Preemption”.
[0002] This application claims priority to U.S. patent application serial number 62 / 860,689, filed on September 23, 2019 by Joachim Loehr, entitled “APPARATUSES, METHODS, AND SYSTEMS FOR DETAILED UE BEHAVIOR FOR INTRA-UE PRIORITIZATION,” which is incorporated herein by reference in its entirety. Technical Field
[0003] The subject matter disclosed herein relates generally to wireless communications, and more particularly to determining data transmission preemption. Background Art
[0004] The following abbreviations are defined herein, at least some of which are referenced in the following description: 3rd Generation Partnership Project ("3GPP"), Fifth Generation ("5G"), NRQoS of V2X communication ("5QI / PQI"), authentication, authorization and accounting ("AAA"), acknowledgement ("ACK"), application function ("AF"), authentication and key agreement ("AKA"), aggregation level ("AL"), acknowledgement mode ("AM"), access and mobility management function ("AMF"), angle of arrival ("AoA"), angle of departure ("AoD"), access point ("AP"), application server ("AS"), application service provider ("ASP"), autonomous uplink ("AUL"), authentication server function ("AUSF"), authentication token ("AUTN"), background data ("BD"), background data transfer ("BDT"), beam failure Fault Detection (“BFD”), Beam Fault Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Contention-Based Random Access (“CBRA”), Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Configuration Configured Grant ("CG"), Closed Loop ("CL"), Coordinated Multipoint ("CoMP"), Channel Occupancy Time ("COT"), Cyclic Prefix ("CP"), Cyclic Redundancy Check ("CRC"), Configuration Scheduling ("CS"), Channel State Information ("CSI"), Channel State Information-Reference Signal ("CSI-RS"), Common Search Space ("CSS"), Control Resource Set ("CORESET"), Discrete Fourier Transform Spread ("DFTS"), Dual Connectivity ("DC"), Downlink Control Information ("DCI"), Downlink Feedback Information ("DFI"), Dynamic Grant ("DG"), Downlink ("DL"), Demodulation Reference Signal ("DMRS"), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Dedicated Short Range Communication (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”), Effective Isotropic Radiated Power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), Framework Based Equipment (“FBE”), Frequency Division Duplexing (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Codes (“FD-OCC”), Frequency Range 1–6Sub-GHz bands and / or 410 MHz to 7125 MHz (“FR1”), Frequency range 2–24.25 GHz to 52.6 GHz (“FR2”), Generic Geographic Area Descriptor (“GAD”), Guaranteed Bit Rate (“GBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), General Public Subscription Identifier (“GPSI”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hashed Expected Response (“HXRES”), Identity or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Key Management Function (“KMF”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), License Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network ( "LAN"), Load Based Equipment ("LBE"), Listen Before Talk ("LBT"), Logical Channel ("LCH"), Logical Channel Group ("LCG"), Logical Channel Priority ("LCP"), Log Likelihood Ratio ("LLR"), Long Term Evolution ("LTE"), Multiple Access ("MA"), Medium Access Control ("MAC"), Multimedia Broadcast Multicast Service ("MBMS"), Maximum Bit Rate ("MBR"), Minimum Communication Range ("MCR"), Modulation and Coding Scheme ("MCS"), Master Information Block ("MIB"), Multimedia Internet Keying ("MIKEY"), Multiple Input Multiple Output ("MI 5G), Mobile Entity (“MME”), Mobile Network Operator (“MNO”), Mobile Originated (“MO”), Massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine Type Communication (“MTC”), Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Negative Acknowledgement (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Exposure Function (“NEF”), Network Function (“NF”), Next Generation (“NG”), NG 5GS-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), Unlicensed NR (“NR-U”), Network Repository Function (“NRF”), Network Scheduling Mode (“NS Mode”) (e.g., Network Scheduling Mode for V2X Communication Resource Allocation – Mode-1 in NR V2X and Mode-3 in LTE V2X), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operations, Administration and Maintenance System or Operation and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Open Loop (“OL”), Other System Information (“OSI”), Power Angular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE-to-UE Interface (“PC5”), Policy and Charging Control (“PCC”), Primary Slice area ("PCell"), Policy Control Function ("PCF"), Physical Cell Identity ("PCI"), Physical Downlink Control Channel ("PDCCH"), Packet Data Convergence Protocol ("PDCP"), Packet Data Network Gateway ("PGW"), Physical Downlink Shared Channel ("PDSCH"), Mode Division Multiple Access ("PDMA"), Packet Data Unit ("PDU"), Physical Hybrid ARQ Indicator Channel ("PHICH"), Power Headroom ("PH"), Power Headroom Report ("PHR"), Physical Layer ("PHY"), Public Land Mobile Network ("PLMN"), PC5 QoS Class Identifier ("PQI"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Proximity Service ("ProSe"), Positioning Reference Signal ("PRS"), Physical Sidelink Control Channel ("PSCCH"), Primary Secondary Cell ("PSCell"), Physical Sidelink Feedback Control Channel ("PSFCH"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), QoS Class Identifier ("QCI"), Quasi Co-location ("QCL"), Quality of Service ("QoS"), Quadrature Phase Shift Keying ("QPSK"), Registration Area ("RA"), RARNTI ("RA-RNTI"), Radio Access Network ("RAN"), Random ("RAND"), Radio Access Technology ("RAT"), Serving RAT ("RAT-1") (serving Uu), Other RAT ("RAT-2") (not serving Uu), Random Access Procedure ("RACH"), Random Access Preamble Identifier ("RAPID"), Random Access Response ("RAR"), Resource Block Assignment ("RBA"), Resource Element Group ("REG"), Radio Link Control ("RLC"), RLC Acknowledgement Mode ("RLC-AM"), RLC Unacknowledged Unknown Mode / Transparent Mode ("RLC-UM / TM"), Radio Link Failure ("RLF"), Radio Link Monitoring ("RLM"), Radio Network Temporary Identifier ("RNTI"), Reference Signal ("RS"), Remaining Minimum System Information ("RMSI"), Radio Resource Control ("RRC"), Radio Resource Management ("RRM"), Resource Extended Multiple Access ("RSMA"), Reference Signal Received Power ("RSRP"), Received Signal Strength Indicator ("RSSI"), Round Trip Time ("RTT"), Reception ("RX"), Sparse Code Multiple Access ("SCMA"), Scheduling Request ("SR"), Sounding Reference Signal ("SRS"), Single Carrier Frequency Division Multiple Access ("SC-FDMA"), Secondary Cell ("SCell"), Secondary Cell Group ("SCG"), Shared Channel ("SCH"), Sidelink Control Information ("SCI"), Subcarrier Spacing ("SCS"), Service Data Unit ("SDU"), Security Anchor Function ("SEAF"), Sidelink Feedback Content Information ("SFCI"), Serving Gateway ("SGW"), System Information Block ("SIB"), System Information Block Type 1 ("SIB1"), System Information Block Type 2 ("SIB2"), Subscriber Identity / Identification Module (“SIM”), Signal-to-Interference-plus-Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signal (“SLSS”), Session Management (“SM”), Session Management Function (“SMF”), Special Cell (“SpCell”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSI, Subscription Hidden Identifier ("SUCI"), Scheduled User Equipment ("SUE"), Supplementary Uplink ("SUL"), Subscriber Permanent Identifier ("SUPI"), Tracking Area ("TA"), TA Identifier ("TAI"), TA Update ("TAU"), Timing Alignment Timer ("TAT"), Transport Block ("TB"), Transport Block Size ("TBS"), Time Division Duplex (TDD) “TDD”, time division multiplexing (“TDM”), time division orthogonal cover code (“TD-OCC”), temporary mobile subscriber identity (“TMSI”), time of flight (“ToF”), transmit power control (“TPC”), transmission reception point (“TRP”), transmission time interval (“TTI”), transmission (“TX”), uplink control information (“UCI”), unified data management function (“UDM”), unified data repository (“UDR”), user entity / equipment (mobile terminal) (“UE”) (e.g., V2X UE), UE Autonomous Mode (UE autonomously selects V2X communication resources - for example, Mode 2 in NRV2X and Mode 4 in LTE V2X. The UE autonomous selection may or may not be based on resource sensing operations), Uplink ("UL"), UL SCH ("UL-SCH"), Universal Mobile Telecommunications System ("UMTS"), User Plane ("UP"), UP Function ("UPF"), Uplink Pilot Time Slot ("UpPTS"), Ultra-Reliable and Low Latency Communication ("URLLC"), UE Routing Selection Policy ("URSP"), Vehicle-to-Vehicle ("V2V"), Vehicle-to-Everything ("V2X"), V2X UE (e.g., UE capable of vehicular communications using 3GPP protocols), Access AMF ("vAMF"), V2X Encryption Key ("VEK"), V2X Group Key ("VGK"), V2X MIKEY Key (“VMK”), Access NSSF (“vNSSF”), Access PLMN (“VPLMN”), V2X Service Key (“VTK”), Wide Area Network (“WAN”) and Worldwide Interoperability for Microwave Access (“WiMAX”).
[0005] In certain wireless communication networks, data transmission contention may occur. Summary of the invention
[0006] Methods for determining data transmission preemption are disclosed. Apparatus and systems also perform the functions of these methods. One embodiment of the method includes receiving a first uplink grant for a first hybrid automatic repeat request process. In some embodiments, the method includes determining that a first data transmission corresponding to the first uplink grant is preempted by a second data transmission corresponding to a second uplink grant for a second hybrid automatic repeat request process. In certain embodiments, the method includes, in response to determining that the first data transmission is preempted by the second data transmission: not generating a transport block for the first uplink grant; and flushing a hybrid automatic repeat request buffer corresponding to the first hybrid automatic repeat request process.
[0007] An apparatus for determining data transmission preemption includes a receiver that receives a first uplink grant for a first hybrid automatic repeat request process. In various embodiments, the apparatus includes a processor that determines that a first data transmission corresponding to the first uplink grant is preempted by a second data transmission corresponding to a second uplink grant for a second hybrid automatic repeat request process; and, in response to determining that the first data transmission is preempted by the second data transmission: not generating a transport block for the first uplink grant; and flushing a hybrid automatic repeat request buffer corresponding to the first hybrid automatic repeat request process.
[0008] One embodiment of a method for transmitting a transport block includes receiving an uplink grant for an initial transmission of data for a hybrid automatic repeat request process. In some embodiments, the method includes determining that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer upon receiving the uplink grant. In some embodiments, the method includes transmitting the transport block in response to determining that a size of the transport block matches a grant size corresponding to the uplink grant.
[0009] Another apparatus for transmitting a transport block includes a receiver that receives an uplink grant for an initial transmission of data for a hybrid automatic repeat request process. In various embodiments, the apparatus includes a processor that determines to store a transport block for the hybrid automatic repeat request process in a hybrid automatic repeat request buffer upon receiving the uplink grant. In some embodiments, the apparatus includes a transmitter that transmits the transport block in response to determining that a size of the transport block matches a grant size corresponding to the uplink grant. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
[0011] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for determining data transmission preemption;
[0012] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to determine data transmission preemption;
[0013] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to determine data transmission preemption;
[0014] Figure 4 is a schematic diagram illustrating one embodiment of a method for determining data transmission preemption; and
[0015] Figure 5 is a schematic diagram illustrating one embodiment of a method for transmitting a transport block. DETAILED DESCRIPTION
[0016] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Thus, the embodiments may take the form of a fully hardware embodiment, a fully software embodiment (including firmware, resident software, microcode, etc.), or a combination of software and hardware aspects, which may all be generally referred to herein as "circuits," "modules," or "systems." In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-temporary, and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device employs only a signal for accessing the code.
[0017] Certain functional units described in this specification may be labeled as modules in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising a custom very large scale integrated ("VLSI") circuit or gate array, off-the-shelf semiconductor such as a logic chip, transistor or other discrete component. A module may also be implemented in a programmable hardware device such as a field programmable gate array, programmable array logic, a programmable logic device, etc.
[0018] Modules may also be implemented in code and / or software to be executed by various types of processors. The identified modules of code may, for example, include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions. However, the executable files of the identified modules need not be physically located together, but may include unrelated instructions stored in different locations, which, when logically combined together, comprise the module and achieve the stated purpose of the module.
[0019] In fact, code module can be a single instruction or many instructions, and can even be distributed on several different code segments, among different programs and across several memory devices.Similarly, in this article, operating data can be identified and illustrated in the module, and can be embodied and organized in the data structure of any appropriate type in any appropriate form.Operational data can be collected as a single data set, or can be distributed in different locations, which are included on different computer-readable storage devices.When a module or a part of a module is implemented in software, the software part is stored on one or more computer-readable storage devices.
[0020] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.
[0021] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection with one or more cables, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
[0022] The code for performing the operations of the embodiments may be any number of lines and may be written in any combination of one or more programming languages including object-oriented programming languages such as Python, Ruby, Java, Smalltalk, C++, and the like, and commonly used procedural programming languages such as the "C" programming language, and / or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer, partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network including a local area network ("LAN") or a wide area network ("WAN"), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0023] References to "one embodiment," "embodiment," or similar language in this specification mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, unless otherwise expressly stated, throughout the specification, the occurrences of the phrases "in one embodiment," "in an embodiment," and similar language may, but not necessarily, all refer to the same embodiment, but rather mean "one or more but not all embodiments." Unless otherwise expressly stated, the terms "include," "comprises," "has," and their variations mean "including but not limited to." Unless otherwise expressly stated, a list of enumerated items does not imply that any or all items are mutually exclusive. Unless otherwise expressly stated, the terms "one," "an," and "the" also refer to "one or more."
[0024] In addition, the features, structures or characteristics of the described embodiments may be combined in any appropriate manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid blurring aspects of the embodiments.
[0025] Aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of the methods, devices, systems, and program products according to the embodiments. It will be understood that each frame of the schematic flow charts and / or schematic block diagrams and the combination of frames in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / operations specified in the schematic flow charts and / or schematic block diagram frames or multiple frames.
[0026] The code may also be stored in a storage device that is capable of instructing a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions / operations specified in the schematic flowchart and / or schematic block diagram box or multiple boxes.
[0027] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, such that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in a box or multiple boxes of the flowchart and / or block diagram.
[0028] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functions and operations of possible implementations of the devices, systems, methods and program products according to different embodiments. In this regard, each box in the schematic flow charts and / or schematic block diagrams may represent a module, a fragment or a portion of a code, which includes one or more executable instructions of the code for implementing a specified logical function.
[0029] It should also be noted that in some alternative embodiments, the functions annotated in the blocks may not occur in the order annotated in the drawings. For example, depending on the functions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. It is conceivable that other steps and methods are equivalent in function, logic or effect to one or more blocks or portions thereof of the illustrated drawings.
[0030] Although various arrow types and line types can be adopted in flow charts and / or block diagrams, it is understood that they do not limit the scope of the corresponding embodiments. In fact, some arrows or other connectors can only be used to indicate the logical flow of the depicted embodiment. For example, an arrow can indicate a waiting or monitoring period of unspecified duration between the steps of the enumeration of the depicted embodiment. It will also be noted that each frame of the block diagram and / or flow chart and the combination of the frames in the block diagram and / or flow chart can be realized by a system based on dedicated hardware that performs a specific function or operation, or by a combination of dedicated hardware and code.
[0031] The description of an element in each figure may refer to an element of the previous figure. In all figures, the same numerals refer to the same elements, including alternative embodiments of the same elements.
[0032] Figure 1 An embodiment of a wireless communication system 100 for determining data transmission preemption is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Although Figure 1 A specific number of remote units 102 and network units 104 are depicted in FIG. 1 , but one skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.
[0033] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (e.g., a router, a switch, a modem), an aerial vehicle, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 102 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, the remote unit 102 may communicate directly with other remote units 102 via side link communications.
[0034] The network elements 104 may be distributed over a geographic area. In some embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node-Bs, eNBs, gNBs, home node-Bs, relay nodes, devices, core networks, air servers, wireless access nodes, APs, NRs, network entities, AMFs, UDMs, UDRs, UDM / UDRs, PCFs, RANs, NSSFs, ASs, NEFs, key management servers, KMFs, or any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers that are communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks, such as the Internet and public switched telephone networks, and the like. These and other elements of the radio access and core networks are not illustrated, but are generally well known to those of ordinary skill in the art.
[0035] In one embodiment, the wireless communication system 100 complies with the NR protocol standardized in 3GPP, wherein the network unit 104 transmits on the DL using an OFDM modulation scheme, and the remote unit 102 transmits on the UL using an SC-FDMA scheme or an OFDM scheme. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfoxx, and other protocols. The present disclosure is not intended to be limited to implementations of any particular wireless communication system architecture or protocol.
[0036] The network unit 104 may serve multiple remote units 102 within a service area, such as a cell or cell sector, via wireless communication links. The network unit 104 transmits DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.
[0037] In various embodiments, the remote unit 102 may receive a first uplink grant for a first hybrid automatic repeat request process. In some embodiments, the remote unit 102 may determine that a first data transmission corresponding to the first uplink grant is preempted by a second data transmission corresponding to a second uplink grant for a second hybrid automatic repeat request process. In some embodiments, the remote unit 102 may, in response to determining that the first data transmission is preempted by the second data transmission: not generate a transport block for the first uplink grant; and flush a hybrid automatic repeat request buffer corresponding to the first hybrid automatic repeat request process. Thus, the remote unit 102 may be used to determine data transmission preemption.
[0038] In some embodiments, the remote unit 102 may receive an uplink grant for an initial transmission of data for a hybrid automatic repeat request process. In some embodiments, the remote unit 102 may determine that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer upon receiving the uplink grant. In some embodiments, the remote unit 102 may transmit the transport block in response to determining that the size of the transport block matches the grant size corresponding to the uplink grant. Thus, the remote unit 102 may be used to determine data transmission preemption.
[0039] Figure 2 An embodiment of an apparatus 200 that can be used to determine data transmission preemption is depicted. Apparatus 200 includes an embodiment of remote unit 102. In addition, remote unit 102 may include processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212. In some embodiments, input device 206 and display 208 are combined into a single device, such as a touch screen. In some embodiments, remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, remote unit 102 may include one or more of processor 202, memory 204, transmitter 210, and receiver 212, and may not include input device 206 and / or display 208.
[0040] In one embodiment, the processor 202 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.
[0041] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and associated data, such as an operating system or other controller algorithms operating on remote unit 102.
[0042] In one embodiment, input device 206 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 206 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 206 includes two or more different devices such as a keyboard and a touch panel.
[0043] In one embodiment, the display 208 may include any known electronically controllable display or display device. The display 208 may be designed to output visual, auditory and / or tactile signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the display 208 may include a wearable display such as a smart watch, smart glasses, a head-up display, etc. In addition, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.
[0044] In some embodiments, the display 208 includes one or more speakers for generating sounds. For example, the display 208 can generate an audible alarm or notification (e.g., a buzzer or beep). In some embodiments, the display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be positioned near the input device 206.
[0045] The receiver 212 may receive a first uplink grant for a first hybrid automatic repeat request process. In various embodiments, the processor 202 may: determine that a first data transmission corresponding to the first uplink grant is preempted by a second data transmission corresponding to a second uplink grant of a second hybrid automatic repeat request process; and, in response to determining that the first data transmission is preempted by the second data transmission: not generate a transport block for the first uplink grant; and flush a hybrid automatic repeat request buffer corresponding to the first hybrid automatic repeat request process.
[0046] The receiver 212 may receive an uplink grant for an initial transmission of data for a hybrid automatic repeat request process. In various embodiments, the processor 202 may determine that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer upon receiving the uplink grant. In some embodiments, the transmitter 210 may transmit the transport block in response to determining that the size of the transport block matches the grant size corresponding to the uplink grant.
[0047] Although only one transmitter 210 and one receiver 212 are shown, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.
[0048] Figure 3 One embodiment of an apparatus 300 that may be used to determine data transmission preemption is depicted. The apparatus 300 includes one embodiment of a network unit 104. In addition, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It is understood that the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.
[0049] In certain embodiments, the receiver 312 may be used to receive information as described herein and / or the transmitter 310 may be used to transmit information as described herein and / or the processor 302 may be used to process information as described herein.
[0050] In certain embodiments, Industrial IoT for URLLC can use both FR1 and FR2 and both TDD and FDD. In various embodiments, L2 and / or L3 enhancements can be made, such as data duplication, multi-connectivity and / or UL and / or DL intra-UE prioritization and / or multiplexing between different classes of traffic in the UE (e.g., prioritization, such as dropping, delaying, or puncturing low priority services), including both data channels and control channels.
[0051] In some embodiments, such as for the uplink, a UE may be scheduled with two uplink grants, thereby allocating overlapping PUSCH resources for data of different priority levels. For example, the gNB may schedule an urgent and / or critical UL LCPUSCH transmission (e.g., transmitted using a highly reliable MCS) to preempt a previously scheduled PUSCH transmission intended for lower priority eMBB data. In some embodiments, the gNB is not aware of whether the UE has generated a TB for a lower priority UL grant. In such embodiments, the gNB may not be aware of whether there are some pending TBs for transmission in the HARQ buffer of the HARQ process associated with the lower priority UL grant. In various embodiments, the UE may receive a dynamic UL grant that schedules a retransmission or an initial transmission. In some embodiments, there may be different behaviors related to whether a TB is pending. In some embodiments, the UE may process deprioritized (e.g., preempted) data and / or UL grants intended to avoid data loss.
[0052] In some embodiments, 3GPP may extend 5G NR to unlicensed spectrum in the 5 GHz and / or 6 GHz bands. In some embodiments, 5G may be operated alone in the unlicensed spectrum without restriction and without any anchor in the licensed spectrum. In various embodiments, AUL transmissions may have separately configured licensed transmissions. In some embodiments, AUL transmissions may be enabled by a combination of RRC signaling and an activation message conveyed by DCI in a physical control channel. In some embodiments, the RRC configuration may include a time slot in which the UE is enabled to transmit autonomously and / or the RRC configuration may include a qualified HARQ process ID. In various embodiments, the activation message may include an RBA and / or MCS from which the UE can determine the transport block size for any AUL transmission.
[0053] In some embodiments, if a TB has been generated for an AUL transmission on a CG resource and the LBT fails, the configuredGrantTimer may not be started. Such an embodiment may result in the configuredGrantTimer not running at the next transmission opportunity of the same HARQ process, which in turn may trigger the UE to generate a new TB. Therefore, in such an embodiment, the previous TB that could not be transmitted due to the LBT failure may be lost. In certain embodiments, the gNB may not know whether the UE has not yet transmitted on the CG resources due to the occurrence of an LBT failure or because the UE has no data for transmission (e.g., UL skipping). In such an embodiment, assuming that the UE has not yet generated a TB, the gNB may schedule an initial transmission for the corresponding HARQ process. In order not to lose data in a potentially pending TB in the HARQ buffer, the UE may transmit the pending TB even if a new transmission has been scheduled by the gNB (e.g., dynamic UL grant). In various embodiments, there may be a recovery process for data that is pending for transmission in the HARQ buffer due to a failed LBT.
[0054] In some embodiments, such as for the case if the UE is configured with two UL carriers for the serving cell, the gNB may need to know when the PHR is generated to know what PHR type (e.g., Type 1 PH or Type 3 PHR) to report in the PHR MAC CE. In some embodiments, the UE may report Type-1 PH or Type-3 PH depending on whether the UE determines a real PH or a virtual PH for the two carriers.
[0055] In various embodiments, if AUL for ungranted access in NR (e.g., NR-U) is used, the gNB may not be able to determine when the UL transmission and / or TB was initially generated due to potential LBT failure, even if subsequent transmissions or retransmissions of the same HARQ process are correctly decoded by the gNB. In such embodiments, the uncertainty may have some negative impact on PHR transmission because the PHR content at the time of transmission may not reflect the state corresponding to when it was generated. This may affect UL scheduling and / or link adaptation. In certain embodiments, two conflicting UL grants may occur (e.g., one higher priority UL grant preempts a lower priority UL grant). In some embodiments, since the gNB may not know whether the UE generated a TB for a lower priority grant, the gNB may not know when the MAC CE was generated by the UE when, for example, receiving a TB on a HARQ process associated with a lower priority grant, including a MAC CE, such as a PHR MAC CE.
[0056] As used herein, eNB and / or gNB may be used to indicate a base station, but it may be replaced with any other suitable radio access node (e.g., BS, eNB, gNB, AP, NR, etc.). In addition, the various methods described herein may be primarily described in the context of 5G NR; however, the methods described herein may be equally applicable to other mobile communication systems supporting service cells and / or carriers configured in unlicensed spectrum LTE mobile wireless or cellular telecommunication systems.
[0057] In a first embodiment, if a UE receives a retransmission grant (e.g., UL) for a HARQ process ID for which a HARQ buffer is empty, e.g., because a higher priority UL grant has preempted the transmission of a TB for the HARQ process ID, the UE generates a new TB according to the retransmission grant and transmits the TB on scheduled resources, e.g., UL resources. In one implementation of the first embodiment, the UL grant scheduled for retransmission is addressed to the CS-RNTI of the UE. In such an implementation, the UE may have a configured UL grant (e.g., and corresponding data for transmission) that conflicts with a higher priority grant (e.g., CG or DG), and the UE may not have generated a TB for the lower priority CG because the higher priority UL grant preempted the lower priority UL transmission on the CG resources. In certain embodiments, if a deprioritized TB is to be transmitted on a configured grant resource, i.e., the deprioritized UL grant is a configured grant, the gNB does not know whether the UE has skipped the configured grant opportunity due to an empty buffer (e.g., no data available for transmission) or due to a higher priority UL grant preempting the CG transmission. In such embodiments, the gNB may not be aware of whether the UE has already generated a TB for a lower priority grant which may depend on the UE implementation (e.g., a higher priority grant may be received when the UE has already started generating a TB for a lower priority UL grant).
[0058] In certain embodiments, if the DCI is addressed to the received CS-RNTI (eg, scheduling a retransmission) and the UL HARQ buffer is empty, the UE may ignore the DCI and / or grant (eg, not generate a new TB generation) as shown in Table 1.
[0059]
[0060] In certain embodiments of the first embodiment, the UE, when having received an uplink grant on a PDCCH addressed to the CS-RNTI and when the HARQ buffer of the identified process is empty due to some conflict with a higher priority UL grant, may generate a MAC PDU based on the received UL grant (e.g., assuming that the MAC PDU contains a MAC SDU—there is no empty MAC PDU).
[0061] In various embodiments, the UE flushes the HARQ buffers of the HARQ processes for which new TBs have not been generated due to some higher priority UL grant preempting the transmission of the HARQ process. In such embodiments, if a UL configured grant is preempted by some higher priority UL grant (e.g., a dynamic grant or a configured grant) and the UE has not generated a TB for the preempted CG, the UE may flush the HARQ buffers of the HARQ processes associated with the preempted CG.
[0062] In the second embodiment, if the grant size matches the TB size stored in the HARQ buffer, the UE may transmit the TB stored in the HARQ buffer of the HARQ process (e.g., the HARQ process associated with the configured grant) when the UL grant for which the HARQ process is scheduled for initial transmission has been received. In one implementation of the second embodiment, if the stored TB is generated for a UL grant (e.g., the configured grant) that is deprioritized / preempted by some higher priority UL grant, the UE is only enabled to send the stored / pending TB on the UL-SCH scheduled for the initial transmission. In various embodiments of the second embodiment, TBs may have been generated for lower priority grants that were preempted by some higher priority grants. In certain embodiments, in order not to lose the pending data (e.g., deprioritized data) in the HARQ buffer, the UE may transmit the TB stored in the HARQ buffer even if the new transmission has been scheduled by the gNB. In such embodiments, the gNB does not know whether the UE has generated a TB for a lower priority (e.g., preempted) UL grant, and therefore, it may be assumed that the UE has not generated a TB for the lower priority UL grant to schedule the initial transmission for the corresponding HARQ process.
[0063] In some embodiments, such as if the grant size (e.g., the initial UL grant) does not match the size of the TB stored in the HARQ buffer of the HARQ process, the UE may generate a new TB based on the initial UL grant, thereby treating the MAC SDU included in the stored TB as an input to the LCP process. In certain implementations of this embodiment, the UE triggers RLC retransmissions for each of the RLC PDUs and / or MAC SDUs contained in the TB stored in the HARQ buffer and then generates a new TB that may include these RLC retransmissions (e.g., or parts of RLC retransmissions). In such implementations, the UE may consider the triggered RLC retransmissions for the generation of new TBs according to the specified LCP process. In addition, according to these implementations, the UE may not wait for the RLC status report from the receiver that triggered the RLC retransmission, but may autonomously trigger RLC retransmissions internally for the RLC PDUs of the logical channel configured with the RLC AM mode (e.g., the MAC entity indicates to the relevant RLC entity that the RLC retransmission is triggered for the RLC PDUs in the pending TBs in the HARQ buffer). In various embodiments, the MAC and / or RLC protocols may facilitate retransmissions to be prioritized over new RLC PDUs and multiplexed into new TBs scheduled by the initial UL grant.
[0064] In certain embodiments, if the TB size indicated by the initial UL grant is smaller than the TB size of the MAC PDU (e.g., deprioritized data) stored in the HARQ buffer, the UE takes MAC subPDUs or MAC SDUs from the stored MAC SDUs in descending order of priority starting from the highest priority MAC SDU until the UL grant is exhausted. In such embodiments, the remaining space may be filled with MAC subPDUs (e.g., new MAC subPDUs) according to the LCP process and / or padding. In some embodiments, the priority of the MAC subPDU and / or MAC SDU may be defined according to the relative priority order and / or logical channel priority configured by RRC signaling. In some embodiments, the UE may instruct the multiplexing and assembly process to newly generate a MAC CE contained in a TB stored in the HARQ buffer. For example, if a BSR MAC CE is contained in a MAC PDU in the HARQ buffer, the UE may generate a new BSR MAC CE (e.g., reflecting the most recent buffer status) and may include it in the MAC PDU (e.g., if there is enough space according to the LCP process). In some embodiments, the BSR MAC CE type may be different (e.g., a truncated BSR MAC CE included in a TB from the HARQ buffer), and a long BSR MAC CE may be included in the new MAC PDU based on the initial UL grant. In various embodiments, if the PHR MAC is included in the MAC PDU stored in the HARQ buffer, the UE may generate a new PHR MAC CE (e.g., based on the current power state). In some embodiments, regenerating the MAC CE may enable the gNB to assume that the MAC CE was generated at the first HARQ transmission.
[0065] In certain embodiments, the UE may make autonomous retransmissions of TBs that were not transmitted due to a higher priority conflicting UL grant. If a TB has been generated for a CG but the TB cannot be transmitted at the CG timing due to a higher priority UL grant preempting the CG transmission, the UE may transmit the pending TB in the next transmission opportunity of the same HARQ process. The next transmission opportunity of the same HARQ process may be a configured granted resource or a scheduled granted resource. In various embodiments, a configuredGrantTimer may be started and / or restarted even if a TB is not transmitted on the configured granted resource due to a higher priority conflicting UL grant (e.g., preemption).
[0066] In a third embodiment, if the transmission of a TB is preempted by a higher priority UL transmission and / or UL grant and the LCP process has been initiated and / or performed by the UE, the UE may be enabled to multiplex padding into the TB instead of multiplexing a MAC CE. According to one implementation of the third embodiment, if the transmission of a TB is preempted by a higher priority UL transmission and / or UL grant, the UE may be enabled to multiplex padding into the TB instead of multiplexing a PHR MAC CE. In some embodiments, if the UL MAC CE is placed at the end of the TB after all MAC SDUs, even if the generation of the TB has already started (for example, if a higher priority UL grant is received), it may be possible not to multiplex the MAC CE in the TB, but to add padding instead without rerunning the LCP process. In some embodiments, the MAC CE may be included in the higher priority UL transmission. Sending padding in a deprioritized TB instead of a MAC CE may be used for some MAC CEs to enable the gNB to know whether a MAC CE has been generated. In such embodiments, the gNB may need to know whether a PHR has been generated to understand whether the PHR MAC CE contains a PHR Type 1 report or a PHR Type 3 report (e.g., for SUL). In some embodiments, the UE may be configured with two UL carriers for the serving cell and the gNB may need to know when (e.g., at what time) a PHR has been generated to know what PHR type (e.g., Type 1 PHR or Type 3 PHR) is reported in the PHR MAC CE. In various embodiments, because the gNB may not know whether the UE has generated a TB for a lower priority UL grant that was preempted by a higher priority grant (e.g., if the two UL grants collide), the gNB may not know the time when the MAC CE contained in the TB was generated by the UE when the TB is received on the HARQ process associated with the preempted lower priority UL grant. For example, the UE may not generate a TB for a lower priority UL grant at a point that collides with a higher priority UL grant, but may generate a TB when a retransmission grant is received. In this example, the gNB may not know whether the received TB has been generated (e.g., at an initial transmission attempt that has been preempted by a higher priority UL grant) or when a retransmission grant has been scheduled. In various embodiments, because the PHR MAC CE may not be multiplexed in a TB, the PHR related timers may not be affected (eg, the UE may act as if the PHR MAC CE has not been triggered and / or sent).
[0067] In certain embodiments, if the UE has two conflicting UL grants, the UE may multiplex a MAC CE (e.g., at least a PHR MAC CE) on a higher priority UL grant. In various embodiments, if the UE and / or MAC is requested to transmit multiple MAC PDUs simultaneously, or if the MAC entity receives multiple UL grants within one or more consistent PDCCH opportunities, the UE implementation may choose an UL grant to multiplex the MAC CE. In some embodiments, if a lower priority UL grant is a configured grant, the UE may multiplex a MAC CE (e.g., a PHR MAC CE) on a higher priority UL grant.
[0068] In various embodiments, if the UE has mapped the MAC CE in a lower priority UL grant, the UE may multiplex the MAC CE on a higher priority UL grant. In such an embodiment, if the PHR MAC CE has been mapped to a lower priority UL grant as a configured grant (e.g., the UE has generated a TB or has started generating a TB based on a lower priority grant), the UE may multiplex the PHR MAC CE on a higher priority UL grant.
[0069] In a fourth embodiment, upon receiving an UL grant scheduling an initial transmission, if the grant size matches the size of a stored TB, the UE may transmit a TB pending due to LBT failure in a HARQ buffer of a HARQ process associated with the configured grant for transmission. In such an embodiment, the UL LBT may have failed due to a configured grant associated with the HARQ process or a PUSCH transmission on an AUL resource (e.g., or a PUSCH transmission attempt), and the UE may receive an initial UL grant (e.g., a dynamic grant addressed to the C-RNTI of the UE). In a fourth embodiment, the UE may transmit the stored TB in the HARQ buffer of the corresponding HARQ process to avoid data loss. In some embodiments, if the UL grant size is larger than the size of the stored TB, the UE may append the new data to the data stored in the pending TB. In various embodiments, the UE may run an LCP process based on the received UL grant and may use a MACsubPDU (e.g., MAC SDU) contained in the stored TB as an input for the LCP process.
[0070] In certain embodiments, the UE generates and transmits a new TB and / or MAC PDU based on the received initial UL grant for the HARQ process for which the TB is pending in the HARQ buffer due to LBT failure and moves the pending TB to another HARQ process available for transmission (e.g., the configuredGrantTimer is not running due to the HARQ process or the empty HARQ buffer). In various embodiments, the UE may transmit the pending TB on the next transmission opportunity (e.g., the configured grant opportunity) for the HARQ process. As can be appreciated, by moving the pending TB (e.g., due to LBT failure) to another available and / or idle HARQ process, data loss may be avoided.
[0071] In a fifth embodiment, the priority of the UL grant and / or UL transmission may be determined for another conflicting UL grant and / or transmission based on the data contained in the corresponding TB and / or MAC PDU. In certain embodiments, for a UL grant that schedules a PUSCH transmission, the priority of the UL grant may be determined based on the logical channel priority of the MAC SDU contained in the TB (for example, the highest priority among the LCHs in which the MAC SDU is contained in the TB determines the priority of the UL grant and / or transmission). In various embodiments, not only the MAC SDU and / or LCH are considered for determining the priority of the UL grant, but also the MAC CE (and its relative priority) contained in the TB. For example, if the TB corresponding to a UL grant contains a BSR MAC CE or a PHRMAC CE, the corresponding UL grant has a higher priority than a UL grant whose corresponding TB does not contain a MAC CE.
[0072] Figure 4 is a flow chart illustrating one embodiment of a method 400 for determining data transmission preemption. In some embodiments, the method 400 is performed by a device such as the remote unit 102. In certain embodiments, the method 400 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.
[0073] In various embodiments, the method 400 includes receiving 402 a first uplink grant for a first hybrid automatic repeat request process. In some embodiments, the method 400 includes determining 404 that a first data transmission corresponding to the first uplink grant is preempted by a second data transmission corresponding to a second uplink grant for a second hybrid automatic repeat request process. In some embodiments, the method 400 includes, in response to determining that the first data transmission is preempted by the second data transmission: not generating 406 a transport block for the first uplink grant; and flushing a hybrid automatic repeat request buffer corresponding to the first hybrid automatic repeat request process.
[0074] In some embodiments, the second uplink grant has a higher priority than the first uplink grant. In some embodiments, the method 400 further includes: receiving a retransmission grant for the first hybrid automatic repeat request process; determining that the hybrid automatic repeat request buffer is empty; and, in response to determining that the hybrid automatic repeat request buffer is empty, generating a new transport block based on the retransmission grant and transmitting the new transport block based on the retransmission grant. In various embodiments, the retransmission grant is addressed to a configured scheduling radio network temporary identifier.
[0075] In one embodiment, the method 400 further includes: receiving a retransmission grant for a first hybrid automatic repeat request process; determining that a hybrid automatic repeat request buffer is empty; and, in response to determining that the hybrid automatic repeat request buffer is empty, generating a medium access control protocol data unit based on the retransmission grant. In some embodiments, the retransmission grant is addressed to a configured dispatch radio network temporary identifier.
[0076] Figure 5 is a flow chart illustrating one embodiment of a method 500 for transmitting a transport block. In some embodiments, the method 500 is performed by a device such as the remote unit 102. In certain embodiments, the method 500 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.
[0077] In various embodiments, the method 500 includes receiving 502 an uplink grant for an initial transmission of data for a hybrid automatic repeat request process. In some embodiments, the method 500 includes determining 504 that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer upon receiving the uplink grant. In some embodiments, the method 500 includes, in response to determining that a size of the transport block matches a grant size corresponding to the uplink grant, transmitting 506 the transport block.
[0078] In some embodiments, the method 500 further includes preempting transmission of the transport block prior to receiving an uplink grant as a result of a higher priority uplink grant. In some embodiments, the method 500 further includes, in response to determining that the size of the transport block does not match the grant size corresponding to the uplink grant, generating a new transport block based on the uplink grant. In various embodiments, generating the new transport block includes using at least one medium access control service data unit contained in the transport block as an input to the logical channel prioritization process.
[0079] In one embodiment, in response to determining that the size of the transport block does not match the grant size corresponding to the uplink grant, a radio link control retransmission is triggered for each of the plurality of radio link control protocol data units contained in the transport block. In some embodiments, generating a new transport block includes generating a new transport block including at least a portion of the radio link control retransmission. In some embodiments, the radio link control retransmission includes at least one radio link control protocol data unit, at least one medium access control service data unit, or a combination thereof contained in the transport block.
[0080] In one embodiment, a method includes: receiving a first uplink grant for a first hybrid automatic repeat request process; determining that a first data transmission corresponding to the first uplink grant is preempted by a second data transmission corresponding to a second uplink grant for a second hybrid automatic repeat request process; and, in response to determining that the first data transmission is preempted by the second data transmission: not generating a transport block for the first uplink grant; and refreshing a hybrid automatic repeat request buffer corresponding to the first hybrid automatic repeat request process.
[0081] In some embodiments, the second uplink grant has a higher priority than the first uplink grant.
[0082] In some embodiments, the method further includes: receiving a retransmission grant for a first hybrid automatic repeat request process; determining that a hybrid automatic repeat request buffer is empty; and, in response to determining that the hybrid automatic repeat request buffer is empty, generating a new transport block based on the retransmission grant and transmitting the new transport block based on the retransmission grant.
[0083] In various embodiments, the retransmission grant is addressed to a configured dispatch radio network temporary identifier.
[0084] In one embodiment, the method further comprises: receiving a retransmission grant for the first hybrid automatic repeat request process; determining that the hybrid automatic repeat request buffer is empty; and, in response to determining that the hybrid automatic repeat request buffer is empty, generating a medium access control protocol data unit based on the retransmission grant.
[0085] In some embodiments, the retransmission grant is addressed to a configured dispatch radio network temporary identifier.
[0086] In one embodiment, a device includes: a receiver that receives a first uplink grant for a first hybrid automatic repeat request process; and a processor that determines that a first data transmission corresponding to the first uplink grant is preempted by a second data transmission corresponding to a second uplink grant in a second hybrid automatic repeat request process; and, in response to determining that the first data transmission is preempted by the second data transmission: not generating a transport block for the first uplink grant; and refreshing a hybrid automatic repeat request buffer corresponding to the first hybrid automatic repeat request process.
[0087] In some embodiments, the second uplink grant has a higher priority than the first uplink grant.
[0088] In some embodiments: the receiver receives a retransmission grant for a first hybrid automatic repeat request process; the processor determines that the hybrid automatic repeat request buffer is empty; and the processor generates a new transport block based on the retransmission grant and transmits the new transport block based on the retransmission grant in response to determining that the hybrid automatic repeat request buffer is empty.
[0089] In various embodiments, the retransmission grant is addressed to a configured dispatch radio network temporary identifier.
[0090] In one embodiment: the receiver receives a retransmission grant for a first hybrid automatic repeat request process; the processor determines that the hybrid automatic repeat request buffer is empty; and the processor generates a medium access control protocol data unit based on the retransmission grant in response to determining that the hybrid automatic repeat request buffer is empty.
[0091] In some embodiments, the retransmission grant is addressed to a configured dispatch radio network temporary identifier.
[0092] In one embodiment, a method includes: receiving an uplink grant for an initial transmission of data for a hybrid automatic repeat request process; determining that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer upon receiving the uplink grant; and, in response to determining that a size of the transport block matches a grant size corresponding to the uplink grant, transmitting the transport block.
[0093] In certain embodiments, the method further comprises preempting transmission of the transport block prior to receiving an uplink grant as a result of a higher priority uplink grant.
[0094] In some embodiments, the method further comprises, in response to determining that the size of the transport block does not match a grant size corresponding to the uplink grant, generating a new transport block based on the uplink grant.
[0095] In various embodiments, generating a new transport block includes taking at least one medium access control service data unit contained in the transport block as input to a logical channel prioritization process.
[0096] In one embodiment, in response to determining that the size of the transport block does not match a grant size corresponding to an uplink grant, a radio link control retransmission of each of the plurality of radio link control protocol data units contained in the transport block is triggered.
[0097] In some embodiments, generating a new transport block comprises generating a new transport block comprising at least a portion of a radio link control retransmission.
[0098] In some embodiments, the radio link control retransmission comprises at least one radio link control protocol data unit, at least one medium access control service data unit, or a combination thereof contained in a transport block.
[0099] In one embodiment, an apparatus includes: a receiver that receives an uplink grant for an initial transmission of data for a hybrid automatic repeat request process; a processor that determines, upon receiving the uplink grant, that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer; and a transmitter that transmits the transport block in response to determining that a size of the transport block matches a grant size corresponding to the uplink grant.
[0100] In certain embodiments, the processor preempts transmission of a transport block prior to receiving an uplink grant as a result of a higher priority uplink grant.
[0101] In some embodiments, the processor generates a new transport block based on the uplink grant in response to determining that the size of the transport block does not match a grant size corresponding to the uplink grant.
[0102] In various embodiments, the processor generating the new transport block includes the processor taking at least one medium access control service data unit contained in the transport block as input to a logical channel prioritization process.
[0103] In one embodiment, the processor triggers a radio link control retransmission of each of the plurality of radio link control protocol data units included in the transport block in response to determining that the size of the transport block does not match a grant size corresponding to an uplink grant.
[0104] In some embodiments, the processor generating the new transport block includes the processor generating the new transport block including at least a portion of a radio link control retransmission.
[0105] In some embodiments, the radio link control retransmission comprises at least one radio link control protocol data unit, at least one medium access control service data unit, or a combination thereof contained in the transport block.
[0106] Embodiments may be practiced in other specific forms. The described embodiments are considered in all respects to be illustrative only and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than the preceding description. All changes within the meaning and equivalent range of the claims are included within their scope.
Claims
1. A method, include: receiving an uplink grant for an initial transmission of data for a hybrid automatic repeat request process; determining, upon receiving the uplink grant, that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer; as well as In response to determining that the size of the transport block matches a grant size corresponding to the uplink grant, the transport block is transmitted.
2. The method according to claim 1, further comprising: include: Transmission of the transport block is preempted prior to receipt of the uplink grant as a result of a higher priority uplink grant.
3. The method according to claim 1, further comprising: include: In response to determining that the size of the transport block does not match the grant size corresponding to the uplink grant, a new transport block is generated based on the uplink grant.
4. The method according to claim 3, in, Generating the new transport block comprises taking at least one medium access control service data unit contained in the transport block as input to a logical channel prioritization procedure.
5. The method according to claim 3, in, In response to determining that the size of the transport block does not match the grant size corresponding to the uplink grant, triggering a radio link control retransmission for each of a plurality of radio link control protocol data units included in the transport block.
6. The method according to claim 3, in, Generating the new transport block comprises generating the new transport block comprising at least a portion of a radio link control retransmission.
7. The method according to claim 6, in, The radio link control retransmission includes at least one radio link control protocol data unit, at least one medium access control service data unit, or a combination thereof contained in the transport block.
8. The method according to claim 6, in, The method is executed by a user equipment.
9. A device, include: a receiver that receives an uplink grant for an initial transmission of data for a hybrid automatic repeat request process; a processor that, upon receiving the uplink grant, determines that a transport block for the hybrid automatic repeat request process is stored in a hybrid automatic repeat request buffer; as well as A transmitter transmits the transport block in response to determining that the size of the transport block matches a grant size corresponding to the uplink grant.
10. The device according to claim 9, further comprising: include: Transmission of the transport block is preempted prior to receipt of the uplink grant as a result of a higher priority uplink grant.
11. The device according to claim 9, further comprising: include: In response to determining that the size of the transport block does not match the grant size corresponding to the uplink grant, a new transport block is generated based on the uplink grant.
12. The device according to claim 11, in, Generating the new transport block comprises taking at least one medium access control service data unit contained in the transport block as input to a logical channel prioritization procedure.
13. The device according to claim 11, in, In response to determining that the size of the transport block does not match the grant size corresponding to the uplink grant, triggering a radio link control retransmission for each of a plurality of radio link control protocol data units included in the transport block.
14. The device according to claim 11, in, Generating the new transport block comprises generating the new transport block comprising at least a portion of a radio link control retransmission.
15. The device according to claim 14, in, The radio link control retransmission includes at least one radio link control protocol data unit, at least one medium access control service data unit, or a combination thereof contained in the transport block.
16. The device according to claim 11, in, The apparatus comprises user equipment.
