Hybrid Automatic Repeat Request Process Determination for Extended Semi-Persistent Scheduling and / or Configured Grant Configuration

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a network entity can transmit, and a user equipment (UE) can receive, a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion. The network entity and the UE can communicate, for each transmission occasion in the pre-scheduled burst of the transmission occasion, a transport block associated with a hybrid automatic repeat request (HARQ) process identifier that is transmitted during the respective transmission occasion and is associated with the HARQ configuration that is at least partially based on the scheduling configuration. Numerous other aspects are described.

Description

Technical Field

[0001] Cross - reference to Related Applications This patent application claims priority to U.S. Provisional Patent Application No. 63 / 365,185, filed on May 23, 2022, and U.S. Non - Provisional Patent Application No. 18 / 314,329, filed on May 9, 2023, both entitled "HYBRID AUTOMATIC REPEAT REQUEST PROCESS DETERMINATION FOR ENHANCED SEMI - PERSISTENT SCHEDULING AND / OR CONFIGURED GRANT CONFIGURATION", which are hereby incorporated by reference in their entirety.

[0002] Aspects of the present disclosure generally relate to wireless communication and relate to techniques and apparatus associated with hybrid automatic repeat request (HARQ) process determination for enhanced semi - persistent scheduling (SPS) and / or configured grant (CG) configuration.

Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system can adopt a multiple access technology that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standards published by the Third Generation Partnership Project (3GPP (registered trademark)).

[0004] A wireless network can include one or more network nodes that support communication for wireless communication devices such as a user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communication and uplink communication. "Downlink" (or "DL") refers to the communication link from the network node to the UE, and "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks can support device-to-device communication via local links (e.g., side link (SL), wireless local area network (WLAN) link, and / or wireless personal area network (WPAN) link, among others).

[0005] The above multi-connectivity technology has been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the urban, national, regional, and / or global scale. New Radio (NR), which can be referred to as 5G, is a set of extensions to the LTE mobile standard published by the 3GPP (registered trademark). NR is designed to better support mobile broadband Internet access through improvements in spectral efficiency, cost reduction, service improvement, utilization of new spectra, and the use of orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the downlink (CP-OFDM), the use of CP-OFDM and / or single-carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink for better integration with other open standards, and support for beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Since the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful.

Summary of the Invention

[0006] Some aspects described in this specification relate to a user equipment (UE) for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive, from a network entity, a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission occasions. The one or more processors may be configured to communicate, for each transmission occasion in the pre-scheduled burst of transmission occasions, a transport block associated with a hybrid automatic repeat request (HARQ) process identifier that is transmitted during the respective transmission occasion and is at least partially based on an HARQ configuration associated with the scheduling configuration.

[0007] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to transmit, to a UE, a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission occasions. The one or more processors may be configured to communicate, for each transmission occasion in the pre-scheduled burst of transmission occasions, a transport block associated with an HARQ process identifier that is transmitted during the respective transmission occasion and is at least partially based on an HARQ configuration associated with the scheduling configuration.

[0008] Some aspects described herein relate to a method of wireless communication performed by a UE. The method can include receiving, from a network entity, a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion. The method can include, for each transmission occasion in the pre-scheduled burst of the transmission occasion, communicating a transport block associated with a HARQ process identifier that is transmitted during the respective transmission occasion and is associated with a HARQ configuration that is at least partially based on the scheduling configuration.

[0009] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method can include transmitting, to a UE, a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion. The method can include, for each transmission occasion in the pre-scheduled burst of the transmission occasion, communicating a transport block associated with a HARQ process identifier that is transmitted during the respective transmission occasion and is associated with a HARQ configuration that is at least partially based on the scheduling configuration.

[0010] Some aspects described herein relate to a non - transitory computer - readable medium storing a set of instructions for wireless communication by a UE. When the set of instructions is executed by one or more processors of the UE, the UE can be caused to receive, from a network entity, a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre - scheduled burst of transmission occasions. When the set of instructions is executed by one or more processors of the UE, for each transmission occasion in a pre - scheduled burst of transmission occasions, the UE can be caused to communicate a transport block that is transmitted during the respective transmission occasion and is associated with a HARQ process identifier that is at least partially based on a HARQ configuration associated with the scheduling configuration.

[0011] Some aspects described herein relate to a non - transitory computer - readable medium storing a set of instructions for wireless communication by a network entity. When the set of instructions is executed by one or more processors of the network entity, the network entity can be caused to transmit, to a UE, a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre - scheduled burst of transmission occasions. When the set of instructions is executed by one or more processors of the network entity, for each transmission occasion in a pre - scheduled burst of transmission occasions, the network entity can be caused to communicate a transport block that is transmitted during the respective transmission occasion and is associated with a HARQ process identifier that is at least partially based on a HARQ configuration associated with the scheduling configuration.

[0012] Some aspects described in this specification relate to an apparatus for wireless communication. The apparatus can include means for receiving a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission opportunities from a network entity. The apparatus can include means for communicating, for each transmission opportunity in a pre-scheduled burst of transmission opportunities, a transport block associated with a HARQ process identifier that is transmitted during the respective transmission opportunity and that is associated with a HARQ configuration that is at least partially based on the scheduling configuration.

[0013] Some aspects described in this specification relate to an apparatus for wireless communication. The apparatus can include means for transmitting to a UE a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission opportunities. The apparatus can include means for communicating, for each transmission opportunity in a pre-scheduled burst of transmission opportunities, a transport block associated with a HARQ process identifier that is transmitted during the respective transmission opportunity and that is associated with a HARQ configuration that is at least partially based on the scheduling configuration.

[0014] Aspects are generally described in this specification with reference to the drawings, the specification, and the appendices, and include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, wireless communication devices, and / or processing systems as shown by the drawings, the specification, and the appendices.

[0015] In the foregoing, the features and technical advantages of the examples according to the present disclosure have been outlined rather extensively so as to better understand the following "Modes for Carrying Out the Invention". Additional features and advantages are described below. The concepts and specific examples of the disclosure can be readily utilized as a basis for modifying or designing other structures for achieving the same object of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein will be better understood by considering both their configurations and operating methods, along with the associated advantages, in relation to the following description with reference to the accompanying drawings. Each of the drawings is provided for purposes of illustration and explanation, rather than as a definition of the limitations of the claims.

[0016] To better understand the above-listed features of the present disclosure in detail, a more detailed description, briefly summarized above, may be obtained by referring to some of the aspects shown in the accompanying drawings. However, it should be noted that the accompanying drawings show only specific exemplary aspects of the present disclosure and, therefore, should not be regarded as limiting the scope of the present disclosure, as the description may recognize other equally effective aspects. The same reference numerals in different drawings can identify the same or similar elements.

Brief Description of the Drawings

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

DETAILED DESCRIPTION OF THE INVENTION

[0018] Various aspects of the present disclosure will be described more fully hereinafter with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be understood by those skilled in the art that the scope of the disclosure herein is intended to cover any other aspect of the disclosure, whether implemented independently of or in combination with any other aspect of the disclosure herein. For example, any number of the aspects described herein can be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to cover such apparatus or methods practiced using other structures, functions, or combinations of structures and functions in addition to, or other than, the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0019] Next, some aspects of a telecommunications system will be shown with reference to various devices and techniques. These devices and techniques are described in the context of embodiments for carrying out the following inventions and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or as software depends on the specific application and the design constraints imposed on the overall system.

[0020] Aspects may be described herein using terms generally associated with 5G or New Radio (NR) radio access technology (RAT), but aspects of the present disclosure can be applied to other RATs such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0021] FIG. 1 is a diagram showing an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be, among other examples, a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements thereof. The wireless network 100 may include one or more network nodes 110 (shown as network nodes 110a, 110b, 110c, and 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UEs 120a, 120b, 120c, 120d, and 120e), and / or other entities. As shown in the figure, the network node 110 can include one or more network nodes. For example, the network node 110 may be an integrated network node, which means that the integrated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, the network node 110 may be a non-integrated network node (sometimes referred to as a non-integrated base station), which means that the network node 110 is configured to utilize a radio protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs), etc.).

[0022] In some embodiments, network node 110 is, or includes, a network entity such as a RU that communicates with UE 120 via a radio access link. In some embodiments, network node 110 is, or includes, a network entity such as a DU that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some embodiments, network node 110 is, or includes, a network entity such as a CU that communicates with other network nodes 110 via a midhaul link or with a core network via a backhaul link. In some aspects, network node 110 (such as a centralized network node 110 or a non-centralized network node 110) may include a plurality of network nodes, such as one or more RUs, one or more DUs, and / or one or more CUs. Network node 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmission reception point (TRP), an RU, a DU, a CU, a network mobility element, a core network node, a network element, network equipment, a RAN node, or a combination thereof. In some embodiments, network node 110 can interconnect with each other and / or with one or more other network nodes 110 within wireless network 100 using any suitable transport network through various types of fronthaul, midhaul, and / or backhaul interfaces such as direct physical connections, air interfaces, or virtual networks.

[0023] In some aspects, network node 110 can provide communication coverage for a specific geographical area. In the 3rd Generation Partnership Project (3GPP (registered trademark)), the term "cell" can refer to the coverage area of a base station and / or the base station subsystem providing services in this coverage area, depending on the context in which the term is used. Network node 110 can provide communication coverage for macro cells, pico cells, femto cells, and / or another type of cell. A macro cell can cover a relatively large geographical area (e.g., several kilometers in radius) and can enable unrestricted access by UEs 120 subscribed to the service. A pico cell can cover a relatively small geographical area and can enable unrestricted access by UEs 120 subscribed to the service. A femto cell can cover a relatively small geographical area (e.g., a home) and can enable restricted access by UEs 120 associated with the femto cell (e.g., UEs 120 within a closed subscriber group (CSG)). The base station for a macro cell may be called a macro base station. The base station for a pico cell may be called a pico base station. The base station for a femto cell may be called a femto base station or a home base station. In the example shown in FIG. 1, network node 110a may be a macro base station for macro cell 102a, network node 110b may be a pico base station for pico cell 102b, and network node 110c may be a femto base station for femto cell 102c. A base station can support one or more (e.g., three) cells.

[0024] In some embodiments, the cell may not necessarily be stationary, and the geographical area of the cell can move according to the location of the network node 110 that is mobile (e.g., a mobile base station).

[0025] Wireless network 100 may include one or more relay nodes. A relay node is a network node that can receive the transmission of data from an upstream node (e.g., network node 110 or UE 120) and send the transmission of data to a downstream node (e.g., UE 120 or network node 110). The relay node may be a UE 120 that can relay the transmissions of other UEs 120 or network nodes 110. In the embodiment shown in FIG. 1, network node 110d (e.g., relay base station) may communicate with network node 110a (e.g., macro base station) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 that relays communication may sometimes be referred to as a relay node, relay base station, relay node, relay, etc.

[0026] Wireless network 100 can be a heterogeneous network including different types of network nodes 110, such as macro base stations, pico base stations, femto base stations, relay base stations, TRPs, RUs, etc. These different types of network nodes 110 may have different transmission power levels, different coverage areas, and / or different impacts on interference in wireless network 100. For example, a macro base station may have a high transmission power level (e.g., 5 - 40 watts), while pico base stations, femto base stations, and relay base stations may have a lower transmission power level (e.g., 0.1 - 2 watts).

[0027] Network controller 130 can be coupled to or communicate with a set of network nodes 110 and may perform coordination and control for these network nodes 110. Network controller 130 may communicate with network nodes 110 via a backhaul communication link or a midhaul communication link. Network nodes 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links. In some aspects, network controller 130 may include a CU or a core network device.

[0028] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be fixed or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a game device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, a UE function of a network node, and / or any other suitable device configured to communicate via a wireless medium.

[0029] Some UEs 120 may be regarded as machine-type communication (MTC) UEs, or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs and / or eMTC UEs can communicate with, for example, a network node, another device (such as a remote device), or some other entity, and may include robots, drones, remote devices, sensors, meters, monitors, and / or location tags. Some UEs 120 may be regarded as Internet-of-Things (IoT) devices and / or may be implemented as narrowband IoT (NB-IoT) devices. Some UEs 120 may be regarded as customer premise equipment. The UEs 120 may be included inside a housing that houses components of the UEs 120, such as a processor component and / or a memory component. In some embodiments, the processor component and the memory component may be coupled together. For example, the processor component (such as one or more processors) and the memory component (such as a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0030] In some embodiments, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, the UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include, for example, vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol), and / or a mesh network. In such embodiments, the UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere in this specification as being performed by the network node 110.

[0031] In general, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a particular RAT and operate on one or more frequencies. The RAT can be referred to as a radio technology, air interface, etc. The frequency can be referred to as a carrier, frequency channel, etc. To avoid interference between wireless networks of different RATs, each frequency can support a single RAT in a given geographical area. In some cases, an NR network or a 5G RAT network may be deployed.

[0032] The devices of the wireless network 100 can communicate using the electromagnetic spectrum that can be re-divided into various classes, bands, channels, etc. according to frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a part of FR1 is higher than 6 GHz, it should be understood that FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise regarding FR2, which, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band, is often (interchangeably) referred to as the "millimeter wave" band in documents and papers.

[0033] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. In recent 5G NR research, the operating bands for these intermediate band frequencies are identified as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus, in effect, the features of FR1 and / or FR2 can be extended to the intermediate band frequencies. In addition, in order to extend 5G NR operation beyond 52.6 GHz, higher frequency bands are currently being explored. For example, three higher operating bands are identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is included within the EHF band.

[0034] With the above examples in mind, unless otherwise specified, terms such as "sub-6 GHz", when used in this specification, may be understood to broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include intermediate band frequencies. Further, unless otherwise specified, terms such as "millimeter wave", when used in this specification, may be understood to broadly represent frequencies that may include intermediate band frequencies, may be within FR2, FR4, FR4-a, or FR4-1, and / or FR5, or may be within the EHF band. The frequencies included within these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be subject to modification, and the techniques described herein are intended to be applicable to those modified frequency ranges.

[0035] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere in this specification, the communication manager 140 receives a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission occasions from a network entity (e.g., network node 110), and for each transmission occasion in the pre-scheduled burst of transmission occasions, processes and communicates a transport block associated with a hybrid automatic repeat request (HARQ) process identifier that is transmitted during the respective transmission occasion and is at least partially based on the HARQ configuration associated with the scheduling configuration. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0036] In some aspects, a network entity (e.g., network node 110) can include a communication manager 150. As described in more detail elsewhere in this specification, the communication manager 150 can transmit to the UE 120 a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion, and for each transmission occasion in the pre-scheduled burst of the transmission occasion, communicate a transport block that is transmitted during the respective transmission occasion and that is associated with a HARQ process identifier that is at least partially based on a HARQ configuration associated with the scheduling configuration. Additionally, alternatively, or instead, the communication manager 150 can perform one or more other operations described herein.

[0037] As noted above, FIG. 1 is provided as one example. Other examples may differ from those described with respect to FIG. 1.

[0038] FIG. 2 is a diagram illustrating one example 200 of a network node 110 communicating with a UE 120 within a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a-234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas, such as antennas 252a-252r, where R≥1. The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 can include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. For example, some network nodes 110 may not include radio frequency components.

[0039] At network node 110, transmit processor 220 may receive data destined for UE 120 (or a set of UEs 120) from data source 212. Transmit processor 220 may select one or more modulation and coding schemes (MCSs) for UE 120, at least in part based on one or more channel quality indicators (CQIs) received from UE 120. Network node 110 may process (e.g., encode and modulate) data for UE 120, at least in part based on the selected MCS(s) for UE 120, and provide data symbols to UE 120. Transmit processor 220 may process system information and control information (e.g., CQI requests, grants, and / or higher layer signaling, e.g., regarding semi-static resource partitioning information (SRPI)), and provide overhead symbols and control symbols. Transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signal (CRS) or demodulation reference signal (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). Transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding), if applicable, on data symbols, control symbols, overhead symbols, and / or reference symbols, and provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a - 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of modem 232.Each modem 232 may use an individual modulator component to obtain an output sample stream and to process an individual output symbol stream (e.g., for OFDM). Each modem 232 may further use an individual modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a downlink signal. Modems 232a-232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) shown as antennas 234a-234t.

[0040] In UE120, a set of antennas 252 (shown as antennas 252a - 252r) may receive downlink signals from network node 110 and / or other network nodes 110, and provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) shown as modems 254a - 254r. For example, each received signal may be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use individual demodulator components to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain input samples. Each modem 254 may further process the input samples to obtain received symbols (e.g., for OFDM). The MIMO detector 256 may obtain received symbols from the modems 254, perform MIMO detection on the received symbols when applicable, and provide the detected symbols. The receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine, among other examples, reference signal received power (RSRP) parameters, received signal strength indicator (RSSI) parameters, reference signal received quality (RSRQ) parameters, and / or CQI parameters. In some embodiments, one or more components of UE120 may be included within the housing 284.

[0041] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices within a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0042] One or more antennas (e.g., antennas 234a - 234t and / or antennas 252a - 252r) may include, among other examples, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, or may be included therein. The antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements, a set of coplanar antenna elements, a set of non - coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting components and / or receiving components such as one or more components of FIG. 2, within a single housing or multiple housings.

[0043] On the uplink, at UE 120, transmission processor 264 can receive and process data from data source 262 and control information (e.g., for reporting including RSRP, RSSI, RSRQ, and / or CQI) from controller / processor 280. Transmission processor 264 can generate reference symbols for one or more reference signals. The symbols from transmission processor 264 can be precoded by TX MIMO processor 266, if applicable, and further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM) and transmitted to network node 110. In some embodiments, modem 254 of UE 120 can include a modulator and a demodulator. In some embodiments, UE 120 includes a transceiver. The transceiver can include any combination of antenna(s) 252, modem(s) 254, MIMO detector 256, receive processor 258, transmission processor 264, and / or TX MIMO processor 266. The transceiver can be used by a processor (e.g., controller / processor 280) and memory 282 to perform any aspect of the methods described herein (e.g., with reference to FIGS. 6 - 10).

[0044] At network node 110, uplink signals from UE 120 and / or other UEs are received by antenna 234, processed by modem 232 (e.g., the demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 if applicable, and further processed by receive processor 238 to obtain decoded data and control information sent by UE 120. Receive processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and can communicate with network controller 130 via communication unit 244. Network node 110 may include a scheduler 246 for scheduling one or more UEs 120 for downlink communication and / or uplink communication. In some embodiments, modem 232 of network node 110 may include a modulator and a demodulator. In some embodiments, network node 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver can be used by a processor (e.g., controller / processor 240) and memory 242 to perform any aspect of the methods described herein (e.g., with reference to FIGS. 6 - 10).

[0045] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) in FIG. 2 may perform one or more techniques associated with HARQ process determination for extended semi-persistent scheduling (SPS) and / or configured grant (CG) configurations, as described in more detail elsewhere in this specification. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or any other component(s) in FIG. 2 may perform or instruct the operations of, for example, process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes as described herein. The memories 242 and 282 can store data and program code for the network node 110 and the UE 120, respectively. In some embodiments, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions may be executed by one or more processors of the network node 110 and / or the UE 120 (e.g., directly, or after being compiled, converted, and / or interpreted) to cause the one or more processors, the UE 120, and / or the network node 110 to perform or instruct the operations of, for example, process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes as described herein. In some embodiments, executing the instructions may include, among other examples, running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions.

[0046] In some aspects, UE 120 includes means for receiving a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission opportunities from a network entity (e.g., network node 110), and / or for each transmission opportunity in a pre-scheduled burst of transmission opportunities, communicating a transport block that is transmitted during the respective transmission opportunity and is associated with a HARQ process identifier that is at least partially based on a HARQ configuration associated with the scheduling configuration. The means by which UE 120 performs the operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0047] In some aspects, a network entity (e.g., network node 110) includes means for transmitting to UE 120 a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission opportunities, and / or for each transmission opportunity in a pre-scheduled burst of transmission opportunities, communicating a transport block that is transmitted during the respective transmission opportunity and is associated with a HARQ process identifier that is at least partially based on a HARQ configuration associated with the scheduling configuration. In some aspects, the means for a network entity to perform the operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0048] Although the blocks in FIG. 2 are shown as separate components, the functions described above with respect to the blocks can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to the transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be implemented by or under the control of the controller / processor 280.

[0049] As described above, FIG. 2 is provided as one example. Other examples may differ from those described with respect to FIG. 2.

[0050] FIG. 3 is a diagram showing an example of a non - aggregated base station according to the present disclosure.

[0051] The deployment of a communication system such as a 5G NR system can be configured in multiple ways using various components or constituent parts. In a 5G NR system or network, a network node can be implemented in an aggregated architecture or a non - aggregated architecture. For example, a network node, or one or more units (or one or more components) that execute network node functions, may be implemented as an aggregated network node (sometimes called a stand - alone base station or a monolithic base station) or a non - aggregated network node. A "network entity" or "network node" may refer to a non - aggregated network node, an aggregated network node, or one or more entities of a non - aggregated network node (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof, etc.).

[0052] A centralized base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A non-centralized base station can be configured to utilize a protocol stack that is physically or logically distributed among two or more units (e.g., one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be collocated with the CU or, alternatively, can be geographically or virtually distributed across one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0053] The operation or network design of a base station type can consider the aggregation characteristics of base station functions. For example, a non-centralized base station can be utilized in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Non-aggregation can include distributing functions across two or more units at various physical locations and virtually distributing the functions of at least one unit, which can enable flexibility in network design. The various units of a non-centralized base station, or a non-centralized RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0054] The architecture of the non - centralized base station 300 can include one or more CU310s that can communicate directly with the core network 320 via a backhaul link or can communicate indirectly with the core network 320 through one or more non - centralized base station units (such as a Near - Real Time (Near - RT) RAN Intelligent Controller (RIC) 325 via an E2 link, or a Non - Real Time (Non - RT) RIC 315 associated with the Service Management and Orchestration (SMO) framework 305, or both). The CU310 can communicate with one or more DU330s via respective mid - haul links such as the F1 interface. The DU330 can communicate with one or more RU340s via respective front - haul links. The front - haul link, mid - haul link, and backhaul link are sometimes generally referred to as "communication links". The RU340 can communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some aspects, a UE 120 can be served simultaneously by multiple RU340s. The DU330 and RU340 are also sometimes referred to as "O - RAN DU (O - DUs)" and "O - RAN RU (O - RUs)", respectively. A network entity can include a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity can include one or more components of a non - centralized base station, such as a non - centralized base station, or a CU, a DU, an RU, or any combination of a CU, a DU, and an RU. A network entity can also include a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or one or more of other components that can provide a network interface for, or serve, a UE, a mobile station, a sensor / actuator, or other wireless devices.

[0055] Each of the units (e.g., CU310, DU330, RU340, and quasi-RT RIC325, non-RT RIC315, and SMO framework 305) includes, or can be coupled to, one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interface of the unit, can be configured to communicate with one or more of the other units via the transmission medium. For example, a unit can include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that can include a receiver, transmitter, or transceiver (such as an RF transceiver), and the wireless interface is configured to receive signals from, transmit signals to, or both, one or more of the other units via a wireless transmission medium.

[0056] In some aspects, CU310 may host one or more upper layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signals using other control functions hosted by CU310. CU310 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU - UP)), control plane functionality (i.e., Central Unit - Control Plane (CU - CP)), or a combination thereof. In some implementations, CU310 can be logically divided into one or more CU - UP units and one or more CU - CP units. When implemented in an O - RAN configuration, the CU - UP units can communicate bidirectionally with the CU - CP units via an interface such as an E1 interface. CU310 can be implemented to communicate with DU330 as needed for network control and signaling.

[0057] The DU330 may correspond to a logical unit including one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) at least partially according to a function split defined by 3GPP (registered trademark). In some aspects, the DU330 may further host one or more low PHY layers. Each layer (or module) can be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU330 or with control functions hosted by the CU310.

[0058] The lower layer functionality can be implemented by one or more RU340s. In some deployments, the RU340s controlled by the DU330 may correspond to logical nodes that host an RF processing function, or a lower PHY layer function (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, at least partially based on function splitting such as lower layer function splitting. In such an architecture, the RU(s) 340 can be implemented to handle over the air (OTA) communication with one or more UEs 120. In some implementations, the real-time and non-real-time aspects of control plane communication and user plane communication with the RU340(s) can be controlled by the corresponding DU330. In some scenarios, this configuration can enable the DU(s) 330 and the CU310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0059] The SMO framework 305 can be configured to support the RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. In the case of non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements that are managed via an operation and maintenance interface (such as an O1 interface). In the case of virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as an Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating a virtualized network element) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network elements can include, but are not limited to, a CU 310, a DU 330, an RU 340, and a quasi-RT RIC 325. In some implementations, the SMO framework 305 can communicate with the hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 311, via an O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via an O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0060] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the quasi-RT RIC 325. The non-RT RIC 315 may be coupled to the quasi-RT RIC 325 or communicate with the quasi-RT RIC 325 (e.g., via the A1 interface). The quasi-RT RIC 325 can be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources via data collection and actions on an interface connecting one or more CU 310s, one or more DUs 330s, or both, and the O-eNB to the quasi-RT RIC 325 (e.g., via the E2 interface).

[0061] In some implementations, the non-RT RIC 315 can receive parameters or external enrichment information from an external server to generate an AI / ML model to be deployed in the quasi-RT RIC 325. Such information may be utilized by the quasi-RT RIC 325 and may be received from non-network data sources or network functions, in the SMO framework 305 or in the non-RT RIC 315. In some examples, the non-RT RIC 315 or the quasi-RT RIC 325 can be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and employ an AI / ML model to perform corrective actions through the SMO framework 305 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies).

[0062] As described above, FIG. 3 is provided as one example. Other examples may differ from those described with respect to FIG. 3.

[0063] Figure 4 is a diagram showing an example 400 of downlink SPS communication and an example 410 of uplink CG communication according to the present disclosure. SPS communication can include periodic downlink communication configured for a UE such that a network node does not need to transmit separate downlink control information (DCI) to schedule each downlink communication, thereby reducing latency and signaling overhead. CG communication can include periodic uplink communication configured for a UE such that a network node does not need to transmit separate DCI to schedule each uplink communication, thereby reducing latency and signaling overhead.

[0064] As shown in example 400, the UE can be configured with an SPS configuration for grant-free downlink communication. For example, the UE can receive the SPS configuration via an RRC message transmitted by the network node. The SPS configuration can indicate a resource allocation associated with SPS downlink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocation is repeated, resulting in a periodically repeated scheduled SPS occasion 405 for the UE. The SPS configuration can also configure HARQ-acknowledgement (HARQ-ACK) feedback resources for the UE to transmit HARQ-ACK feedback for physical downlink shared channel (PDSCH) communication received during the SPS occasion 405. For example, the SPS configuration can indicate a feedback timing value from the PDSCH to the HARQ, sometimes referred to as a K1 value in a wireless communication standard (e.g., a 3GPP standard).

[0065] The network node can send SPS activation DCI to the UE to activate the SPS configuration for the UE. The network node can indicate in the SPS activation DCI communication parameters such as MCS, resource block (RB) allocation, and / or antenna port for the SPS PDSCH communication to be transmitted in the scheduled SPS occasion 405. Based at least in part on receiving the SPS activation DCI, the UE can start monitoring the SPS occasion 405. For example, starting from the next scheduled SPS occasion 405 after receiving the SPS activation DCI, the UE can monitor the scheduled SPS occasion 405 to decode the PDSCH communication using the communication parameters indicated in the SPS activation DCI. The UE can refrain from monitoring the configured SPS occasion 405 before receiving the SPS activation DCI.

[0066] The network node can send SPS reactivation DCI to the UE to change the communication parameters for the SPS PDSCH communication. Based at least in part on receiving the SPS reactivation DCI, the UE can start monitoring the scheduled SPS occasion 405 using the communication parameters indicated in the SPS reactivation DCI. For example, starting from the next scheduled SPS occasion 405 after receiving the SPS reactivation DCI, the UE can monitor the scheduled SPS occasion 405 to decode the PDSCH communication based on the communication parameters indicated in the SPS reactivation DCI.

[0067] In some cases, such as when the network node has no downlink traffic to send to the UE, the network node can send SPS cancellation DCI to the UE to temporarily cancel or deactivate one or more subsequent SPS occasions 405 for the UE. The SPS cancellation DCI can deactivate only one subsequent SPS occasion 405 or only N subsequent SPS occasions 405 (N is an integer). The SPS occasions 405 after one or more (e.g., N) SPS occasions 405 after the SPS cancellation DCI may remain activated. Based at least in part on receiving the SPS cancellation DCI, the UE can refrain from monitoring one or more (e.g., N) SPS occasions 405 after receiving the SPS cancellation DCI. As shown in embodiment 400, the SPS cancellation DCI cancels one subsequent SPS occasion 405 for the UE. After the SPS occasion 405 (or N SPS occasions) after receiving the SPS cancellation DCI, the UE can automatically resume monitoring the scheduled SPS occasions 405.

[0068] The network node can send SPS release DCI to the UE to deactivate the SPS configuration for the UE. Based at least in part on receiving the SPS release DCI, the UE can stop monitoring the scheduled SPS occasions 405. For example, the UE can refrain from monitoring any scheduled SPS occasions 405 until another SPS activation DCI is received from the base station. The SPS cancellation DCI can deactivate only one subsequent SPS occasion 405 or only N subsequent SPS occasions 405, but the SPS release DCI deactivates all subsequent SPS occasions 405 for a given SPS configuration for the UE until the given SPS configuration is reactivated by a new SPS activation DCI.

[0069] As shown in Example 410, the UE can be configured with a CG configuration for grant-free uplink communication. For example, the UE can receive the CG configuration via an RRC message transmitted by a network node. The CG configuration can indicate a resource allocation associated with CG uplink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain), and the periodicity with which the resource allocation is repeated, resulting in a periodically repeated scheduled CG occasion 415 for the UE. In some embodiments, the CG configuration can identify one or more resource pools available to the UE for uplink transmission. The CG configuration can configure contention-free CG communication (e.g., if the resources are dedicated for the UE to transmit uplink communication), or contention-based CG communication (e.g., if the UE contends for access to the channel during the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).

[0070] The network node can send CG activation DCI to the UE to activate the CG configuration for the UE. The network node can indicate in the CG activation DCI communication parameters such as MCS, RB allocation, and / or antenna port for the CG physical uplink shared channel (PUSCH) communication to be transmitted in the scheduled CG occasion 415. Based at least in part on receiving the CG activation DCI, the UE can start transmission in the CG occasion 415. For example, starting from the next scheduled CG occasion 415 after receiving the CG activation DCI, the UE can use the communication parameters indicated in the CG activation DCI to transmit PUSCH communication in the scheduled CG occasion 415. Before receiving the CG activation DCI, the UE can refrain from transmitting in the configured CG occasion 415.

[0071] The network node can send CG reactivation DCI to the UE to change the communication parameters for the CG PUSCH communication. Based at least in part on receiving the CG reactivation DCI, the UE can start transmission in the scheduled CG occasion 415 using the communication parameters indicated in the CG reactivation DCI. For example, starting from the next scheduled CG occasion 415 after receiving the CG reactivation DCI, the UE can transmit PUSCH communication in the scheduled CG occasion 415 based at least in part on the communication parameters indicated in the CG reactivation DCI.

[0072] In some cases, such as when the base station needs to override the scheduled CG communication for higher priority communication, the network node can send a CG cancellation DCI to the UE to temporarily cancel or deactivate one or more subsequent CG occasions 415 for the UE. The CG cancellation DCI can deactivate only one subsequent CG occasion 415 or only the subsequent N CG occasions 415 (where N is an integer). The CG occasions 415 after one or more (e.g., N) CG occasions 415 after the CG cancellation DCI may remain active. Based at least in part on receiving the CG cancellation DCI, the UE can refrain from transmitting in one or more (e.g., N) CG occasions 415 after receiving the CG cancellation DCI. As shown in embodiment 410, the CG cancellation DCI cancels one subsequent CG occasion 415 for the UE. After the CG occasion 415 (or N CG occasions) after receiving the CG cancellation DCI, the UE can automatically resume transmitting in the scheduled CG occasion 415.

[0073] The network node can send a CG release DCI to the UE to deactivate the CG configuration for the UE. Based at least in part on receiving the CG release DCI, the UE can stop transmitting in the scheduled CG occasion 415. For example, the UE can refrain from transmitting in any scheduled CG occasion 415 until another CG activation DCI is received from the base station. The CG cancellation DCI can deactivate only one subsequent CG occasion 415 or only the subsequent N CG occasions 415, but the CG release DCI deactivates all subsequent CG occasions 415 for a given CG configuration for the UE until the given CG configuration is reactivated by a new CG activation DCI.

[0074] As described above, FIG. 4 is provided as an example. Other examples may differ from those described with respect to FIG. 4.

[0075] FIG. 5 is a diagram showing an example 500 of SPS and / or CG configured communication for supporting bursty traffic according to the present disclosure. For example, as described herein, the SPS and / or CG configuration shown in FIG. 5 can be used to support traffic of extended reality (XR), which is an umbrella term covering immersive technologies such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and levels of virtualization interpolated between VR, AR, and MR.

[0076] For example, VR is a rendered version of a visual and auditory scene, and the rendering is designed to mimic the visual and auditory stimuli of the real world as naturally as possible for an observer or user as they move within limits defined by a VR application. VR typically requires the user to wear a head mounted display (HMD) to completely replace the field of view with a simulated visual component and use headphones and / or speakers to listen to the accompanying audio. To ensure that items and sound sources remain consistent with the user's movement from the user's perspective, tracking of the user's head and movement is also typically required in a VR application to enable the simulated visual and auditory components to be updated. In an AR application, the user is generally provided with additional information or artificially generated items or content that are overlaid on the current environment. The additional information or content is typically visual and / or audible, and the observation of the current environment may be direct, without intermediate sensing, processing, and rendering, or indirect, where the perception of the environment is relayed, extended, or processed via sensors. MR is an advanced form of AR in which some virtual elements are inserted into the physical scene to provide the illusion that the elements are part of the real scene.

[0077] XR, among other examples, is expected to improve the productivity and convenience of consumers, enterprises, and public institutions in various application fields such as entertainment, training, education, remote support, remote control, communication, and / or virtual conferencing. XR can be used in many industrial fields including healthcare, real estate, shopping, transportation, manufacturing, and / or other industrial sectors. VR has already been used for gaming both at home and in dedicated locations, virtual tours in the context of real estate, educational training purposes, and remote participation in live events such as concerts and sports. Furthermore, the use cases of AR and MR have great potential. For example, while VR applications rely on HMDs that separate the user from the physical environment and limit mobility, AR and MR applications enable the user to be present in and move freely in the real world, even when using an HMD. Many smartphone users have already experienced basic forms of AR through games that involve exploring virtual objects in the real-world environment and apps that enable shoppers to visualize new furniture in their homes before purchase. Additionally, AR technology may be used with an HMD to free the user's hands, thereby increasing operator efficiency by providing the ability to overlay information on the real world while keeping the hands available for other tasks.

[0078] However, configuring a wireless network to support waiting time requirements, quality of experience (QoE) requirements, and high data rates associated with XR traffic presents various challenges. For example, in an XR-capable UE, XR traffic can include pose data (e.g., related to position and orientation in space), video data, audio data, and / or other data transmitted by and / or to the XR-capable UE, can have a video frame size that changes over time, and / or can have a quasi-periodic packet arrival time with application jitter (e.g., changing the XR traffic arrival time). Further, the traffic arrival time at a network node (e.g., a RAN node) is periodic with non-negligible jitter due to uncertain application processing times. In addition to the video frame size not being fixed over time, it is one order of magnitude larger than packets in voice or industrial control communications. Rather, segmentation of each frame is expected, which means that packets arrive in bursts, and the bursts must be processed together to meet strict latency requirements. For example, as described herein, a burst, traffic burst, transmission burst, etc. can refer to a sequence of consecutive packets with a shorter inter-packet arrival time and / or a higher traffic volume than packets arriving before or after the sequence of consecutive packets in the burst. Thus, since packets arrive in bursts, XR traffic can have different characteristics from voice or other applications designed to be processed by SPS and / or CG configurations. For example, in existing (e.g., legacy) SPS and / or CG configurations (e.g., as described above with reference to FIG. 4), SPS and / or CG occasions can be matched to regular traffic patterns, such as 1 packet every 20 milliseconds for voice traffic. In existing SPS and / or CG configurations, each SPS and / or CG occasion is an independent transmission opportunity (e.g., a single transport block can be transmitted for each SPS and / or CG occasion).In contrast, XR traffic has a much higher data rate than voice, and many packets arrive very close together in time, and then there is an idle period before the next cycle starts and the next traffic burst arrives, meaning that it tends to be very bursty (e.g., a bursty traffic pattern can include sudden increases and / or decreases in traffic volume and / or inter-packet arrival times).

[0079] Accordingly, in some aspects, FIG. 5 shows an extended SPS and / or CG configuration that can enable multiple transport blocks to be transmitted within a cycle to support an XR application or an application associated with a bursty traffic pattern. For example, as shown in FIG. 5, the extended SPS and / or CG configuration can include a cycle 510 that includes a sequence of multiple SPS and / or CG occasions 520, which can be similar to how the physical downlink control channel (PDCCH) search space is configured. Further shown, the number of SPS and / or CG occasions 520 included in cycle 510 can be at least partially based on the maximum burst size (e.g., the maximum amount of data that can be transmitted to or by a UE during a given time interval) and the estimated or measured jitter (e.g., the variation or difference in latency or delay experienced by different packets as they cross the network from the transmitter to the receiver). For example, in some aspects, the number of SPS and / or CG occasions 520 included in cycle 510 of the extended SPS and / or CG configuration can be the sum of the maximum burst size and twice (2x) the estimated or measured jitter. For example, the estimated or measured jitter can have a positive or negative value (e.g., subsequent packets can have a larger or smaller delay than the previous packet), such that the number of SPS and / or CG occasions 520 included in cycle 510 needs to cover potential jitter in both directions. Further, as shown in FIG. 5, the packet arrival interval 530 can be defined as the time between adjacent SPS and / or CG occasions 520, and the frame periodicity 540 is defined as the periodicity between two adjacent cycles 510.In this way, the extended SPS and / or CG configuration provides a cluster of transmission opportunities (e.g., SPS and / or CG occasions 520) to enable the transmission of multiple transport blocks in each cycle 510, thereby providing a much shorter time gap (e.g., packet arrival interval 530) between adjacent occasions than the periodicity of the legacy SPS and / or CG configuration (e.g., bursts in XR traffic can arrive every 16 milliseconds, and there can be several packets in each burst arriving very close in time, such as all being 1 millisecond apart), and by providing an extra CG occasion 520 in each cycle 510 to address jitter that could otherwise disrupt streaming video and / or audio data, it may be suitable for XR applications or other applications with bursty traffic patterns.

[0080] In a wireless network, a HARQ process can be used to request retransmission of a transport block and / or to enable HARQ feedback for performing HARQ combining (sometimes called soft combining or HARQ using soft combining) over multiple transmissions of a transport block. For example, in a typical HARQ protocol, a HARQ process identifier may be associated with a data communication (e.g., a transport block). When HARQ-ACK feedback is supported, a receiver can send an acknowledgement (ACK) to a transmitter when a transport block is successfully decoded. Otherwise, when the receiver experiences an error with respect to reception and / or decoding of a data communication, the receiver can send a negative acknowledgement (NACK) to request retransmission of the transport block. In some cases, a NACK-only HARQ-ACK feedback mode can be used, where the receiver does not send an ACK and sends a NACK only when the receiver experiences an error with respect to reception and / or decoding of a data communication. Additionally or alternatively, when HARQ combining is supported, the receiver can store received data (which can include erroneously received data) in a soft buffer and associate a HARQ process with the soft buffer. The same HARQ process can be used for one or more retransmissions of a data communication such that the receiver can associate data included in the retransmission(s) with data stored in the soft buffer (e.g., data from the original communication and / or any previous retransmission). In this way, the receiver can combine the retransmitted data with the buffered data (e.g., using soft combining or another technique to combine data from multiple transmissions which can include different redundant versions of a data communication), thereby improving decoding performance.

[0081] HARQ feedback and / or HARQ combining has the potential to significantly improve the reliability and / or decoding performance of transport blocks transmitted over the air interface. However, techniques for mapping HARQ process identifiers to transmission opportunities in extended SPS and / or CG configurations pose challenges. For example, as described above, each transmission opportunity in legacy SPS and / or CG configurations is typically an independent transmission opportunity for a single transport block, such that the HARQ process identifier associated with each SPS and / or CG opportunity in legacy SPS and / or CG configurations is determined according to a hard-coded mapping specified in one or more wireless communication standards (e.g., based on the slot index of the SPS and / or CG opportunity). For example, if a legacy SPS or CG configuration is configured with N HARQ process identifiers, HARQ process 1 is assigned to the first SPS or CG opportunity, HARQ process N is assigned to the Nth SPS or CG opportunity, and then the N HARQ process identifiers are sequentially repeated in the time domain. However, in extended SPS and / or CG configurations used to support XR applications or other applications associated with bursty traffic patterns, multiple transport blocks can be transmitted in a pre-scheduled burst of transmission opportunities. However, since each period or cycle can be very short, the sequential mapping of HARQ process identifiers to SPS or CG transmission opportunities can be problematic in XR (or similar) applications. For example, when an XR application operates at a frame rate of 120 milliseconds, the duration of each burst is 8.3 milliseconds, which can approach the typical HARQ process length that is three times the round-trip time across the air interface (e.g., each round-trip time is about 1 millisecond or 2 milliseconds).In particular, when the channel condition is poor and the HARQ process takes more than three round-trip times (or three retransmissions), the HARQ process may interrupt the next cycle, which may cause the HARQ process to block a new transmission using the same HARQ process in the next cycle. Thus, as will be described in more detail below with reference to FIG. 6, some aspects described herein relate to techniques for associating a HARQ process identifier with each transmission occasion in an extended SPS or CG configuration used to support transmitting a plurality of transport blocks in a pre-scheduled burst of an SPS or CG occasion.

[0082] As described above, FIG. 5 is provided as one example. Other examples may differ from those described with respect to FIG. 5.

[0083] FIG. 6 is a diagram illustrating one example 600 associated with HARQ process determination for an extended SPS and / or CG configuration according to the present disclosure. As shown in FIG. 6, example 600 includes communication between network node 110 and UE 120. In some aspects, network node 110 and UE 120 may be included in a wireless network such as wireless network 100. Network node 110 and UE 120 may communicate via a wireless access link that can include an uplink and a downlink.

[0084] As indicated by reference number 610, the network node 110 can transmit, and the UE 120 can receive, a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion. For example, as described in more detail above with reference to FIG. 5, the scheduling configuration may include an extended SPS configuration that constitutes a plurality of transport blocks to be transmitted from the network node 110 to the UE 120 in a pre-scheduled burst of a transmission occasion. Additionally or alternatively, the scheduling configuration can include an extended CG configuration that constitutes a plurality of transport blocks to be transmitted from the UE 120 to the network node 110 in a pre-scheduled burst of a transmission occasion. For example, as described herein, the scheduling configuration can include a cycle that includes a sequence of pre-scheduled bursts of transmission occasions, and the number of transmission occasions included in the cycle can be at least partially based on the maximum burst size (e.g., the maximum amount of data that can be transmitted to or by the UE during a given time interval) and the estimated or measured jitter (e.g., the variation or difference in the waiting time or delay experienced by different packets as they cross the network from the transmitter to the receiver). For example, in some aspects, the number of transmission occasions included in the cycle of the scheduling configuration can be the sum of the maximum burst size and twice (2×) the estimated or measured jitter (e.g., to cover potential jitter in both the positive and negative directions). Further, the packet arrival interval may be defined as the time between adjacent transmission occasions, and the frame periodicity may be defined as the periodicity between two adjacent cycles.In this way, the scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion can provide a cluster of transmission opportunities (e.g., SPS occasions and / or CG occasions) for transmitting a plurality of transport blocks in each cycle, provide a time gap between adjacent occasions that is shorter than the periodicity of legacy SPS and / or CG configurations, and provide an extra transmission occasion in each cycle to address potential jitter that may otherwise disrupt streaming video and / or audio data, making it suitable for XR applications or other applications with bursty traffic patterns.

[0085] As further shown in FIG. 6, the scheduling configuration provided by network node 110 can be associated with a HARQ configuration that defines a mapping between a HARQ process identifier and each transmission occasion in a pre-scheduled burst of a transmission occasion. For example, the HARQ process identifier associated with each transmission occasion can enable HARQ-based retransmission and / or HARQ combining over multiple repetitions and / or retransmissions of a transport block, as described in more detail elsewhere in this specification. Thus, in some aspects, network node 110 and UE 120 can process each transmission occasion in a pre-scheduled burst of a transmission occasion by associating a HARQ process identifier with each respective transmission occasion based on the HARQ configuration associated with the extended scheduling configuration.

[0086] For example, as indicated by reference numeral 620, the HARQ configuration can limit the number of HARQ process identifiers used per cycle to not exceed the number of transmission opportunities per cycle (e.g., the number of HARQ process identifiers used per cycle is less than or equal to the number of transmission opportunities per cycle). In such a case, the pattern used to map HARQ process identifiers to the transmission opportunities in a pre-scheduled burst of transmission opportunities may be the same in each cycle. For example, within each cycle of the scheduling configuration, the HARQ process identifiers may be associated with each transmission opportunity based on a slot index or another suitable allocation pattern, and the same pattern can be used in each cycle of the scheduling configuration. For example, reference numeral 620 shows an embodiment where there are four transmission opportunities per cycle and three HARQ process identifiers (h1, h2, h3) per cycle. In this case, in the time domain, the first HARQ process may be assigned to the first transmission opportunity within the cycle, the second HARQ process may be assigned to the next transmission opportunity within the cycle, and so on, and then the HARQ process identifiers sequentially repeat in the time domain. However, in some cases, limiting the number of HARQ process identifiers to less than or equal to the number of transmission opportunities per cycle may potentially cause one or more transmission opportunities to be blocked (e.g., when one or more transmission opportunities are used for retransmission and as a result, when the number of transmission opportunities is less than or equal to the number of HARQ processes per cycle and the HARQ process identifiers wrap around in a cycle).

[0087] Thus, as indicated by reference numeral 630, the HARQ configuration associated with the scheduling configuration can allow or enable (but not necessarily require) the number of HARQ processes per cycle to be greater than or equal to the number of occasions per cycle, thereby avoiding the potential problem that one or more transmission occasions may be potentially blocked due to retransmissions associated with one or more HARQ process identifiers. For example, if the number of HARQ processes per cycle can exceed the number of occasions in a cycle of the scheduling configuration, the pattern used to map HARQ process identifiers to transmission occasions may be independent of SPS and / or CG cycles. For example, rather than associating HARQ process identifiers with transmission occasions based on the slot index of each respective transmission occasion, the HARQ configuration can define an expression for associating HARQ process identifiers with the index of each transmission occasion in a sequence, cycle, or burst of pre-scheduled transmission occasions with wraparound enabled across different bursts. For example, in some aspects, the occasion index O i associated with transmission occasion i can be at least partially based on the slot index s i associated with the transmission occasion, the cycle length T, and the number of occasions N per cycle. For example, the occasion index O i associated with transmission occasion i can be defined as follows.

[0088] [Number]

[0089] In some aspects, the HARQ process identifier associated with a particular transmission occasion can then, as follows, be the occasion index O iIt can be determined based on the number H of HARQ processes configured for SPS or CG scheduling configuration and the offset. HARQ ID = (offset + O i ) modulo H Wherein the offset is an integer within the range from 0 to the total number of HARQ processes assigned to the SPS or CG scheduling configuration. In this way, the HARQ process identifier associated with each transmission occasion in the pre-scheduled burst of the transmission occasion can be used to transmit a plurality of transport blocks. Regardless of the burst pattern underlying the SPS cycle and / or CG cycle, by associating the HARQ process identifier with each transmission occasion, potential blocking transmissions can be avoided. For example, the modulo operation in the formula given above can result in a wrap-around, whereby the HARQ processes are sequentially associated with different transmission occasions, and the HARQ process identifier wraps around after the number of transmission occasions exceeds the total number of HARQ process identifiers configured for the SPS or CG configuration.

[0090] Accordingly, UE120 and network node 110 can communicate transport blocks in a pre-scheduled burst of transmission occasions associated with an extended scheduling configuration based on the HARQ configuration. For example, in FIG. 6, reference numerals 640 and 650 illustrate communication between UE120 and network node 110 when the extended scheduling configuration is an extended SPS configuration. In such an embodiment, as indicated by reference numeral 640, network node 110 can transmit multiple transport blocks to UE120 in multiple SPS occasions included in a cycle, and each transport block is associated with a HARQ process identifier. In some aspects, UE120 can then determine the HARQ process identifier associated with each SPS occasion based on the applicable HARQ configuration (e.g., whether the number of HARQ processes is restricted such that it does not exceed the number of SPS occasions in a cycle, or is permitted to exceed the number of SPS occasions in a cycle). As indicated by reference numeral 650, UE120 can attempt to decode each transport block transmitted in an SPS occasion and transmit a HARQ feedback (e.g., ACK or NACK) associated with the HARQ process identifier to network node 110 (e.g., to trigger a retransmission or otherwise indicate a decoding result). Additionally or alternatively, when the extended scheduling configuration is an extended configured grant configuration, substantially the same techniques can be used in reverse.For example, in an extended configured grant configuration, UE 120 can transmit a plurality of transport blocks to network node 110 in a plurality of configured grant occasions, each associated with a HARQ process identifier, and network node 110 can determine the HARQ process identifier associated with each CG occasion based on the applicable HARQ configuration, attempt to decode each transport block transmitted in the configured grant occasion, and / or transmit HARQ feedback associated with the HARQ process identifier to UE 120 to indicate the corresponding decoding result.

[0091] As described above, FIG. 6 is provided as one example. Other examples may differ from those described with respect to FIG. 6.

[0092] FIG. 7 is a diagram illustrating an exemplary process 700 that may be performed, for example, by a UE in accordance with the present disclosure. The exemplary process 700 is one example in which a UE (e.g., UE 120) performs operations associated with HARQ process determination for extended SPS and / or CG configurations.

[0093] As shown in FIG. 7, in some aspects, process 700 can include receiving, from a network entity, a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission occasions (block 710). For example, the UE can receive, from the network entity, a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission occasions as described above (e.g., using communication manager 140 and / or receiving component 902 shown in FIG. 9).

[0094] As further shown in FIG. 7, in some aspects, process 700 can include communicating, for each transmission occasion in a pre-scheduled burst of transmission occasions, a transport block that is transmitted during the respective transmission occasion and is associated with a HARQ process identifier that is at least partially based on a HARQ configuration associated with the scheduling configuration (block 720). For example, the UE can (e.g., using communication manager 140 and / or HARQ process determination component 908 shown in FIG. 9) process, for each transmission occasion in a pre-scheduled burst of transmission occasions as described above, the transport blocks transmitted during the respective transmission occasions according to a HARQ process identifier that is at least partially based on a HARQ configuration associated with the scheduling configuration.

[0095] Process 700 can include additional aspects such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere in this specification.

[0096] In a first aspect, the scheduling configuration is an SPS configuration that constitutes a plurality of transport blocks to be transmitted from a network entity to the UE in a pre-scheduled burst of transmission occasions.

[0097] In a second aspect, alone or in combination with the first aspect, the scheduling configuration is a CG configuration that constitutes a plurality of transport blocks to be transmitted from the UE to a network entity in a pre-scheduled burst of transmission occasions.

[0098] In a third aspect, alone or in combination with one or more of the first and second aspects, the HARQ configuration limits the number of HARQ process identifiers in a burst scheduled prior to a transmission occasion to be less than or equal to the number of transmission occasions in the burst scheduled prior to the transmission occasion.

[0099] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the pattern associating the HARQ process identifier with each respective transmission occasion in a burst scheduled prior to a transmission occasion is the same in each cycle of the scheduling configuration.

[0100] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the HARQ configuration permits the number of HARQ process identifiers in a burst scheduled prior to a transmission occasion to be greater than or equal to the number of transmission occasions in the burst scheduled prior to the transmission occasion.

[0101] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the pattern associating the HARQ process identifier with each respective transmission occasion in a burst scheduled prior to a transmission occasion is at least partially based on the index associated with each respective transmission occasion, the offset associated with the scheduling configuration, and the number of HARQ process identifiers in the burst scheduled prior to the transmission occasion.

[0102] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the index associated with each respective transmission occasion is at least partially based on the slot index associated with each respective transmission occasion, the cycle length associated with the scheduling configuration, and the number of transmission occasions in the burst scheduled prior to the transmission occasion.

[0103] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, an offset associated with a scheduling configuration is an integer within a range from 0 to the total number of HARQ process identifiers assigned to the scheduling configuration.

[0104] FIG. 7 shows exemplary blocks of process 700, but in some aspects, process 700 can include additional blocks, fewer blocks, different blocks, or blocks configured differently than those shown in FIG. 7. Additionally or alternatively, two or more of the blocks of process 700 can be executed in parallel.

[0105] FIG. 8 is a diagram showing an exemplary process 800 performed, for example, by a network entity in accordance with the present disclosure. The exemplary process 800 is an example in which a network entity (e.g., network node 110, CU 310, DU 330, RU 340, etc.) performs operations associated with HARQ process determination for an extended SPS and / or CG configuration.

[0106] As shown in FIG. 8, in some aspects, process 800 can include transmitting to a UE a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion (block 810). For example, a network entity can transmit to a UE, as described above (e.g., using communication manager 150 and / or transmission component 1004 shown in FIG. 10), a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion.

[0107] As further shown in FIG. 8, in some aspects, process 800 can include communicating, for each transmission occasion in a pre-scheduled burst of transmission occasions, a transport block that is transmitted during that respective transmission occasion and is associated with a HARQ process identifier that is at least partially based on a HARQ configuration associated with a scheduling configuration (block 820). For example, a network entity can (e.g., using communication manager 150 and / or HARQ process determination component 1008 shown in FIG. 10) process, for each transmission occasion in a pre-scheduled burst of transmission occasions as described above, a transport block transmitted during that respective transmission occasion according to a HARQ process identifier that is at least partially based on a HARQ configuration associated with a scheduling configuration.

[0108] Process 800 can include additional aspects such as any single aspect or any combination of aspects described below and / or in relation to one or more other processes described elsewhere in this specification.

[0109] In a first aspect, the scheduling configuration is an SPS configuration that constitutes a plurality of transport blocks to be transmitted from a network entity to a UE in a pre-scheduled burst of transmission occasions.

[0110] In a second aspect, alone or in combination with the first aspect, the scheduling configuration is a CG configuration that constitutes a plurality of transport blocks to be transmitted from a UE to a network entity in a pre-scheduled burst of transmission occasions.

[0111] In a third aspect, alone or in combination with one or more of the first and second aspects, the HARQ configuration limits the number of HARQ process identifiers in a burst scheduled prior to a transmission occasion to be less than or equal to the number of transmission occasions in the burst scheduled prior to the transmission occasion.

[0112] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the pattern associating the HARQ process identifier with each respective transmission occasion in a burst scheduled prior to a transmission occasion is the same in each cycle of the scheduling configuration.

[0113] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the HARQ configuration permits the number of HARQ process identifiers in a burst scheduled prior to a transmission occasion to be greater than or equal to the number of transmission occasions in the burst scheduled prior to the transmission occasion.

[0114] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the pattern associating the HARQ process identifier with each respective transmission occasion in a burst scheduled prior to a transmission occasion is at least partially based on the index associated with each respective transmission occasion, the offset associated with the scheduling configuration, and the number of HARQ process identifiers in the burst scheduled prior to the transmission occasion.

[0115] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the index associated with each respective transmission occasion is at least partially based on the slot index associated with each respective transmission occasion, the cycle length associated with the scheduling configuration, and the number of transmission occasions in the burst scheduled prior to the transmission occasion.

[0116] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, an offset associated with a scheduling configuration is an integer in the range from 0 to the total number of HARQ process identifiers assigned to the scheduling configuration.

[0117] FIG. 8 shows an exemplary block of process 800, but in some aspects, process 800 can include additional blocks, fewer blocks, different blocks, or blocks configured differently than those shown in FIG. 8. Additionally or alternatively, two or more of the blocks of process 800 can be executed in parallel.

[0118] FIG. 9 is a diagram of an exemplary apparatus 900 for wireless communication. Apparatus 900 can be a UE, or a UE can include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As illustrated, apparatus 900 can communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further illustrated, apparatus 900 can include a communication manager 140. As further illustrated, communication manager 140 can include, among other examples, a HARQ process determination component 908.

[0119] In some aspects, apparatus 900 can be configured to perform one or more operations described herein in connection with FIG. 6. Additionally or alternatively, apparatus 900 can be configured to perform one or more processes described herein, such as process 700 of FIG. 7. In some aspects, apparatus 900 and / or one or more components shown in FIG. 9 can include one or more components of the UE described in connection with FIG. 2. Additionally or alternatively, one or more components shown in FIG. 9 can be implemented within one or more components described in connection with FIG. 2. In addition, or instead, one or more components of a set of components can be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) can be stored in a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0120] Receiving component 902 can receive communications from apparatus 906, such as a reference signal, control information, data communications, or combinations thereof. Receiving component 902 can provide the received communications to one or more other components of apparatus 900. In some aspects, receiving component 902 can perform signal processing (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and provide the processed signals to one or more other components of apparatus 900. In some aspects, receiving component 902 can include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the UE described in connection with FIG. 2.

[0121] The transmitting component 904 can transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 906. In some aspects, one or more other components of the device 900 can generate a communication and provide the generated communication to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 can perform signal processing (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communication and transmit the processed signal to the device 906. In some aspects, the transmitting component 904 can include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE described in connection with FIG. 2. In some aspects, the transmitting component 904 can be collocated with the receiving component 902 in a transceiver.

[0122] The receiving component 902 can receive a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion from a network entity. The HARQ process determination component 908 can communicate, for each transmission occasion in a pre-scheduled burst of a transmission occasion, a transport block associated with a HARQ process identifier that is transmitted during the respective transmission occasion and is at least partially based on the HARQ configuration associated with the scheduling configuration.

[0123] The number and configuration of components shown in FIG. 9 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently configured components compared to the components shown in FIG. 9. Further, two or more components shown in FIG. 9 can be implemented within a single component, or a single component shown in FIG. 9 can be implemented as a plurality of distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG. 9 can perform one or more functions described as being performed by another set of components shown in FIG. 9.

[0124] FIG. 10 is a diagram of an exemplary apparatus 1000 for wireless communication. Apparatus 1000 may be a network entity, or a network entity may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As illustrated, apparatus 1000 can use receiving component 1002 and transmitting component 1004 to communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device). As further illustrated, apparatus 1000 can include a communication manager 150. As further illustrated, communication manager 150 can include, among other examples, a HARQ process determination component 1008.

[0125] In some aspects, apparatus 1000 can be configured to perform one or more operations described herein in connection with FIG. 6. Additionally or alternatively, apparatus 1000 can be configured to perform one or more processes described herein, such as process 800 of FIG. 8. In some aspects, apparatus 1000 and / or one or more components shown in FIG. 10 can include one or more components of the network entities described in connection with FIG. 2. Additionally or alternatively, one or more components shown in FIG. 10 can be implemented within one or more components described in connection with FIG. 2. Additionally or instead, one or more components of a set of components can be implemented, at least in part, as software stored in a memory. For example, a component (or a portion of a component) can be stored in a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0126] Receiving component 1002 can receive communications from apparatus 1006, such as a reference signal, control information, data communication, or a combination thereof. Receiving component 1002 can provide the received communications to one or more other components of apparatus 1000. In some aspects, receiving component 1002 can perform signal processing (among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and provide the processed signals to one or more other components of apparatus 1000. In some aspects, receiving component 1002 can include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the network entities described in connection with FIG. 2.

[0127] The transmitting component 1004 can transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 1006. In some aspects, one or more other components of the device 1000 can generate the communication and provide the generated communication to the transmitting component 1004 for transmission to the device 1006. In some aspects, the transmitting component 1004 can perform signal processing (among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communication and transmit the processed signal to the device 1006. In some aspects, the transmitting component 1004 can include one or more antennas, modems, modulators, transmitting MIMO processors, transmitting processors, controllers / processors, memories, or combinations thereof of the network entities described in connection with FIG. 2. In some aspects, the transmitting component 1004 can be collocated with the receiving component 1002 in a transceiver.

[0128] The transmitting component 1004 can transmit a scheduling configuration that constitutes a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion to the UE. The HARQ process determination component 1008 can communicate, for each transmission occasion in a pre-scheduled burst of a transmission occasion, a transport block associated with a HARQ process identifier that is transmitted during the respective transmission occasion and is at least partially based on a HARQ configuration associated with the scheduling configuration.

[0129] The number and configuration of the components shown in FIG. 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently configured components compared to the components shown in FIG. 10. Further, two or more of the components shown in FIG. 10 can be implemented within a single component, or a single component shown in FIG. 10 can be implemented as a plurality of distributed components. Additionally or alternatively, a set of (one or more) components shown in FIG. 10 can perform one or more functions described as being performed by another set of components shown in FIG. 10.

[0130] The following provides an overview of some aspects of the present disclosure.

[0131] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving, from a network entity, a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission occasions; and for each transmission occasion in the pre-scheduled burst of transmission occasions, communicating a transport block that is transmitted during the respective transmission occasion and that is associated with a HARQ process identifier based at least in part on a HARQ configuration associated with the scheduling configuration.

[0132] Aspect 2: The method of aspect 1, wherein the scheduling configuration is an SPS configuration that configures a plurality of transport blocks to be transmitted from the network entity to the UE in a pre-scheduled burst of transmission occasions.

[0133] Aspect 3: The method of aspect 1 or 2, wherein the scheduling configuration is a CG configuration that configures a plurality of transport blocks to be transmitted from the UE to the network entity in a pre-scheduled burst of transmission occasions.

[0134] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the HARQ configuration restricts the number of HARQ process identifiers in a burst scheduled in advance for a transmission occasion to be less than or equal to the number of transmission occasions in the burst scheduled in advance for the transmission occasion.

[0135] Aspect 5: The method according to Aspect 4, wherein the pattern associating the HARQ process identifier with each respective transmission occasion in a burst scheduled in advance for the transmission occasion is the same in each cycle of the scheduling configuration.

[0136] Aspect 6: The method according to any one of Aspects 1 to 3, wherein the HARQ configuration permits the number of HARQ process identifiers in a burst scheduled in advance for a transmission occasion to be greater than or equal to the number of transmission occasions in the burst scheduled in advance for the transmission occasion.

[0137] Aspect 7: The method according to Aspect 6, wherein the pattern associating the HARQ process identifier with each respective transmission occasion in a burst scheduled in advance for the transmission occasion is at least partially based on the index associated with each respective transmission occasion, the offset associated with the scheduling configuration, and the number of HARQ process identifiers in the burst scheduled in advance for the transmission occasion.

[0138] Aspect 8: The method according to Aspect 7, wherein the index associated with each respective transmission occasion is at least partially based on the slot index associated with each respective transmission occasion, the cycle length associated with the scheduling configuration, and the number of transmission occasions in the burst scheduled in advance for the transmission occasion.

[0139] Aspect 9: The method according to aspect 7 or 8, wherein the offset associated with the scheduling configuration is an integer within the range from 0 to the total number of HARQ process identifiers assigned to the scheduling configuration.

[0140] Aspect 10: A method of wireless communication performed by a network entity, the method including: transmitting to a UE a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion; and for each transmission occasion in the pre-scheduled burst of the transmission occasion, communicating a transport block associated with a HARQ process identifier that is transmitted during the respective transmission occasion and is associated at least in part with a HARQ configuration associated with the scheduling configuration.

[0141] Aspect 11: The method according to aspect 10, wherein the scheduling configuration is an SPS configuration that configures a plurality of transport blocks to be transmitted from the network entity to the UE in a pre-scheduled burst of a transmission occasion.

[0142] Aspect 12: The method according to aspect 10 or 11, wherein the scheduling configuration is a CG configuration that configures a plurality of transport blocks to be transmitted from the UE to the network entity in a pre-scheduled burst of a transmission occasion.

[0143] Aspect 13: The method according to any one of aspects 10 to 12, wherein the HARQ configuration limits the number of HARQ process identifiers in a pre-scheduled burst of a transmission occasion to be less than or equal to the number of transmission occasions in the pre-scheduled burst of the transmission occasion.

[0144] Aspect 14: The method according to aspect 13, wherein the pattern associating the HARQ process identifier with each respective transmission occasion in a pre-scheduled burst of transmission occasions is the same in each cycle of the scheduling configuration.

[0145] Aspect 15: The method according to any one of aspects 10 to 12, wherein the HARQ configuration permits that the number of HARQ process identifiers in a pre-scheduled burst of transmission occasions is greater than or equal to the number of transmission occasions in the pre-scheduled burst of transmission occasions.

[0146] Aspect 16: The method according to aspect 15, wherein the pattern associating the HARQ process identifier with each respective transmission occasion in a pre-scheduled burst of transmission occasions is at least partially based on the index associated with each respective transmission occasion, the offset associated with the scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled burst of transmission occasions.

[0147] Aspect 17: The method according to aspect 16, wherein the index associated with each respective transmission occasion is at least partially based on the slot index associated with each respective transmission occasion, the cycle length associated with the scheduling configuration, and the number of transmission occasions in the pre-scheduled burst of transmission occasions.

[0148] Aspect 18: The method according to aspect 16 or 17, wherein the offset associated with the scheduling configuration is an integer within the range from 0 to the total number of HARQ process identifiers assigned to the scheduling configuration.

[0149] Aspect 19: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the device to execute one or more of the methods of Aspects 1 to 9.

[0150] Aspect 20: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors being configured to execute one or more of the methods of Aspects 1 to 9.

[0151] Aspect 21: A device for wireless communication, comprising at least one means for executing one or more of the methods of Aspects 1 to 9.

[0152] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to execute one or more of the methods of Aspects 1 to 9.

[0153] Aspect 23: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to execute one or more of the methods of Aspects 1 to 9.

[0154] Aspect 24: A device for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the device to execute one or more of the methods of Aspects 10 to 18.

[0155] Aspect 25: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to execute one or more of the methods of Aspects 10 to 18.

[0156] Aspect 26: An apparatus for wireless communication, comprising at least one means for executing one or more of the methods of Aspects 10 to 18.

[0157] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to execute one or more of the methods of Aspects 10 to 18.

[0158] Aspect 28: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to execute one or more of the methods of Aspects 10 to 18.

[0159] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Modifications and variations can be added in light of the foregoing disclosure, or obtained from practice of the aspects.

[0160] Further disclosure is included in the appendix. The appendix is provided by way of example only and is to be considered a part of the specification. Definitions, illustrations, or other explanations in the appendix do not replace or invalidate similar information in the detailed description or drawings. Further, definitions, illustrations, or other explanations in the detailed description or drawings do not replace or invalidate similar information in the appendix. Further, the appendix is not intended to limit the disclosure of possible aspects.

[0161] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. "Software" shall be broadly construed to mean, among other things, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or by another name. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or combinations of hardware and software. The actual specialized control hardware code or software code used to implement these systems and / or methods does not limit the aspects. Thus, those skilled in the art will understand that software and hardware can be designed, at least in part based on the description herein, to implement the systems and / or methods. Accordingly, in this specification, the operation and behavior of the systems and / or methods are described without reference to specific software code.

[0162] As used herein, "meeting a threshold" may, depending on the context, refer to a value being greater than a threshold, being greater than or equal to a threshold, being less than a threshold, being less than or equal to a threshold, being equal to a threshold, not being equal to a threshold, etc.

[0163] Even if certain combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure in any way. Many of these features may be combined in ways not specifically recited in the claims and / or not disclosed herein. The disclosure in various aspects includes each dependent claim combined with every other claim within the set of claims. As used herein, the phrase referring to an enumeration of items "at least one of" refers to any combination of those items including a single member. By way of example, "at least one of a, b, or c" includes a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination having multiple of the same element (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other order of a, b, and c).

[0164] None of the elements, acts, or instructions used in this specification should be construed as important or essential unless explicitly described as such. Also, as used in this specification, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Further, as used in this specification, the definite article "the" is intended to include one or more items referred to by the definite article "the" and may be used interchangeably with "one or more". Additionally, as used in this specification, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more". When only one item is intended, the phrase "only one" or similar words are used. Also, as used in this specification, terms such as "has", "have", "having", etc. shall be considered open-ended terms that do not limit the elements they modify (e.g., an element "having" A can also have B). Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified. Also, as used in this specification, the term "or" is intended to be inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise specified (e.g., when used in combination with "either" or "only one of").

Claims

1. A method of wireless communication performed by a user device (UE), Receiving a scheduling configuration from a network entity that comprises multiple transport blocks to be transmitted in pre-scheduled bursts of transmission occasions included in each cycle, For each transmit occasion in the pre-scheduled burst of transmit occasions, communicate a transport block transmitted during each transmit occasion and associated with a HARQ process identifier that is at least partially based on a Hybrid Auto Retransmission Request (HARQ) configuration associated with the scheduling configuration, Includes, The scheduling configuration is either a semi-persistent scheduling configuration or a configured authorization configuration, which constitutes a plurality of transport blocks to be sent from the network entity to the UE in the pre-scheduled burst sequence of the transmission occasion. The HARQ configuration allows the number of HARQ process identifiers in the pre-scheduled burst of a transmit occasion to be greater than or equal to the number of transmit occasions in the pre-scheduled burst of a transmit occasion. The pattern for associating the HARQ process identifier with each transmission occasion in the pre-scheduled burst of the transmission occasion is at least partially based on the index associated with each transmission occasion, the offset associated with the scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled burst of the transmission occasion, method.

2. The method according to claim 1, wherein the index associated with each respective transmission occasion is at least partially based on the slot index associated with each respective transmission occasion, the cycle length associated with the scheduling configuration, and the number of transmission occasions in the pre-scheduled burst of transmission occasions.

3. The method according to claim 1, wherein the offset associated with the scheduling configuration is an integer within the range of 0 to the total number of HARQ process identifiers assigned to the scheduling configuration.

4. A method of wireless communication performed by a network entity, Sending a scheduling configuration to the user equipment (UE) that comprises multiple transport blocks to be transmitted in a pre-scheduled burst of a transmission occasion, For each transmit occasion in the pre-scheduled burst of transmit occasions, communicate a transport block transmitted during each transmit occasion and associated with a HARQ process identifier that is at least partially based on a Hybrid Auto Retransmission Request (HARQ) configuration associated with the scheduling configuration, Includes, The scheduling configuration is either a semi-persistent scheduling configuration or a configured authorization configuration, which comprises a plurality of transport blocks to be sent from the network entity to the UE in the pre-scheduled burst of the transmission occasion. The HARQ configuration allows the number of HARQ process identifiers in the pre-scheduled burst of a transmit occasion to be greater than or equal to the number of transmit occasions in the pre-scheduled burst of a transmit occasion. The pattern for associating the HARQ process identifier with each transmission occasion in the pre-scheduled burst of the transmission occasion is at least partially based on the index associated with each transmission occasion, the offset associated with the scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled burst of the transmission occasion, method.

5. The method according to claim 4, wherein the index associated with each respective transmission occasion is at least in part based on the slot index associated with each respective transmission occasion, the cycle length associated with the scheduling configuration, and the number of transmission occasions in the pre-scheduled burst of transmission occasions.

6. The method according to claim 4, wherein the offset associated with the scheduling configuration is an integer within the range of 0 to the total number of HARQ process identifiers assigned to the scheduling configuration.

7. A user device (UE) for wireless communications comprising at least one means for performing the method according to any one of claims 1 to 3.

8. A non-temporary computer-readable medium for storing a code for wireless communication, wherein the code includes instructions that can be executed by a processor to perform the method according to any one of claims 1 to 3.

9. A network entity for wireless communications comprising at least one means for performing the method described in any one of claims 4 to 6.

10. A non-temporary computer-readable medium for storing a code for wireless communication, wherein the code includes instructions that can be executed by a processor to perform the method according to any one of claims 4 to 6.

Images