System and method for automatic transmission of reduced priority protocol data units
By automatically transmitting data units on the next configured authorized PUSCH instance when PUSCH priority is reduced due to channel overlap in a wireless communication system, the resource waste and latency issues caused by channel overlap are resolved, and the transmission efficiency and latency performance of the system are improved.
Patent Information
- Application Number
- CN202080073984.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-11-05
- Filing Date
- 2020-11-06
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-11-06
AI Technical Summary
When existing wireless communication systems experience channel overlap, and the priority of the Licensed Physical Uplink Shared Channel (PUSCH) instance is reduced, they cannot effectively handle the automatic transmission of allocated data units, resulting in resource waste and delays.
By automatically sending the de-priority data unit on the next configuration-authorized PUSCH instance when channel overlap is detected as a cause of priority reduction, the configuration-authorized retransmission timer and timer mechanism are used to avoid waiting for network confirmation and improve transmission efficiency.
It improves transmission delay and resource utilization efficiency when channels overlap, ensures timely transmission of data units, and reduces PDCCH resource waste.
Smart Images

Figure CN114631282B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Application No. 62 / 932,326, filed on November 7, 2019, and U.S. Non-Provisional Application No. 17 / 090,207, filed on November 5, 2020, the entire contents of which are hereby expressly incorporated herein by reference. Technical Field
[0003] The application technology discussed below relates to wireless communication systems, and more particularly to automatic transmission of a protocol data unit (PDU) with a reduced priority when an original channel associated with the PDU is deprioritized due to channel overlap. Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include multiple base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may also be referred to as user equipment (UE). Summary of the invention
[0005] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an extensive overview of all contemplated features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in summary form as a preface to a more detailed description presented later.
[0006] For example, in one aspect of the present disclosure, a method of wireless communication includes: obtaining, at a user equipment (UE), a protocol data unit (PDU) for transmission on a first configured authorized physical uplink shared channel (PUSCH) instance, detecting, at the UE, priority reduction information that the first configured authorized PUSCH instance is downgraded due to channel overlap, and automatically sending, on a second configured authorized PUSCH instance, the PDU originally associated with the first configured authorized PUSCH instance.
[0007] In another aspect of the present disclosure, a wireless communication UE includes a processor and a transceiver. The processor is configured to obtain a protocol data unit (PDU) for transmission on a first configuration grant physical uplink shared channel (PUSCH) instance, and detect, at the UE, priority reduction information that the first configuration grant PUSCH instance is reduced in priority due to channel overlap. The transceiver is configured to automatically transmit the PDU originally associated with the first configuration grant PUSCH instance on a second configuration grant PUSCH instance.
[0008] In another aspect of the present disclosure, a processor-readable non-transitory storage medium storing processor-executable instructions for wireless communication is disclosed. The instructions are executed by a processor to perform operations, the operations including: obtaining a protocol data unit (PDU) for transmission on a first configuration grant PUSCH instance at a UE, detecting priority reduction information at the UE that the first configuration grant PUSCH instance is deprioritized due to channel overlap, and automatically transmitting the PDU originally associated with the first configuration grant PUSCH instance on a second configuration grant PUSCH instance.
[0009] In another aspect of the present disclosure, a system for wireless communication includes: a component for obtaining a protocol data unit (PDU) for sending on a first configuration authorization PUSCH instance at a UE, a component for detecting at the UE priority reduction information that the first configuration authorization PUSCH instance is downgraded due to channel overlap, and a component for automatically sending the PDU originally associated with the first configuration authorization PUSCH instance on a second configuration authorization PUSCH instance.
[0010] By reviewing the following description of specific exemplary aspects of the present invention in conjunction with the accompanying drawings, other aspects, features, and aspects of the present invention will become apparent to those of ordinary skill in the art. Although features of the present invention may be discussed with respect to certain aspects and drawings below, all aspects of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more aspects may be discussed as having certain advantageous features, one or more of these features may also be used in accordance with the various aspects of the present invention discussed herein. In a similar manner, although exemplary aspects may be discussed below as aspects of devices, systems, or methods, it should be understood that such exemplary aspects may be implemented in a variety of devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 A wireless communication network in accordance with some aspects of the present disclosure is illustrated.
[0012] Figure 2 The present disclosure is shown in FIG. Figure 1The scenario shown is when channel overlap occurs in a wireless communication network.
[0013] Figure 3 FIG. 1 illustrates a response to an aspect of the present disclosure. Figure 2 Automatic data transmission scheme for the channel overlapping scenario shown in .
[0014] Figure 4 is a block diagram of a user equipment (UE) according to some aspects of the present disclosure.
[0015] Figure 5 is a block diagram of an exemplary base station (BS) according to some aspects of the present disclosure.
[0016] Figure 6 The present disclosure is illustrated in accordance with aspects of Figure 3 1 is a logic flow chart executed by the UE corresponding to the automatic sending scheme shown in .
[0017] Figure 7 The present invention is used to implement Figure 6 The sending timeline for the automatic sending scenario shown in .
[0018] Figure 8 A logic flow diagram executed by a UE corresponding to an alternative embodiment of an automatic transmission scheme according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION
[0019] In conjunction with the accompanying drawings, the detailed description set forth below is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, in order to avoid confusing these concepts, well-known structures and components are shown in block diagram form.
[0020] The present disclosure generally relates to wireless communication systems, which are also referred to as wireless communication networks. In various aspects, these techniques and devices can be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global mobile communication systems (GSM) networks, 5th generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.
[0021] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project (3GPP)", while cdma2000 is described in documents provided by an organization named "3rd Generation Partnership Project 2 (3GPP2)". These various radio technologies and standards are known or are being developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunications association groups to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. This disclosure focuses on the evolution of wireless technology from LTE, 4G, 5G, NR, and shared access to wireless spectrum between networks using a set of new and different radio access technologies or radio air interfaces.
[0022] In particular, 5G networks allow for diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to extend to provide coverage (1) for networks with ultra-high density (e.g., ~1M nodes / km) 2 )), ultra-low complexity (e.g., ~10s of bit / sec), ultra-low energy (e.g., ~10 years+ battery life), and deep coverage to reach challenging locations; (2) including mission-critical controls with strong security to protect sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1ms), and users with widespread mobility or lack of mobility; and (3) with enhanced mobile broadband, including extremely high capacity (e.g., ~10Tbps / km 2 ), extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep perception with advanced discovery and optimization.
[0023] 5G NR can be implemented using an optimized OFDM-based waveform with a scalable digital hierarchy and transmission time interval (TTI); a general, flexible framework to efficiently multiplex services and features using dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital hierarchy in 5G NR and the scaling of subcarrier spacing can effectively address the operation of different services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of FDD / TDD implementations less than 3 GHz, the subcarrier spacing may appear at 15 kHz on bandwidths (BWs) such as 5, 10, 20 MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3 GHz, the subcarrier spacing may appear at 30 kHz on a BW of 80 / 100 MHz. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, subcarrier spacing may occur at 60kHz on 160MHz BW. Finally, for various deployments that transmit with mmWave components on TDD at 28GHz, subcarrier spacing may occur at 120kHz on 500MHz BW.
[0024] The scalable digital system of 5G NR facilitates scalable TTI for different latency and quality of service (QoS) requirements. For example, shorter TTI can be used for low latency and high reliability, while longer TTI can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design that includes uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and the adapted uplink / downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.
[0025] Various other aspects and features of the present disclosure are further described below. Obviously, the teachings of this article can be embodied in various forms, and any specific structure, function or both disclosed herein are merely representative, not restrictive. Based on the teachings of this article, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, in addition to one or more of the aspects set forth herein, or in addition to one or more of the aspects set forth herein, other structures, functions, or structures and functions can be used to implement such a device or practice such a method. For example, the method can be implemented as a system, device, apparatus, and / or as a part of an instruction stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect can include at least one element of a claim.
[0026] Figure 1 A wireless communication network 100 according to some aspects of the present disclosure is illustrated. The network 100 may be a 5G network. The network 100 includes a plurality of base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BS 105 may be a station that communicates with the UE 115, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to this particular geographic coverage area of the BS 105 and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.
[0027] The BS 105 may provide communication coverage for macro cells or small cells (e.g., pico cells or femto cells) and / or other types of cells. A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs that subscribe to services with a network provider. Small cells, such as pico cells, typically cover a relatively small geographic area and may allow unrestricted access by UEs that subscribe to services with a network provider. Small cells, such as femto cells, will also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cells (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1In the example shown, BS 105d and 105e may be conventional macro BSs, while BS 105a-105c may be macro BSs enabled with one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. BS 105a-105c may utilize its higher-dimensional MIMO performance to utilize 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. BS 105f may be a small cell BS, which may be a home node or a portable access point. BS 105 may support one or more (e.g., two, three, four, etc.) cells.
[0028] Network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be roughly aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.
[0029] UE 115 is dispersed throughout the wireless network 100, and each UE 115 may be fixed or mobile. UE 115 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, UE 115 may be a device including a universal integrated circuit card (UICC). In another aspect, UE may be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC may also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the network 100. UE 115 may also be a machine specifically configured for connecting communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. UE 115e-115k is an example of various machines configured for communications of accessing the network 100. UE 115 is able to communicate with any type of BS, whether macro BS, small cell, etc. Figure 1 In the figure, the lightning shape (e.g., communication link) indicates wireless transmission between UE 115 and serving BS 105 (serving BS 105 is a BS designated to serve UE 115 on downlink and / or uplink), or expected transmission between BSs, and backhaul transmission between BSs.
[0030] In operation, BS 105a-105c may use 3D beamforming and coordinated spatial techniques such as coordinated multipoint (CoMP) or multi-connectivity to serve UEs 115a and 115b. Macro BS 105d may perform backhaul communications with BS 105a-105c and small cells, BS 105f. Macro BS 105d may also transmit multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.
[0031] The BS 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling for communications with the UE 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., through the core network) over a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.
[0032] The network 100 may also support mission-critical communications through ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and links from small cell BS 105f. Other machine-type devices, such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device) may communicate directly with a BS (such as small cell BS 105f and macro BS 105e) through the network 100, or in a multi-hop configuration by communicating with another user device to relay its information to the network, such as UE 115f transmitting temperature measurement information to smart meter UE 115g, which then reports to the network through small cell BS 105f. The network 100 may also provide additional network efficiency through dynamic, low-latency TDD / FDD communications, such as in vehicle-to-vehicle (V2V).
[0033] In some embodiments, the network 100 communicates using an OFDM-based waveform. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, etc. Each subcarrier can be modulated with data. In some cases, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other cases, the subcarrier spacing and / or the duration of the TTI can be scalable.
[0034] BS 105 may allocate or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS 105 to UE 115, and UL refers to the transmission direction from UE 115 to BS 105. Communication may be in the form of radio frames. A radio frame may be divided into a plurality of subframes or time slots, for example, about 10. Each time slot may also be divided into micro-time slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL band and a DL subframe in a DL band. In TDD mode, UL and DL transmissions are performed using the same frequency band in different time periods. For example, a subset of subframes (e.g., DL subframes) in a radio frame may be used for DL transmissions, and another subset of subframes (e.g., UL subframes) in a radio frame may be used for UL transmissions.
[0035] DL subframes and UL subframes can be further divided into several areas. For example, each DL or UL subframe can have a predefined area for sending reference signals, control information and data. Reference signals are predetermined signals that facilitate communication between BS 105 and UE 115. For example, reference signals can have a specific pilot mode or structure, wherein pilot frequency modulation can span the BW or frequency band of operation, and each pilot frequency modulation is located at a predetermined time and a predetermined frequency. For example, BS 105 can send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate the DL channel. Similarly, UE 115 can send a sounding reference signal (SRS) to enable BS 105 to estimate the UL channel. Control information may include resource allocation and protocol control. Data may include protocol data and / or operational data. In some aspects, BS 105 and UE 115 may communicate using self-contained subframes. Self-contained subframes may include a portion for DL communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a communication duration for DL that is longer than a communication duration for UL. A UL-centric subframe may include a communication duration for UL that is longer than a communication duration for UL.
[0036] In some aspects, the network 100 may be an NR network deployed on a licensed spectrum. The BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network 100 to facilitate synchronization. The BS 105 may broadcast system information associated with the network 100 (e.g., including a master information block (MIB), residual system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some cases, the BS 105 may broadcast the PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on a physical broadcast channel (PBCH), and may broadcast the RMSI and / or OSI on a physical downlink shared channel (PDSCH).
[0037] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting the PSS from the BS 105. The PSS may enable synchronization of periodic timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value that may be combined with the physical layer identification value to identify a cell. The PSS and SSS may be located in the center portion of the carrier or at any suitable frequency within the carrier.
[0038] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, and SRS.
[0039] After obtaining the MIB, RMSI and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL authorization, temporary cell-radio network temporary identifier (C-RNTI) and / or a backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105, and the BS 105 may respond with a connection response. The connection response may indicate a contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as message 1 (MSG 1), message 2 (MSG 2), message 3 (MSG 3), and message 4 (MSG 4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.
[0040] After the connection is established, the UE 115 and the BS 105 may enter a normal operation phase, in which operational data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL communications. The BS 105 may send UL and / or DL scheduling grants to the UE 115 via the PDCCH. The BS 105 may send DL communication signals to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may send UL communication signals to the BS 105 via the PUSCH and / or PUCCH according to the UL scheduling grant.
[0041] In some instances, BS 105 may communicate data with UE 115 using hybrid automatic repeat request (HARQ), thereby improving communication reliability. BS 105 may schedule UE 115 for PDSCH communication by sending a DL grant in PDCCH. BS 105 may send a DL data packet to UE 115 according to the scheduling in PDSCH. The DL data packet may be sent in the form of a transport block (TB). If UE 115 successfully receives the DL data packet, UE 115 may send a HARQ ACK to BS 105. Conversely, if UE 115 fails to successfully receive the DL transmission, UE 115 may send a HARQ NACK to BS 105. After receiving the HARQ NACK from UE 115, BS 105 may retransmit the DL data packet to UE 115. The retransmission may include a coded version of the DL data that is the same as the initial transmission. Alternatively, the retransmission may include a coded version of the DL data that is different from the initial transmission. The UE 115 may apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. The BS 105 and the UE 115 may also apply HARQ for UL communications using a substantially similar mechanism as DL HARQ.
[0042] In some aspects, the network 100 may operate on a system BW or a component carrier BW. The network 100 may divide the system BW into multiple BWPs (e.g., multiple parts). The BS 105 may dynamically assign the UE 115 to operate on a certain BWP (e.g., a certain part of the system BW). The assigned BWP may be referred to as an active BWP. The UE 115 may monitor the active BWP for signaling information from the BS 105. The BS 105 may schedule the UE 115 to perform UL or DL communications in the active BWP. In some aspects, the BS 105 may assign a pair of BWPs within a component carrier to the UE 115 for UL and DL communications. For example, the BWP pair may include one BWP for UL communication and one BWP for DL communication. The BS 105 may additionally configure the UE 115 with one or more CORESETs in the BWP. A CORESET may include a set of frequency resources that span multiple symbols in time. The BS 105 may configure one or more search spaces for PDCCH monitoring for the UE 115 based on the CORESETS. The UE 115 may perform blind decoding in the search space to search for DL control information (e.g., UL and / or DL scheduling grants) from the BS. In an example, the BS 105 may configure the BWP, CORESETS, and / or PDCCH search space for the UE 115 via RRC configuration.
[0043] In some aspects, the network 100 may operate on a shared or unlicensed frequency band, for example, at about 3.5 gigahertz (GHz), less than 6 GHz or higher frequencies in the mmWave band. The network 100 may divide the frequency band into a plurality of channels, for example, each channel occupies about 20 megahertz (MHz). The BS 105 and the UE 115 may be operated by a plurality of network operation entities that share resources in a shared communication medium, and may obtain a channel occupancy time (COT) in a shared medium for communication. The COT may be discontinuous in time, and may refer to the amount of time that a wireless node may send a frame when it wins a competition for a wireless medium. Each COT may include a plurality of transmission time slots. The COT may also be referred to as a transmit opportunity (TXOP). The BS 105 or UE 115 may perform LBT in the frequency band before transmitting in the frequency band. The LBT may be based on energy detection or signal detection. For energy detection, when the signal energy measured from the channel is greater than a certain signal energy threshold, the BS 105 or UE 115 may determine that the channel is busy or occupied. For signal detection, when a certain reserved signal (eg, a preamble sequence) is detected in a channel, the BS 105 or the UE 115 may determine that the channel is busy or occupied.
[0044] Additionally, BS 105 may configure UE 115 with narrowband operation capabilities (eg, transmission and / or reception limited to a BW of 20 MHz or less) to perform BWP frequency hopping for channel monitoring and communications. Mechanisms for performing BWP frequency hopping are described in greater detail herein.
[0045] Figure 2 It is shown that according to aspects of the present disclosure Figure 1 The scenario in which channel overlap occurs in the wireless communication network shown in FIG. Figure 1 As discussed, the BS 105 may configure uplink grants for uplink data transmission for the UE 115. For example, as shown in diagram 200, the BS 105 may allocate configuration grant instances 201-203 (e.g., configuration grant opportunities or configuration grant PUSCHs, etc.) to multiple UEs 115, and when each UE 115 has data to transmit, the UE 115 may randomly utilize the instances 201-203, for example, each configuration grant PUSCH 201-203 is associated with a PDU 211-213, respectively.
[0046] As another example, instead of using a pre-scheduled configured grant instance allocated by BS 105, when UE 115 has a PDU to send, UE 115 may send a service request to BS 105, and BS 105 may then allocate one or more dynamic uplink grants in a downlink control indicator (DCI) to UE 115. UE 115 may then send data (e.g., PDU 214) in the allocated dynamic uplink grant (e.g., 204).
[0047] Figure 200 shows that the channels allocated for the configuration grant 202 and the dynamic grant 204 can overlap in time, can be located in the same serving cell of the UE, or can be located in any serving cell of the UE. In this case, 3GPP Release 16 proposes a priority scheme between overlapping channels, for example, when the channels overlap, one dynamic grant is prioritized over another dynamic grant, one dynamic grant is prioritized over a configuration grant, one configuration grant is prioritized over another configuration grant, or a service request / uplink control information (UCI) is prioritized over a physical uplink shared channel (PUSCH) / UCI. In a corresponding example, when a configuration grant PUSCH instance 202 conflicts with a dynamic grant PUSCH instance 204, the priority scheme can prioritize the dynamic grant PUSCH instance 204 over the configuration grant PUSCH instance 202, as shown by the dashed line when the configuration grant PUSCH instance 202 is deprioritized. In other examples, the configuration grant PUSCH instance can be deprioritized by a service request, UCI (e.g., HARQ-ACK, etc.), and / or the like.
[0048] When the configuration grant PUSCH instance 202 is deprioritized, the PDU 212 originally allocated to the configuration grant PUSCH instance 202 is also considered to be deprioritized. Therefore, allocating resources to transmit the PDU 212 is still a problem.
[0049] In a wireless system, uplink transmission from one or more UEs to a BS may include configuration grant transmission and / or dynamic grant transmission. For example, multiple UEs are allowed to use configuration grants to periodically use resources for data transmission. The BS allocates configuration grant instances to multiple UEs, and when each of the multiple UEs has data to send, the UEs may randomly utilize these instances. For another example, the UE may send a service request to the BS, and the BS may then allocate one or more dynamic uplink grants to the UE in a downlink control indicator (DCI). The UE may then send data in the allocated dynamic uplink grant.
[0050] In some cases, configuration grants and dynamic grants may be allocated on overlapping channels, thus causing conflicts. For example, the channels allocated for configuration grants and dynamic grants may overlap in time, may be in the same serving cell of the UE, or may be in any serving cell of the UE. The Third Generation Partnership Project (3GPP) proposes a priority scheme between overlapping channels, for example, when channels overlap, giving priority to one dynamic grant over another dynamic grant, giving priority to one dynamic grant over a configuration grant, giving priority to one configuration grant over another configuration grant, or giving priority to a service request / uplink control information (UCI) over a physical uplink shared channel (PUSCH) / UCI. However, when a channel such as a configuration grant PUSCH is deprioritized, data units that have been associated with the deprioritized channel cannot be sent without allocated transmission resources. Therefore, when the initially allocated configuration grant is deprioritized, an automatic transmission scheme needs to be configured for the deprioritized data units.
[0051] Existing systems do not allow the use of a configuration grant instance (e.g., a basic configuration grant according to 3GPP Release 15) to send a PDU generated for a previous configuration grant instance, except when using repetitions pre-configured by the network - which are typically not triggered by unpredictable events (such as a de-prioritization of the configuration grant or a LBT failure). In this case, existing protocols only allow the use of a retransmission grant for a HARQ process associated with the previous configuration grant instance to transmit the PDU of the previous configuration grant instance, such as PDU 212. However, this mechanism requires the BS to use more PDCCH resources to transmit the retransmission grant (and DCI) to the UE. In addition, the radio area network (RAN) now knows for sure whether the configuration grant PUSCH instance 202 that has been de-prioritized has been allocated a PDU. Therefore, if the BS transmits a retransmission grant to the UE every time the configuration grant PUSCH instance is de-prioritized, then if the de-prioritized configuration grant PUSCH instance has no data to send, the PDCCH used to transmit the retransmission grant is essentially wasted.
[0052] Considering the need to configure the automatic transmission scheme of PDU 212 when the associated configuration grant PUSCH is deprioritized, UE automatic transmission of the deprioritized PDU is provided, which may be consistent with the transmission of the PDU that cannot be transmitted due to LBT failure. For example, in the case of LBT failure, in addition to the configuration grant timer (configuredGrantTimer) supported by 3GPP Release 15, the UE also retains a timer called the configuration grant retransmission timer (configuredGrantRetransmissionTimer). The duration of the configuration grant retransmission timer is usually set to be less than the duration of the configuration grant timer, so that the configuration grant retransmission timer will not expire before the configuration grant timer. When LBT failure occurs and the configuration grant retransmission timer expires, the current configuration grant PUSCH can be used for retransmission of the PDU even if the configuration grant timer is still running. If LBT does not fail for the current configuration grant PUSCH, a confirmation message is indicated by the BS for the configuration grant PUSCH, and the configuration grant retransmission timer and the configuration grant timer are both stopped so that the next configuration grant PUSCH can be used for initial / new transmission. Therefore, the concept of using two timers (eg, a configuration grant retransmission timer and a configuration grant timer) is used to handle the automatic transmission of a PDU with reduced priority.
[0053] Figure 3 The response according to aspects of the present disclosure is shown in Figure 2 Figure 300 shows a plurality of configuration grant PUSCH instances 301-303, each of which can be allocated to transmit PDUs 311-313, respectively. When the configuration grant PUSCH instance 303 is de-prioritized (e.g., by Figure 2 ), the UE may stop the configuration grant retransmission timer instead of waiting for a retransmission grant, which causes the transmission of the PDU 313 in the next configuration grant PUSCH instance 304.
[0054] In this way, the configuration grant retransmission timer is stopped only when the priority reduction information is detected, which is handled in a similar way to receiving a non-confirmation message from the BS. The UE does not need to wait for the BS to allocate a retransmission grant for sending a PDU with a reduced priority. Therefore, the transmission delay and resource efficiency can be improved.
[0055] Figure 4 4 is a block diagram of an exemplary UE 400 according to some aspects of the present disclosure. For example, UE 400 may be the Figure 11 or the UE 202 shown in other figures. As shown, the UE 400 may include a processor 402, a memory 404, a PDU transmission module 408, a communication interface 409, a transceiver 410 including a modem subsystem 412 and a radio frequency (RF) unit 414, and one or more antennas 416. These elements may communicate with each other directly or indirectly, for example, via one or more buses.
[0056] The processor 402 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 402 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.
[0057] The memory 404 may include cache memory (e.g., cache memory of the processor 402), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, the memory 404 includes a non-transitory computer-readable medium. The memory 404 may store or have recorded thereon instructions 406. The instructions 406 may include instructions that, when executed by the processor 402, cause the processor 402 to perform various aspects of the present disclosure described herein with reference to the UE 115 (e.g., Figure 3 A to Figure 3 C and Figure 6 A to various aspects of Figure 10) instructions for the operations described. Instructions 406 may also be referred to as program code. The program code may be used to cause the wireless communication device to perform these operations, for example, by causing one or more processors (such as processor 402) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be broadly interpreted to include any type of (one or more) computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, processes, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.
[0058] The PDU transmission module 408 can communicate with the communication interface 409 to receive a message from another device or send a message to another device. Each of the PDU transmission module 408 and the communication interface 409 can be implemented via hardware, software, or a combination thereof. For example, each of the PDU transmission module 408 and the communication interface 409 can be implemented as a processor, a circuit, and / or an instruction 406 stored in the memory 404 and executed by the processor 402. In some examples, the PDU transmission module 408 and the communication interface 409 can be integrated in the modem subsystem 412. For example, the PDU transmission module 408 and the communication interface 409 can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 412. In some examples, the UE may include one of the PDU transmission module 408 and the communication interface 409. In other examples, the UE may include both the PDU transmission module 408 and the communication interface 409.
[0059] The PDU sending module 408 and the communication interface 409 may be used in various aspects of the present disclosure, for example, Figures 2 to 3 and Figures 6 to 8 The PDU transmission module 408 is configured to receive a configuration grant and / or a dynamic grant from a BS (e.g., 105). The PDU transmission module 408 is also configured to transmit a PDU to the base station through the configuration grant and / or the dynamic grant. The PDU transmission module 408 is also configured to determine whether the transmission channels overlap and apply a priority. When a configuration grant PUSCH instance is deprioritized, the PDU transmission module 408 is configured to transmit the PDU with the deprioritized PDU in another configuration grant PUSCH instance.
[0060] The communication interface 409 is configured to coordinate with the PDU transmission module 408 to receive an uplink or downlink scheduling grant from the BS and / or communicate with the BS according to the uplink or downlink scheduling grant. The communication interface 409 is also configured to transmit a PDU to the BS.
[0061] As shown, the transceiver 410 may include a modem subsystem 412 and an RF unit 414. The transceiver 410 may be configured to communicate bidirectionally with other devices, such as the BS 105. The modem subsystem 412 may be configured to modulate and / or encode data from the memory 404, the PDU transmission module 408, and / or the communication interface 409 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 414 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (e.g., PUCCH, PUSCH, channel reports, ACK / NACK) from the modem subsystem 412 (on outbound transmissions) or from transmissions originating from another source, such as the UE 115 or the BS 105. The RF unit 414 may also be configured to perform analog beamforming in combination with digital beamforming. Although shown as integrated together in transceiver 410, modem subsystem 412 and RF unit 414 may be separate devices that are coupled together at UE 115 to enable UE 115 to communicate with other devices.
[0062] The RF unit 414 may provide modulated and / or processed data (e.g., a data packet (or more generally, a data message that may include one or more data packets and other information)) to the antenna 416 for transmission to one or more other devices. The antenna 416 may further receive data messages transmitted from other devices. The antenna 416 may provide received data messages for processing and / or demodulation at the transceiver 410. The transceiver 410 may provide demodulated and decoded data (e.g., DL data blocks, PDSCH, PUSCH, BWP frequency hopping configuration and / or instructions) to the PDU transmission module 408 and / or the communication interface 409 for processing. The antenna 416 may include multiple antennas of similar or different designs to maintain multiple transmission links. The RF unit 414 may configure the antenna 416.
[0063] In one aspect, the UE 400 may include multiple transceivers 410 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 400 may include a single transceiver 410 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 410 may include various components, where different combinations of components may implement different RATs.
[0064] Figure 5 is a block diagram of an exemplary BS 500 according to some aspects of the present disclosure. For example, BS 500 may be as described above in Figure 11 or BS 204 described in other figures. As shown, BS 500 may include a processor 502, a memory 504, a PDU transmission module 508, a communication interface 509, a transceiver 510 including a modem subsystem 512 and an RF unit 514, and one or more antennas 516. These elements may communicate with each other directly or indirectly, for example, via one or more buses.
[0065] The processor 502 may have various features as a special-purpose type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 502 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.
[0066] The memory 504 may include cache memory (e.g., cache memory of the processor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 504 may include non-transitory computer-readable media. The memory 504 may store instructions 506. The instructions 506 may include instructions that, when executed by the processor 502, cause the processor 502 to perform the operations described herein (e.g., Figures 2 to 3 and Figure 6 to Figure 1 6 and various aspects of FIG. 18). Instructions 506 may also be referred to as code, which may be broadly interpreted as including the above reference Figure 4 Any type of computer-readable statement(s) in question.
[0067] The PDU transmission module 508 can communicate with the communication interface 509 to receive a message from another device or send a message to another device. Each of the PDU transmission module 508 and the communication interface 509 can be implemented via hardware, software, or a combination thereof. For example, each of the PDU transmission module 508 and the communication interface 509 can be implemented as a processor, a circuit, and / or an instruction 506 stored in the memory 504 and executed by the processor 502. In some examples, the PDU transmission module 508 and the communication interface 509 can be integrated in the modem subsystem 512. For example, the PDU transmission module 508 and the communication interface 509 can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 512. In some examples, the UE may include one of the PDU transmission module 508 and the communication interface 509. In other examples, the UE may include both of the PDU transmission module 508 and the communication interface 509.
[0068] The PDU sending module 508 and the communication interface 509 may be used in various aspects of the present disclosure, for example, Figures 2 to 3 and Figures 6 to 8 The PDU transmission module 508 is configured to allocate and transmit uplink and / or downlink scheduling grants to UEs, and to confirm or not confirm receipt of data from UEs.
[0069] The communication interface 509 is configured to coordinate with the PDU sending module 508 to send a scheduling grant to the UE. The communication interface 509 is also configured to receive uplink data from the UE.
[0070] As shown, the transceiver 510 may include a modem subsystem 512 and an RF unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices, such as UE 115 and / or 400 and / or another core network element. The modem subsystem 512 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) modulated / encoded data (e.g., BWP frequency hopping configuration and instructions, PDCCH, PDSCH) from the modem subsystem 512 (on outbound transmissions) or from another source, such as UE 115 and 400. The RF unit 514 may also be configured to perform analog beamforming in combination with digital beamforming. Although shown as integrated together in transceiver 510, modem subsystem 512 and RF unit 514 may be separate devices that are coupled together at BS 105 to enable BS 105 to communicate with other devices.
[0071] The RF unit 514 may provide modulated and / or processed data (e.g., data packets, or more generally, data messages that may include one or more data packets and other information) to the antenna 516 for transmission to one or more other devices. For example, according to aspects of the present disclosure, this may include the transmission of information for completing attachment to a network and communication with a resident UE 115 or 400. The antenna 516 may also receive data messages sent from other devices and provide received data messages for processing and / or demodulation at the transceiver 510. The transceiver 510 may provide demodulated and decoded data (e.g., channel reports, PUSCH, PUCCH, HARQ ACK / NACK) to the PDU transmission module 508 and / or the communication interface 509 for processing. The antenna 516 may include multiple antennas of similar or different designs to maintain multiple transmission links.
[0072] In one aspect, the BS 500 may include multiple transceivers 510 that implement different RATs (e.g., NR and LTE). In one aspect, the BS 500 may include a single transceiver 510 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 510 may include various components, where different combinations of components may implement different RATs.
[0073] Figure 6 The present disclosure is illustrated in accordance with aspects of Figure 3 The method 600 describes a logic flow diagram executed by a UE corresponding to the automatic transmission scheme shown in FIG. 600 describes a method of transmitting a reduced priority PDU (e.g., Figure 2 212 or Figure 3 313) in UE behavior.
[0074] The steps of method 600 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable components for performing the steps. For example, a wireless communication device (such as UE 115 or UE 400) may utilize one or more components (such as a processor 402, a memory 404, a PDU transmission module 408, a communication interface 409, a transceiver 410, a modem 412, and one or more antennas 416) to perform the steps of method 600. Method 600 may be combined with the above description of Figure 3300 is used for describing. As illustrated, method 600 includes a plurality of enumerated steps, but aspects of method 600 include additional steps before, after, and between these enumerated steps. In some aspects, one or more of these enumerated steps may be omitted or performed in a different order.
[0075] In step 602, the UE may obtain a PDU for transmission on a first configured grant PUSCH instance. For example, the first configured grant PUSCH instance may be a configured grant opportunity, a configured grant PUSCH, etc. Figure 3 As shown, the configuration grant PUSCH 303 may be allocated to transmit the PDU 313 .
[0076] At step 604, the UE may detect the priority reduction information indicating that the first configuration grant PUSCH instance is reduced in priority due to channel overlap. Figure 2 As shown, when the configuration grant PUSCH 202 conflicts with the dynamic grant PUSCH 214 in time, the configuration grant PUSCH 202 can be deprioritized. In some aspects, the deprioritization of the configuration grant PUSCH can occur in the PHY layer, and thus, the deprioritization information is detected based on an indication from the PHY layer. In some aspects, the deprioritization information can be detected based on an indication to the MAC layer.
[0077] At step 606, the priority-reduced PDU originally associated with the first configuration grant PUSCH instance is automatically transmitted on the second configuration grant PUSCH instance. Figure 3 As shown, the reduced priority PDU 313 originally assigned to the configuration grant PUSCH 303 is subsequently transmitted on the next configuration grant PUSCH 304.
[0078] In some aspects, the second configuration grants a PUSCH instance (eg, Figure 3 304) with the first symbol of the instance with reduced priority (e.g., Figure 2 204 in) or a first configuration authorization PUSCH instance (eg, Figure 3 303 in 3GPP TS 38.214). The threshold duration may be determined by the network. In this way, a minimum time interval between the initially allocated configuration grant PUSCH instance and the next configuration grant PUSCH instance used to send a PDU with reduced priority may be guaranteed. In some aspects, the threshold duration is determined based on the PUSCH preparation time (e.g., the time between the DCI and the first symbol of the dynamically granted PUSCH). The threshold duration may be calculated by a function of the subcarrier spacing defined in 3GPP TS 38.214.
[0079] In some aspects, a configuration grant configuration (eg, configuration grant periodicity, repetition, configuration grant timer, configuration grant retransmission timer, etc.) of the first configuration grant instance may be determined or deemed permissible based in part on a threshold duration.
[0080] In some aspects, the UE may determine whether the second configuration grant PUSCH instance is capable of transmitting a reduced priority PDU. For example, when the transport block size of the second configuration grant PUSCH instance is smaller than the transport block size of the first configuration grant PUSCH instance or smaller than the size of the reduced priority PDU, the UE may determine that the second configuration grant PUSCH instance cannot transmit the reduced priority PDU and may discard the PDU. In another aspect, the transport block size of the second configuration grant PUSCH instance may be different from the transport block size of the first configuration grant PUSCH instance - this may occur upon activation or update of an uplink configuration grant.
[0081] In some aspects, the reduced priority PDU may be sent in the next configured grant PUSCH instance using the same or a different HARQ process ID as the first configured grant PUSCH instance.
[0082] Figure 7 The present invention is used to implement Figure 6 The sending timeline of the automatic sending scheme shown in FIG. 700 describes, Figure 6 The method 600 in the embodiment may be implemented by stopping configuring the grant retransmission timer when the priority reduction information is detected. In this way, the UE may process the priority reduction in a similar manner as receiving a NACK from the BS.
[0083] For example, diagram 700 shows that UE 115 can be at 701 (similar to Figure 6UE 115 may maintain two timers at 702, a configuration grant retransmission timer and a configuration grant timer. At 703, the HARQ process at UE 115 may receive downlink feedback information from BS 105, or priority reduction information. If the feedback information at 703 is an ACK from BS 105, UE 115 may stop the configuration grant retransmission timer if the configuration grant retransmission timer is already running, and may also stop the configuration grant timer if the configuration grant timer is already running. If a NACK is received from BS 105 at 713 or an indication of priority reduction (e.g., via an indication from the PHY layer or an indication to the MAC layer), UE 115 may stop the configuration grant retransmission timer at 714 if the configuration grant retransmission timer is already running. In this way, when the configuration grant retransmission timer stops, UE 115 may send a PDU with reduced priority in a new / next configuration grant PUSCH.
[0084] In some aspects, when ACK / NACK is available in non-NR-U situations, the NACK at ACK 703 or 713 may be optional, but as long as the priority reduction information is detected, at 714, the UE may stop the configured grant retransmission timer if it is already running.
[0085] In some aspects, the configuration grant retransmission timer is set equal to or greater than the configuration grant timer. Thus, when there is no priority reduction, the configuration grant retransmission timer will not expire before the configuration grant timer.
[0086] Figure 8 800 describes a logic flow diagram performed by a UE corresponding to an alternative embodiment of an automatic transmission scheme according to aspects of the present disclosure. Method 800 describes attempting to transmit a reduced priority PDU (e.g., Figure 2 212 or Figure 3 313) and the UE behavior of discarding the PDU if no available configured authorized PUSCH instance is found.
[0087] The steps of method 800 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable components for performing the steps. For example, a wireless communication device (such as UE 115 or UE 400) may utilize one or more components (such as a processor 402, a memory 404, a PDU sending module 408, a communication interface 409, a transceiver 410, a modem 412, and one or more antennas 416) to perform the steps of method 800. Method 800 may be combined with the above description of Figure 3 As shown, method 800 includes a plurality of enumerated steps, but aspects of method 800 include additional steps before, after, and between these enumerated steps. In some aspects, one or more of these enumerated steps may be omitted or performed in a different order.
[0088] Method 800 can be obtained from Figure 6 The UE may start at step 604 in step 803. At step 803, the UE may retrieve a next configuration grant PUSCH instance, such as configuration grant 304, which is next in time to the configuration grant 303 with a reduced priority. At 805, the UE may determine whether the next configuration grant PUSCH instance is available, for example, whether the next configuration grant PUSCH instance is also reduced in priority, or whether it has been allocated to another PDU, etc.
[0089] At step 806, if the next configured grant PUSCH is available, the method 800 proceeds to step 807, where the UE transmits the reduced priority PDU on the next configured grant PUSCH instance.
[0090] In step 808, if the next configured grant PUSCH is not available, the UE may optionally discard the PDU. Alternatively, in step 808, the UE may record a count of the total number of transmission attempts for the same PDU so far, for example by increasing the attempt count by one. In step 810, if the total number of attempts is greater than a threshold number of attempts, the UE may discard the PDU in step 812. Otherwise, if the total number of attempts is less than the threshold number of attempts, method 800 may repeat to step 803, in which the UE may look for another potential configured grant PUSCH instance. Therefore, in this way, method 800 allows a maximum threshold number of attempts before discarding the PDU. The threshold number of attempts may be configured by the network and sent from the BS to the UE via RRC signaling, system information, etc.
[0091] Information and signals may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0092] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0093] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, these functions can be stored or sent on a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the above functions can be implemented using software, hardware, firmware, hard wiring, or any combination thereof executed by a processor. The features that implement the functions can also be physically located in various locations, including being distributed so that the various parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), the "or" used in a list of items (e.g., a list of items beginning with words such as "at least one of..." or "one or more of...") represents an inclusive list, so that, for example, a list of [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).
[0094] As will be appreciated by those skilled in the art and depending on the particular application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific aspects illustrated and described herein (as they are merely examples of the present disclosure), but should correspond fully to the scope of the appended claims and their functional equivalents.
Claims
1. A method of wireless communication, comprising: Obtaining, at a user equipment UE, a protocol data unit PDU for transmission on a first configured authorized physical uplink shared channel PUSCH instance; detecting, at the UE, priority reduction information indicating that the first configuration grant PUSCH instance is reduced in priority due to channel overlap; In response to receiving the priority reduction information, terminating an already running configuration grant retransmission timer at the UE; and The PDU originally associated with the first configured grant PUSCH instance is automatically sent on the second configured grant PUSCH instance without waiting for scheduling information of a base station BS scheduling a retransmission grant for sending the PDU.
2. The method according to claim 1, wherein the configured grant retransmission timer is greater than or equal to the configured grant timer. 3 . The method according to claim 1 , wherein the priority reduction information is detected based on an indication from a physical layer of the UE. 4 . The method according to claim 1 , wherein the priority reduction information is detected based on an indication of a medium access control (MAC) layer of the UE.
5. The method of claim 1, wherein the second configuration grants a PUSCH instance having a first symbol that starts at a time greater than a threshold duration away from an end of a priority-reduced instance or a last symbol of the first configuration grants a PUSCH instance. The method of claim 5 , wherein the threshold duration is configured by a network.
7. The method of claim 6, wherein the threshold duration is configured by the network based on one or more of a PUSCH preparation time or a subcarrier spacing.
8. The method of claim 5, wherein the first configuration grant PUSCH instance is associated with a configuration grant configuration, the configuration grant configuration being determined or deemed allowed based in part on the threshold duration.
9. The method of claim 8, wherein the configuring the grant configuration comprises one or more of configuring grant periodicity, repetition, configuring a grant timer, or configuring a grant retransmission timer.
10. The method according to claim 1, further comprising: In response to receiving additional priority reduction information that the second configuration grant PUSCH instance is also downgraded, the PDU originally associated with the first configuration grant PUSCH instance is automatically sent on a third configuration grant PUSCH instance.
11. The method according to claim 7, further comprising: In response to determining that a threshold number of automatic transmission attempts of the PDU originally associated with the first configured granted PUSCH instance on a new configured granted PUSCH instance has been reached, the PDU is discarded. The method of claim 11 , wherein the threshold number is configured by a network.
13. The method according to claim 1, further comprising: In response to determining that the second configuration authorized PUSCH instance cannot send the PDU, discarding the PDU.
14. The method according to claim 13, wherein the determining that the second configuration authorizes the PUSCH instance to be unable to send the PDU comprises: Determine that the transport block size of the PUSCH instance authorized by the second configuration is less than one of the following: The first configuration authorizes a transport block size for a PUSCH instance, and The size of the PDU.
15. A user equipment UE for wireless communication, comprising: The processor is configured as: obtaining a protocol data unit (PDU) for transmission on a first configured granted physical uplink shared channel (PUSCH) instance, detecting, at the UE, priority reduction information indicating that the first configuration grant PUSCH instance is reduced in priority due to channel overlap, and In response to receiving the priority reduction information, terminating a configuration grant retransmission timer that is already running; and The transceiver is configured to automatically send the PDU originally associated with the first configuration grant PUSCH instance on a second configuration grant PUSCH instance without waiting for scheduling information of a base station BS scheduling a retransmission grant for sending the PDU.
16. The UE according to claim 15, wherein the configured grant retransmission timer is greater than or equal to the configured grant timer.
17. The UE of claim 15, wherein the priority reduction information is detected based on an indication from a physical layer of the UE.
18. The UE according to claim 15, wherein the priority reduction information is detected based on an indication of a medium access control (MAC) layer of the UE.
19. The UE of claim 15, wherein the second configuration grants a PUSCH instance having a first symbol that starts at a time greater than a threshold duration from an end of a priority-reduced instance or a last symbol of the first configuration grants a PUSCH instance.
20. The UE of claim 19, wherein the threshold duration is configured by a network.
21. The UE of claim 20, wherein the threshold duration is configured by the network based on one or more of a PUSCH preparation time or a subcarrier spacing.
22. The UE of claim 19, wherein the first configuration grant PUSCH instance is associated with a configuration grant configuration, the configuration grant configuration being determined or deemed allowed based in part on the threshold duration.
23. The UE of claim 22, wherein the configuring the grant configuration comprises one or more of configuring grant periodicity, repetition, configuring a grant timer, or configuring a grant retransmission timer.
24. The UE according to claim 15, wherein the transceiver is further configured to: In response to receiving additional priority reduction information that the second configuration grant PUSCH instance is also downgraded, the PDU originally associated with the first configuration grant PUSCH instance is automatically sent on a third configuration grant PUSCH instance.
25. The UE according to claim 21, wherein the processor is further configured to: In response to determining that a threshold number of automatic transmission attempts of the PDU originally associated with the first configured granted PUSCH instance on a new configured granted PUSCH instance has been reached, the PDU is discarded.
26. The UE of claim 25, wherein the threshold number is configured by a network.
27. The UE according to claim 15, wherein the processor is further configured to: In response to determining that the second configuration authorized PUSCH instance cannot send the PDU, discarding the PDU.
28. The UE according to claim 27, wherein the processor is further configured to determine that the second configuration authorizes the PUSCH instance to be unable to send the PDU by: Determine that the transport block size of the PUSCH instance authorized by the second configuration is less than one of the following: The first configuration authorizes a transport block size for a PUSCH instance, and The size of the PDU.
29. A processor-readable non-transitory storage medium storing processor-executable instructions for wireless communications, the instructions being executed by a processor to perform operations comprising: Obtaining, at a user equipment UE, a protocol data unit PDU for transmission on a first configured authorized physical uplink shared channel PUSCH instance; detecting, at the UE, priority reduction information indicating that the first configuration grant PUSCH instance is reduced in priority due to channel overlap; In response to receiving the priority reduction information, terminating an already running configuration grant retransmission timer at the UE; and The PDU originally associated with the first configured grant PUSCH instance is automatically sent on the second configured grant PUSCH instance without waiting for scheduling information of a base station BS scheduling a retransmission grant for sending the PDU.
30. The medium of claim 29, wherein the configured grant retransmission timer is greater than or equal to a configured grant timer.
31. The medium of claim 29, wherein the priority reduction information is detected based on an indication from a physical layer of the UE.
32. The medium of claim 29, wherein the priority reduction information is detected based on an indication of a medium access control (MAC) layer of the UE.
33. The medium of claim 29, wherein the second configuration grants a PUSCH instance having a first symbol that begins at a time greater than a threshold duration from an end of a priority-reduced instance or a last symbol of the first configuration grants a PUSCH instance.
34. The medium of claim 33, wherein the threshold duration is configured by a network.
35. The medium of claim 34, wherein the threshold duration is configured by the network based on one or more of a PUSCH preparation time or a subcarrier spacing.
36. The medium of claim 33, wherein the first configuration grant PUSCH instance is associated with a configuration grant configuration, the configuration grant configuration being determined or deemed allowed based in part on the threshold duration.
37. The medium of claim 36, wherein the configuring grant configuration comprises one or more of configuring grant periodicity, repetition, configuring a grant timer, or configuring a grant retransmission timer.
38. The medium of claim 29, wherein the operations further comprise: In response to receiving additional priority reduction information that the second configuration grant PUSCH instance is also downgraded, the PDU originally associated with the first configuration grant PUSCH instance is automatically sent on a third configuration grant PUSCH instance.
39. The medium of claim 35, wherein the operations further comprise: In response to determining that a threshold number of automatic transmission attempts of the PDU originally associated with the first configured granted PUSCH instance on a new configured granted PUSCH instance has been reached, the PDU is discarded.
40. The medium of claim 39, wherein the threshold amount is configured by a network.
41. The medium of claim 29, wherein the operations further comprise: In response to determining that the second configuration authorized PUSCH instance cannot send the PDU, discarding the PDU.
42. The medium of claim 41 , wherein the determining that the second configuration authorizes the PUSCH instance to not transmit the PDU comprises: Determine that the transport block size of the PUSCH instance authorized by the second configuration is less than one of the following: The first configuration authorizes a transport block size for a PUSCH instance, and The size of the PDU.
43. A wireless communication system, comprising: means for obtaining, at a user equipment UE, a protocol data unit PDU for transmission on a first configured granted physical uplink shared channel PUSCH instance; means for detecting, at the UE, priority reduction information indicating that the first configuration grant PUSCH instance is reduced in priority due to channel overlap; means for terminating, at the UE, an already running configuration grant retransmission timer in response to receiving the priority reduction information; as well as Means for automatically sending said PDU originally associated with said first configured grant PUSCH instance on a second configured grant PUSCH instance without waiting for scheduling information of a base station BS scheduling a retransmission grant for sending said PDU.
44. The system of claim 43, wherein the configured grant retransmission timer is greater than or equal to the configured grant timer.
45. The system of claim 43, wherein the priority reduction information is detected based on an indication from a physical layer of the UE.
46. The system of claim 43, wherein the priority reduction information is detected based on an indication of a medium access control (MAC) layer of the UE.
47. The system of claim 43, wherein the second configuration grants a PUSCH instance having a first symbol that begins at a time greater than a threshold duration from an end of a priority-reduced instance or a last symbol of the first configuration grants a PUSCH instance.
48. The system of claim 47, wherein the threshold duration is configured by a network.
49. The system of claim 48, wherein the threshold duration is configured by the network based on one or more of a PUSCH preparation time or a subcarrier spacing.
50. The system of claim 47, wherein the first configuration grant PUSCH instance is associated with a configuration grant configuration, the configuration grant configuration being determined or deemed allowed based in part on the threshold duration.
51. The system of claim 50, wherein the configuring grant configuration comprises one or more of configuring grant periodicity, repetition, configuring a grant timer, or configuring a grant retransmission timer.
52. The system of claim 43, further comprising: means for automatically sending said PDU originally associated with said first configuration grant PUSCH instance on a third configuration grant PUSCH instance in response to receiving additional priority reduction information that said second configuration grant PUSCH instance is also downgraded.
53. The system of claim 43, further comprising: means for discarding the PDU in response to determining that a threshold number of automatic transmission attempts of the PDU originally associated with the first configured granted PUSCH instance on a new configured granted PUSCH instance has been reached.
54. The system of claim 53, wherein the threshold number is configured by a network.
55. The system of claim 43, further comprising: means for discarding the PDU in response to determining that the second configuration authorizes the PUSCH instance to be unable to transmit the PDU.
56. The system of claim 55, wherein the means for discarding the PDU in response to determining that the second configuration grants a PUSCH instance that cannot transmit the PDU comprises: Means for determining that the transport block size of the PUSCH instance granted by the second configuration is less than one of: The first configuration authorizes a transport block size for a PUSCH instance, and The size of the PDU.
