Hybrid automatic repeat request process determination for grant configuration for enhanced semi-persistent scheduling and / or configuration

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network entity is capable of transmitting and a user equipment (UE) is capable of receiving a scheduling configuration that configures a plurality of transport blocks to be transmitted in a pre-scheduled transmission opportunity burst. The network entity and UE can transmit, for each transmission occasion in the pre-scheduled transmission occasion burst, a transport block transmitted in the respective transmission occasion and associated with a Hybrid Automatic Repeat Request (HARQ) process identifier, the Hybrid Automatic Repeat Request (HARQ) process identifier based at least in part on a HARQ configuration associated with the scheduling configuration. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to the following: U.S. Provisional Patent Application No. 63 / 365,185, filed on May 23, 2022, entitled "HYBRID AUTOMATIC REPEATREQUEST PROCESSDETERMINATION FOR ENHANCED SEMI-PERSISTENT SCHEDULING AND / OR CONFIGURED GRANT CONFIGURATION," and U.S. Non-Provisional Patent Application No. 18 / 314,329, filed on May 9, 2023, entitled "HYBRID AUTOMATIC REPEAT REQUEST PROCESSDETERMINATION FOR ENHANCED SEMI-PERSISTENT SCHEDULING AND / OR CONFIGURED GRANT CONFIGURATION," which are hereby expressly incorporated herein by reference. Technical Field

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

[0004] Related technologies

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit 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 standard promulgated by the Third Generation Partnership Project (3GPP).

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

[0007] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0008] Some aspects described herein 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 a scheduling configuration for configuring a plurality of transmission blocks to be sent in a pre-scheduled transmission opportunity burst from a network entity. The one or more processors may be configured to: transmit, for each transmission opportunity in the pre-scheduled transmission opportunity burst, a transmission block that is sent in the corresponding transmission opportunity and is associated with a hybrid automatic repeat request (HARQ) process identifier, the hybrid automatic repeat request (HARQ) process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0009] 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: send a scheduling configuration to a UE that configures a plurality of transport blocks to be sent in a pre-scheduled transmit opportunity burst. The one or more processors may be configured to: transmit, for each transmit opportunity in the pre-scheduled transmit opportunity burst, a transport block that is sent in the corresponding transmit opportunity and is associated with a HARQ process identifier, the HARQ process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0010] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a scheduling configuration from a network entity that configures a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities. The method may include transmitting, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block that is sent in the corresponding transmit opportunity and is associated with a HARQ process identifier, the HARQ process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0011] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include: sending a scheduling configuration to a UE configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities. The method may include: transmitting, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block that is sent in the respective transmit opportunity and is associated with a HARQ process identifier, the HARQ process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a scheduling configuration configuring a plurality of transmission blocks to be sent in a pre-scheduled transmission opportunity burst from a network entity. The instruction set, when executed by one or more processors of the UE, may cause the UE to transmit, for each transmission opportunity in the pre-scheduled transmission opportunity burst, a transmission block that is sent in the corresponding transmission opportunity and is associated with a HARQ process identifier, the HARQ process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send a scheduling configuration to a UE that configures a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to transmit, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block that is sent in the corresponding transmit opportunity and is associated with a HARQ process identifier, the HARQ process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network entity, a scheduling configuration configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities. The apparatus may include means for transmitting, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block to be sent in the respective transmit opportunity and associated with a HARQ process identifier, the HARQ process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0015] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a scheduling configuration to a UE configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities. The apparatus may include means for transmitting, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block to be sent in the respective transmit opportunity and associated with a HARQ process identifier, the HARQ process identifier being based at least in part on a HARQ configuration associated with the scheduling configuration.

[0016] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings, specifications and appendices and as illustrated in the drawings, specifications and appendices.

[0017] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of downlink semi-persistent scheduling (SPS) communication and an example of uplink configured grant (CG) communication according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of SPS and / or CG configuration communications for supporting burst services according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example associated with a hybrid automatic repeat request (HARQ) process determination for enhanced SPS and / or CG configuration according to the present disclosure.

[0025] Figures 7 and 8 is a diagram illustrating an example process associated with HARQ process determination for enhanced SPS and / or CG configuration according to the present disclosure.

[0026] Figures 9 and 10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0030] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. As shown, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged 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 disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 is configured to utilize a radio protocol stack that is physically or logically distributed between 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).

[0031] In some examples, the network node 110 is or includes a network entity (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the 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 examples, the 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 communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more DUs, and / or one or more CUs. For example, the network node 110 may include 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 transmit receive point (TRP), a RU, a DU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other and / or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0032] In some aspects, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station and / or a base station subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station for a macro cell may be referred to as a macro base station. A base station for a pico cell may be referred to as a pico base station. A base station for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown, 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 may support one or more (eg, three) cells.

[0033] In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (eg, a mobile base station).

[0034] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120 or network nodes 110. Figure 1 In the example shown, network node 110d (e.g., a relay base station) can communicate with network node 110a (e.g., a macro base station) and UE 120d to facilitate communication between network node 110a and UE 120d. A network node 110 that relays communications may be referred to as a relay station, relay base station, relay node, relay, etc.

[0035] The wireless network 100 may 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 transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0036] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may include a CU or a core network device.

[0037] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, 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, an 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.

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

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

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

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0042] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0043] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0044] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a scheduling configuration configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmission opportunities from a network entity (e.g., network node 110); and process, for each transmission opportunity in the pre-scheduled burst of transmission opportunities, transmit a transport block that is sent in the corresponding transmission opportunity and is associated with a hybrid automatic repeat request (HARQ) process identifier, the hybrid automatic repeat request (HARQ) process identifier being based at least in part 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.

[0045] In some aspects, a network entity (e.g., network node 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send to the UE 120 a scheduling configuration configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities; and transmit, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block that is sent in a respective transmit opportunity and is associated with a HARQ process identifier that is based at least in part on a HARQ configuration associated with the scheduling configuration. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0046] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0047] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (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 may 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 a radio frequency component.

[0048] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may 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 to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 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 to 234t).

[0049] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 110 and may 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 to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may 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 a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0050] 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 in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0051] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0052] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform operations described herein (eg, with reference to Figures 6 to 10 ) or any aspects of any of the methods described herein.

[0053] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be configured by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to FIG. 2 ). Figures 6 to 10 ) or any aspects of any of the methods described herein.

[0054] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or ... Figure 2 Any other component of may perform or direct e.g. Figure 7 The process of 700 Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or 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, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example, Figure 7 The process of 700 Figure 8 The process 800 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

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

[0056] In some aspects, a network entity (e.g., network node 110) includes: means for sending a scheduling configuration to UE 120 configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities; and / or means for transmitting, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block to be sent in a corresponding transmit opportunity and associated with a HARQ process identifier, the HARQ process identifier being based at least in part on the HARQ configuration associated with the scheduling configuration. In some aspects, means for the network entity to perform operations described herein may include, for example, one or more of the following: 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.

[0057] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0058] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0059] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0060] The deployment of a communication system (such as a 5G NR system) may be arranged with various components or components in a variety of ways. In a 5GNR system or network, a network node may be implemented in an aggregated architecture or a decomposed architecture. For example, a network node or one or more units (or one or more components) that perform network node functionality may be implemented as an aggregated network node (sometimes referred to as an independent base station or a monolithic base station) or a decomposed network node. A "network entity" or "network node" may refer to a decomposed network node, an aggregated network node, or one or more entities of a decomposed network node (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0061] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0062] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0063] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed 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 a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via respective fronthaul links. Fronthaul links, midhaul links, and backhaul links may be generally referred to as "communication links." The RU 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. DU330 and RU 340 may also be referred to as “O-RAN DU (O-DU)” and “O-RAN RU (O-RU)”, respectively. A network entity may include a CU, a DU, a RU, or any combination of CU, DU, and RU. A network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. A network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0064] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as 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 these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

[0065] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. 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 specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0066] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of the following depending at least in part on a functional split such as that defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0067] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0068] The SMO framework 305 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may 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 virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0069] The non-RT RIC 315 may be configured to include logic 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 near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0071] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

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

[0073] As shown in example 400, the UE may be configured with an SPS configuration for grant-free downlink communications. For example, the UE may receive the SPS configuration via an RRC message sent by a network node. The SPS configuration may indicate resource allocations associated with the SPS downlink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations are repeated, so that scheduled SPS opportunities 405 for the UE are periodically repeated. The SPS configuration may also configure HARQ acknowledgment (HARQ-ACK) feedback resources for the UE to send HARQ-ACK feedback for SPS physical downlink shared channel (PDSCH) communications received in the SPS opportunity 405. For example, the SPS configuration may indicate a PDSCH to HARQ feedback timing value, which may be referred to as a K1 value in a wireless communication standard (e.g., a 3GPP standard).

[0074] The network node may send an SPS activation DCI to the UE to activate the SPS configuration for the UE. The network node may indicate communication parameters, such as MCS, resource block (RB) allocation, and / or antenna port in the SPS activation DCI for SPS PDSCH communications to be sent in the scheduled SPS opportunity 405. The UE may begin monitoring the SPS opportunity 405 based at least in part on receiving the SPS activation DCI. For example, starting with the next scheduled SPS opportunity 405 after receiving the SPS activation DCI, the UE may monitor the scheduled SPS opportunity 405 to decode the PDSCH communication using the communication parameters indicated in the SPS activation DCI. The UE may avoid monitoring the configured SPS opportunity 405 before receiving the SPS activation DCI.

[0075] The network node may send an SPS reactivation DCI to the UE to change the communication parameters used for SPS PDSCH communications. Based at least in part on receiving the SPS reactivation DCI, the UE may begin monitoring scheduled SPS opportunities 405 using the communication parameters indicated in the SPS reactivation DCI. For example, starting with the next scheduled SPS opportunity 405 after receiving the SPS reactivation DCI, the UE may monitor the scheduled SPS opportunity 405 to decode PDSCH communications based on the communication parameters indicated in the SPS reactivation DCI.

[0076] In some cases, such as when the network node does not have downlink traffic to be sent to the UE, the network node may send an SPS elimination DCI to the UE to temporarily eliminate or deactivate one or more subsequent SPS opportunities 405 for the UE. The SPS elimination DCI may only deactivate a subsequent SPS opportunity 405 or subsequent N SPS opportunities 405 (where N is an integer). The SPS opportunity 405 after one or more (e.g., N) SPS opportunities 405 after the SPS elimination DCI may remain activated. Based at least in part on receiving the SPS elimination DCI, the UE may avoid monitoring one or more (e.g., N) SPS opportunities 405 after receiving the SPS elimination DCI. As shown in example 400, the SPS elimination DCI eliminates a subsequent SPS opportunity 405 for the UE. After receiving the SPS elimination DCI after the SPS opportunity 405 (or N SPS opportunities), the UE may automatically resume monitoring the scheduled SPS opportunity 405.

[0077] The network node may send an SPS release DCI to the UE to deactivate the SPS configuration for the UE. The UE may stop monitoring the scheduled SPS opportunity 405 based at least in part on receiving the SPS release DCI. For example, the UE may avoid monitoring any scheduled SPS opportunity 405 until another SPS activation DCI is received from the base station. However, the SPS elimination DCI may only deactivate a subsequent SPS opportunity 405 or subsequent N SPS opportunities 405, and the SPS release DCI deactivates all subsequent SPS opportunities 405 for a given SPS configuration of the UE until the given SPS configuration is activated again by a new SPS activation DCI.

[0078] As shown in example 410, the UE may be configured with a CG configuration for grant-free uplink communication. For example, the UE may receive the CG configuration via an RRC message sent by a network node. The CG configuration may indicate resource allocations associated with the CG uplink communication (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations are repeated, so that scheduled CG opportunities 415 for the UE occur periodically. In some examples, the CG configuration may identify a resource pool or multiple resource pools available to the UE for uplink transmission. The CG configuration may configure contention-free CG communication (e.g., where resources are dedicated to the UE for transmitting uplink communications) or contention-based CG communication (e.g., where the UE contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).

[0079] The network node may send a CG activation DCI to the UE to activate the CG configuration for the UE. The network node may indicate in the CG activation DCI communication parameters, such as MCS, RB allocation and / or antenna port, for CG physical uplink shared channel (PUSCH) communications to be sent in the scheduled CG opportunity 415. The UE may start sending in the CG opportunity 415 based at least in part on receiving the CG activation DCI. For example, starting with the next scheduled CG opportunity 415 after receiving the CG activation DCI, the UE may send PUSCH communications in the scheduled CG opportunity 415 using the communication parameters indicated in the CG activation DCI. The UE may avoid sending in the configured CG opportunity 415 before receiving the CG activation DCI.

[0080] The network node may send a CG reactivation DCI to the UE to change the communication parameters used for CG PUSCH communications. Based at least in part on receiving the CG reactivation DCI, the UE may begin transmitting in scheduled CG occasions 415 using the communication parameters indicated in the CG reactivation DCI. For example, starting with the next scheduled CG occasion 415 after receiving the CG reactivation DCI, the UE may transmit PUSCH communications in scheduled CG occasions 415 based at least in part on the communication parameters indicated in the CG reactivation DCI.

[0081] In some cases, such as when the base station needs to override scheduled CG communications for higher priority communications, the network node may send a CG elimination DCI to the UE to temporarily eliminate or deactivate one or more subsequent CG opportunities 415 for the UE. The CG elimination DCI may deactivate only a subsequent CG opportunity 415 or subsequent N CG opportunities 415 (where N is an integer). The CG opportunities 415 after one or more (e.g., N) CG opportunities 415 after the CG elimination DCI may remain activated. Based at least in part on receiving the CG elimination DCI, the UE may avoid transmitting in one or more (e.g., N) CG opportunities 415 after receiving the CG elimination DCI. As shown in example 410, the CG elimination DCI eliminates a subsequent CG opportunity 415 for the UE. After the CG opportunity 415 (or N CG opportunities) after receiving the CG elimination DCI, the UE may automatically resume transmission in the scheduled CG opportunity 415.

[0082] The network node may send a CG release DCI to the UE to deactivate the CG configuration for the UE. The UE may stop transmitting in the scheduled CG occasions 415 based at least in part on receiving the CG release DCI. For example, the UE may avoid transmitting in any scheduled CG occasions 415 until another CG activation DCI is received from the base station. However, the CG elimination DCI may only deactivate a subsequent CG occasion 415 or subsequent N CG occasions 415, and the CG release DCI deactivates all subsequent CG occasions 415 for a given CG configuration of the UE until the given CG configuration is activated again by a new CG activation DCI.

[0083] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0084] Figure 5 5 is a diagram illustrating an example 500 of SPS and / or CG configuration communications for supporting burst services according to the present disclosure. For example, as described herein, Figure 5The SPS and / or CG configuration shown in may be used to support extended reality (XR) services, which is an umbrella term covering immersive technologies such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and virtualization levels interpolated between VR, AR, and MR.

[0085] For example, VR is a rendered version of an audiovisual scene, where the rendering is designed to simulate the visual and auditory stimulation of the real world as naturally as possible when the observer or user moves within the limits defined by the VR application. VR typically requires the user to wear a head-mounted display (HMD) to completely replace the field of view with simulated visual components and use headphones and / or speakers to listen to the accompanying audio. In VR applications, the user's head and motion tracking are also typically required to allow the simulated visual and audio components to be updated to ensure that from the user's perspective, the items and sound sources remain consistent with the user's movement. In AR applications, additional information or artificially generated items or content are generally provided to the user overlaid on the current environment. The additional information or content is typically visual and / or audible, and the observation of the current environment can be direct (without intermediate sensing, processing, and rendering) or indirect (where the perception of the environment can be relayed via sensors and enhanced or processed). 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.

[0086] It is expected that XR will improve productivity and convenience for consumers, enterprises and public institutions in various application areas such as entertainment, training, education, remote support, remote control, communication and / or virtual meetings. XR can be used in many industry sectors, including health care, real estate, shopping, transportation, manufacturing and / or other industry sectors. VR has been used for games at home and in dedicated venues, for virtual tours in the context of real estate, for education and training purposes, and for remote participation in live events such as concerts and sports. In addition, AR and MR use cases have significant potential. For example, although VR applications rely on HMDs that separate users from the physical environment and limit mobility, AR and MR applications allow users to appear in reality and even move freely when using HMDs. Many smartphone users have experienced the basic form of AR through games involving searching for virtual objects in a real-world environment and applications that enable shoppers to visualize new furniture in their homes before making a purchase. In addition, AR technology can be used with HMDs to free the user's hands, thereby improving worker efficiency by providing the ability to free up hands while overlaying information in the real world.

[0087] However, configuring wireless networks to support latency requirements, quality of experience (QoE) requirements, and high data rates associated with XR services presents various challenges. For example, at an XR-enabled UE, the XR service may include posture data (e.g., related to positioning and orientation in space), video data, audio data, and / or other data sent by and / or to an XR-enabled UE, may have a video frame size that varies over time, and / or may have a quasi-periodic packet arrival time with application jitter (e.g., causing the XR service arrival time to vary). In addition, due to the uncertain application processing time, the service arrival time at the network node (e.g., RAN node) is periodic, with non-negligible jitter. In addition to not being fixed over time, the video frame size is an order of magnitude larger than the packets in voice or industrial control communications. Instead, each frame is expected to be segmented, which means that packets arrive in bursts that must be processed together to meet strict bounded latency requirements. For example, as described herein, a burst, a traffic burst, a transmit burst, etc., may refer to a continuous sequence of packets having a shorter inter-packet arrival time and / or a higher traffic volume than packets arriving before or after the continuous sequence of packets in the burst. Thus, because packets arrive in bursts, XR traffic may have different characteristics than voice or other applications that the SPS and / or CG configurations are designed to handle. For example, in existing (e.g., legacy) SPS and / or CG configurations (e.g., as described above with reference to Figure 4 In the prior art (described in the specification), the SPS and / or CG opportunities can be aligned with normal traffic patterns, such as one packet every twenty (20) milliseconds for voice traffic. In existing SPS and / or CG configurations, each SPS and / or CG opportunity is an independent transmission opportunity (e.g., each SPS and / or CG opportunity can transmit a single transport block). In contrast, XR traffic has a much higher data rate than voice and tends to be highly bursty in the sense that many packets arrive very close in time, followed by an idle period before the next cycle begins and the next traffic burst arrives (e.g., a bursty traffic pattern can include sudden increases and / or decreases in traffic volume and / or inter-packet arrival times).

[0088] Therefore, in some respects, Figure 5 The enhanced SPS and / or CG configurations that may enable sending multiple transport blocks in a cycle to support XR applications or applications associated with burst traffic patterns are illustrated. Figure 5As shown in , an enhanced SPS and / or CG configuration may include a loop 510 that includes a sequence of multiple SPS and / or CG opportunities 520, which may be similar to how a physical downlink control channel (PDCCH) search space is configured. As further shown, the number of SPS and / or CG opportunities 520 included in the loop 510 may be based at least in part on a maximum burst size (e.g., the maximum amount of data that can be sent to or by a UE in a given time interval) and an estimated or measured jitter (e.g., a variation or difference in the latency or delay experienced by different packets as they traverse a network from a transmitter to a receiver). For example, in some aspects, the number of SPS and / or CG opportunities 520 included in the loop 510 of the enhanced SPS and / or CG configuration may be the sum of the maximum burst size and twice (2x) the estimated or measured jitter. For example, the estimated or measured jitter may have positive or negative values ​​(e.g., a subsequent packet may have a greater or lesser delay than a previous packet), and thus the number of SPS and / or CG opportunities 520 included in the loop 510 needs to cover the potential jitter in both directions. Figure 5 As shown in , the packet arrival interval 530 can be defined as the time between adjacent SPS and / or CG opportunities 520, and the frame periodicity 540 is defined as the periodicity between two adjacent cycles 510. In this way, the enhanced SPS and / or CG configuration can be suitable for XR applications or other applications with bursty business patterns by: providing a cluster of transmission opportunities (e.g., SPS and / or CG opportunities 520) so that multiple transmission blocks can be sent in each cycle 510; providing a time gap (e.g., packet arrival interval 530) between adjacent opportunities that is much shorter than the periodicity of a traditional SPS and / or CG configuration (e.g., a burst in XR business can arrive once every sixteen (16) milliseconds, and there can be several packets in each burst, all of which arrive very close in time, such as one (1) millisecond apart); and providing additional CG opportunities 520 in each cycle 510 to accommodate jitter that might otherwise interfere with streaming video and / or audio data.

[0089] In a wireless network, a HARQ process may be used to enable HARQ feedback to request retransmission of a transport block and / or to perform HARQ combining (sometimes referred to as soft combining or HARQ with soft combining) within 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). In the case of supporting HARQ-ACK feedback, when the transport block is successfully decoded, the receiver may send an acknowledgment (ACK) to the transmitter. Otherwise, when the receiver experiences an error with respect to the reception and / or decoding of the data communication, the receiver may send a negative acknowledgment (NACK) to request retransmission of the transport block. In some cases, a NACK-only HARQ-ACK feedback mode may be used, in which when the receiver experiences an error with respect to the reception and / or decoding of the data communication, the receiver does not send an ACK and only sends a NACK. Additionally or alternatively, in the case of supporting HARQ combining, the receiver may store the received data (which may include erroneously received data) in a soft buffer, and the HARQ process may be associated with the soft buffer. The same HARQ process may be used to perform one or more retransmissions of a data communication so that a receiver can associate the data included in the retransmission with data stored in a soft buffer (e.g., data from the original communication and / or any previous retransmissions). In this way, a receiver can combine the retransmitted data with the buffered data (e.g., using soft combining or another technique to combine data from multiple transmissions that may include different redundant versions of the data communication), thereby improving decoding performance.

[0090] Although HARQ feedback and / or HARQ combining have the potential to significantly improve the reliability and / or decoding performance of transport blocks sent over the air interface, the technology for mapping HARQ process identifiers to transmission opportunities in enhanced SPS and / or CG configurations presents challenges. For example, as described above, each transmission opportunity in a traditional SPS and / or CG configuration is typically an independent transmission opportunity for a single transport block, whereby the HARQ process identifier associated with each SPS and / or CG opportunity in the traditional SPS and / or CG configuration is determined according to a hard-coded mapping specified in one or more wireless communication standards (e.g., based on a time slot index of the SPS and / or CG opportunity). For example, where a traditional SPS or CG configuration is configured to have N HARQ process identifiers, HARQ process 1 is assigned to the first SPS or CG opportunity, HARQ process N is assigned to the NSPS or CG opportunity, and the N HARQ process identifiers are then repeated sequentially in the time domain. However, in an enhanced SPS and / or CG configuration for supporting XR applications or other applications associated with a burst traffic pattern, multiple transport blocks may be sent in a pre-scheduled burst of transmission opportunities. However, the sequential mapping of HARQ process identifiers to SPS or CG transmission opportunities may be problematic in XR (or similar) applications because each period or cycle may be very short. For example, when an XR application runs at a frame rate of 120 milliseconds, the period of each burst is 8.3 milliseconds, which may be close to a typical HARQ process length of three (3) times the round-trip time across the air interface (e.g., where each round-trip time is approximately one or two milliseconds). In particular, when channel conditions are poor and the HARQ process takes more than three round-trip times (or three retransmissions), the HARQ process may cut into the next cycle, which creates the possibility of the HARQ process blocking a new transmission using the same HARQ process in the next cycle. Therefore, as described below with reference to Figure 6 Described in further detail, some aspects described herein relate to techniques for associating a HARQ process identifier with each transmission opportunity in an enhanced SPS or CG configuration for supporting transmission of multiple transport blocks in a pre-scheduled SPS or CG opportunity burst.

[0091] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

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

[0093] As indicated by reference numeral 610, the network node 110 may send and the UE 120 may receive a scheduling configuration configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmission opportunities. Figure 5 Described in further detail, the scheduling configuration may include an enhanced SPS configuration that configures a plurality of transport blocks to be sent from the network node 110 to the UE 120 in a pre-scheduled burst of transmission opportunities. Additionally or alternatively, the scheduling configuration may include an enhanced CG configuration that configures a plurality of transport blocks to be sent from the UE 120 to the network node 110 in a pre-scheduled burst of transmission opportunities. For example, as described herein, the scheduling configuration may include a cycle that includes a sequence of pre-scheduled bursts of transmission opportunities, wherein the number of transmission opportunities included in the cycle may be based at least in part on a maximum burst size (e.g., a maximum amount of data that can be sent to or by the UE in a given time interval) and an estimated or measured jitter (e.g., a variation or difference in latency or delay experienced by different packets when traversing a network from a transmitter to a receiver). For example, in some aspects, the number of transmission opportunities included in the cycle of the scheduling configuration may be the sum of the maximum burst size and twice (2×) the estimated or measured jitter (e.g., to cover potential jitter in both positive and negative directions). In addition, the packet arrival interval may be defined as the time between adjacent transmission opportunities, and the frame periodicity may be defined as the periodicity between two adjacent cycles. In this way, a scheduling configuration for configuring multiple transport blocks to be sent in a burst of pre-scheduled transmit opportunities can be adapted for XR applications or other applications with bursty traffic patterns by: providing a cluster of transmit opportunities (e.g., SPS opportunities and / or CG opportunities) for sending multiple transport blocks in each cycle; providing a shorter time gap between adjacent opportunities than the periodicity of conventional SPS and / or CG configurations; and providing additional transmit opportunities in each cycle to accommodate potential jitter that might otherwise interfere with streaming video and / or audio data.

[0094] like Figure 6As further shown in , the scheduling configuration provided by the network node 110 can be associated with a HARQ configuration that defines a mapping between a HARQ process identifier and a corresponding transmission opportunity in a pre-scheduled transmission opportunity burst. For example, the HARQ process identifier associated with the corresponding transmission opportunity can enable HARQ-based retransmission and / or HARQ combining within multiple repetitions and / or retransmissions of a transport block, as described in further detail elsewhere herein. Therefore, in some aspects, the network node 110 and the UE 120 can process each transmission opportunity in a pre-scheduled transmission opportunity burst by associating a HARQ process identifier with each corresponding transmission opportunity based on the HARQ configuration associated with the enhanced scheduling configuration.

[0095] For example, as shown by reference numeral 620, the HARQ configuration may limit the number of HARQ process identifiers used per cycle to no more than the number of transmit opportunities per cycle (e.g., the number of HARQ process identifiers used per cycle is less than or equal to the number of transmit opportunities per cycle). In such cases, the pattern used to map the HARQ process identifiers to the transmit opportunities in the pre-scheduled transmit opportunity bursts may be the same in each cycle. For example, within each cycle of the scheduling configuration, the HARQ process identifier may be associated with each transmit opportunity based on a slot index or another suitable allocation pattern, and the same pattern may be used in each cycle of the scheduling configuration. For example, reference numeral 620 depicts an example in which there are four (4) transmit opportunities per cycle and three (3) 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 transmit opportunity in the cycle, the second HARQ process may be assigned to the next transmit opportunity in the cycle, and so on, and the HARQ process identifiers are then repeated sequentially in the time domain. However, in some cases, limiting the number of HARQ process identifiers to be less than or equal to the number of transmit opportunities per cycle may potentially cause one or more transmit opportunities to be blocked (e.g., when one or more transmit opportunities are used for retransmission such that the HARQ process identifier wraps around in a cycle when the number of transmit opportunities is less than or equal to the number of HARQ processes per cycle).

[0096] Thus, as indicated by reference numeral 630, a HARQ configuration associated with a scheduling configuration may permit or otherwise allow (but not necessarily require) a number of HARQ processes per cycle to be greater than or equal to a number of opportunities per cycle, which may avoid potential issues with one or more transmit opportunities potentially being blocked due to retransmissions associated with one or more HARQ process identifiers. For example, in situations where the number of HARQ processes per cycle may exceed the number of opportunities in a cycle of the scheduling configuration, the pattern for mapping HARQ process identifiers to transmit opportunities may be independent of the SPS and / or CG cycles. For example, rather than associating a HARQ process identifier with a transmit opportunity based on a timeslot index for each corresponding transmit opportunity, the HARQ configuration may define a formula to associate a HARQ process identifier with an index of a corresponding transmit opportunity in a sequence, cycle, or burst of pre-scheduled transmit opportunities, where wraparound is enabled within different bursts. For example, in some aspects, the opportunity index O associated with transmit opportunity i may be defined as follows: i The timing of the transmission may be based at least in part on i The associated time slot index, the length T of the cycle and the number of opportunities per cycle N. For example, the opportunity index O associated with the transmission opportunity i i can be defined as follows:

[0097]

[0098] In some aspects, the HARQ process identifier associated with a particular transmission opportunity may then be based on the opportunity index assigned to the transmission opportunity. i , the number H of HARQ processes configured for SPS or CG scheduling configuration and the offset are determined as follows:

[0099] HARQ ID = (offset + i )modulo H

[0100] Wherein the offset is an integer ranging from zero (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 opportunity in the pre-scheduled transmission opportunity burst can avoid potential blocking transmission by associating the HARQ process identifier with the corresponding transmission opportunity independently of the underlying burst mode of the SPS and / or CG cycle that can be used to transmit multiple transport blocks. For example, the modulo operation in the equation provided above can produce a wraparound whereby the HARQ process is sequentially associated with different transmission opportunities, and the HARQ process identifier wraps around after the number of transmission opportunities exceeds the total number of HARQ process identifiers configured for the SPS or CG configuration.

[0101] Therefore, the UE 120 and the network node 110 may transmit the transport block in a pre-scheduled transmission opportunity burst associated with the enhanced scheduling configuration based on the HARQ configuration. Figure 6 , reference numerals 640 and 650 depict communications between UE 120 and network node 110 when the enhanced scheduling configuration is an enhanced SPS configuration. In this example, as shown by reference numeral 640, network node 110 may send multiple transport blocks to UE 120 in multiple SPS opportunities included in a cycle, wherein each transport block is associated with a HARQ process identifier. In some aspects, UE 120 may then determine the HARQ process identifier associated with each SPS opportunity based on the applicable HARQ configuration (e.g., depending on whether the number of HARQ processes is limited to not exceed the number of SPS opportunities in the cycle or is permitted to exceed the number of SPS opportunities in the cycle). As shown by reference numeral 650, UE 120 may attempt to decode each transport block sent in the SPS opportunity, and may send HARQ feedback (e.g., ACK or NACK) associated with the HARQ process identifier to network node 110 (e.g., to trigger retransmission or otherwise indicate the decoding result). Additionally or alternatively, in the case where the enhanced scheduling configuration is a grant configuration of the enhanced configuration, substantially the same technique may be used in reverse. For example, in the grant configuration of the enhanced configuration, the UE 120 may send a plurality of transport blocks to the network node 110 in a plurality of configured grant opportunities each associated with a HARQ process identifier, and the network node 110 may determine the HARQ process identifier associated with each CG opportunity based on the applicable HARQ configuration, attempt to decode each transport block sent in the configured grant opportunity, and / or send HARQ feedback associated with the HARQ process identifier to the UE 120 to indicate the corresponding decoding result.

[0102] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0103] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a UE in accordance with the present disclosure. Example process 700 is an example of operations in which a UE (eg, UE 120) performs operations associated with HARQ process determination for enhanced SPS and / or CG configuration.

[0104] like Figure 7 As shown in FIG. 7 , in some aspects, process 700 may include receiving a scheduling configuration from a network entity that configures a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmission opportunities (block 710). For example, a UE (e.g., using Fig. 9The communication manager 140 and / or receiving component 902 depicted in FIG. 1 may receive a scheduling configuration configuring a plurality of transport blocks to be sent in a pre-scheduled transmit opportunity burst from a network entity, as described above.

[0105] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include transmitting, for each transmission opportunity in a pre-scheduled transmission opportunity burst, a transport block that is transmitted in a corresponding transmission opportunity and is associated with a HARQ process identifier that is based at least in part on a HARQ configuration associated with a scheduling configuration (block 720). For example, a UE (e.g., using Fig. 9 The communication manager 140 and / or the HARQ process determination component 908 depicted in the figure can process, for each transmission opportunity in a pre-scheduled transmission opportunity burst, a transmission block transmitted in a corresponding transmission opportunity according to a HARQ process identifier, which is at least partially based on a HARQ configuration associated with the scheduling configuration, as described above.

[0106] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0107] In a first aspect, the scheduling configuration is an SPS configuration configuring a number of transport blocks to be sent from a network entity to a UE in a pre-scheduled burst of transmit opportunities.

[0108] In a second aspect, alone or in combination with the first aspect, the scheduling configuration is a CG configuration configuring a plurality of transport blocks to be sent from the UE to the network entity in a pre-scheduled burst of transmission opportunities.

[0109] 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 pre-scheduled transmit opportunity burst to be less than or equal to the number of transmit opportunities in the pre-scheduled transmit opportunity burst.

[0110] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the pattern of associating a HARQ process identifier with each respective transmit opportunity in a pre-scheduled transmit opportunity burst is the same in each cycle of the scheduling configuration.

[0111] In a fifth aspect, either 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 pre-scheduled transmit opportunity burst to be equal to or exceed the number of transmit opportunities in the pre-scheduled transmit opportunity burst.

[0112] In a sixth aspect, either alone or in combination with one or more of aspects one to five, a pattern of associating a HARQ process identifier with each corresponding transmission opportunity in a pre-scheduled transmission opportunity burst is based at least in part on an index associated with each corresponding transmission opportunity, an offset associated with a scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst.

[0113] In a seventh aspect, either alone or in combination with one or more of aspects one to six, an index associated with each respective transmission opportunity is based at least in part on a time slot index associated with the respective transmission opportunity, a cycle length associated with a scheduling configuration, and the number of transmission opportunities in a pre-scheduled transmission opportunity burst.

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

[0115] although Figure 7 An example block diagram of process 700 is shown, but in some aspects, process 700 may include Figure 7 The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks in the blocks of the process 700 may be performed in parallel.

[0116] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a network entity according to the present disclosure. Example 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 enhanced SPS and / or CG configuration.

[0117] like Figure 8 As shown in FIG. 8 , in some aspects, process 800 may include sending a scheduling configuration to a UE that configures a plurality of transport blocks to be sent in a pre-scheduled burst of transmission opportunities (block 810). For example, a network entity (e.g., using Fig.10 The communication manager 150 and / or the transmitting component 1004 depicted in FIG. 1004 may send a scheduling configuration to the UE configuring a plurality of transport blocks to be sent in a pre-scheduled transmit opportunity burst, as described above.

[0118] like Figure 8As further shown in FIG. 8 , in some aspects, process 800 may include transmitting, for each transmission opportunity in a pre-scheduled transmission opportunity burst, a transport block that is transmitted in the corresponding transmission opportunity and is associated with a HARQ process identifier that is based at least in part on a HARQ configuration associated with a scheduling configuration (block 820). For example, a network entity (e.g., using Fig.10 The communication manager 150 and / or the HARQ process determination component 1008 depicted in the figure can process, for each transmission opportunity in a pre-scheduled transmission opportunity burst, a transmission block sent in a corresponding transmission opportunity according to a HARQ process identifier, which HARQ process identifier is at least partially based on a HARQ configuration associated with the scheduling configuration, as described above.

[0119] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0120] In a first aspect, the scheduling configuration is an SPS configuration configuring a number of transport blocks to be sent from a network entity to a UE in a pre-scheduled burst of transmit opportunities.

[0121] In a second aspect, alone or in combination with the first aspect, the scheduling configuration is a CG configuration configuring a plurality of transport blocks to be sent from the UE to the network entity in a pre-scheduled burst of transmission opportunities.

[0122] 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 pre-scheduled transmit opportunity burst to be less than or equal to the number of transmit opportunities in the pre-scheduled transmit opportunity burst.

[0123] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the pattern of associating a HARQ process identifier with each respective transmit opportunity in a pre-scheduled transmit opportunity burst is the same in each cycle of the scheduling configuration.

[0124] In a fifth aspect, either 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 pre-scheduled transmit opportunity burst to be equal to or exceed the number of transmit opportunities in the pre-scheduled transmit opportunity burst.

[0125] In a sixth aspect, either alone or in combination with one or more of aspects one to five, a pattern of associating a HARQ process identifier with each corresponding transmission opportunity in a pre-scheduled transmission opportunity burst is based at least in part on an index associated with each corresponding transmission opportunity, an offset associated with a scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst.

[0126] In a seventh aspect, either alone or in combination with one or more of aspects one to six, an index associated with each respective transmission opportunity is based at least in part on a time slot index associated with the respective transmission opportunity, a cycle length associated with a scheduling configuration, and the number of transmission opportunities in a pre-scheduled transmission opportunity burst.

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

[0128] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted in the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks in the blocks of the process 800 may be performed in parallel.

[0129] Fig. 9 is a diagram of an example apparatus 900 for wireless communication. Apparatus 900 may be a UE, or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may 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 shown, apparatus 900 may include a communication manager 140. As further shown, communication manager 140 may include a HARQ process determination component 908, etc.

[0130] In some aspects, the apparatus 900 may be configured to perform the Figure 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 and / or Fig. 9 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig. 9One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0131] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or a combination thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a described UE.

[0132] Transmit component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to transmit component 904 for transmission to device 906. In some aspects, transmit component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 906. In some aspects, transmit component 904 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0133] The receiving component 902 can receive a scheduling configuration configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities from a network entity. The HARQ process determining component 908 can transmit, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block to be sent in a corresponding transmit opportunity and associated with a HARQ process identifier based at least in part on a HARQ configuration associated with the scheduling configuration.

[0134] Fig. 9The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 9 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 9 Two or more components shown in the figure may be implemented in a single component, or Fig. 9 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig. 9 One or more functions performed by another group of components shown in the figure.

[0135] Fig.10 1 is a diagram of an example 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 may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 150. As further shown, communication manager 150 may include, among other things, a HARQ process determination component 1008.

[0136] In some aspects, the apparatus 1000 may be configured to perform the Figure 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0137] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

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

[0139] The transmitting component 1004 can transmit, to the UE, a scheduling configuration configuring a plurality of transport blocks to be transmitted in a pre-scheduled burst of transmit opportunities. The HARQ process determining component 1008 can transmit, for each transmit opportunity in the pre-scheduled burst of transmit opportunities, a transport block to be transmitted in the respective transmit opportunity and associated with a HARQ process identifier based at least in part on the HARQ configuration associated with the scheduling configuration.

[0140] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.10 Two or more components shown in the figure may be implemented in a single component, or Fig.10The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.10 One or more functions performed by another group of components shown in the figure.

[0141] The following provides an overview of some aspects of the disclosure:

[0142] Aspect 1: A method of wireless communication performed by a UE, comprising: receiving a scheduling configuration from a network entity that configures multiple transmission blocks to be sent in a pre-scheduled transmission opportunity burst; and for each transmission opportunity in the pre-scheduled transmission opportunity burst, transmitting a transmission block that is sent in the corresponding transmission opportunity and is associated with a HARQ process identifier, wherein the HARQ process identifier is at least partially based on the HARQ configuration associated with the scheduling configuration.

[0143] Aspect 2: The method according to aspect 1, wherein the scheduling configuration is an SPS configuration configuring a plurality of transport blocks to be sent from the network entity to the UE in the pre-scheduled transmission opportunity burst.

[0144] Aspect 3: A method according to any one of Aspects 1 to 2, wherein the scheduling configuration is a CG configuration configuring multiple transmission blocks to be sent from the UE to the network entity in the pre-scheduled transmission opportunity burst.

[0145] Aspect 4: A method according to any one of Aspects 1 to 3, wherein the HARQ configuration limits the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst to be less than or equal to the number of transmission opportunities in the pre-scheduled transmission opportunity burst.

[0146] Aspect 5: The method according to aspect 4, wherein the pattern of associating the HARQ process identifier with each respective transmission opportunity in the pre-scheduled transmission opportunity burst is the same in each cycle of the scheduling configuration.

[0147] Aspect 6: A method according to any one of aspects 1 to 3, wherein the HARQ configuration permits the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst to be equal to or exceed the number of transmission opportunities in the pre-scheduled transmission opportunity burst.

[0148] Aspect 7: A method according to Aspect 6, wherein a pattern of associating the HARQ process identifier with each corresponding transmission opportunity in the pre-scheduled transmission opportunity burst is at least partially based on an index associated with each corresponding transmission opportunity, an offset associated with the scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst.

[0149] Aspect 8: A method according to Aspect 7, wherein the index associated with each respective transmission opportunity is based at least in part on a time slot index associated with the respective transmission opportunity, a cycle length associated with the scheduling configuration, and the number of transmission opportunities in the pre-scheduled transmission opportunity burst.

[0150] Aspect 9: The method according to any one of aspects 7 to 8, wherein the offset associated with the scheduling configuration is an integer ranging from zero to a total number of HARQ process identifiers assigned to the scheduling configuration.

[0151] Aspect 10: A method of wireless communication performed by a network entity, comprising: sending a scheduling configuration to a UE that configures multiple transmission blocks to be sent in a pre-scheduled transmission opportunity burst; and for each transmission opportunity in the pre-scheduled transmission opportunity burst, transmitting a transmission block that is sent in the corresponding transmission opportunity and is associated with a HARQ process identifier, wherein the HARQ process identifier is at least partially based on the HARQ configuration associated with the scheduling configuration.

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

[0153] Aspect 12: A method according to any one of Aspects 10 to 11, wherein the scheduling configuration is a CG configuration configuring a plurality of transmission blocks to be sent from the UE to the network entity in the pre-scheduled transmission opportunity burst.

[0154] Aspect 13: A method according to any one of Aspects 10 to 12, wherein the HARQ configuration limits the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst to be less than or equal to the number of transmission opportunities in the pre-scheduled transmission opportunity burst.

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

[0156] Aspect 15: A method according to any one of aspects 10 to 12, wherein the HARQ configuration permits the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst to be equal to or exceed the number of transmission opportunities in the pre-scheduled transmission opportunity burst.

[0157] Aspect 16: A method according to Aspect 15, wherein the pattern of associating the HARQ process identifier with each corresponding transmission opportunity in the pre-scheduled transmission opportunity burst is at least partially based on an index associated with each corresponding transmission opportunity, an offset associated with the scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst.

[0158] Aspect 17: A method according to Aspect 16, wherein the index associated with each respective transmission opportunity is based at least in part on a time slot index associated with the respective transmission opportunity, a cycle length associated with the scheduling configuration, and the number of transmission opportunities in the pre-scheduled transmission opportunity burst.

[0159] Aspect 18: The method according to any one of aspects 16 to 17, wherein the offset associated with the scheduling configuration is an integer ranging from zero to a total number of HARQ process identifiers assigned to the scheduling configuration.

[0160] Aspect 19: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 9.

[0161] Aspect 20: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 9.

[0162] Aspect 21: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 1 to 9.

[0163] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 9.

[0164] Aspect 23: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 9.

[0165] Aspect 24: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in aspects 10 to 18.

[0166] Aspect 25: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 10 to 18.

[0167] Aspect 26: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 10 to 18.

[0168] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 10 to 18.

[0169] Aspect 28: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 10 to 18.

[0170] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0171] Further disclosure is included in the appendix. This appendix is ​​provided as an example only and should be considered a part of this specification. The definitions, illustrations, or other descriptions in the appendix do not replace or cover similar information contained in the specific embodiments or figures. In addition, the definitions, illustrations, or other descriptions in the specific embodiments or figures do not replace or cover similar information included in the appendix. In addition, this appendix is ​​not intended to limit the disclosure of possible aspects.

[0172] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

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

[0174] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, 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 sorting of a, b and c).

[0175] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory and configured to: receiving, from a network entity, a scheduling configuration configuring a plurality of transport blocks to be sent in a burst of pre-scheduled transmission opportunities; as well as For each transmission opportunity in the pre-scheduled transmission opportunity burst, a transport block is transmitted in the corresponding transmission opportunity and is associated with a hybrid automatic repeat request (HARQ) process identifier, wherein the hybrid automatic repeat request (HARQ) process identifier is at least partially based on a HARQ configuration associated with the scheduling configuration.

2. The UE according to claim 1, wherein the scheduling configuration is a semi-persistent scheduling configuration configuring a plurality of transport blocks to be sent from the network entity to the UE in the pre-scheduled burst of transmission opportunities.

3. The UE of claim 1, wherein the scheduling configuration is a grant configuration configuring a configuration of a plurality of transport blocks to be sent from the UE to the network entity in the pre-scheduled burst of transmission opportunities.

4. The UE of claim 1, wherein the HARQ configuration limits the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst to be less than or equal to the number of transmission opportunities in the pre-scheduled transmission opportunity burst.

5. The UE of claim 4, wherein a pattern of associating the HARQ process identifier with each respective transmit opportunity in the pre-scheduled transmit opportunity burst is the same in each cycle of the scheduling configuration.

6. The UE of claim 1, wherein the HARQ configuration permits a number of HARQ process identifiers in the pre-scheduled burst of transmit opportunities to be equal to or exceed a number of transmit opportunities in the pre-scheduled burst of transmit opportunities.

7. A UE according to claim 6, wherein the pattern of associating the HARQ process identifier with each corresponding transmission opportunity in the pre-scheduled transmission opportunity burst is at least partially based on an index associated with each corresponding transmission opportunity, an offset associated with the scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst.

8. The UE of claim 7, wherein the index associated with each respective transmit opportunity is based at least in part on a time slot index associated with the respective transmit opportunity, a cycle length associated with the scheduling configuration, and the number of transmit opportunities in the pre-scheduled transmit opportunity burst.

9. The UE of claim 7, wherein the offset associated with the scheduling configuration is an integer ranging from zero to a total number of HARQ process identifiers assigned to the scheduling configuration.

10. A network entity for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory and configured to: sending a scheduling configuration to a user equipment (UE) configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmit opportunities; and For each transmission opportunity in the pre-scheduled transmission opportunity burst, a transport block is transmitted in the corresponding transmission opportunity and is associated with a hybrid automatic repeat request (HARQ) process identifier, wherein the hybrid automatic repeat request (HARQ) process identifier is at least partially based on a HARQ configuration associated with the scheduling configuration.

11. The network entity of claim 10, wherein the scheduling configuration is a semi-persistent scheduling configuration configuring a plurality of transport blocks to be sent from the network entity to the UE in the pre-scheduled burst of transmit opportunities.

12. The network entity of claim 10, wherein the scheduling configuration is a grant configuration configuring a configuration of a plurality of transport blocks to be sent from the UE to the network entity in the pre-scheduled burst of transmit opportunities.

13. The network entity of claim 10, wherein the HARQ configuration limits the number of HARQ process identifiers in the pre-scheduled burst of transmit opportunities to be less than or equal to the number of transmit opportunities in the pre-scheduled burst of transmit opportunities.

14. The network entity of claim 13, wherein a pattern of associating the HARQ process identifier with each respective transmit opportunity in the pre-scheduled burst of transmit opportunities is the same in each cycle of the scheduling configuration.

15. The network entity of claim 10, wherein the HARQ configuration permits a number of HARQ process identifiers in the pre-scheduled burst of transmit opportunities to be equal to or exceed a number of transmit opportunities in the pre-scheduled burst of transmit opportunities.

16. A network entity according to claim 15, wherein the pattern of associating the HARQ process identifier with each corresponding transmission opportunity in the pre-scheduled transmission opportunity burst is at least partially based on an index associated with each corresponding transmission opportunity, an offset associated with the scheduling configuration, and the number of the HARQ process identifiers in the pre-scheduled transmission opportunity burst.

17. The network entity of claim 16, wherein the index associated with each respective transmit opportunity is based at least in part on a time slot index associated with the respective transmit opportunity, a cycle length associated with the scheduling configuration, and the number of transmit opportunities in the pre-scheduled transmit opportunity burst.

18. The network entity of claim 16, wherein the offset associated with the scheduling configuration is an integer ranging from zero to a total number of HARQ process identifiers assigned to the scheduling configuration.

19. A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a network entity, a scheduling configuration configuring a plurality of transport blocks to be sent in a burst of pre-scheduled transmission opportunities; as well as For each transmission opportunity in the pre-scheduled transmission opportunity burst, a transport block is transmitted in the corresponding transmission opportunity and is associated with a hybrid automatic repeat request (HARQ) process identifier, wherein the hybrid automatic repeat request (HARQ) process identifier is at least partially based on a HARQ configuration associated with the scheduling configuration.

20. The method of claim 19, wherein the scheduling configuration is a semi-persistent scheduling configuration configuring a plurality of transport blocks to be sent from the network entity to the UE in the pre-scheduled burst of transmit opportunities.

21. The method of claim 19, wherein the scheduling configuration is a grant configuration configuring a configuration of a plurality of transport blocks to be sent from the UE to the network entity in the pre-scheduled burst of transmit opportunities.

22. The method of claim 19, wherein the HARQ configuration limits the number of HARQ process identifiers in the pre-scheduled burst of transmit opportunities to be less than or equal to the number of transmit opportunities in the pre-scheduled burst of transmit opportunities.

23. The method of claim 19, wherein the HARQ configuration permits a number of HARQ process identifiers in the pre-scheduled burst of transmit opportunities to equal or exceed a number of transmit opportunities in the pre-scheduled burst of transmit opportunities.

24. A method according to claim 23, wherein the pattern of associating the HARQ process identifier with each corresponding transmission opportunity in the pre-scheduled transmission opportunity burst is at least partially based on an index associated with each corresponding transmission opportunity, an offset associated with the scheduling configuration, and the number of HARQ process identifiers in the pre-scheduled transmission opportunity burst.

25. A method of wireless communication performed by a network entity, comprising: sending a scheduling configuration to a user equipment (UE) configuring a plurality of transport blocks to be sent in a pre-scheduled burst of transmission opportunities; as well as For each transmission opportunity in the pre-scheduled transmission opportunity burst, a transport block is transmitted in the corresponding transmission opportunity and is associated with a hybrid automatic repeat request (HARQ) process identifier, wherein the hybrid automatic repeat request (HARQ) process identifier is at least partially based on a HARQ configuration associated with the scheduling configuration.

26. The method of claim 25, wherein the scheduling configuration is a semi-persistent scheduling configuration configuring a plurality of transport blocks to be sent from the network entity to the UE in the pre-scheduled burst of transmit opportunities.

27. The method of claim 25, wherein the scheduling configuration is a grant configuration configuring a configuration of a plurality of transport blocks to be sent from the UE to the network entity in the pre-scheduled burst of transmit opportunities.

28. The method of claim 25, wherein the HARQ configuration limits the number of HARQ process identifiers in the pre-scheduled burst of transmit opportunities to be less than or equal to the number of transmit opportunities in the pre-scheduled burst of transmit opportunities.

29. The method of claim 28, wherein the pattern of associating the HARQ process identifier with each respective transmit opportunity in the pre-scheduled burst of transmit opportunities is the same in each cycle of the scheduling configuration.

30. The method of claim 25, wherein the HARQ configuration permits a number of HARQ process identifiers in the pre-scheduled burst of transmit opportunities to equal or exceed a number of transmit opportunities in the pre-scheduled burst of transmit opportunities.

Images