Uplink Extended Reality Scheduling

Abstract

Certain aspects of the present disclosure are techniques for wireless communication by a user equipment (UE), including receiving, from a network entity, one or more configuration grants (CGs) each defining at least one CG opportunity within a data period, obtaining traffic in the form of one or more bursts (e.g., periodic uplink), and transmitting the traffic to the network entity within a plurality of physical uplink shared channels (PUSCHs) within the data period.

Description

Technical Field

[0001] (Cross - reference to related applications)

[0001] This application claims the benefit and priority of U.S. Patent Application No. 17 / 664,583, filed on May 23, 2022, which is incorporated herein by reference.

Background Art

[0002]

[0002] Aspects of the present disclosure relate to wireless communication, and more particularly, to techniques for scheduling resources for uplink (UL) traffic, such as extended reality (XR) uplink traffic.

[0003] (Description of related technologies)

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephone communication, video, data, messaging, broadcast, or other similar types of services. These wireless communication systems can employ multi - connection technologies capable of supporting communication with multiple users by sharing the available wireless communication system resources with those users.

[0004]

[0004] Wireless communication systems have made great technological progress over the years, but there are still problems. For example, a complex and dynamic environment may still attenuate or block signals between a wireless transmitter and a wireless receiver. Therefore, for example, improving communication speed and data transfer capacity, improving the utilization efficiency of a shared communication medium, reducing the power consumed by a transmitter and a receiver during communication, improving the reliability of wireless communication, avoiding redundant transmission and / or reception and related processing, improving the coverage area of wireless communication, increasing the number and types of devices that can access a wireless communication system, improving the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc., are still desired to improve the technical performance of wireless communication systems. Therefore, in order to overcome the above-mentioned technical problems and the like, further improvements in wireless communication systems are needed.

Summary of the Invention

[0005]

[0005] One aspect provides a method for wireless communication by a user equipment (UE). The method includes receiving, from a network entity, one or more configured grant (CG) configurations each specifying at least one CG opportunity within a data period, obtaining traffic in the form of one or more bursts, and transmitting the traffic to the network entity within a plurality of physical uplink shared channels (PUSCHs) during the data period.

[0006]

[0006] Another aspect provides a method for wireless communication by a network entity. The method includes transmitting, to the UE, one or more CG configurations each specifying at least one CG opportunity within a data period, and monitoring uplink traffic from the UE within a plurality of PUSCHs during the data period.

[0007]

[0007] Another aspect provides an apparatus, a non-transitory computer-readable medium having instructions thereon for causing the apparatus to perform the method described above and the methods described elsewhere in this specification when executed by a processor of the apparatus, a computer program product embodied on a computer-readable storage medium having code for performing the methods described above and the methods described elsewhere in this specification, and / or an apparatus having means for performing the methods described above and the methods described elsewhere in this specification. By way of example, the apparatus may comprise a processing system, a device having the processing system, or a processing system cooperating via one or more networks.

[0008]

[0008] The following description and the accompanying drawings set forth some features by way of illustration.

Brief Description of the Drawings

[0009]

[0009] The accompanying drawings show some features of the various aspects described herein and should not be regarded as limiting the scope of the disclosure.

Figure 1

[0010] A diagram illustrating an exemplary wireless communication network.

Figure 2

[0011] A diagram illustrating an exemplary distributed base station architecture.

Figure 3

[0012] A diagram illustrating aspects of an exemplary base station and an exemplary user equipment.

Figure 4A

[0013] A diagram illustrating various exemplary aspects of data structures for a wireless communication network.

Figure 4B

Figure 4C

Figure 4D

Figure 5

[0014] A diagram showing dynamic scheduling and configured grant (CG) scheduling for uplink (UL) traffic.

Figure 6

[0015] A diagram showing exemplary UL traffic distribution.

Figure 7

[0016] A diagram showing exemplary downlink control information (DCI) supporting multiple consecutive physical uplink shared channels (PUSCHs) per slot.

Figure 8A

[0017] A diagram showing exemplary DCI supporting multiple PUSCHs for single and multiple transmission and reception points (TRPs).

Figure 8B

Figure 9

[0018] An exemplary timing diagram for multiple PUSCH dynamic scheduling for extended reality (XR) traffic.

Figure 10

[0019] A call flow diagram for wireless communication between a UE and a network entity according to aspects of the present disclosure.

Figure 11A

[0020] A diagram showing multiple PUSCH scheduling during a data period for XR traffic according to aspects of the present disclosure.

Figure 11B

Figure 12

[0021] A diagram showing a combination of a configuration grant (CG) and dynamic scheduling for XR traffic according to an aspect of the present disclosure.

Figure 13A - B

[0022] A diagram showing periodic scheduling with multiple configuration grant (CG) opportunities for XR traffic according to an aspect of the present disclosure.

Figure 14

[0023] A diagram showing multiple PUSCH scheduling using wake-up-signaling (WUS) for XR traffic according to an aspect of the present disclosure.

Figure 15

[0024] A table explaining various ways to schedule XR traffic according to an aspect of the present disclosure.

Figure 16

[0025] A diagram showing a method for wireless communication.

Figure 17

[0026] A diagram showing a method for wireless communication.

Figure 18

[0027] A diagram showing aspects of an exemplary communication device.

Figure 19

[0028] A diagram showing aspects of an exemplary communication device.

DETAILED DESCRIPTION OF THE INVENTION

[0010]

[0029] Aspects of the present disclosure provide an apparatus, a method, a processing system, and a computer-readable medium for scheduling resources for uplink (UL) traffic, such as uplink extended reality (XR) scheduling.

[0011]

[0030] XR traffic can be characterized by the mixture of pose and video traffic to or from an XR device (e.g., a headset). Such traffic can be characterized by video frame sizes that change over time and bursty (quasi-periodic) packet arrivals (application jitter) at different latencies.

[0012]

[0031] In current wireless systems (e.g., 5G new radio (NR)), network entities can schedule radio resources periodically via a configured grant (CG). The resources within the CG enable the user equipment (UE) to transmit data to the network entity within a known time frame, eliminating the need for costly control scheduling associated with dynamic resource scheduling and dynamic grants (DGs).

[0013]

[0032] However, 5G support for extended reality and augmented reality (XR / AR) has increased the need for uplink (UL) transmission of burst traffic. As described above, such traffic may have data packets of greatly varying sizes, and each packet may have its own associated latency. As a result, the benefits of latency and cost associated with CG scheduling can be reduced because the periodicity of the CG cannot be configured to optimally transmit burst traffic with unpredictable variability.

[0014]

[0033] Aspects of the present disclosure provide techniques for enhancing CG-based resource scheduling for burst traffic. In some aspects, one or more CG configurations may utilize physical uplink shared channel (PUSCH) transmissions within a CG opportunity to reduce UL transmission overhead. In some aspects, the CG configuration may be implemented with dynamic grant (DG)-based scheduling to efficiently schedule data transmitted between CG opportunities. In some aspects, the CG configuration may utilize a wake-up signal (WUS) to mitigate resource latency (i.e., jitter).

[0015]

[0034] The enhanced CG scheduling methods presented herein can address variability in burst traffic, enabling higher throughput and minimizing latency through increased scheduling flexibility.

[0016] Overview of Wireless Communication Networks

[0035] The techniques and methods described herein can be used in various wireless communication networks. Aspects may be described herein using terms commonly associated with 3G, 4G, and / or 5G wireless technologies, but aspects of the present disclosure may be equally applicable to other communication systems and standards not explicitly recited herein.

[0017]

[0036] FIG. 1 shows an example of a wireless communication network 100 in which aspects described herein can be implemented.

[0018]

[0037] Generally, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). Network entities are generally communication devices and / or communication functions executed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). For example, various functions of the network, as well as various devices associated with and interacting with the network, can be regarded as network entities. Further, the wireless communication network 100 includes terrestrial modes such as terrestrial-based network entities (e.g., BS102) and non-terrestrial modes such as satellites 140 and aircraft 145 that can communicate with other network elements (e.g., terrestrial BS) and user equipment, including onboard network entities (e.g., one or more BSs).

[0019]

[0038] In the illustrated embodiment, the wireless communication network 100 includes a BS102, a UE104, and one or more core networks such as an Evolved Packet Core (EPC) 160 and a 5G Core (5GC) network 190, which interoperate to provide communication services via various communication links including wired and wireless links.

[0020]

[0039] FIG. 1 shows various exemplary UEs 104, which more generally can include a mobile phone, smartphone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA), satellite radio, global positioning system, multimedia device, video device, digital audio player, camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small kitchen appliance, healthcare device, implant, sensor / actuator, display, internet of things (IoT) device, always on (AON) device, edge processing device, or other similar devices. The UE 104 can also more generally be referred to as a mobile device, wireless device, wireless communication device, station, mobile station, subscriber station, mobile subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, remote device, access terminal, mobile terminal, wireless terminal, remote terminal, handset, etc.

[0021]

[0040] The BS 102 wirelessly communicates with the UE 104 via a communication link 120 (e.g., transmits a signal to the UE 104 or receives a signal from the UE 104). The communication link 120 between the BS 102 and the UE 104 can include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the BS 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the BS 102 to the UE 104. The communication link 120 can use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity in various aspects.

[0022]

[0041] BS102 can generally include a NodeB, an enhanced NodeB (eNB), a next generation enhanced NodeB (ng-eNB), a next generation NodeB (gNB or gNodeB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a transmission and reception point, and / or others. Each of the BS102s can provide communication coverage to its respective geographical coverage area 110, and each of the respective geographical coverage areas 110 may be called a cell and may, in some cases, overlap (for example, the small cell 102’ can have a coverage area 110’ that overlaps with the coverage area 110 of the macro cell). The BS can provide communication coverage to, for example, a macro cell (covering a relatively large geographical area), a pico cell (covering a relatively smaller geographical area such as a sports stadium), a femto cell (a relatively smaller geographical area (e.g., a home)), and / or other types of cells.

[0023]

[0042] BS102 is shown in various ways as a single communication device, but BS102 can be implemented in various configurations. For example, one or more components of the base station can be separated. To name a few, it includes a central unit (CU), one or more distributed units (DUs), one or more radio units (RUs), a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS102) can include components located at a single physical location or components located at various physical locations. In an example where the base station includes components located at various physical locations, each of the various components can perform functions such that the various components collectively achieve a function similar to that of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a split radio access network architecture, such as an Open RAN (O-RAN) or a Virtualized RAN (VRAN) architecture. FIG. 2 illustrates and describes an exemplary split base station architecture.

[0024]

[0043] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies such as 3G, 4G, and / or 5G. For example, a BS 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) of the Universal Mobile Telecommunications System (UMTS)) can interface with the EPC 160 via a first backhaul link 132 (e.g., the S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with the 5GC 190 via a second backhaul link 184. The BSs 102 can communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) via a third backhaul link 134 (e.g., the X2 interface) that can be wired or wireless.

[0025]

[0044] Wireless communication network 100 can subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, the subdivision is brought about based on wavelength and frequency, and the frequency may also be referred to as a carrier, sub-carrier, frequency channel, tone, or sub-band. For example, 3GPP currently defines Frequency Range 1 (FR1) as including 410 MHz to 7125 MHz, which is often (interchangeably) referred to as "sub-6 GHz". Similarly, 3GPP currently defines Frequency Range 2 (FR2) as including 24,250 MHz to 52,600 MHz, which may be (interchangeably) referred to as "millimeter wave" ("mmW" or "mm wave"). A base station configured to communicate using the mm wave / sub-mm wave radio frequency band (e.g., an mm wave base station such as BS180) can utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0026]

[0045] The communication link 120 between BS102 and, for example, UE104 can have different bandwidths (e.g., 5, 10, 15, 20, 100, 400, and / or other MHz) and can pass through one or more carriers that can be aggregated in various ways. The carriers may or may not be adjacent to each other. The carrier assignment may also be asymmetric for the DL and UL (e.g., more carriers or fewer carriers may be assigned for the DL than for the UL).

[0027]

[0046] Communication using a higher frequency band may have higher path loss and a shorter range compared to lower frequency communication. Thus, some base stations (e.g., 180 in FIG. 1) can utilize beamforming 182 with UE104 to improve path loss and range. For example, BS180 and UE104 can each include a plurality of antennas such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming. In some cases, BS180 can transmit a beamformed signal to UE104 in one or more transmission directions 182’. UE104 can receive a beamformed signal from BS180 in one or more reception directions 182’’. UE104 can also transmit a beamformed signal to BS180 in one or more transmission directions 182’’. BS180 can also receive a beamformed signal from UE104 in one or more reception directions 182’. Then, BS180 and UE104 can perform beam training to determine the best reception and transmission directions for each of BS180 and UE104. In particular, the transmission and reception directions of BS180 may or may not be the same. Similarly, the transmission and reception directions of UE104 may or may not be the same.

[0028]

[0047] The wireless communication network 100 further includes, for example, a Wi-Fi AP 150 that communicates with Wi-Fi stations (STAs) 152 via a communication link 154 within the 2.4 GHz and / or 5 GHz unlicensed frequency spectrum.

[0029]

[0048] Some UEs 104 can communicate with each other using device - to - device (D2D) communication link 158. D2D communication link 158 can use one or more sidelink channels such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0030]

[0049] The EPC 160 can include various functional components, for example, as shown in the illustrated example, Mobility Management Entity (MME) 162, other MMEs 164, serving gateway 166, Multimedia Broadcast Multicast Service (MBMS) gateway 168, Broadcast Multicast Service Center (BM - SC) 170, and / or Packet Data Network (PDN) gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is a control node that processes signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management.

[0031]

[0050] Generally, user Internet Protocol (IP) packets are transferred through the serving gateway 166, and the serving gateway 166 itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to an IP service 176, which can include, for example, the Internet, an intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming service, and / or other IP services.

[0032]

[0051] The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may function as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS transmission. The MBMS gateway 168 may be used to deliver MBMS traffic to the BS 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a specific service, and / or may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0033]

[0052] 5GC 190 can include various functional components, including an Access and Mobility Management Function (AMF) 192, other AMFs 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may communicate with a Unified Data Management (UDM) 196.

[0034]

[0053] AMF 192 is a control node that processes signaling between the UE 104 and the 5GC 190. AMF 192 provides, for example, quality of service (QoS) flow and session management.

[0035]

[0054] Internet Protocol (IP) packets are transferred via the UPF 195, which is connected to an IP service 197 and provides UE IP address allocation and other functions for the 5GC 190. The IP service 197 can include, for example, the Internet, an intranet, IMS, a PS streaming service, and / or other IP services.

[0036]

[0055] In various aspects, a network entity or network node can be implemented as, by way of example, an aggregated base station, a disaggregated base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, or a sidelink node.

[0037]

[0056] FIG. 2 shows the architecture of an exemplary distributed base station 200. The architecture of the distributed base station 200 can include one or more central units (CUs) 210 that can communicate directly with the core network 220 via a backhaul link or indirectly with the core network 220 via one or more distributed base station units (such as a near-real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both). The CU 210 can communicate with one or more distributed units (DUs) 230 via respective midhaul links such as an F1 interface. The DU 230 can communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UEs 104 can be served simultaneously by multiple RUs 240.

[0038]

[0057] Each of the units, e.g., CU210, DU230, RU240, and also quasi-RT RIC225, non-RT RIC215, and SMO framework 205, includes one or more interfaces configured to receive or transmit signals, data, or information (collectively signals) via a wired or wireless transmission medium, or can be coupled to one or more interfaces. Each of the units, or an associated processor or controller that provides instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, a unit can include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Additionally, or alternatively, a unit can include a wireless interface that includes a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive, transmit, or receive and transmit signals to one or more of the other units via a wireless transmission medium.

[0039]

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

[0040]

[0059] DU230 can correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU240. In some embodiments, DU230 is the 3rd Generation Partnership Project (3 rdAt least partially in response to functional splitting such as that defined by the Generation Partnership Project (3GPP), it is possible to host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules related to forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some aspects, the DU230 can further host one or more lower PHY layers. Each layer (or module) can implement an interface configured to communicate signals with other layers (and modules) hosted by the DU230 or with control functions hosted by the CU210.

[0041]

[0060] The lower layer functions can be implemented by one or more RU240s. In some deployments, the RU240s controlled by the DU230 can correspond to logical nodes that host the RF processing function, or the lower 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, at least partially based on function splitting such as lower layer function splitting. In such an architecture, the RU(s) 240 can be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some implementations, the real-time and non-real-time aspects of control and user plane communication with the RU(s) 240 can be controlled by the corresponding DU230. In some scenarios, this configuration can enable the DU(s) 230 and the CU210 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0042]

[0061] The SMO framework 205 can be configured to support the RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. In the case of non-virtualized network elements, the SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements that are managed via an operation and maintenance interface (such as an O1 interface). In the case of virtualized network elements, the SMO framework 205 can be configured to interact with a cloud computing platform (such as an Open Cloud (O-Cloud) 290) 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 can include, but are not limited to, a CU 210, a DU 230, an RU 240, and a quasi-RT RIC 225. In some implementations, the SMO framework 205 can communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 211, via an O1 interface. Additionally, in some implementations, the SMO framework 205 can communicate directly with one or more RUs 240 via an O1 interface. The SMO framework 205 can also include a non-RT RIC 215 that is configured to support the functions of the SMO framework 205.

[0043]

[0062] The non-RT RIC 215 can be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, an artificial intelligence / machine learning (AI / ML) workflow including model training and updating, or policy-based guidance of applications / features in the quasi-RT RIC 225. The non-RT RIC 215 may be coupled to the quasi-RT RIC 225 or communicate with the quasi-RT RIC 225 (e.g., via an A1 interface). The quasi-RT RIC 225 can be configured to include a logical function that enables quasi-real-time control and optimization of RAN elements and resources via data collection and actions (e.g., via an E2 interface) through one or more CU 210, one or more DU 230, or both, and an interface connecting the O-eNB to the quasi-RT RIC 225.

[0044]

[0063] In some implementations, the non-RT RIC 215 may receive parameters or external enrichment information from an external server to generate an AI / ML model deployed in the quasi-RT RIC 225. Such information may be utilized by the quasi-RT RIC 225 and may be received from a non-network data source or a network function, in the SMO framework 205 or in the non-RT RIC 215. In some examples, the non-RT RIC 215 or the quasi-RT RIC 225 can be configured to adjust RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns regarding performance and employ an AI / ML model to execute corrective measures via the SMO framework 205 (such as reconfiguration via O1) or via the creation of RAN management policies (such as A1 policies).

[0045]

[0064] FIG. 3 shows exemplary aspects of the BS 102 and the UE 104.

[0046]

[0065] Generally, BS102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a - t (collectively 334), transceivers 332a - t (collectively 332) including modulators and demodulators, and other aspects enabling wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS102 can transmit and receive data between BS102 and UE104. BS102 includes a controller / processor 340 configured to implement various functions described herein related to wireless communication.

[0047]

[0066] Generally, UE104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a - r (collectively 352), transceivers 354a - r (collectively 354) including modulators and demodulators, and other aspects enabling wireless transmission of data (e.g., received from data source 362) and wireless reception of data (e.g., provided to data sink 360). UE104 includes a controller / processor 380 configured to implement various functions described herein related to wireless communication.

[0048]

[0067] Regarding exemplary downlink transmission, BS102 includes a transmission processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0049]

[0068] The transmission processor 320 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols respectively. The transmission processor 320 can also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0050]

[0069] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., precoding) on data symbols, control symbols, and / or reference symbols when applicable, and can provide an output symbol stream to the modulators (MODs) within the transceivers 332a - 332t. Each modulator within the transceivers 332a - 332t can process its respective output symbol stream to obtain an output sample stream. Each modulator can further process the output sample stream (e.g., convert to analog, amplify, filter, and upconvert) to obtain a downlink signal. The downlink signals from the modulators within the transceivers 332a - 332t can be transmitted via each of the antennas 334a - 334t.

[0051]

[0070] To receive downlink transmissions, the UE 104 includes antennas 352a - 352r that can receive downlink signals from the BS 102 and can each provide the received signal to a demodulator (DEMOD) within the transceivers 354a - 354r. Each demodulator within the transceivers 354a - 354r can condition (e.g., filter, amplify, downconvert, and digitize) its respective received signal to obtain input samples. Each demodulator may further process the input samples to obtain received symbols.

[0052]

[0071] The MIMO detector 356 can obtain received symbols from all the demodulators within the transceivers 354a - 354r, perform MIMO detection on the received symbols when applicable, and provide the detected symbols. The receive processor 358 can process the detected symbols (e.g., demodulate, deinterleave, and decode), provide the decoded data for the UE 104 to the data sink 360, and provide the decoded control information to the controller / processor 380.

[0053]

[0072] Regarding exemplary uplink transmission, the UE 104 may further include a transmission processor 364 that can receive and process data from a data source 362 (e.g., for PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmission processor 364 can also generate reference symbols for a reference signal (e.g., for a sounding reference signal (SRS)). Symbols from the transmission processor 364 can be precoded by a TX MIMO processor 366, if applicable, and further processed by a modulator in transceivers 354a - 354r (e.g., for SC-FDM) and transmitted to the BS 102.

[0054]

[0073] At the BS 102, an uplink signal from the UE 104 is received by antennas 334a - t, processed by a demodulator in transceivers 332a - 332t, detected by an MIMO detector 336, if applicable, and further processed by a receiving processor 338 to obtain the decoded data and control information transmitted by the UE 104. The receiving processor 338 can provide the decoded data to a data sink 339 and the decoded control information to a controller / processor 340.

[0055]

[0074] Memories 342 and 382 may store data and program codes for the BS 102 and the UE 104, respectively.

[0056]

[0075] A scheduler 344 can schedule the UE for data transmission on the downlink and / or uplink.

[0057]

[0076] In various aspects, BS102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms for outputting data, such as outputting data from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a - t, antennas 334a - t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms for acquiring data, such as acquiring data from antennas 334a - t, transceivers 332a - t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0058]

[0077] In various aspects, UE104 can similarly be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, "transmitting" can refer to various mechanisms for outputting data, such as outputting data from data source 362, memory 382, transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a - t, antennas 352a - t, and / or other aspects described herein. Similarly, "receiving" can refer to various mechanisms for acquiring data, such as acquiring data from antennas 352a - t, transceivers 354a - t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, and / or other aspects described herein.

[0059]

[0078] In some aspects, a processor can be configured to perform various operations, such as operations associated with the methods described herein, and to transmit (output) data to or receive (acquire) data from another interface configured to respectively transmit or receive the data.

[0060]

[0079] FIGS. 4A, 4B, 4C, and 4D illustrate aspects of data structures for a wireless communication network, such as the wireless communication network 100 of FIG. 1.

[0061]

[0080] In particular, FIG. 4A is a diagram 400 showing an example of a first subframe within a 5G (e.g., 5G NR) frame structure, FIG. 4B is a diagram 430 showing an example of a DL channel within a 5G subframe, FIG. 4C is a diagram 450 showing an example of a second subframe within a 5G frame structure, and FIG. 4D is a diagram 480 showing an example of a UL channel within a 5G subframe.

[0062]

[0081] A wireless communication system can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such a system can also support half-duplex operation using time division duplexing (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) divide the system bandwidth into a plurality of orthogonal subcarriers (e.g., as shown in FIGS. 4B and 4D). Each subcarrier can be modulated with data. Modulation symbols can be transmitted using OFDM in the frequency domain and / or SC-FDM in the time domain.

[0063]

[0082] The wireless communication frame structure can be frequency division duplexing (FDD) in which, for a particular set of subcarriers, the subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure can also be time division duplexing (TDD) in which, for a particular set of subcarriers, the subframes within the set of subcarriers are dedicated to both DL and UL.

[0064]

[0083] In FIGS. 4A and 4C, the wireless communication frame structure is TDD, D is DL, U is UL, and X is flexible for use between DL / UL. The UE can be configured with a slot format via the received slot format indicator (SFI) (dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling). In the illustrated example, a 10 ms frame is divided into 10 equal-sized 1 ms subframes. Each subframe may include one or more time slots. In some examples, each slot may include 7 or 14 symbols depending on the slot format. A subframe may also include minislots having fewer symbols than the entire slot in general. Other wireless communication technologies may have different frame structures and / or different channels.

[0065]

[0084] In some aspects, the number of slots in a subframe is based on the slot configuration and numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 5 allow 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different numerologies 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the numerology. The subcarrier spacing is 2 μIt may be equal to ×15 kHz, where μ is a numerology from 0 to 5. Therefore, numerology μ = 0 has a subcarrier spacing of 15 kHz, and numerology μ = 5 has a subcarrier spacing of 480 kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. FIGS. 4A, 4B, 4C, and 4D provide an example of slot configuration 0 with 14 symbols per slot and numerology μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0066]

[0085] As shown in FIGS. 4A, 4B, 4C, and 4D, a resource grid can be used to represent the frame structure. Each time slot includes resource blocks (RBs) (also called physical RBs (PRBs)) that extend, for example, over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0067]

[0086] As shown in FIG. 4A, some of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 104 in FIGS. 1 and 3). The RS may include demodulation RS (DMRS) and / or channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).

[0068]

[0087] Figure 4B shows an example of various DL channels within a subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more control channel elements (CCEs), where each CCE includes, for example, nine resource element groups (REGs), and each REG includes, for example, four consecutive resource elements within an OFDM symbol.

[0069]

[0088] The Primary Synchronization Signal (PSS) may be present within symbol 2 of a specific subframe of a frame. The PSS is used by a UE (e.g., 104 in FIGS. 1 and 3) to determine subframe / symbol timing and physical layer identification information.

[0070]

[0089] The Secondary Synchronization Signal (SSS) may be present within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the group number of the physical layer cell identification information and the timing of the radio frame.

[0071]

[0090] Based on the physical layer identification information and the group number of the physical layer cell identification information, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the position of the above-mentioned DMRS. The Physical Broadcast Channel (PBCH) that carries the Master Information Block (MIB) may be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of resource blocks (RBs) within the system bandwidth and the system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH such as system information blocks (SIBs), and / or paging messages.

[0072]

[0091] As shown in Figure 4C, some of the REs carry DMRS for channel estimation at the base station (shown as R for one particular configuration, although other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS can be transmitted, for example, within the first one or two symbols of the PUSCH. The PUCCH DMRS can be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used. The UE104 can transmit a sounding reference signal (SRS). The SRS can be transmitted, for example, within the last symbol of the subframe. The SRS can have a comb configuration and the UE can transmit the SRS with one of those combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0073]

[0092] Figure 4D shows an example of various UL channels within a subframe of a frame. The PUCCH can be arranged as shown in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0074] Aspects regarding scheduling resources for UL XR

[0093] The enhanced CG scheduling method presented herein can address variability in burst traffic, enable higher throughput through increased scheduling flexibility, and minimize latency.

[0075]

[0094] As described above, in a particular wireless communication system (e.g., a 5G NR wireless communication network), the network may configure a UE using periodic uplink resources via a configured grant (CG). The CG may reduce latency and resource overhead associated with dynamic resource scheduling via a dynamic grant (DG) transmitted via downlink control information (DCI) within a physical downlink control channel (PDCCH).

[0076]

[0095] FIG. 5 shows both dynamic grant (DG) scheduling and CG scheduling. The DG may require that the PDCCH schedule a physical uplink shared channel (PUSCH) transmission. Therefore, DG-based scheduling may result in additional packet transmission delay and increased resource usage. In contrast, uplink resources scheduled via the CG occur periodically (referred to as CG opportunities) without requiring control signaling, eliminating the costs and delays associated with the DG.

[0077]

[0096] CG parameters are typically configured via RRC signaling, and grant activation is via RRC or L1 signaling. Typically, the periodicity and configuration parameters (e.g., the number of resource blocks (RBs), modulation and coding scheme (MCS), number of repetitions) are the same for all CG opportunities within a CG configuration.

[0078]

[0097] Conventional CG-scheduled uplink resource allocation may not be optimal for certain types of uplink traffic, such as extended reality (XR) and augmented reality (AR) related traffic. In XR use cases, as shown in the top timeline of FIG. 6, certain types of uplink data (e.g., 3D estimation of human body postures, or essential “Pose” data) can be generated periodically. When the CG configuration matches the periodicity of data arrival, such as CG Config 1 shown in FIG. 6, the CG resources may be well-suited for the delivery of UL traffic.

[0079]

[0098] However, other types of traffic, such as AR traffic (e.g., video or other media) traffic, as shown in the third timeline of FIG. 6, can have widely varying packet sizes and transmission delays. The variability in both the number of packets per burst and the size of each packet within the burst can effectively render the latency benefits of CG scheduling meaningless. For example, packets from one or more AR traffic bursts may require more UL resources than are allocated within the first CG opportunity period. As a result, according to some CG configurations, as shown in the fourth timeline of FIG. 6 for CG Config 2, some of the AR traffic will be delayed until the next CG opportunity.

[0080]

[0099] In some cases, AR and XR traffic may also be transmitted within multiple traffic flows (streams) and may be configured with variable parameters and characteristics, which presents additional challenges for the resources to be CG scheduled. In some cases, the CG scheduling configuration may become unable to meet the data transmission requirements of multi-flow AR / XR traffic. In some cases, packets from one or more traffic bursts may have a periodicity that does not match the periodicity of the CG opportunities. As a result, an AR traffic burst that falls outside of the CG opportunities within a CG period may be delayed until the next CG period. This delay may continue as long as the traffic and the CG period do not match. In some cases, the resources for actual traffic transmission may not be synchronized with the resources for transmission scheduled via CG, resulting in transmission jitter. UL jitter may be caused by encoding delay in the UE. Jitter may also cause latency in UL transmissions that cannot be easily corrected using periodic scheduling.

[0081]

[0100] In some cases, as shown in FIG. 7, a dynamic grant may be used to schedule multiple PUSCHs (using a single DCI). The DCI in FIG. 7 may address specific variability associated with bursty traffic (e.g., AR / XR traffic). For example, a UL burst having a long channel occupancy time (COT) may be scheduled on multiple consecutive PUSCHs over multiple slots / minislots by a single DCI. As a result, fewer instances of costly control signaling required by the UL burst may be sufficient. In such cases, each transmission block (TB) may be mapped to one slot or one minislot. The PUSCHs in FIG. 7 may have different lengths but are adjacent in the time domain and may share most parameters except for the hybrid automatic repeat request (HARQ) process identifier, redundancy version ID (RVID), new data indicator (NDI), and time domain resource allocation (TDRA).

[0082]

[0101] As shown in FIG. 8A, in some cases, a single DCI may schedule multiple PUSCHs within a single slot. In some cases, gaps between adjacent PUSCHs may be allowed, and there may be no maximum gap limit (except for those derived from RRC parameters). The TDRA may indicate PUSCHs in consecutive or non-consecutive slots by configuring, for each PUSCH within a row of the TDRA table, a start and length indicator value (SLIV), a mapping type, and a scheduling offset (e.g., K0 or K2). As shown in FIG. 8B, depending on the UE's capabilities, there may be one TB per slot in a single transmission and reception point (TRP) configuration, and one TB per TRP in a multiple TRP configuration.

[0083]

[0102] In one example, a single DCI of DCI format DCI0_1 may schedule multiple PUSCHs. In this case, the frequency domain resource allocation (FDRA), MCS, scheduling request indicator (SRI), number of layers, precoding, antenna port, and open loop power control are not changed and are applied to all scheduled PUSCHs. A new TDRA table supporting multiple SLIVs (up to 8) may be defined. Discontinuous SLIVs are also supported. This format may have 1 bit of NDI per TB and 1 bit of RVID per TB (e.g., between RVID 0 and 2) when multiple TBs are scheduled, or 2 bits when only one PUSCH is scheduled. The HARQ ID may be applied to the first scheduled PUSCH. Each additional scheduled PUSCH may have an incremented HARQ ID.

[0084]

[0103] In some cases, a single DCI that schedules multiple PUSCHs can be used to increase the efficiency for AR / XR scheduling. As shown in FIG. 9, different bursts can arrive within different periods. In the illustrated example, bursts 1 to 3 arrive within one data period, while burst 4 arrives within another period. As shown, the UE may request uplink resources for transmitting bursts 1 to 3 via the first SR. In response, the network may send a DCI that schedules multiple PUSCHs (via the PDCCH), enabling the transmission of bursts 1 to 3. As shown, only one scheduling request (SR) and one PDCCH may be required to transmit bursts 1 to 3, reducing the overall control signaling requirements associated with the XR traffic included in a single XR data period. In this example, burst 4 arrives after the first XR data period and thus requires an additional SR and a DL grant (for just that single burst).

[0085]

[0104] Often, the packet size and the number of packets per burst can vary. In such cases, the SR can be a request for resources that includes parameters (e.g., the number of PUSCHs, MCS). For XR, the MCS can vary to accommodate varying packet sizes.

[0086]

[0105] Aspects of the present disclosure provide techniques for enhancing CG scheduling for burst traffic (e.g., AR and XR traffic). In some aspects, one or more CG configurations may enable multiple PUSCH transmissions within a CG opportunity to reduce UL transmission overhead. In some aspects, CG and DG scheduling may be combined to efficiently schedule uplink traffic. In some aspects, a CG configuration may be combined with a wake-up signal (WUS) to reduce jitter of arriving packets. As described above, the enhanced CG scheduling techniques proposed herein can address variability in AR / XR traffic, enable higher throughput, and minimize latency through increased scheduling flexibility.

[0087]

[0106] The CG scheduling techniques proposed herein can be understood with reference to the call flow diagram 1000 of FIG. 10, which illustrates the scheduling of uplink traffic from UE 1002 to network entity 1004. In some aspects, network entity 1002 may be an embodiment of BS 102 illustrated and described with respect to FIGS. 1 and 3, or a separate base station illustrated and described with respect to FIG. 2. Similarly, UE 1004 may be an embodiment of UE 104 illustrated and described with respect to FIGS. 1 and 3. However, in other aspects, UE 104 may be another type of wireless communication device, and BS 102 may be another type of network entity or network node, such as those described herein.

[0088]

[0107] At 1006, the network entity configures the UE using one or more CG configurations, each defining at least one CG opportunity within data period 1014. At 1008, the UE obtains (e.g., periodic uplink) traffic in the form of one or more bursts (e.g., XR traffic such as pose and AR traffic). As shown, the UE transmits uplink traffic within multiple PUSCHs during the data period based on the configuration (as monitored by the network entity).

[0089]

[0108] According to certain aspects, one or more CG configurations (configured at 1006 in FIG. 10) may have multiple PUSCHs per CG opportunity, as described above. In such cases, as shown in FIG. 11A, when one or more data bursts arrive at the UE, the UE may transmit the data bursts within the multiple PUSCHs of the first CG opportunity. In some cases, the UE may be configured to have a maximum number M of PUSCHs per CG opportunity. In some cases, the pre - configuration of various parameters (e.g., MCS, number of RBs, etc.) may vary between PUSCHs. If there is little or no jitter, the network entity may place the CG opportunity near the first arriving packet. Thus, the UE may transmit the packet within the first PUSCH.

[0090]

[0109] In some cases, the UE may send an indicator (a "skip indicator") to inform the network entity when it does not intend to use all PUSCHs within a CG opportunity, whereby the network entity may skip monitoring one or more future PUSCHs. The UE may send this indicator before sending the scheduled skipped PUSCH, taking into account the network entity processing time. In some cases, the indicator may indicate to the network entity the end of a burst for a cycle.

[0091]

[0110] In the example shown in FIG. 11A, the UE does not plan to use PUSCH M-1 and M. The UE sends an indicator within PUSCH3 of CG opportunity 1, enabling the network entity to skip monitoring for these PUSCHs. If the UE does not send a skip indicator (e.g., for PUSCH of CG opportunity 2), the network entity may monitor up to the maximum number M of PUSCHs. In some cases, the indicator may indicate that more PUSCHs (e.g., PUSCH > M) than those initially activated can be used within the CG configuration. This extended PUSCH indicator may be preconfigured by the network entity.

[0092]

[0111] In some cases, requests for parameter changes for future PUSCHs may be piggybacked on such an indicator. Parameter changes may include changes to CG parameters (e.g., MCS, number of RBs, number of PUSCHs per CG opportunity, etc.) within the same CG opportunity, the next CG opportunity, or a group of CG opportunities. The UE may use sequence-based signaling (e.g., demodulation reference signaling (DMRS)), PDCCH (e.g., DCI), or PUSCH (e.g., media access control (MAC) control element (CE)) to send requests for parameter changes on the indicator.

[0093]

[0112] FIG. 11B shows a comparison between DG-based scheduling and scheduling using multiple PUSCH CG configurations. In the second timeline of FIG. 11B, a single DCI PUSCH reduces latency for the first three traffic bursts by resolving control signaling for each PUSCH. In the third timeline, multiple PUSCH CG configurations further reduce latency by completely resolving the control signaling.

[0094]

[0113] According to certain aspects, one or more CG configurations transmitted by a network entity may be configured using multiple PUSCHs and may be transmitted together with a DG configuration. In many cases, the DG configuration implemented together with the CG configuration may further reduce the latency for retransmission.

[0095]

[0114] Figure 12 shows the scheduling of UL data transmission using a combination of DG and CG scheduling. In the first timeline of Figure 12, XR data traffic arrives in the form of bursts (i.e., bursts 1 to 4).

[0096]

[0115] The second timeline of Figure 12 shows DG-based scheduling that a UE may use to transmit bursts 1 to 4 to a network entity. In this case, control signaling (SR, PDCCH) is required for each burst, increasing latency and resource usage compared to other scheduling methods.

[0097]

[0116] The third timeline of Figure 12 shows periodic resource scheduling that a UE may use to transmit bursts 1 to 4 to a network entity. In this case, the first CG opportunity may only transmit burst 1. The UE has to wait until the start of the second CG period to transmit bursts 2 and 3 within the second CG opportunity and until the start of the third CG period to transmit burst 4 within the third CG opportunity. Therefore, transmitting XR traffic only on CG-configured resources can be particularly inefficient in terms of latency.

[0098]

[0117] The fourth timeline in Figure 12 shows composite CG and DG-based resource scheduling. In this case, burst 1 is sent within the first CG opportunity. However, instead of waiting for the second CG opportunity, the UE sends an SR to request resources, receives DG, and enables bursts 2 and 3 to be sent earlier. This enables burst 4 to be sent within the second CG opportunity instead of waiting until the third CG opportunity. This composite scheduling scheme successfully achieves a balance as it reduces control signaling compared to a pure dynamic scheduling configuration and reduces latency compared to a pure periodic scheduling configuration.

[0099]

[0118] As shown in the fifth timeline of Figure 12, when using a composite CG and DG-based resource scheduling scheme, the UE may also utilize an additional data indicator. The additional data indicator may inform a network entity that the UE has additional uplink data and may use additional PUSCH resources. Therefore, the additional data indicator may effectively eliminate the need for separate SR transmissions. In other words, after detecting the additional data indicator, the network entity may send a PDCCH using a dynamic grant without waiting for an SR from the UE. As a result, control signaling and latency may be further reduced.

[0100]

[0119] In some cases, the UE may send an (skip and / or additional data) indicator via sequence-based signaling (e.g., DMRS) or via PUSCH (e.g., MAC CE). In some cases, the DMRS pattern may indicate different resource allocations. In some cases, the PUSCH-based indicator may allow for a larger indicator payload. In some cases, if there is uplink control information (UCI) that is sent before resources are needed, the indicator may be PUCCH-based.

[0101]

[0120] According to certain aspects, a network entity may configure a UE using multiple (different) CG configurations. In some cases, the network entity may activate multiple such CG configurations. As a result, even if the CG period of each CG configuration may have only one CG opportunity, for example, the UE may transmit burst traffic within multiple CG opportunities included in a single data period.

[0102]

[0121] As shown in FIG. 13A, when one or more data bursts (i.e., bursts 1-3) arrive at the UE, the UE may transmit burst 1 within the first available CG opportunity (according to CG Config 1) within the data period. The UE may transmit bursts 2 and 3 within the second CG opportunity (according to CG Config 2) of the first data period. Within the second data period, the second, larger burst may be sent within the CG opportunities of all three CG configurations. This approach may reduce latency by increasing the amount of transmission resources available to the UE during the data period, while eliminating the need for control signaling associated with dynamic signaling.

[0103]

[0122] As shown in the timeline in Figure 13B, when configured using multiple CG configurations, the UE may send a skip indicator to inform the network entity that it may skip monitoring one or more CG opportunities. Since one or more future CG opportunities are often empty at the time of transmission, this may help save resources. As described above, the UE may send this indicator before sending the skipped CG opportunities, taking into account the network entity processing time. In the illustrated example, the UE sends a skip indicator within the CG opportunity of CG Config 2, indicating that it intends to skip the CG opportunity of CG Config 3. If the UE does not send a skip indicator, the network entity may monitor all of the configured CG opportunities. In some cases, the indicator may indicate that more CG opportunities than those initially activated may be used within the CG configuration. This extended CG opportunity indicator may be preconfigured by the network entity.

[0104]

[0123] According to certain aspects, a wake-up signal (WUS) may be sent by the UE to bring the CG opportunity closer to the start of the data period. The WUS may indicate to the network that the UE has data, and the network may adjust the period accordingly. Thus, WUS transmission may correct the latency associated with jitter. In some cases, the WUS may reduce power consumption compared to dynamic grant-based transmission.

[0105]

[0124] Figure 14 shows the WUS-based CG configuration (in the 4th timeline). The first three timelines in Figure 14 faithfully replicate the first three timelines in Figure 12 and are provided for comparison. In row 4 of Figure 14, the UE transmits WUS to the network entity at the start of the data period. Although jitter cannot be predicted on the UL, in case of necessity, WUS-based CG can be used to effectively bring the CG opportunity closer to the data arrival in order to minimize latency. The UE may have a window given to transmit the CG (in accordance with the CG), and thus, the gNB can monitor for WUS during this window. In some cases, WUS may be sequence-based in order to reduce power consumption. In some cases, parameter changes for future CG opportunities can be piggybacked on WUS. The UE can transmit WUS using sequence-based signaling (e.g., demodulation reference signaling (DMRS)), PDCCH (e.g., DCI), UCI, or PUSCH (e.g., medium access control (MAC) control element (CE)).

[0106]

[0125] Figure 15 is a table summarizing various parameters associated with various scheduling methods, including the enhanced scheduling method proposed herein. The first column indicates the scheduling method, the second column indicates the maximum number or SR / WUS signal, the third column indicates the maximum number of PDCCH, while the fourth column indicates the maximum number of PUSCH. The fifth column indicates the maximum number of blind PUSCH decoding (performed at the network entity), the sixth column indicates the latency for the scheduling method, while the seventh column indicates the power consumption for each scheduling method. In the table, "M" defines the maximum number of WUS within the network entity monitoring window for each configuration. "N" defines the number of packets that can be transmitted per data period. "D" defines the number of PUSCH that can be implemented within multiple PUSCH configurations. "S" defines the number of configured CG configurations. The relationship between M, N, D, and S may depend on the traffic type and UE capabilities.

[0107]

[0126] As described by FIG. 15, the enhanced UL resource scheduling technique implemented in accordance with the aspects of the present disclosure reduces latency and decreases power consumption for UL burst traffic. Specifically, the table shows how, by using the enhanced technique proposed herein, the number of SR and PDCCH transmissions, while incurring a cost (in some cases) with respect to the number of blind decodes in the network entity, is reduced (or eliminated) with a corresponding reduction in latency.

[0108] Exemplary operation of a user equipment

[0127] FIG. 16 shows a method 1600 for wireless communication by a UE, such as UE 104 of FIGS. 1 and 3.

[0109]

[0128] Method 1600 begins at step 1605 of receiving, from a network entity, one or more CG configurations each defining at least one CG opportunity within a data period. In some cases, the operation of this step may refer to or be performed by a receiving circuit and / or receiving code as described with reference to FIG. 18.

[0110]

[0129] Next, method 1600 proceeds to step 1610 of obtaining traffic in the form of one or more bursts (e.g., periodic uplink). In some cases, the operation of this step may refer to or be performed by an obtaining circuit and / or obtaining code as described with reference to FIG. 18.

[0111]

[0130] Next, method 1600 proceeds to step 1615 of transmitting the traffic to the network entity within a plurality of PUSCHs during the data period. In some cases, the operation of this step may refer to or be performed by a transmitting circuit and / or transmitting code as described with reference to FIG. 18.

[0112]

[0131] In some aspects, one or more CG configurations indicate the maximum number of PUSCHs per CG opportunity.

[0113]

[0132] In some aspects, one or more CG configurations also indicate CG parameters for each of the PUSCHs.

[0114]

[0133] In some aspects, at least some of the transmission parameters vary between PUSCHs within a CG opportunity or between different CG opportunities within a data period.

[0115]

[0134] In some aspects, method 1600 further includes the UE transmitting an indication that it does not intend to use all of the maximum number of PUSCHs within a CG opportunity. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0116]

[0135] In some aspects, method 1600 further includes transmitting an indication of at least one of a change in one or more CG parameters for one or more subsequent PUSCHs or a request for a change in one or more CG parameters for one or more subsequent PUSCHs. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0117]

[0136] In some aspects, the request is for a change in one or more CG parameters for one or more subsequent PUSCHs within the same CG opportunity, a subsequent CG opportunity, or a group of subsequent CG opportunities.

[0118]

[0137] In some aspects, the change or request for change is indicated via at least one of sequenced-based signaling, UCI, or MAC-CE.

[0119]

[0138] In some aspects, method 1600 further includes the UE transmitting an indication that it intends to use more PUSCHs than the maximum number within a CG opportunity. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0120]

[0139] In some aspects, transmitting traffic to a network entity within a plurality of PUSCHs during a data period includes transmitting one or more PUSCHs within at least one CG opportunity and transmitting one or more PUSCHs scheduled via one or more dynamic grants.

[0121]

[0140] In some aspects, method 1600 further includes transmitting at least one SR, with at least one of the dynamic grants being sent in response to the SR. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0122]

[0141] In some aspects, method 1600 further includes transmitting an additional data indication that triggers a preconfigured PUSCH resource. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0123]

[0142] In some aspects, method 1600 further includes transmitting a PUSCH on at least a portion of the preconfigured PUSCH resources. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0124]

[0143] In some aspects, method 1600 further includes transmitting an indication indicating the end of one of the data bursts within one of the PUSCHs. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0125]

[0144] In some aspects, method 1600 further includes transmitting an additional data indication within one of the PUSCHs, and at least one of the dynamic grants is sent in response to the additional data indication. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0126]

[0145] In some aspects, the additional data indicator is transmitted via at least one of DMRS, MAC-CE, or UCI.

[0127]

[0146] In some aspects, one or more CG configurations include a plurality of CG configurations each having at least one associated CG opportunity within a data period.

[0128]

[0147] In some aspects, transmitting traffic to a network entity within a plurality of PUSCHs during a data period includes transmitting the traffic within a plurality of CG opportunities each associated with one of the plurality of CG configurations.

[0129]

[0148] In some aspects, method 1600 further includes transmitting an additional data indication indicating that the UE is scheduled to use at least one CG opportunity or CG configuration during a data period. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0130]

[0149] In some aspects, the additional data indicator also indicates a modification of one or more CG parameters.

[0131]

[0150] In some aspects, method 1600 further includes the UE transmitting an indication that it does not intend to use at least one CG opportunity or CG configuration during a data period. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0132]

[0151] In some aspects, the indication is transmitted via at least one of sequence-based signaling, UCI, PUSCH, or MAC-CE.

[0133]

[0152] In some aspects, method 1600 further includes the UE transmitting a WUS to a network entity to indicate that the UE actually intends to use at least one CG opportunity during a data period at the start of the data period. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 18.

[0134]

[0153] In some aspects, the WUS is transmitted at a fixed offset from the first PUSCH transmitted by the UE.

[0135]

[0154] In some aspects, the WUS also indicates a modification of one or more CG parameters.

[0136]

[0155] In some aspects, the WUS is transmitted via at least one of sequence-based signaling, UCI, or MAC-CE.

[0137]

[0156] In one aspect, method 1600, or any aspect related thereto, may be performed by an apparatus such as communication device 1800 of FIG. 18, including various components configured, arranged, or adapted to operate to perform method 1600. Communication device 1800 will be described in further detail below.

[0138]

[0157] Note that FIG. 16 is merely an example of a method, and other methods including fewer, additional, or alternative steps may be possible consistent with the present disclosure.

[0139] Exemplary Operations of Network Entities

[0158] FIG. 17 shows a method 1700 for wireless communication by a network entity, such as BS 102 of FIGS. 1 and 3, or a distributed base station as described with respect to FIG. 2.

[0140]

[0159] Method 1700 begins at step 1705 of transmitting one or more CG configurations to a UE, each defining at least one CG opportunity within a data period. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 19.

[0141]

[0160] Method 1700 then proceeds to step 1710 of monitoring for uplink traffic from the UE within a plurality of PUSCHs during the data period. In some cases, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0142]

[0161] In some aspects, one or more CG configurations indicate a maximum number of PUSCHs per CG opportunity.

[0143]

[0162] In some aspects, one or more CG configurations also indicate CG parameters for each of the PUSCHs.

[0144]

[0163] In some aspects, at least some of the CG parameters change during PUSCH within a CG opportunity or between different CG opportunities within a data period.

[0145]

[0164] In some aspects, method 1700 further includes the UE receiving an indication that it is not intended to use all of the maximum number of PUSCH within a CG opportunity. In some cases, the operation of this step may refer to or be performed by a receiving circuit and / or receiving code as described with reference to FIG. 19.

[0146]

[0165] In some aspects, method 1700 further includes monitoring for an indication of at least one of a change in one or more CG parameters for one or more subsequent PUSCH or a request for a change in one or more CG parameters for one or more subsequent PUSCH. In some cases, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0147]

[0166] In some aspects, the request is for a change in one or more CG parameters for one or more subsequent PUSCH within the same CG opportunity, a subsequent CG opportunity, or a group of subsequent CG opportunities.

[0148]

[0167] In some aspects, the change or request for change is indicated via at least one of sequence-based signaling, UCI, or MAC-CE.

[0149]

[0168] In some aspects, method 1700 further includes the UE monitoring for an indication that it is intended to use more than the maximum number of PUSCH within a CG opportunity. In some cases, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0150]

[0169] In some aspects, monitoring uplink traffic from a UE within a plurality of PUSCHs during a data period includes monitoring one or more PUSCHs within at least one CG opportunity and monitoring one or more PUSCHs scheduled via one or more dynamic grants.

[0151]

[0170] In some aspects, method 1700 further includes monitoring at least one SR. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0152]

[0171] In some aspects, method 1700 further includes transmitting at least one of the dynamic grants in response to at least one SR. In some cases, the operation of this step may refer to or be performed by a transmission circuit and / or transmission code as described with reference to FIG. 19.

[0153]

[0172] In some aspects, method 1700 further includes monitoring an additional data indication that triggers a preconfigured PUSCH resource. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0154]

[0173] In some aspects, method 1700 further includes monitoring a PUSCH on at least a portion of the preconfigured PUSCH resources. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0155]

[0174] In some aspects, method 1700 further includes monitoring for an indication within one of the PUSCHs that indicates the end of one of the data bursts. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0156]

[0175] In some aspects, method 1700 further includes monitoring for an additional data indication within one of the PUSCHs, and at least one of the dynamic grants is sent in response to the additional data indication. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0157]

[0176] In some aspects, the additional data indicator is transmitted via at least one of DMRS, MAC-CE, or UCI.

[0158]

[0177] In some aspects, one or more CG configurations include a plurality of CG configurations, each having at least one associated CG opportunity during a data period.

[0159]

[0178] In some aspects, monitoring for uplink traffic from the UE in a plurality of PUSCHs during a data period includes monitoring for traffic within a plurality of CG opportunities, each associated with one of the plurality of CG configurations.

[0160]

[0179] In some aspects, method 1700 further includes monitoring for an additional data indication that indicates that the UE intends to use at least one CG opportunity or CG configuration during a data period. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0161]

[0180] In some aspects, the additional data indicator also indicates a modification of one or more CG parameters.

[0162]

[0181] In some aspects, method 1700 further includes the UE monitoring for an indication that the UE does not intend to use at least one CG opportunity or CG configuration during a data period. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0163]

[0182] In some aspects, the indication is transmitted via at least one of sequence-based signaling, UCI, PUSCH, or MAC-CE.

[0164]

[0183] In some aspects, method 1700 further includes the UE monitoring for a WUS from the UE to indicate that the UE actually intends to use at least one CG opportunity during the data period at the start of the data period. Optionally, the operation of this step may refer to or be performed by a monitoring circuit and / or monitoring code as described with reference to FIG. 19.

[0165]

[0184] In some aspects, the WUS also indicates a modification of one or more CG parameters.

[0166]

[0185] In some aspects, the WUS is transmitted at a fixed offset from the first PUSCH transmitted by the UE.

[0167]

[0186] In some aspects, the WUS is transmitted via at least one of sequence-based signaling, UCI, or MAC-CE.

[0168]

[0187] In one aspect, method 1700, or any aspect related thereto, may be performed by an apparatus such as communication device 1900 of FIG. 19, which includes various components configured, arranged, or adapted to operate so as to perform method 1700. Communication device 1900 will be described in more detail below.

[0169]

[0188] Note that FIG. 17 is only an example of a method, and other methods including fewer, additional, or alternative steps are possible consistent with the present disclosure.

[0170] Exemplary communication device

[0189] FIG. 18 shows an aspect of exemplary communication device 1800. In some aspects, communication device 1800 is a user equipment such as UE 104 described above with respect to FIGS. 1 and 3.

[0171]

[0190] Communication device 1800 includes a processing system 1805 coupled to a transceiver 1855 (e.g., a transmitter and / or a receiver). Transceiver 1855 is configured to transmit and receive signals for communication device 1800, such as various signals as described herein, via antenna 1860. Processing system 1805 may be configured to perform processing functions for communication device 1800, including processing signals received by and / or to be transmitted by communication device 1800.

[0172]

[0191] The processing system 1805 includes one or more processors 1810. In various aspects, the one or more processors 1810 can represent one or more of the receiving processor 358, the transmitting processor 364, the TX MIMO processor 366, and / or the controller / processor 380 as described with respect to FIG. 3. The one or more processors 1810 are coupled to the computer-readable medium / memory 1830 via a bus 1850. In some aspects, the computer-readable medium / memory 1830 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1810, cause the one or more processors 1810 to execute the method 1600 described with respect to FIG. 16, or any aspect related thereto. Note that references to a processor that executes the functions of the communication device 1800 can include the one or more processors 1810 that execute that function of the communication device 1800.

[0173]

[0192] In the illustrated example, the computer-readable medium / memory 1830 stores code (e.g., executable instructions) such as receive code 1835, acquisition code 1840, and transmit code 1845. The processing of the receive code 1835, the acquisition code 1840, and the transmit code 1845 can cause the communication device 1800 to execute the method 1600 described with respect to FIG. 16, or any aspect related thereto.

[0174]

[0193] The one or more processors 1810 include circuitry configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1830, such as receive circuitry 1815, acquisition circuitry 1820, and transmit circuitry 1825. The processing by the receive circuitry 1815, the acquisition circuitry 1820, and the transmit circuitry 1825 can cause the communication device 1800 to execute the method 1600 described with respect to FIG. 16, or any aspect related thereto.

[0175]

[0194] The various components of communication device 1800 can provide means for performing method 1600 described with respect to FIG. 16, or any aspect related thereto. For example, means for transmitting, sending, or outputting for transmission can include transceiver 354 and / or antenna(s) 352 of UE 104 shown in FIG. 3, and / or transceiver 1855 and antenna 1860 of communication device 1800 in FIG. 18. Means for receiving or acquiring can include transceiver 354 and / or antenna(s) 352 of UE 104 shown in FIG. 3, and / or transceiver 1855 and antenna 1860 of communication device 1800 in FIG. 18.

[0176]

[0195] FIG. 19 shows an exemplary aspect of communication device 1900. In some aspects, communication device 1900 is a network entity such as BS 102 of FIGS. 1 and 3, or a distributed base station as described with respect to FIG. 2.

[0177]

[0196] Communication device 1900 includes a processing system 1905 coupled to a transceiver 1955 (e.g., a transmitter and / or a receiver) and / or a network interface 1965. Transceiver 1955 is configured to transmit and receive signals for communication device 1900, such as various signals as described herein, via antenna 1960. Network interface 1965 is configured to acquire and transmit signals for communication device 1900 via communication link(s) (singular or plural) such as a backhaul link, a midhaul link, and / or a fronthaul link as described herein, such as with respect to FIG. 2. Processing system 1905 can be configured to perform processing functions for communication device 1900, including processing signals received by and / or to be transmitted by communication device 1900.

[0178]

[0197] The processing system 1905 includes one or more processors 1910. In various aspects, the one or more processors 1910 can represent one or more of the receiving processor 338, the transmitting processor 320, the TX MIMO processor 330, and / or the controller / processor 340 as described with respect to FIG. 3. The one or more processors 1910 are coupled to the computer-readable medium / memory 1930 via a bus 1950. In some aspects, the computer-readable medium / memory 1930 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1910, cause the one or more processors 1910 to execute the method 1700 described with respect to FIG. 17 or any aspect related thereto. Note that references to the processor of the communication device 1900 that performs a function can include one or more processors 1910 of the communication device 1900 that perform that function.

[0179]

[0198] In the illustrated example, the computer-readable medium / memory 1930 stores code (e.g., executable instructions) such as transmission code 1935, monitoring code 1940, and reception code 1945. The processing of the transmission code 1935, the monitoring code 1940, and the reception code 1945 can cause the communication device 1900 to execute the method 1700 described with respect to FIG. 17 or any aspect related thereto.

[0180]

[0199] The one or more processors 1910 include circuits configured to implement (e.g., execute) the code stored in the computer-readable medium / memory 1930, such as a transmission circuit 1915, a monitoring circuit 1920, and a reception circuit 1925. The processing by the transmission circuit 1915, the monitoring circuit 1920, and the reception circuit 1925 can cause the communication device 1900 to execute the method 1700 as described with respect to FIG. 17 or any aspect related thereto.

[0181]

[0200] The various components of communication device 1900 may provide means for performing method 1700 described with respect to FIG. 17, or any aspect related thereto. The means for transmitting, sending, or outputting for transmission may include transceiver 332 and / or antenna(s) 334 of BS 102 shown in FIG. 3, and / or transceiver 1955 and antenna 1960 of communication device 1900 shown in FIG. 19. The means for receiving or acquiring may include transceiver 332 and / or antenna(s) 334 of BS 102 shown in FIG. 3, and / or transceiver 1955 and antenna 1960 of communication device 1900 shown in FIG. 19.

[0182] Exemplary clauses

[0201] In the following numbered clauses, implementation examples will be described.

[0183]

[0202] Clause 1: A method for wireless communication by a UE, comprising receiving, from a network entity, one or more CG configurations each defining at least one CG opportunity within a data period; acquiring traffic in the form of one or more bursts; and transmitting the traffic to the network entity within a plurality of PUSCHs during the data period.

[0184]

[0203] Clause 2: The method according to clause 1, wherein the one or more CG configurations indicate the maximum number of PUSCHs per CG opportunity.

[0185]

[0204] Clause 3: The method according to clause 2, wherein the one or more CG configurations also indicate CG parameters for each of the PUSCHs.

[0186]

[0205] Clause 4: The method according to clause 3, wherein at least some of the transmission parameters vary between PUSCHs within a CG opportunity or between different CG opportunities during the data period.

[0187]

[0206] The method according to clause 2, further comprising: the UE transmitting an indication that it does not intend to use all of the maximum number of PUSCHs within the CG opportunity.

[0188]

[0207] The method according to clause 5, further comprising: transmitting an indication of at least one of a change in one or more CG parameters for one or more subsequent PUSCHs, or a request for a change in one or more CG parameters for one or more subsequent PUSCHs.

[0189]

[0208] The method according to clause 6, wherein the request is for a change in one or more CG parameters for one or more subsequent PUSCHs within the same CG opportunity, a subsequent CG opportunity, or a group of subsequent CG opportunities.

[0190]

[0209] The method according to clause 6, wherein the change or request for change is indicated via at least one of sequence-based signaling, UCI, or MAC-CE.

[0191]

[0210] The method according to clause 2, further comprising: the UE transmitting an indication that it intends to use a PUSCH exceeding the maximum number within the CG opportunity.

[0192]

[0211] The method according to clause 2, wherein transmitting traffic to a network entity within a plurality of PUSCHs during a data period includes transmitting one or more PUSCHs within at least one CG opportunity and transmitting one or more PUSCHs scheduled via one or more dynamic grants.

[0193]

[0212] The method according to clause 10, further comprising: transmitting at least one SR, and at least one of the dynamic grants being sent in response to the SR.

[0194]

[0213] Clause 12: The method according to Clause 10, further comprising transmitting an additional data indication for triggering a pre-configured PUSCH resource and transmitting a PUSCH on at least a part of the pre-configured PUSCH resources.

[0195]

[0214] Clause 13: The method according to Clause 10, further comprising transmitting an indication indicating the end of one of the data bursts within one of the PUSCHs.

[0196]

[0215] Clause 14: The method according to Clause 10, further comprising transmitting an additional data indication within one of the PUSCHs, wherein at least one of the dynamic grants is sent in response to the additional data indication.

[0197]

[0216] Clause 15: The method according to Clause 14, wherein the additional data indicator is transmitted via at least one of DMRS, MAC-CE, or UCI.

[0198]

[0217] Clause 16: The method according to any one of Clauses 1 to 15, comprising a plurality of CG configurations, wherein each of the one or more CG configurations has at least one associated CG opportunity during the data period.

[0199]

[0218] Clause 17: The method according to Clause 16, wherein transmitting traffic to a network entity within a plurality of PUSCHs during a data period includes transmitting the traffic within a plurality of CG opportunities, each associated with one of the plurality of CG configurations.

[0200]

[0219] Clause 18: The method according to Clause 16, further comprising transmitting an additional data indication indicating that the UE intends to use at least one CG opportunity or CG configuration during the data period.

[0201]

[0220] Clause 19: The method according to Clause 16, wherein the additional data indicator also indicates a modification of one or more CG parameters.

[0202]

[0221] The method according to clause 16, further comprising: the UE transmitting an indication that it does not plan to use at least one CG opportunity or CG configuration during the data period.

[0203]

[0222] The method according to clause 20, wherein the indication is transmitted via at least one of sequence-based signaling, UCI, PUSCH, or MAC-CE.

[0204]

[0223] The method according to any one of clauses 1 to 21, further comprising: at the start of the data period, the UE transmitting a WUS to the network entity to indicate that it actually plans to use at least one CG opportunity during the data period.

[0205]

[0224] The method according to clause 22, wherein the WUS is transmitted at a fixed offset from the first PUSCH transmitted by the UE.

[0206]

[0225] The method according to clause 22, wherein the WUS also indicates a modification of one or more CG parameters.

[0207]

[0226] The method according to clause 22, wherein the WUS is transmitted via at least one of sequence-based signaling, UCI, or MAC-CE.

[0208]

[0227] A method for wireless communication by a network entity, comprising: transmitting to the UE one or more CG configurations each defining at least one CG opportunity during the data period; and monitoring uplink traffic from the UE in a plurality of PUSCHs during the data period.

[0209]

[0228] The method according to clause 26, wherein one or more CG configurations indicate the maximum number of PUSCHs per CG opportunity.

[0210]

[0229] Clause 28: The method according to clause 27, wherein one or more CG configurations also indicate CG parameters for each of the PUSCHs.

[0211]

[0230] Clause 29: The method according to clause 28, wherein at least some of the CG parameters vary between PUSCHs within a CG opportunity or between different CG opportunities within a data period.

[0212]

[0231] Clause 30: The method according to clause 27, further comprising the UE receiving an indication that it is not intended to use all of the maximum number of PUSCHs within a CG opportunity.

[0213]

[0232] Clause 31: The method according to clause 30, further comprising monitoring for an indication of at least one of a change in one or more CG parameters for one or more subsequent PUSCHs or a request for a change in one or more CG parameters for one or more subsequent PUSCHs.

[0214]

[0233] Clause 32: The method according to clause 31, wherein the request is for a change in one or more CG parameters for one or more subsequent PUSCHs within the same CG opportunity, a subsequent CG opportunity, or a group of subsequent CG opportunities.

[0215]

[0234] Clause 33: The method according to clause 31, wherein the change or request for change is indicated via at least one of sequence-based signaling, UCI, or MAC-CE.

[0216]

[0235] Clause 34: The method according to clause 27, further comprising the UE monitoring for an indication that it is intended to use more PUSCHs than the maximum number within a CG opportunity.

[0217]

[0236] Clause 35: The method according to clause 27, wherein monitoring the uplink traffic from the UE in a plurality of PUSCHs within a data period includes monitoring one or more PUSCHs within at least one CG opportunity and monitoring one or more PUSCHs scheduled via one or more dynamic grants.

[0218]

[0237] Clause 36: The method according to clause 35, further comprising monitoring at least one SR and transmitting at least one of the dynamic grants in response to at least one SR.

[0219]

[0238] Clause 37: The method according to clause 35, further comprising monitoring an additional data indication for triggering a preconfigured PUSCH resource and monitoring a PUSCH on at least a part of the preconfigured PUSCH resources.

[0220]

[0239] Clause 38: The method according to clause 35, further comprising monitoring an indication within one of the PUSCHs indicating the end of one of the data bursts.

[0221]

[0240] Clause 39: The method according to clause 35, further comprising monitoring an additional data indication within one of the PUSCHs, wherein at least one of the dynamic grants is sent in response to the additional data indication.

[0222]

[0241] Clause 40: The method according to clause 39, wherein the additional data indicator is transmitted via at least one of DMRS, MAC-CE, or UCI.

[0223]

[0242] Clause 41: The method according to any one of clauses 26 to 40, wherein one or more CG configurations include a plurality of CG configurations each having at least one associated CG opportunity within a data period.

[0224]

[0243] Clause 42: The method according to Clause 41, wherein monitoring the uplink traffic from the UE in a plurality of PUSCHs within a data period includes monitoring the traffic in a plurality of CG opportunities, each associated with one of the plurality of CG configurations.

[0225]

[0244] Clause 43: The method according to Clause 41, further including monitoring for an additional data indication that indicates that the UE intends to use at least one CG opportunity or CG configuration during a data period.

[0226]

[0245] Clause 44: The method according to Clause 41, wherein the additional data indicator also indicates a modification of one or more CG parameters.

[0227]

[0246] Clause 45: The method according to Clause 41, further including monitoring for an indication that the UE does not intend to use at least one CG opportunity or CG configuration during a data period.

[0228]

[0247] Clause 46: The method according to Clause 45, wherein the indication is transmitted via at least one of sequence-based signaling, UCI, PUSCH, or MAC-CE.

[0229]

[0248] Clause 47: The method according to any one of Clauses 26 to 46, further including monitoring, at the start of a data period, for a WUS from the UE to indicate that the UE actually intends to use at least one CG opportunity during the data period.

[0230]

[0249] Clause 48: The method according to Clause 47, wherein the WUS also indicates a modification of one or more CG parameters.

[0231]

[0250] Clause 49: The method according to Clause 47, wherein the WUS is transmitted at a fixed offset from the first PUSCH transmitted by the UE.

[0232]

[0251] Clause 50: The method according to clause 49, wherein the WUS is transmitted via at least one of sequence-based signaling, UCI, or MAC-CE.

[0233]

[0252] Clause 51: An apparatus comprising a memory including executable instructions and a processor configured to execute the executable instructions to cause the apparatus to perform the method according to any one of clauses 1 to 50.

[0234]

[0253] Clause 52: An apparatus comprising means for performing the method according to any one of clauses 1 to 50.

[0235]

[0254] Clause 53: A non-transitory computer-readable medium comprising executable instructions that, when executed by a processor of an apparatus, cause the apparatus to perform the method according to any one of clauses 1 to 50.

[0236]

[0255] Clause 54: A computer program product embodied on a computer-readable storage medium comprising code for performing the method according to any one of clauses 1 to 50.

[0237] Additional Considerations

[0256] The foregoing description has been provided to enable any person skilled in the art to practice the various aspects described herein. The examples described herein are not intended to limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects as well. For example, changes may be made to the functions and arrangements of the elements described without departing from the scope of the present disclosure. The various examples may omit, substitute, or add various procedures or components as necessary. For example, the methods described may be performed in an order different from the order described, various actions may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, any number of the aspects described herein may be used to implement an apparatus or practice a method. In addition, the scope of the present disclosure is intended to include apparatuses or methods practiced using other structures, functions, or a combination of structures and functions in addition to, or other than, the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0238]

[0257] The various illustrative logical blocks, modules, and circuits described in connection with the present disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0239]

[0258] As used herein, the phrase “at least one of” in reference to a list of items refers to any combination of those items including at least one member. As an example, “at least one of a, b, or c” refers to a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having multiple of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c, or any other order of a, b, and c).

[0240]

[0259] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Further, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Additionally, "determining" may include solving, selecting, choosing, establishing, and the like.

[0241]

[0260] The methods disclosed herein include one or more actions for achieving the methods. The actions of those methods can be interchanged with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above can be implemented by any suitable means capable of performing the corresponding functions. Those means can include, but are not limited to, circuits, application specific integrated circuits (ASICs), or processors, and can include various hardware components and / or software components (singular or plural), and / or various hardware modules and / or software modules (singular or plural).

[0242]

[0261] The following claims are not intended to be limited to the aspects shown in this specification, but rather the full scope consistent with the language of the claims should be recognized. In the claims, a reference to an element in the singular is not intended to mean "one and only one" unless so stated, but rather is intended to mean "one or more." Unless otherwise specified, the term "some" refers to one or more. Claim elements should not be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for." All structural and functional equivalents of the elements of the various aspects described throughout this disclosure, known or later coming to be known to those of ordinary skill in the art, are expressly incorporated herein by reference and are intended to be encompassed by the claims. Furthermore, nothing disclosed herein is intended to be dedicated to the public whether or not such disclosure is expressly recited in the claims.

Claims

1. A method for wireless communication using user equipment (UE), Receiving one or more CG configurations from a network entity, each defining at least one configuration grant (CG) opportunity within a data period, To acquire traffic in the form of one or more bursts, The traffic is transmitted to the network entity within a plurality of physical uplink shared channels (PUSCHs) within the data period. A method comprising, wherein the one or more CG configurations indicate the maximum number of PUSCHs per CG opportunity.

2. The one or more CG configurations also specify CG parameters for each of the PUSCHs, Preferably, at least a portion of the CG parameters are It changes during the PUCH within the CG machine, or Varies between different CG opportunities within the data period. The method according to claim 1, further comprising transmitting an instruction that the UE intends to use more than the maximum number of PUSCHs in the CG machine.

3. The method according to claim 1, further comprising the UE transmitting an instruction that it intends not to use any of the maximum number of PUSCHs in the CG machine.

4. Modifying one or more CG parameters for one or more subsequent pushes, or The method according to claim 3, further comprising transmitting an instruction for at least one of the following: a request for a change in one or more CG parameters for one or more subsequent pushes.

5. The request is for changing one or more CG parameters for the same CG opportunity, a subsequent CG opportunity, or one or more subsequent PUSCH within a group of subsequent CG opportunities, or The method according to claim 4, wherein the change or request for the change is indicated via at least one of sequenced-based signaling, uplink control information (UCI), or media access control (MAC) control elements (CE).

6. Sending the aforementioned traffic to the network entity within multiple PUSCHs within the aforementioned data period is Transmitting one or more PUSCHs within the at least one CG machine, and Sending one or more PUSCHs scheduled via one or more dynamic grants, The method according to claim 1, including the method described in claim 1.

7. Sending at least one scheduling request (SR), wherein at least one of the dynamic grants is sent in response to the SR, or Sending additional data instructions to trigger a pre-configured PUSCH resource, and Sending a PUSCH on at least some of the pre-configured PUSCH resources, or Within one of the aforementioned PUSCHs, transmit an instruction to terminate one of the aforementioned bursts. The method according to claim 6, further comprising:

8. The further includes transmitting an additional data instruction within one of the PUSCHs, wherein at least one of the dynamic grants is sent in response to the additional data instruction. Preferably, the method according to claim 6, wherein the additional data indicator is transmitted via at least one of the demodulation reference signals (DMRS), media access control (MAC) control elements (CE), or uplink control information (UCI).

9. The method according to claim 1, comprising a plurality of CG configurations, each of which has at least one related CG opportunity within the data period.

10. Transmitting the traffic to the network entity within a plurality of PUSCHs within the data period includes transmitting the traffic within a plurality of CG opportunities, each associated with one of the plurality of CG configurations, or The UE further includes transmitting additional data instructions indicating that it plans to use at least one CG opportunity or CG configuration within the data period, or The method according to claim 9, wherein the additional data indicator also instructs the modification of one or more CG parameters.

11. The UE further includes sending an instruction that it does not intend to use at least one CG opportunity or CG configuration during the data period. Preferably, the instruction is transmitted via at least one of sequence-based signaling, uplink control information (UCI), PUSCH, or media access control (MAC) control elements (CE), according to claim 9.

12. At the start of the data period, the UE further includes sending a wake-up signal (WUS) to the network entity to indicate that it intends to actually use at least one CG opportunity within the data period, preferably, The WUS is transmitted at a fixed offset from the first PUSCH transmitted by the UE, or The WUS may also instruct the modification of one or more CG parameters, The method according to claim 1, wherein the WUS is transmitted via at least one of sequenced-based signaling, uplink control information (UCI), or media access control (MAC) control elements (CE).

13. A method for wireless communication by a network entity, To transmit one or more CG configurations to the user equipment (UE), each defining at least one configuration grant (CG) opportunity within the data period, Monitoring of uplink traffic from the UE within multiple physical uplink shared channels (PUSCHs) during the aforementioned data period, A method comprising, wherein the one or more CG configurations indicate the maximum number of PUSCHs per CG opportunity.

14. A user device (UE) configured for wireless communication, comprising memory containing computer executable instructions, and one or more processors that execute the computer executable instructions and provide the UE with The network entity receives one or more CG configurations, each defining at least one configuration grant (CG) opportunity within the data period. To capture traffic in the form of one or more bursts, The traffic is transmitted to the network entity within a plurality of physical uplink shared channels (PUSCHs) within the data period. One or more processors configured as such, A user device (UE) comprising, wherein one or more CG configurations indicate the maximum number of PUSCHs per CG opportunity.

15. A network entity configured for wireless communication, comprising memory containing computer executable instructions, and one or more processors that execute the computer executable instructions and provide the network entity with The user equipment (UE) is instructed to transmit one or more configuration grant (CG) configurations, each defining at least one CG opportunity within the data period. The system monitors the uplink traffic from the UE within multiple physical uplink shared channels (PUSCHs) during the aforementioned data period. One or more processors configured as such, A network entity comprising, wherein one or more CG configurations indicate the maximum number of PUSCHs per CG opportunity.

Images