Configuring multiple channels within grant opportunity
By employing multiple channels within configuration grant and semi-persistent scheduling opportunities, and coordinating discontinuous reception cycles, the method enhances data transmission efficiency in wireless communication systems.
Patent Information
- Application Number
- CN202380035713.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-03-15
- Filing Date
- 2023-03-16
- Publication Date
- 2024-12-03
AI Technical Summary
Existing wireless communication systems face challenges in efficiently utilizing multiple channels for configuration grant and semi-persistent scheduling opportunities, leading to suboptimal data transmission performance.
Implementing methods and apparatuses that enable the use of multiple physical uplink and downlink shared channels within configuration grant and semi-persistent scheduling opportunities, along with coordinated discontinuous reception cycles, to enhance data transmission efficiency.
Improves data transmission efficiency by allowing simultaneous utilization of multiple channels, optimizing resource allocation and reducing latency in wireless communication systems.
Smart Images

Figure CN119072873A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 363,931, filed on April 29, 2022, entitled “DISCONTINUOUS RECEPTION FOR MULTIPLE DATA FLOWS,” and U.S. Provisional Patent Application No. 63 / 363,933, filed on April 29, 2022, entitled “MULTIPLE CHANNELS WITHIN SEMI-PERSISTENT SCHEDULING OCCASIONS AND CONFIGURED GRANT OCCASIONS,” and U.S. Non-Provisional Patent Application No. 18 / 184,310, filed on March 15, 2023, entitled “MULTIPLE CHANNELS WITHIN CONFIGURED GRANT OCCASIONS,” which are hereby expressly incorporated herein by reference. Technical Field
[0003] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for using multiple channels for configuration grant opportunities. Background Art
[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.
[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. The new radio (NR), which may be referred to as 5G, is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention
[0007] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving a configuration associated with a configuration grant (CG) indicating a plurality of physical uplink shared channels (PUSCHs) within each CG opportunity of the UE. The method may include sending a plurality of packets across a plurality of PUSCHs within at least one CG opportunity of the UE.
[0008] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a configuration associated with a CG, the configuration indicating multiple PUSCHs within each CG opportunity of the UE. The one or more processors may be further configured to send multiple packets across multiple PUSCHs within at least one CG opportunity of the UE.
[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. One or more instructions, when executed by one or more processors of the UE, may cause the UE to receive a configuration associated with a CG, the configuration indicating multiple PUSCHs within each CG opportunity of the UE. One or more instructions, when executed by one or more processors of the UE, may further cause the UE to send multiple packets across multiple PUSCHs within at least one CG opportunity of the UE.
[0010] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving a configuration associated with a CG, the configuration indicating a plurality of PUSCHs within each CG opportunity of the apparatus. The apparatus may also include a component for sending a plurality of packets across a plurality of PUSCHs within at least one CG opportunity of the apparatus.
[0011] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending a configuration associated with a CG, the configuration indicating a plurality of PUSCHs within each CG opportunity of the UE. The method may include receiving a plurality of packets across the plurality of PUSCHs within at least one CG opportunity of the UE.
[0012] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send a configuration associated with a CG, the configuration indicating multiple PUSCHs within each CG opportunity of the UE. The one or more processors may be further configured to receive multiple packets across multiple PUSCHs within at least one CG opportunity of the UE.
[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. One or more instructions, when executed by one or more processors of the network entity, may cause the network entity to send a configuration associated with a CG, the configuration indicating multiple PUSCHs within each CG opportunity of the UE. One or more instructions, when executed by one or more processors of the network entity, may further cause the network entity to receive multiple packets across multiple PUSCHs within at least one CG opportunity of the UE.
[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending a configuration associated with a CG, the configuration indicating multiple PUSCHs within each CG opportunity of the UE. The apparatus may also include a component for receiving multiple packets across multiple PUSCHs within at least one CG opportunity of the UE.
[0015] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a configuration associated with semi-persistent scheduling (SPS), the configuration indicating multiple physical downlink shared channels (PDSCHs) within each SPS opportunity of the UE. The method may include receiving multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE.
[0016] Some aspects described herein relate to a device for wireless communication at a UE. The device may include a memory and one or more processors coupled to the memory. One or more processors may be configured to receive a configuration associated with an SPS, which indicates multiple PDSCHs within each SPS opportunity of the UE. One or more processors may be further configured to receive multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE.
[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. One or more instructions, when executed by one or more processors of the UE, may cause the UE to receive a configuration associated with an SPS, the configuration indicating multiple PDSCHs within each SPS opportunity of the UE. One or more instructions, when executed by one or more processors of the UE, may further cause the UE to receive multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE.
[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for receiving a configuration associated with an SPS, the configuration indicating a plurality of PDSCHs within each SPS opportunity of the apparatus. The apparatus may also include a component for receiving a plurality of packets across a plurality of PDSCHs within at least one SPS opportunity of the apparatus.
[0019] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending a configuration associated with an SPS, the configuration indicating a plurality of PDSCHs within each SPS opportunity of a UE. The method may include sending a plurality of packets across a plurality of PDSCHs within at least one SPS opportunity of the UE.
[0020] Some aspects described herein relate to a device for wireless communication at a network entity. The device may include a memory and one or more processors coupled to the memory. One or more processors may be configured to send a configuration associated with an SPS, which indicates multiple PDSCHs within each SPS opportunity of the UE. One or more processors may be further configured to send multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE.
[0021] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. One or more instructions, when executed by one or more processors of the network entity, may cause the network entity to send a configuration associated with SPS, the configuration indicating multiple PDSCHs within each SPS opportunity of the UE. One or more instructions, when executed by one or more processors of the network entity, may further cause the network entity to send multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE.
[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include a component for sending a configuration associated with SPS, the configuration indicating multiple PDSCHs within each SPS opportunity of the UE. The apparatus may also include a component for sending multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE.
[0023] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an indication of a timing of a discontinuous reception (DRX) On Duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The method may include monitoring communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0024] Some aspects described herein relate to a method of wireless communications performed by a network entity. The method may include sending an indication of a timing of a DRX On Duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The method may include sending communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0025] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving an indication of a timing of a DRX On Duration occasion, the timing being associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The method may include monitoring communications of the first data stream and the second data stream at the DRX On Duration occasion.
[0026] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending an indication of a timing of a DRX On Duration opportunity, the timing associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The method may include sending communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0027] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a timing of a DRX On Duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The one or more processors may be configured to monitor communication of the first data stream and the second data stream at the DRX On Duration opportunity.
[0028] Some aspects described herein relate to a network entity for wireless communications. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an indication of a timing of a DRX On Duration opportunity, the timing associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The one or more processors may be configured to send communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0029] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of a timing of a DRX On Duration opportunity, the timing being associated with a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream, whichever is greater. The one or more processors may be configured to monitor communication of the first data stream and the second data stream at the DRX On Duration opportunity.
[0030] Some aspects described herein relate to a network entity for wireless communications. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send an indication of a timing of a DRX On Duration opportunity, the timing being associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The one or more processors may be configured to send communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0031] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an indication of a timing of a DRX On Duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0032] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to send an indication of a timing of a DRX On Duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to send communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0033] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication of a timing of a DRX on-duration opportunity, the timing being associated with a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream, which is greater. The instruction set, when executed by one or more processors of the UE, may cause the UE to monitor communications of the first data stream and the second data stream at the DRX on-duration opportunity.
[0034] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to send an indication of a timing of a DRX On Duration opportunity, the timing being associated with the greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to send communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0035] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a timing of a DRX On Duration opportunity, the timing associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The apparatus may include means for monitoring communication of the first data stream and the second data stream at the DRX On Duration opportunity.
[0036] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of a timing of a DRX On Duration opportunity, the timing associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The apparatus may include means for sending communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0037] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a timing of a DRX On Duration opportunity, the timing associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The apparatus may include means for monitoring communication of the first data stream and the second data stream at the DRX On Duration opportunity.
[0038] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending an indication of a timing of a DRX On Duration opportunity, the timing being associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The apparatus may include means for sending communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0039] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer readable media, user equipment, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the accompanying drawings and description.
[0040] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.
[0041] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user equipment, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence equipment). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.
[0043] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.
[0044] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.
[0045] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.
[0046] Figure 4 is a diagram illustrating an example of an extended reality (XR) system according to the present disclosure.
[0047] Figure 5 is a diagram illustrating an example of a discontinuous reception (DRX) cycle according to the present disclosure.
[0048] Figure 6 is a diagram illustrating an example of an XR stream according to the present disclosure.
[0049] Figure 7 is a diagram illustrating an example of timing of multiple DRX cycles according to the present disclosure.
[0050] Figure 8 is a diagram illustrating an example of non-uniform DRX cycles for multiple data streams according to the present disclosure.
[0051] Fig. 9 is a diagram illustrating an example associated with DRX of multiple data streams according to the present disclosure.
[0052] Fig.10 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.
[0053] Fig.11 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.
[0054] Fig.12 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.
[0055] Fig.13 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.
[0056] Fig.14 and Fig.15 is a diagram of an example apparatus for wireless communications according to the present disclosure.
[0057] Fig.16 and Fig.17 is a diagram illustrating an example associated with using multiple channels for a semi-persistent scheduling (SPS) opportunity according to the present disclosure.
[0058] Fig.18 and Fig.19 is a diagram illustrating an example associated with using multiple channels for a configuration grant (CG) opportunity according to the present disclosure.
[0059] Fig. 20 and Fig.21 is a diagram illustrating an example process associated with using multiple channels for SPS opportunities according to the present disclosure.
[0060] Fig. 22 and Fig.23 is a diagram illustrating an example process associated with using multiple channels for CG opportunities according to the present disclosure.
[0061] Fig.24 and Fig.25 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION
[0062] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of protection of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.
[0063] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0064] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).
[0065] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS 110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a B node, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.
[0066] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.
[0067] In some examples, the cell may not necessarily be fixed, and the geographic area of the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network via various types of backhaul interfaces (such as direct physical connections or virtual networks).
[0068] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographical location or in different geographical locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not the other. In this way, a single device may include more than one base station.
[0069] The wireless network 100 may include one or more relay stations. A relay station is a network entity that can receive transmissions of data from an upstream station (e.g., a network entity or UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a network entity). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.
[0070] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).
[0071] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for these network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may communicate with each other directly or indirectly via a wireless or wired backhaul communication link.
[0072] UE 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.
[0073] Some UEs 120 may be considered as machine type communication (MTC) UEs or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as user premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.
[0074] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. Frequency may be referred to as a carrier, a frequency channel, etc. In a given geographic area, each frequency may support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.
[0075] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using a network entity as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.
[0076] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).
[0077] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.
[0078] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0079] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may receive an indication of a timing of a discontinuous reception (DRX) On Duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The communication manager 140 may monitor communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0080] In some aspects, the communication manager 140 may receive an indication of a timing of a DRX On Duration opportunity that is associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The communication manager 140 may monitor communications of the first data stream and the second data stream at the DRX On Duration opportunity. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0081] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send an indication of a timing of a DRX On Duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The communication manager 150 may send communications for the first data stream and the second data stream at the DRX On Duration opportunity.
[0082] In some aspects, the communication manager 150 may send an indication of a timing of a DRX On Duration opportunity that is associated with the greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. The communication manager 150 may send communications of the first data stream and the second data stream at the DRX On Duration opportunity. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0083] In some aspects, a UE (e.g., UE 120) may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may receive a configuration associated with a semi-persistent scheduling (SPS) indicating a plurality of physical downlink shared channels (PDSCHs) within each SPS opportunity of the UE 120; and receive a plurality of packets across the plurality of PDSCHs within at least one SPS opportunity of the UE 120. Additionally or alternatively, as described in greater detail elsewhere herein, the communication manager 140 may receive a configuration associated with a configuration grant (CG) indicating a plurality of physical uplink shared channels (PUSCHs) within each CG opportunity of the UE 120; and send a plurality of packets across the plurality of PUSCHs within at least one CG opportunity of the UE 120. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0084] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send a configuration associated with SPS indicating a plurality of PDSCHs within each SPS opportunity of UE 120; and send a plurality of packets across the plurality of PDSCHs within at least one SPS opportunity of UE 120. Additionally or alternatively, as described in greater detail elsewhere herein, the communication manager 150 may send a configuration associated with CG indicating a plurality of PUSCHs within each CG opportunity of UE 120; and receive a plurality of packets across the plurality of PUSCHs within at least one CG opportunity of UE 120. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0085] As indicated above, Figure 1 Other examples can be found in the Figure 1 The examples described are different.
[0086] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).
[0087] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).
[0088] At the UE 120, a set of antennas 252 (shown as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a through 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.
[0089] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with network entities via the communication unit 294.
[0090] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.
[0091] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to a network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 4 to 25 ) or any aspect of any of the methods described herein.
[0092] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 25 ) or any aspect of any of the methods described herein.
[0093] A controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2Any other components of the base station 110 may perform one or more techniques associated with DRX with multiple streams, use of multiple channels for SPS opportunities, or use of multiple channels for CG opportunities, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 The process of 1300 Fig. 20 The process of 2000, Fig.21 Process 2100, Fig. 22 The process 2200 Fig.23 2300 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network entities and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of the network entity and / or UE 120, may cause the one or more processors, UE 120, and / or the network entity to perform or direct, for example, Fig.10 The process of 1000 Fig.11 Process 1100, Fig.12 The process 1200 Fig.13 Process 1300, Fig. 20 The process of 2000, Fig.21 Process 2100, Fig. 22 The process 2200 Fig.23 The process 2300 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.
[0094] In some aspects, the UE 120 includes means for receiving an indication of a timing of a DRX on duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream; and / or means for monitoring communications of the first data stream and the second data stream at the DRX on duration opportunity. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.
[0095] In some aspects, a network entity (e.g., base station 110) includes means for sending an indication of a timing of a DRX on duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream; and / or means for sending a communication of the first data stream and the second data stream at the DRX on duration opportunity. In some aspects, means for the network entity to perform operations described herein may include, for example, one or more of the following: communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.
[0096] In some aspects, UE 120 includes components for receiving an indication of a timing of a DRX On Duration occasion, the timing being associated with the greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream; and / or components for monitoring communication of the first data stream and the second data stream at the DRX On Duration occasion.
[0097] In some aspects, the network entity includes components for sending an indication of the timing of a DRX On Duration opportunity, the timing being associated with the greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream; and / or components for sending communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0098] In some aspects, a UE (e.g., UE 120 and / or Fig.24The device 2400 may include a component for receiving a configuration associated with SPS, the configuration indicating multiple PDSCHs within each SPS opportunity of the UE; and / or a component for receiving multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE. Additionally or alternatively, the UE may include a component for receiving a configuration associated with CG, the configuration indicating multiple PUSCHs within each CG opportunity of the UE. And / or a component for sending multiple packets across multiple PUSCHs within at least one CG opportunity of the UE. The components for the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.
[0099] In some aspects, a network entity (e.g., base station 110, CU 310, DU 330, RU 340, and / or Fig.25 The apparatus 2500 may include a component for sending a configuration associated with the SPS, the configuration indicating that the UE (e.g., UE 120 and / or Fig.24 2400); and / or a component for sending multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE. Additionally or alternatively, the network entity may include a component for sending a configuration associated with a CG, the configuration indicating multiple PUSCHs within each CG opportunity of the UE; and / or a component for receiving multiple packets across multiple PUSCHs within at least one CG opportunity of the UE. In some aspects, the components for the network entity to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.
[0100] Although Figure 2 The blocks in the 200 and 210 are shown as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.
[0101] As indicated above, Figure 2 Other examples can be found in the Figure 2 The examples described are different.
[0102] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.
[0103] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) performing base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.
[0104] An aggregated base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more Dus, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more Dus may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A Du may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).
[0105] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0106] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near RTRIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more Dus 330 via corresponding midhaul links (such as an F1 interface). The Du 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with corresponding UEs 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The Du 330 and the RU 340 may also be referred to as "O-RAN Du (O-Du)" and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of Cu, Du, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of Cu, Du, and RU. The network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.
[0107] Each of these units (e.g., Cu 310, Du 330, RU 340, and near-RT RIC 325, non-RTRIC 315, and SMO framework 305) may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) that is configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.
[0108] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.
[0109] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as defined by 3GPP. In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.
[0110] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).
[0111] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, Cu 310, Du 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN such as an open eNB (O-eNB) 311 via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .
[0112] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more Cu 310, one or more Du 330, or both, and O-eNBs with the near-RT RIC 325.
[0113] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).
[0114] As indicated above, Figure 3 Other examples can be found in the Figure 3 The examples described are different.
[0115] Figure 4 is a diagram illustrating an example 400 of an extended reality (XR) system according to the present disclosure.
[0116] Some devices, including those for XR, may require low-latency traffic to and from an edge server or cloud environment. Example 400 illustrates communication between an XR device and an edge server or cloud environment via a base station (e.g., a gNB). The XR device may be an augmented reality (AR) glasses device, a virtual reality (VR) glasses device, or other gaming device. The XR device may have limited battery capacity while being expected to have the battery life of a smartphone (e.g., all-day use). Even if the XR device is connected to a smartphone and uses the same smartphone battery, battery power is an issue. XR device power consumption may be limited and may result in an uncomfortable user experience and / or short battery life.
[0117] Power consumption can be reduced by limiting the amount of active time that the processing resources of the XR device are used for computing and power consumption. Some wireless communication systems may support UEs, such as XR devices, operating in DRX mode. A UE in DRX mode can transition between a sleep state for power saving and an active state for data transmission and reception. The active state for data transmission and reception may be referred to as the DRX "on duration". UEs using different DRX cycles may have inconsistent cycle durations within a DRX time period. This inconsistent cycle duration may provide a DRX on duration that is aligned with the periodicity of downlink traffic to the UE. In some cases, a DRX time period may correspond to an anchor cycle that spans a DRX cycle set, and a subset of a DRX cycle set may have a cycle duration different from other DRX cycles in the DRX cycle set. In some cases, an on duration offset value may be indicated for one or more DRX cycles within a DRX time period (e.g., via downlink control information (DCI) or MAC CE).
[0118] By offloading some computations to the edge server, the XR device can save processing resources. Example 400 shows a scenario in which the XR device can split computations for an application with an edge server on the other side of a base station. The edge server can render video frames (such as intra-coded (I) frames and predicted (P) frames), encode video frames, align video frames with user pose information, and perform other related computations. However, this means that there may be more traffic between the XR device and the edge server, which will cause the XR device to consume more power and signaling resources. XR downlink traffic (e.g., video frames) may have a periodic pattern corresponding to the frame rate of the video data being sent (e.g., H.264 / H.265 encoded video). This downlink traffic can be quasi-periodic, with one burst of data per frame at one frame per second (1fps), or one burst of data per frame at one frame per second (1fps). 1 / 2fps rate with two possible staggered "eye buffers". For example, XR downlink traffic may include more than 100 kilobytes (KB) of data at 45, 60, 75, or 90 frames per second (e.g., every 11ms, 13ms, 16ms, or 22ms). XR uplink traffic may include controller information for games, information for VR split rendering, and / or user posture information. XR uplink traffic may include 100 bytes every 2ms (500Hz). XR devices may reduce this periodicity to align XR uplink traffic with XR downlink traffic.
[0119] For low-latency applications, the DRX cycle and the start offset of the DRX cycle will be aligned with the downlink traffic arrival time. For example, an XR device may serve a user and enter a short sleep state in the DRX cycle and between video frames. The XR device and the edge server may attempt to align the uplink and downlink DRX cycles as part of connected DRX (CDRX). However, there is a DRX multimedia timing mismatch, which prevents such alignment and prevents the successful use of CDRX. For example, the update rate may be, for example, 120Hz or 60Hz, resulting in a downlink traffic burst arrival periodicity of 8.333ms or 16.667ms, respectively. However, a conventional DRX configuration may have one millisecond as the finest granularity of the DRX cycle, and the start of the on-duration may be aligned with a millisecond time boundary. These partial millisecond differences may be compounded with each instance of the cycle to misalign the DRX cycle with the XR traffic periodicity. For example, the XR traffic cycle may drift to the middle of the DRX cycle. This results in increased latency and power consumption.
[0120] As indicated above, Figure 4 Other examples can be found in the Figure 4 The examples described are different.
[0121] Figure 5is a diagram illustrating an example 500 of a DRX cycle according to the present disclosure.
[0122] The example 500 illustrates a downlink traffic burst arrival 505 , which may include multiple downlink traffic bursts 510 transmitted according to a periodic pattern. The example 500 also illustrates a DRX configuration 515 .
[0123] The downlink traffic burst 510 may include, for example, XR downlink traffic with a periodic pattern corresponding to the frame rate of the data being transmitted (e.g., H.264 / H.265 encoded video). The update rate may be, for example, 120 Hz or 60 Hz, resulting in a downlink traffic burst arrival periodicity of 8.333 ms or 16.667 ms, respectively. If the DRX configuration 515 has an on-duration opportunity aligned with the downlink traffic burst 510-a, the second downlink traffic burst 510-b and the third downlink traffic burst 510-a will also each be within the next two on-durations.
[0124] As indicated above, Figure 5 Other examples can be found in the Figure 5 The examples described are different.
[0125] Figure 6 is a diagram illustrating an example 600 of an XR flow according to the present disclosure.
[0126] Example 600 shows XR stream 1 and XR stream 2 whose XR traffic bursts are periodic with some time jitter in arrival. The packet size of a particular burst and its number of packets can be variable. Multiple traffic streams can be used for downlinks with different periodicities. However, configuring multiple CDRXs for multiple different periodicity streams requires the UE to sleep less time, which consumes power.
[0127] As indicated above, Figure 6 Other examples can be found in the Figure 6 The examples described are different.
[0128] Figure 7 is a diagram illustrating an example 700 of timing of multiple DRX cycles according to the present disclosure.
[0129] According to various aspects described herein, a UE may receive an indication of the timing of a DRX on duration opportunity. The timing may be associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The data stream may be an XR data stream having periodic traffic and / or traffic bursts. The UE may monitor communications of the first data stream and the second data stream at the DRX on duration opportunity. In some aspects, the timing may be associated with the larger of the first DRX cycle and the second DRX cycle.
[0130] Each stream may have a configured CDRX cycle with parameters customized for that traffic. For example, the CDRX on duration timing may be at different locations for different CDRX cycles. The UE knows the number of streams received on the downlink. If the minimum CDRX cycle is a non-integer, it is expected that the CDRX cycle will be extended to accommodate XR traffic with a typical periodicity such as 16.67 milliseconds (ms) or 8.33 ms. Example 700 shows that the CDRX cycle for multiple streams may be the minimum of CDRX_cycle_1 for XR stream 1 and CDRX_cycle_2 for XR stream 2.
[0131] In some aspects, in a CDRX on-duration opportunity aligned with a CDRX cycle, a next wake-up on-duration opportunity that is not aligned with a multi-stream CDRX cycle may be indicated by a notification (e.g., DCI) based on a physical downlink control channel (PDCCH). The notification based on the PDCCH may also include a parameter change. For example, a DCI in the first CDRX cycle on-duration opportunity of XR stream 1 may indicate the location of the CDRX on-duration opportunity of XR stream 2. For jitter processing, PDCCH monitoring may start a few time slots before the CDRX on-duration opportunity or end a few time slots after the CDRX on-duration opportunity.
[0132] In some aspects, the designated PDCCH monitoring occasion may be in the CDRX on duration (e.g., the first PDCCH monitoring occasion) during which the "next wakeup notification" is sent. The network entity (e.g., the gNB) may or may not align the initial transmission from multiple streams.
[0133] Example 702 shows that the CDRX cycle of multiple streams can be the maximum CDRX cycle of the CDRX of these streams. This may affect the latency of streams with less periodicity, but the packet delay budget (PDB) may be long enough to accommodate this. In some aspects, the multi-stream CDRX cycle can be a function of PDB_1, PDB_2, Periodicity_1, and Periodicity_2. For example, multi-stream CDRX cycle = min(PDB_1×Periodicity_1, PDB_2×Periodicity_2) / PDB_min, where PDB_min is the PDB of stream min(PDB_1×Periodicity_1, PDB_2×Periodicity_2).
[0134] As indicated above, Figure 7 Other examples can be found in the Figure 7 The examples described are different.
[0135] Figure 8 is a diagram illustrating an example 800 of non-uniform DRX cycling for multiple data streams according to the present disclosure.
[0136] Example 800 shows non-uniform CDRX cycles occurring during a larger cycle. The non-uniform pattern may be fixed during a large cycle and updated in the next large cycle if any parameters need to be changed. The non-uniform CDRX cycles may be a predefined sequence within an epoch, where an epoch includes multiple CDRX cycles. In some aspects, messaging may be sent once per epoch to adjust parameters within that epoch.
[0137] As indicated above, Figure 8 Other examples can be found in the Figure 8 The examples described are different.
[0138] Fig. 9 is a diagram illustrating an example 900 associated with DRX of multiple data streams according to the present disclosure. Fig. 9 As shown, a network entity 910 (eg, base station 110) and a UE 920 (eg, UE 120) may communicate with one another over a wireless network (eg, wireless network 100).
[0139] As indicated by reference numeral 925, the network entity 910 may send an indication of the timing of a DRX on duration opportunity, the timing being associated with a combination (or greater) of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. The timing may include a time position of a DRX on duration opportunity that takes into account multiple DRX cycles of a data stream (e.g., an XR stream) for a periodic application (e.g., an XR application). This may include overlapping or non-overlapping DRX on duration opportunities. This may include non-uniform timing positions of one stream between periodic timing positions of another stream. Some DRX on duration opportunities of one stream or DRX cycle may include information about the position of a DRX on duration opportunity of another stream or DRX cycle. A DRX cycle may be an anchor cycle used as a time or timing reference for one or more other DRX cycles. The anchor cycles and DRX on duration opportunities of multiple DRX cycles may be based at least in part on the periodicity and / or PDB of each DRX cycle.
[0140] UE 920 may monitor communications at the DRX On Duration opportunity according to the timing, as shown by reference numeral 930. In this way, when network entity 910 sends communications at the DRX On Duration opportunity, UE 920 may receive communications while sleeping longer and saving more power, as shown by reference numeral 935.
[0141] In some aspects, the network entity 910 may also adjust timing to help save power for the UE 920. This may include overlapping and / or combining DRX On-Duration opportunities from multiple DRX cycles.
[0142] As indicated above, Fig. 9 Other examples can be found in the Fig. 9 The examples described are different.
[0143] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a UE according to the present disclosure. Example process 1000 is an example in which a UE (eg, UE 120, UE 920) performs operations associated with DRX of multiple flows.
[0144] like Fig.10 As shown, in some aspects, process 1000 may include receiving an indication of a timing of a DRX On-Duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream (block 1010). For example, a UE (e.g., using Fig.14The depicted communication manager 1408 and / or receiving component 1402) may receive an indication of a timing of a DRX on-duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream, as described above.
[0145] like Fig.10 As further shown, in some aspects, process 1000 may include monitoring communications of the first data stream and the second data stream at a DRX on-duration opportunity (block 1020). Fig.14 The depicted communications manager 1408 and / or monitoring component 1410) can monitor communications of the first data flow and the second data flow at the DRX On-Duration occasions, as described above.
[0146] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0147] In a first aspect, the indication identifies the first DRX cycle or the second DRX cycle as an anchor cycle, and the DRX On-Duration occasion of the anchor cycle includes information indicating an On-Duration occasion of a non-anchor DRX cycle.
[0148] In a second aspect, either alone or in combination with the first aspect, the anchor cycle has a periodicity that is a minimum of the first periodicity and the second periodicity.
[0149] In a third aspect, alone or in combination with one or more of the first and second aspects, the anchor cycle has a periodicity that is a maximum of the first periodicity and the second periodicity.
[0150] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a DCI in a DRX On Duration opportunity of a first DRX cycle indicates a position of a DRX On Duration opportunity of a second DRX cycle.
[0151] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the timing is based at least in part on a first PDB of a first DRX cycle, a first periodicity, a second PDB of a second DRX cycle, and a second periodicity.
[0152] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the timing is at least partially based on a minimum value of the first PDB×first periodicity and the second PDB×second periodicity divided by a minimum PDB, which is the PDB of the flow minimum value of the first PDB×first periodicity and the second PDB×second periodicity.
[0153] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the timing of the DRX On-Duration occasions comprises a non-uniform DRX cycle.
[0154] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the timing is specified for epochs of a plurality of connected mode DRX cycles.
[0155] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, one or more of the first DRX cycle or the second DRX cycle corresponds to a periodicity of XR traffic.
[0156] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, one or more of the first data stream or the second data stream comprises XR traffic.
[0157] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the process 1000 includes monitoring communications in one or more time slots before or after a DRX On-Duration opportunity.
[0158] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.
[0159] Fig.11 is a diagram illustrating an example process 1100, for example, performed by a network entity, according to the present disclosure. The example process 1100 is an example in which a network entity (eg, base station 110, network entity 910) performs operations associated with DRX of multiple flows.
[0160] like Fig.11 As shown, in some aspects, process 1100 may include sending an indication of a timing of a DRX On Duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream (block 1110). For example, a network entity (e.g., using Fig.15 The depicted communication manager 1508 and / or transmitting component 1504) may transmit an indication of a timing of a DRX on-duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream, as described above.
[0161] like Fig.11 As further shown, in some aspects, process 1100 may include sending communications of the first data stream and the second data stream at a DRX on-duration opportunity (block 1120). Fig.15 The depicted communications manager 1508 and / or transmitting component 1504) can transmit communications of the first data stream and the second data stream at the DRX On Duration occasion, as described above.
[0162] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0163] In a first aspect, the indication identifies the first DRX cycle or the second DRX cycle as an anchor cycle, and the DRX OnDuration occasions of the anchor cycle indicate OnDuration occasions of the non-anchor DRX cycle.
[0164] In a second aspect, either alone or in combination with the first aspect, the anchor cycle has a periodicity that is a minimum of the first periodicity and the second periodicity.
[0165] In a third aspect, alone or in combination with one or more of the first and second aspects, a DCI in a DRX On Duration opportunity of a first DRX cycle indicates a location of a DRX On Duration opportunity of a second DRX cycle.
[0166] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the timing is based at least in part on a first PDB of a first DRX cycle, a first periodicity, a second PDB of a second DRX cycle, and a second periodicity.
[0167] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the timing is at least partially based on the minimum value of the first PDB×first periodicity and the second PDB×second periodicity divided by a minimum PDB, which is the PDB of the flow minimum value of the first PDB×first periodicity and the second PDB×second periodicity.
[0168] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the timing of the DRX On-Duration occasions comprises a non-uniform DRX cycle.
[0169] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the timing is specified for epochs of a plurality of connected mode DRX cycles.
[0170] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, one or more of the first DRX cycle or the second DRX cycle corresponds to the periodicity of the extended reality traffic.
[0171] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, one or more of the first data stream or the second data stream comprises augmented reality traffic.
[0172] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.
[0173] Fig.12 is a diagram illustrating an example process 1200 performed, for example, by a UE in accordance with the present disclosure. The example process 1200 is an example of operations in which a UE (eg, UE 120) performs operations associated with DRX for multiple flows.
[0174] like Fig.12 As shown, in some aspects, process 1200 may include receiving an indication of a timing of a DRX On-Duration opportunity, the timing being associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream (block 1210). For example, a UE (e.g., using Fig.14 The depicted communication manager 1408 and / or receiving component 1402) may receive an indication of a timing of a DRX on-duration opportunity associated with the greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream, as described above.
[0175] like Fig.12 As further shown, in some aspects, process 1200 may include monitoring communications of the first data stream and the second data stream at a DRX on-duration opportunity (block 1220). Fig.14 The depicted communications manager 1408 and / or monitoring component 1410) can monitor communications of the first data flow and the second data flow at the DRX On-Duration occasions, as described above.
[0176] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0177] In a first aspect, one or more of the first DRX cycle or the second DRX cycle corresponds to a periodicity of XR traffic.
[0178] In a second aspect, alone or in combination with the first aspect, one or more of the first data stream or the second data stream comprises XR traffic.
[0179] In a third aspect, alone or in combination with one or more of the first and second aspects, a DCI in a DRX On Duration opportunity of a first DRX cycle indicates a location of a DRX On Duration opportunity of a second DRX cycle.
[0180] although Fig.12 An example block diagram of process 1200 is shown, but in some aspects, process 1200 may include Fig.12 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.
[0181] Fig.13 is a diagram illustrating an example process 1300 performed, for example, by a network entity in accordance with the present disclosure. The example process 1300 is an example in which a network entity (eg, base station 110, network entity 910) performs operations associated with DRX of multiple flows.
[0182] like Fig.13 As shown, in some aspects, process 1300 may include sending an indication of a timing of a DRX On Duration opportunity that is associated with a greater of a first periodicity of a first DRX cycle of a first data flow or a second periodicity of a second DRX cycle of a second data flow (block 1310). For example, a network entity (e.g., using Fig.15 The depicted communication manager 1508 and / or transmitting component 1504) may transmit an indication of a timing of a DRX on-duration opportunity associated with the greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream, as described above.
[0183] like Fig.13 As further shown, in some aspects, process 1300 may include sending communications of the first data stream and the second data stream at a DRX on-duration opportunity (block 1320). Fig.15 The depicted communications manager 1508 and / or transmitting component 1504) can transmit communications of the first data stream and the second data stream at the DRX On Duration occasion, as described above.
[0184] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0185] In a first aspect, one or more of the first DRX cycle or the second DRX cycle corresponds to a periodicity of XR traffic.
[0186] In a second aspect, alone or in combination with the first aspect, one or more of the first data stream or the second data stream comprises XR traffic.
[0187] In a third aspect, alone or in combination with one or more of the first and second aspects, a DCI in a DRX On Duration opportunity of a first DRX cycle indicates a location of a DRX On Duration opportunity of a second DRX cycle.
[0188] although Fig.13 Example blocks of process 1300 are shown, but in some aspects, process 1300 may include Fig.13 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1300 may be performed in parallel.
[0189] Fig.14 1400 is a diagram of an example apparatus 1400 for wireless communication. Apparatus 1400 may be a UE (e.g., UE 120, UE 920), or a UE may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a transmitting component 1404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and transmitting component 1404. As further shown, apparatus 1400 may include a communication manager 1408. Communication manager 1408 may control and / or otherwise manage one or more operations of receiving component 1402 and / or transmitting component 1404. In some aspects, communication manager 1408 may include a communication manager 1408 in conjunction with receiving component 1402 and / or transmitting component 1404. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. The communication manager 1408 may be or be similar to Figure 1 and Figure 2For example, in some aspects, the communications manager 1408 can be configured to perform one or more of the functions described as being performed by the communications manager 140. In some aspects, the communications manager 1408 can include a receiving component 1402 and / or a sending component 1404. The communications manager 1408 can include a monitoring component 1410, among other things.
[0190] In some aspects, the apparatus 1400 may be configured to perform Figures 1 to 9 Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig.11 The process of 1000 Fig.12 In some aspects, Fig.14 The device 1400 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.14 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0191] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1400. In some aspects, the receiving component 1402 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.
[0192] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.
[0193] In some aspects, receiving component 1402 can receive an indication of a timing of a DRX On Duration opportunity associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream. Monitoring component 1410 can monitor communications of the first data stream and the second data stream at the DRX On Duration opportunity. Monitoring component 1410 can monitor communications at one or more time slots before or after the DRX On Duration opportunity.
[0194] In some aspects, receiving component 1402 can receive an indication of a timing of a DRX On Duration opportunity associated with a greater of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream. Monitoring component 1410 can monitor communications of the first data stream and the second data stream at the DRX On Duration opportunity.
[0195] Fig.14 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.14 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.14 Two or more components shown may be implemented in a single component, or Fig.14 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The illustrated set (one or more) of components may be described as being executable by Fig.14 Another group of components shown performs one or more functions.
[0196] Fig.151 is a diagram of an example apparatus 1500 for wireless communication. Apparatus 1500 may be a network entity (e.g., base station 110, network entity 910), or a network entity may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a transmitting component 1504 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and transmitting component 1504. As further shown, apparatus 1500 may include a communication manager 1508. Communication manager 1508 may control and / or otherwise manage one or more operations of receiving component 1502 and / or transmitting component 1504. In some aspects, communication manager 1508 may include a communication manager 1508 in conjunction with receiving component 1502 and / or transmitting component 1504. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network entities. The communication manager 1508 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1508 can be configured to perform one or more of the functions described as being performed by the communication manager 1508. In some aspects, the communication manager 1508 can include a receiving component 1502 and / or a sending component 1504. The communication manager 1508 can include a timing component 1510, among other things.
[0197] In some aspects, the apparatus 1500 may be configured to perform Figures 1 to 9 Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.11 Process 1100, Fig.13 In some aspects, Fig.15 The device 1500 and / or one or more components shown may include a combination of Figure 2 One or more components of the network entity. Additionally or alternatively, Fig.15 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0198] The receiving component 1502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1506. The receiving component 1502 may provide the received communications to one or more other components of the device 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1500. In some aspects, the receiving component 1502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network entity.
[0199] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network entity. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.
[0200] In some aspects, the transmitting component 1504 may transmit an indication of the timing of the DRX on duration opportunity, the timing associated with a combination of a first DRX cycle having a first periodicity for the first data stream and a second DRX cycle having a second periodicity for the second data stream. The timing component 1510 may generate the timing based on UE capabilities, channel conditions, or traffic conditions (e.g., number of XR streams, amount of data in each XR stream, periodicity of the XR streams). The transmitting component 1504 may transmit communications of the first data stream and the second data stream at the DRX on duration opportunity.
[0201] In some aspects, the transmitting component 1504 may transmit an indication of the timing of the DRX on duration opportunity, the timing being associated with the greater of the first periodicity of the first DRX cycle of the first data stream or the second periodicity of the second DRX cycle of the second data stream. The timing component 1510 may generate the timing based on UE capabilities, channel conditions, or traffic conditions (e.g., the number of XR streams, the amount of data in each XR stream, the periodicity of the XR streams). The transmitting component 1504 may transmit communications of the first data stream and the second data stream at the DRX on duration opportunity.
[0202] Fig.15 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.15 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.15 Two or more components shown may be implemented in a single component, or Fig.15 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 The illustrated set (one or more) of components may be described as being executable by Fig.15 Another group of components shown performs one or more functions.
[0203] Burst traffic (such as XR traffic, VR traffic, and other similar types of traffic) is particularly sensitive to latency. Using dynamic grant (DG) to configure the sending and receiving of burst traffic consumes a lot of power, processing resources, and network overhead. Compared with DG, using SPS (for downlink) and CG (for uplink) to configure the sending and receiving of burst traffic saves power, processing resources, and network overhead. However, too long SPS timing and CG timing result in a waste of power and processing resources for any one device being received, while too short SPS timing and CG timing increase latency.
[0204] Some techniques and apparatuses described herein enable a network entity (e.g., network entity 1601, base station 110, CU 310, DU 330, RU 340, and / or Fig.25 The device 2500 is capable of configuring an SPS opportunity with multiple PDSCHs and a CG opportunity with multiple PUSCHs. Therefore, the network entity can configure longer SPS opportunities and CG opportunities to reduce the delay of burst traffic sent during the SPS opportunities and CG opportunities.
[0205] Additionally, in some aspects, when the network entity 1601 indicates that some PDSCHs in the SPS opportunities may be skipped, the UE (eg, Fig.24UE 120 and / or device 2400) saves power and processing resources. Similarly, when UE 120 indicates that some PUSCHs in the CG opportunity can be skipped, network entity 1601 saves processing resources and network overhead. Additionally or alternatively, network entity 1601 can configure the characteristics (e.g., MCS) of each PDSCH and each PUSCH separately. Therefore, network entity 1601 can increase the reliability and / or quality of traffic sent during SPS opportunities and CG opportunities.
[0206] Fig.16 1 is a diagram illustrating an example 1600 associated with using multiple channels for SPS opportunities according to the present disclosure. Fig.16 As shown, the network entity 1601 (eg, RU 340 and / or a device controlling RU 340, such as CU 310 and / or DU 330) and UE 120 may communicate with each other (eg, over a wireless network, such as Figure 1 wireless network 100).
[0207] As indicated by reference numeral 1605, the network entity 1601 may send (e.g., directly or via the RU 340 controlled by the network entity 1601) and the UE 120 may receive a configuration associated with the SPS indicating a plurality of PDSCHs within each SPS opportunity of the UE 120. For example, as described in conjunction with Figure 5 As described, each SPS opportunity may include multiple PDSCHs to allow the network entity 1601 to send burst traffic (eg, XR packets, VR packets, and / or other types of packets) to the UE 120 .
[0208] In some aspects, the configuration may be included in an RRC message. For example, the network entity 1601 may encode the configuration in an SPS-Config data structure as defined in a 3GPP specification and / or another standard. In some aspects, the configuration may indicate periodicity based on frames per second (fps) (e.g., in a periodicity data structure as defined in a 3GPP specification and / or another standard). For example, when associated with traffic characterized by 60 fps, the configuration may indicate a periodicity of 16.67 milliseconds (ms). Similarly, when associated with traffic characterized by 120 fps, the configuration may indicate a periodicity of 8.33 ms.
[0209] Thus, the network entity 1601 may determine the configuration based at least in part on one or more traffic statistics associated with multiple packets to be sent using multiple PDSCHs. For example, the network entity 1601 may determine the periodicity based on a periodicity associated with the multiple packets (e.g., fps associated with the multiple packets). Additionally or alternatively, the network entity 1601 may determine the size of each PDSCH (e.g., the number of symbols in time and / or the number of resource blocks (RBs) in frequency) based on an average size or median size of packets within the multiple packets. Additionally or alternatively, the network entity 1601 may determine the length of each SPS opportunity (e.g., the number of symbols in time) based on an average number of packets in each burst associated with the multiple packets and / or an average total size of each burst.
[0210] Each PDSCH may be associated with a single transport block (TB). As used herein, a "transport block" refers to a data payload passed from a higher layer (e.g., a MAC layer of UE 120) to a lower layer (e.g., a PHY layer of UE 120). A TB may include a portion of a packet from a plurality of packets to be sent, a single packet, or multiple packets.
[0211] In addition, each of the multiple PDSCHs is associated with a corresponding MCS, a corresponding redundancy version (RV), and a corresponding start and length indicator value (SLIV). Therefore, the network entity 1601 may assign different MCSs to different PDSCHs in the same SPS opportunity (e.g., using different mcs-Table data structures as defined in the 3GPP specification and / or another standard). Similarly, the network entity 1601 may assign different RVs to different PDSCHs in the same SPS opportunity. Therefore, some PDSCHs may be associated with greater reliability, while other PDSCHs are associated with greater throughput, depending on the associated MCS. Similarly, the network entity 1601 may assign different SLIVs to different PDSCHs in the same SPS opportunity. Therefore, some PDSCHs may be able to carry a larger payload than other PDSCHs.
[0212] In addition, each SPS opportunity is associated with a maximum number of PDSCHs. For example, the network entity 1601 may indicate a maximum number of PDSCHs for the UE 120 to monitor during each SPS opportunity. As described below, the network entity 1601 may use less than the maximum number of PDSCHs.
[0213] Thus, as indicated by reference numeral 1610, the network entity 1601 may send (e.g., directly or via a RU 340 controlled by the network entity 1601) and the UE 120 may receive activation of the SPS configuration. For example, the network entity 1601 may use downlink control information (DCI) and / or a MAC control element (MAC CE) to activate the SPS opportunity associated with the configuration.
[0214] For example, as indicated by reference numeral 1615, the network entity 1601 may activate an SPS configuration to queue traffic (e.g., burst traffic, such as XR packets, VR packets, and / or similar packets) for multiple PDSCHs in each SPS opportunity. Thus, the network entity 1601 may encode multiple packets across TBs for transmission on the PDSCH. As indicated by reference numeral 1620, the network entity 1601 may transmit (e.g., directly or via a RU 340 controlled by the network entity 1601) and the UE 120 may receive multiple packets on multiple PDSCHs in at least one SPS opportunity associated with the SPS configuration.
[0215] In addition, UE 120 may send and network entity 1601 may receive (e.g., directly or via RU 340 controlled by network entity 1601) multiple confirmation signals (e.g., confirmation (ACK) signals and / or negative confirmation (NACK) signals) associated with multiple packets. In some aspects, UE 120 may multiplex the confirmation signals into a single physical uplink control channel (PUCCH). For example, the PUCCH may be indicated in an SPS configuration (e.g., as described in conjunction with reference numeral 1605) or in an SPS activation (e.g., as described in conjunction with reference numeral 1610).
[0216] Based on receiving one or more NACK signals, network entity 1601 may send (e.g., directly or via RU 340 controlled by network entity 1601) and UE 120 may receive a dynamic grant (DG) for receiving one or more packets of the plurality of packets. Thus, according to the DG, network entity 1601 may retransmit (e.g., directly or via RU 340 controlled by network entity 1601) and UE 120 may receive the one or more packets. Thus, the retransmission to UE 120 may be performed outside of an SPS opportunity.
[0217] In some aspects, as shown by reference numeral 1625a, the network entity 1601 may send (e.g., directly or via an RU 340 controlled by the network entity 1601) and the UE 120 may receive an indication associated with skipping one or more of the plurality of PDSCHs within at least one SPS opportunity. For example, the queue associated with the one or more PDSCHs may be empty. In some aspects, the indication may be sent via a DMRS, a PDCCH, and / or a PDSCH, such as in conjunction with Figure 5 Thus, as shown by reference numeral 1630a, during one or more PDSCHs, the UE 120 may avoid monitoring and the network entity 1601 may avoid transmitting, which saves power and processing resources.
[0218] Additionally or alternatively, as indicated by reference numeral 1625b, the network entity 1601 may send (e.g., directly or via an RU 340 controlled by the network entity 1601) and the UE 120 may receive an indication associated with adding one or more additional PDSCHs within at least one SPS opportunity. For example, the queue associated with the SPS opportunity may include data. In some aspects, the indication may be sent via a DMRS, a PDCCH, and / or a PDSCH, such as in conjunction with Figure 5 Thus, as shown by reference numeral 1630b, during one or more additional PDSCHs, UE 120 may monitor and network entity 1601 may transmit, which reduces latency associated with data still in the queue.
[0219] Additionally or alternatively, as further indicated by reference numeral 1625b, the network entity 1601 may send (e.g., directly or via an RU 340 controlled by the network entity 1601) and the UE 120 may receive an indication associated with modifying a characteristic of one or more of the plurality of PDSCHs within at least one SPS opportunity. For example, the network entity 1601 may attempt to increase reliability, quality, and / or throughput associated with the one or more PDSCHs. In some aspects, the indication may be sent via a DMRS, a PDCCH, and / or a PDSCH, such as in conjunction with Figure 5 Thus, as shown by reference numeral 1630b, based on the modified characteristics, during one or more PDSCHs, the UE 120 may monitor and the network entity 1601 may transmit.
[0220] By using such as combining Fig.16With the described techniques, the network entity 1601 may configure an SPS opportunity with multiple PDSCHs. Therefore, the network entity 1601 may configure a longer SPS opportunity to reduce the latency of burst traffic sent during the SPS opportunity. In addition, in some aspects, when the network entity 1601 indicates that some PDSCHs in the SPS opportunity can be skipped, the UE 120 saves power and processing resources. Additionally or alternatively, the network entity 1601 may configure the characteristics (e.g., MCS) of each PDSCH separately. Therefore, the network entity 1601 may increase the reliability and / or quality of traffic sent during the SPS opportunity.
[0221] As indicated above, Fig.16 Other examples can be found in the Fig.16 The examples described are different.
[0222] Fig.17 1 is a diagram illustrating an example 1700 associated with using multiple channels for SPS opportunities according to the present disclosure. Fig.17 As shown, example 1700 includes a plurality of downlink packets encoding XR traffic (or another type of burst traffic) (e.g., for transmission from network entity 1601 to UE 120). Network entity 1601 may queue downlink packets for transmission in TBs associated with SPS opportunities (e.g., SPS opportunity 1701a, SPS opportunity 1701b, etc. in example 1700). In some aspects, XR traffic may be associated with a periodicity such that network entity 1601 selects a corresponding periodicity for the SPS opportunity (e.g., a closest periodicity from a plurality of possible periodicities).
[0223] like Fig.17 As further shown, each SPS opportunity 1701 includes multiple PDSCHs. In example 1700, each SPS opportunity 1701 includes PDSCH 1703-1, PDSCH 1703-2, ..., PDSCH 1703-(N-2), PDSCH 1703-(N-1), and PDSCH 1703-N, where N is a positive integer representing the number of PDSCHs per SPS opportunity.
[0224] In some aspects, the network entity 1601 may send an indication 1705 for skipping one or more PDSCHs. In example 1700, PDSCH 1703-N is skipped based on the indication 1705 sent on PDSCH 1703-(N-1). The indication 1705 may identify a specific PDSCH to be skipped, command the UE 120 to skip a subsequent number of PDSCHs after the indication 1705, command the UE 120 to skip a pattern of PDSCHs after the indication 1705 (e.g., all PDSCHs associated with even symbols and / or time slot indices or all PDSCHs associated with odd symbols and / or time slot indices, etc.). The PDSCH to be skipped may be in the same SPS timing as the SPS timing at which the indication 1705 is sent or in a different SPS timing. The indication 1705 may be included in the DMRS of the PDSCH (e.g., PDSCH 1703-(N-1) in example 1700) (e.g., by selecting a specific sequence for encoding the DMRS). Additionally or alternatively, indication 1705 may be sent as a MACCE on a PDSCH (e.g., PDSCH 1703-(N-1) in Example 1700) or as a DCI carried on a PDSCH (e.g., PDSCH 1703-(N-1) in Example 1700). Additionally or alternatively, indication 1705 may be sent as a DCI on a PDCCH (e.g., a PDCCH during an SPS opportunity 1701a in Example 1700).
[0225] Alternatively, indication 1705 may add one or more PDSCHs. Indication 1705 may identify a specific PDSCH to be added, command UE 120 to monitor a specific number of PDSCHs after indication 1705, and command UE 120 to monitor a pattern of PDSCHs after indication 1705. The PDSCH to be added may be in the same SPS timing as the SPS timing at which indication 1705 is sent or in a different SPS timing. Indication 1705 may be included in the DMRS of the PDSCH (e.g., by selecting a specific sequence for encoding the DMRS). Additionally or alternatively, indication 1705 may be sent as a MAC CE on a PDSCH (e.g., PDSCH 1703-(N-1) in Example 1700) or as a DCI carried on a PDSCH (e.g., PDSCH 1703-(N-1) in Example 1700). Additionally or alternatively, the indication 1705 may be sent as a DCI on a PDCCH (eg, the PDCCH during the SPS opportunity 1701a in example 1700).
[0226] Additionally or alternatively, indication 1705 may modify one or more PDSCHs in the PDSCH. For example, indication 1705 may modify MCS, RV, SLIV and / or another similar characteristic of the PDSCH. The PDSCH to be modified may be in the same SPS timing as the SPS timing at which indication 1705 is sent or in a different SPS timing. Indication 1705 may be included in the DMRS of the PDSCH (e.g., by selecting a specific sequence for encoding the DMRS). Additionally or alternatively, indication 1705 may be sent as a MAC CE on a PDSCH (e.g., PDSCH 1703-(N-1) in Example 1700) or as a DCI carried on a PDSCH (e.g., PDSCH 1703-(N-1) in Example 1700). Additionally or alternatively, indication 1705 may be sent as a DCI on a PDCCH (e.g., a PDCCH during SPS timing 1701a in Example 1700).
[0227] As indicated above, Fig.17 Other examples can be found in the Fig.17 The examples described are different.
[0228] Fig.18 1 is a diagram illustrating an example 1800 associated with using multiple channels for CG opportunities according to the present disclosure. Fig.18 As shown, the network entity 1601 (eg, RU 340 and / or a device controlling RU 340, such as CU 310 and / or DU 330) and UE 120 may communicate with each other (eg, over a wireless network, such as Figure 1 wireless network 100).
[0229] As indicated by reference numeral 1805, the network entity 1601 may send (e.g., directly or via the RU 340 controlled by the network entity 1601) and the UE 120 may receive a configuration associated with the CG indicating a plurality of PUSCHs within each CG opportunity of the UE 120. For example, as shown in conjunction with Fig.19 As described, each CG opportunity may include multiple PUSCHs to allow UE 120 to send burst traffic (e.g., XR packets, VR packets, and / or other types of packets) to network entity 1601.
[0230] In some aspects, the configuration may be included in an RRC message. For example, the network entity 1601 may encode the configuration in a ConfiguredGrantConfig data structure as defined in a 3GPP specification and / or another standard. In some aspects, the configuration may indicate a periodicity based on fps (e.g., in a periodicity data structure as defined in a 3GPP specification and / or another standard). For example, when associated with traffic characterized by 60 fps, the configuration may indicate a periodicity of 16.67 ms. Similarly, when associated with traffic characterized by 120 fps, the configuration may indicate a periodicity of 8.33 ms.
[0231] Thus, the UE 120 may request the configuration based at least in part on one or more traffic statistics associated with multiple packets to be sent using multiple PUSCHs. For example, the UE 120 may request the periodicity based on a periodicity associated with the multiple packets (e.g., fps associated with the multiple packets). Additionally or alternatively, the UE 120 may request the size of each PUSCH (e.g., the number of symbols in time and / or the number of RBs in frequency) based on an average size or median size of packets within the multiple packets. Additionally or alternatively, the UE 120 may request the length of each CG opportunity (e.g., the number of symbols in time) based on an average number of packets in each burst associated with the multiple packets and / or an average total size of each burst.
[0232] Each PUSCH may be associated with a single TB. In addition, each PUSCH in the multiple PUSCHs is associated with a corresponding MCS and a corresponding number of RBs. As used herein, a "resource block" or "RB" may refer to one or more subcarriers (e.g., each subcarrier may include one or more frequencies), which may be continuous in the frequency domain. Thus, an RB may include multiple resource elements (REs), each of which corresponds to a single subcarrier. In addition, each RE may correspond to a single symbol in the time domain (e.g., an OFDM symbol and / or another symbol according to a multiplexing scheme used by the network entity 1601 and / or the RU 340 controlled by the network entity 1601).
[0233] Thus, the network entity 1601 may assign different MCSs to different PUSCHs in the same CG opportunity (e.g., using different mcs-Table data structures as defined in the 3GPP specification and / or another standard). Thus, some PUSCHs may be associated with greater reliability, while other PUSCHs may be associated with greater throughput, depending on the associated MCS. Similarly, the network entity 1601 may assign different numbers of RBs to different PUSCHs in the same CG opportunity (e.g., using different rbg-Size data structures as defined in the 3GPP specification and / or another standard). Thus, some PUSCHs may be able to carry a larger payload than other PUSCHs.
[0234] In addition, each CG opportunity is associated with a maximum number of PUSCHs. For example, the network entity 1601 may indicate a maximum number of PUSCHs for use by the UE 120 during each SPS opportunity. As described below, the UE 120 may use less than the maximum number of PUSCHs.
[0235] Thus, as indicated by reference numeral 1810, the network entity 1601 may send (e.g., directly or via RU 340 controlled by the network entity 1601) and the UE 120 may receive activation of the CG configuration. For example, the network entity 1601 may use DCI and / or MAC CE to activate the CG opportunity associated with the configuration.
[0236] For example, as shown by reference numeral 1815, the network entity 1601 may activate a CG configuration so that the UE 120 may queue traffic (e.g., burst traffic, such as XR packets, VR packets, and / or similar packets) for multiple PUSCHs in each CG opportunity. Thus, the UE 120 may encode multiple packets across TBs for transmission on the PUSCH. As shown by reference numeral 1820, the UE 120 may transmit and the network entity 1601 may receive (e.g., directly or via a RU 340 controlled by the network entity 1601) multiple packets on multiple PUSCHs in at least one CG opportunity associated with the CG configuration.
[0237] When network entity 1601 does not receive one or more packets, network entity 1601 may send (e.g., directly or via RU 340 controlled by network entity 1601) and UE 120 may receive a DG for retransmitting one or more packets of the plurality of packets. Thus, according to the DG, UE 120 may retransmit and network entity 1601 may receive (e.g., directly or via RU 340 controlled by network entity 1601) one or more packets. Thus, retransmission to network entity 1601 may be performed outside of a CG opportunity.
[0238] In some aspects, as shown by reference numeral 1825a, UE 120 may send and network entity 1601 may receive (e.g., directly or via RU 340 controlled by network entity 1601) an indication associated with skipping one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity. For example, a queue associated with one or more PUSCHs may be empty. In some aspects, the indication may be sent via DMRS, PUCCH, and / or PUSCH, such as in conjunction with Fig.19 Thus, as shown by reference numeral 1830a, during one or more PUSCHs, the network entity 1601 may refrain from monitoring (or instruct the RU 340 to refrain from monitoring), and the UE 120 may refrain from transmitting, which saves power and processing resources.
[0239] Additionally or alternatively, as indicated by reference numeral 1825b, UE 120 may send and network entity 1601 may receive (e.g., directly or via RU 340 controlled by network entity 1601) a request associated with adding one or more additional PUSCHs within at least one CG opportunity. For example, the queue associated with the CG opportunity may include data. In some aspects, the request may be sent via DMRS, PUCCH, and / or PUSCH, such as in conjunction with Fig.19 Thus, the network entity 1601 may send (e.g., directly or via a RU 340 controlled by the network entity 1601) and the UE 120 may receive an approval of the request such that, as indicated by reference numeral 1830b, during one or more additional PUSCHs, the UE 120 may send and the network entity 1601 may monitor, which reduces latency associated with data still in the queue.
[0240] Additionally or alternatively, as further indicated by reference numeral 1825b, the UE 120 may send and the network entity 1601 may receive (e.g., directly or via an RU 340 controlled by the network entity 1601) a request associated with modifying characteristics of one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity. For example, the UE 120 may attempt to increase reliability, quality, and / or throughput associated with one or more PUSCHs. In some aspects, the indication may be sent via a DMRS, a PUCCH, and / or a PUSCH, such as in conjunction with Fig.19 Thus, the network entity 1601 may send (e.g., directly or via a RU 340 controlled by the network entity 1601) and the UE 120 may receive an approval of the request such that, based on the modified characteristics, during one or more PUSCHs, the UE 120 may send and the network entity 1601 may monitor, as indicated by reference numeral 1830b.
[0241] By using such as combining Fig.18 With the described techniques, the network entity 1601 may configure a CG opportunity with multiple PUSCHs. Thus, the network entity 1601 may configure a longer CG opportunity to reduce the latency of burst traffic sent during the CG opportunity. In addition, in some aspects, when the UE 120 indicates that some PUSCHs in the CG opportunity can be skipped, the network entity 1601 saves network overhead and processing resources. Additionally or alternatively, the network entity 1601 may configure the characteristics (e.g., MCS) of each PUSCH individually. Thus, the network entity 1601 may increase the reliability and / or quality of traffic sent during the CG opportunity.
[0242] As indicated above, Fig.18 Other examples can be found in the Fig.18 The examples described are different.
[0243] Fig.19 1 is a diagram illustrating an example 1900 associated with using multiple channels for CG opportunities according to the present disclosure. Fig.19 As shown, example 1900 includes a plurality of uplink packets encoding XR traffic (or another type of burst traffic) (e.g., for transmission from UE 120 to network entity 1601). UE 120 may queue uplink packets for transmission in TBs associated with CG opportunities (e.g., CG opportunity 1901a, CG opportunity 1901b, etc. in example 1900). In some aspects, XR traffic may be associated with a periodicity such that UE 120 requests a corresponding periodicity (e.g., a closest periodicity from a plurality of possible periodicities) for the CG opportunity.
[0244] like Fig.19 As further shown, each CG opportunity 1901 includes multiple PUSCHs. In example 1900, each CG opportunity 1901 includes PUSCH 1903-1, PUSCH 1903-2, PUSCH 1903-3, ..., PUSCH 1903-(M-2), PUSCH 1903-(M-1), and PUSCH 1903-N, where M is a positive integer representing the number of PUSCHs per CG opportunity.
[0245] In some aspects, UE 120 may send an indication 1905 for skipping one or more PUSCHs. In example 1900, PUSCH 1903-(M-1) and PUSCH 1903-M are skipped based on indication 1905 sent on PUSCH 1903-3. Fig.19As further shown, UE 120 may send indication 1905 in advance in time based on the amount of time T for how long network entity 1601 needs to process indication 1905 to meet a threshold (e.g., the threshold may be indicated by network entity 1601 and / or configured based on a standard such as a 3GPP specification). Indication 1905 may identify a specific PUSCH to be skipped, command network entity 1601 to skip a subsequent number of PUSCHs after indication 1905, command network entity 1601 to skip a pattern of PUSCHs after indication 1905 (e.g., all PUSCHs associated with even symbols and / or time slot indices or all PUSCHs associated with odd symbols and / or time slot indices, etc.). The PUSCH to be skipped may be in the same CG timing as the CG timing at which indication 1905 is sent or in a different CG timing. Indication 1905 may be included in the DMRS of a PUSCH (e.g., PUSCH 1903-3 in example 1900) (e.g., by selecting a specific sequence for encoding the DMRS). Additionally or alternatively, the indication 1905 may be sent as a MAC CE on a PUSCH (e.g., PUSCH 1903-3 in Example 1900) or as uplink control information (UCI) carried on a PUSCH (e.g., PUSCH 1903-3 in Example 1900). Additionally or alternatively, the indication 1905 may be sent as UCI on a PUCCH (e.g., PUCCH during CG opportunity 1901a in Example 1900).
[0246] Alternatively, indication 1905 may request the addition of one or more PUSCHs. Indication 1905 may identify a specific PUSCH to be added, request network entity 1601 to approve a specific number of PUSCHs after indication 1905, and request network entity 1601 to approve a pattern of PUSCHs after indication 1905. The PUSCH to be added may be in the same CG timing as the CG timing at which indication 1905 is sent or in a different CG timing. Indication 1905 may be included in the DMRS of the PUSCH (e.g., by selecting a specific sequence for encoding the DMRS). Additionally or alternatively, indication 1905 may be sent as a MAC CE on a PUSCH (e.g., PUSCH 1903-3 in Example 1900) or as UCI carried on a PUSCH (e.g., PUSCH 1903-3 in Example 1900). Additionally or alternatively, indication 1905 may be sent as UCI on a PUCCH (e.g., PUCCH during CG opportunity 1901a in Example 1900).
[0247] Additionally or alternatively, indication 1905 may request modification of one or more PUSCHs in the PUSCH. For example, indication 1905 may request modification of MCS, RV, SLIV and / or another similar characteristic of the PUSCH. The PUSCH to be modified may be in the same CG timing as the CG timing at which indication 1905 is sent or in a different CG timing. Indication 1905 may be included in the DMRS of the PUSCH (e.g., by selecting a specific sequence for encoding the DMRS). Additionally or alternatively, indication 1905 may be sent as a MAC CE on a PUSCH (e.g., PUSCH 1903-3 in Example 1900) or as UCI carried on a PUSCH (e.g., PUSCH 1903-3 in Example 1900). Additionally or alternatively, indication 1905 may be sent as UCI on a PUCCH (e.g., PUCCH during CG timing 1901a in Example 1900).
[0248] As indicated above, Fig.19 Other examples can be found in the Fig.19 The examples described are different.
[0249] Fig. 20 2 is a diagram illustrating an example process 2000 performed, for example, by a UE according to the present disclosure. Example process 2000 is a diagram in which a UE (e.g., UE 120 and / or Fig.24 An example of a device 2400) performing operations associated with using multiple channels within an SPS opportunity.
[0250] like Fig. 20 As shown, in some aspects, process 2000 may include receiving a configuration associated with an SPS that indicates a plurality of PDSCHs within each SPS opportunity of a UE (block 2010). For example, a UE (e.g., using Fig.24 The depicted communications manager 140 and / or receiving component 2402) may receive a configuration associated with SPS indicating a plurality of PDSCHs within each SPS opportunity for a UE, as described herein.
[0251] like Fig. 20 As further shown, in some aspects, process 2000 may include receiving a plurality of packets across a plurality of PDSCHs within at least one SPS opportunity of the UE (block 2020). For example, the UE (e.g., using communication manager 140 and / or receiving component 2402) may receive a plurality of packets across a plurality of PDSCHs within at least one SPS opportunity of the UE, as described above.
[0252] Process 2000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0253] In a first aspect, the plurality of packets include one or more XR packets, one or more VR packets, or a combination thereof.
[0254] In a second aspect, either alone or in combination with the first aspect, process 2000 also includes receiving (e.g., using communication manager 140 and / or receiving component 2402) a configuration associated with a DG for retransmitting one or more packets of a plurality of packets, and receiving (e.g., using communication manager 140 and / or receiving component 2402) one or more retransmissions of the one or more packets based on the DG.
[0255] In a third aspect, alone or in combination with one or more of the first and second aspects, each PDSCH of the plurality of PDSCHs is associated with a single TB.
[0256] In a fourth aspect, alone or in combination with one or more of the first to third aspects, each PDSCH of the plurality of PDSCHs is associated with a corresponding MCS, a corresponding RV, and a corresponding SLIV.
[0257] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, each SPS opportunity is associated with a maximum number of PDSCHs.
[0258] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the process 2000 also includes receiving (e.g., using the communication manager 140 and / or the receiving component 2402) an indication associated with skipping one or more PDSCHs of a plurality of PDSCHs within at least one SPS opportunity, and avoiding monitoring during the one or more PDSCHs (e.g., using Fig.24 Communications manager 140 and / or monitoring component 2408 as depicted).
[0259] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 2000 also includes receiving (e.g., using communications manager 140 and / or receiving component 2402) an indication associated with adding one or more additional PDSCHs within at least one SPS opportunity, and monitoring (e.g., using communications manager 140 and / or monitoring component 2408) during one or more additional PDSCHs.
[0260] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 2000 also includes receiving (e.g., using communications manager 140 and / or receiving component 2402) an indication associated with modifying characteristics of one or more of a plurality of PDSCHs within at least one SPS opportunity, and monitoring (e.g., using communications manager 140 and / or monitoring component 2408) during one or more PDSCHs based on the modified characteristics.
[0261] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the process 2000 further comprises sending (e.g., using Fig.24 The depicted communication manager 140 and / or transmitting component 2404) is associated with multiple packets, multiplexed into a single PUCCH.
[0262] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the configuration indicates a periodicity of 16.67 ms or 8.33 ms.
[0263] although Fig. 20 An example block diagram of process 2000 is shown, but in some aspects, process 2000 may include Fig. 20 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 2000 may be performed in parallel.
[0264] Fig.21 21 is a diagram illustrating an example process 2100 performed, for example, by a network entity according to the present disclosure. The example process 2100 is a diagram in which a network entity (e.g., network entity 1601 and / or Fig.25 An example of a device 2500) performing operations associated with using multiple channels within an SPS opportunity.
[0265] like Fig.21 As shown, in some aspects, process 2100 may include sending a configuration associated with the SPS, the configuration indicating that the UE (e.g., UE 120 and / or Fig.24 For example, a network entity (e.g., using Fig.25 The depicted communication manager 150 and / or transmitting component 2504) may transmit a configuration associated with SPS indicating a plurality of PDSCHs within each SPS opportunity for the UE, as described herein.
[0266] like Fig.21As further shown, in some aspects, process 2100 may include sending a plurality of packets across a plurality of PDSCHs within at least one SPS opportunity of the UE (block 2120). For example, a network entity (e.g., using Fig.25 The depicted communication manager 150 and / or transmitting component 2504) may transmit multiple packets across multiple PDSCHs within at least one SPS opportunity of the UE, as described herein.
[0267] Process 2100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0268] In a first aspect, the plurality of packets include one or more XR packets, one or more VR packets, or a combination thereof.
[0269] In a second aspect, either alone or in combination with the first aspect, process 2100 also includes sending (e.g., using communication manager 150 and / or sending component 2504) a configuration associated with a DG for retransmitting one or more of a plurality of packets, and retransmitting (e.g., using communication manager 150 and / or sending component 2504) one or more packets based on the DG.
[0270] In a third aspect, alone or in combination with one or more of the first and second aspects, each PDSCH of the plurality of PDSCHs is associated with a single TB.
[0271] In a fourth aspect, alone or in combination with one or more of the first to third aspects, each PDSCH of the plurality of PDSCHs is associated with a corresponding MCS, a corresponding RV, and a corresponding SLIV.
[0272] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, each SPS opportunity is associated with a maximum number of PDSCHs.
[0273] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the process 2100 also includes sending (e.g., using the communication manager 150 and / or the sending component 2504) an indication associated with skipping one or more of the multiple PDSCHs within at least one SPS opportunity, and avoiding sending (e.g., using) during one or more PDSCHs. Fig.25 Communications manager 150 and / or scheduling component 2508 as depicted).
[0274] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 2100 also includes sending (e.g., using communication manager 150 and / or sending component 2504) an indication associated with adding one or more additional PDSCHs within at least one SPS opportunity, and sending (e.g., using communication manager 150 and / or sending component 2504) during one or more additional PDSCHs.
[0275] In an eighth aspect, either alone or in combination with one or more of aspects one to seven, process 2100 further includes sending (e.g., using communication manager 150 and / or sending component 2504) an indication associated with modifying characteristics of one or more of a plurality of PDSCHs within at least one SPS opportunity, and transmitting during one or more PDSCHs based on the modified characteristics (e.g., using communication manager 150 and / or sending component 2504).
[0276] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the process 2100 further comprises receiving (e.g., using Fig.25 The depicted communications manager 150 and / or receiving component 2502) is associated with multiple packets, multiplexed into a single PUCCH, for multiple acknowledgment signals.
[0277] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 2100 further comprises determining (e.g., using Fig.25 The communications manager 150 and / or determination component 2510) is depicted as being configured.
[0278] although Fig.21 An example block diagram of process 2100 is shown, but in some aspects, process 2100 may include Fig.21 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 2100 may be performed in parallel.
[0279] Fig. 22 2200 is a diagram illustrating an example process 2200 performed, for example, by a UE according to the present disclosure. The example process 2200 is a diagram in which a UE (e.g., UE 120 and / or Fig.24 An example of a device 2400) performing operations associated with using multiple channels within a CG opportunity.
[0280] like Fig. 22As shown, in some aspects, process 2200 may include receiving a configuration associated with a CG, the configuration indicating a plurality of PUSCHs within each CG opportunity of the UE (block 2210). For example, a UE (e.g., using Fig.24 The depicted communications manager 140 and / or receiving component 2402) may receive a configuration associated with a CG indicating multiple PUSCHs within each CG opportunity for the UE, as described herein.
[0281] like Fig. 22 As further shown, in some aspects, process 2200 may include sending multiple packets across multiple PUSCHs within at least one CG opportunity of the UE (block 2220). For example, a UE (e.g., using Fig.24 The depicted communication manager 140 and / or sending component 2404) may send multiple packets across multiple PUSCHs within at least one CG opportunity of the UE, as described herein.
[0282] Process 2200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0283] In a first aspect, the plurality of packets include one or more XR packets, one or more VR packets, or a combination thereof.
[0284] In a second aspect, either alone or in combination with the first aspect, process 2200 also includes receiving (e.g., using communication manager 140 and / or receiving component 2402) a configuration associated with a DG for retransmitting one or more of a plurality of packets, and retransmitting (e.g., using communication manager 140 and / or sending component 2404) one or more packets based on the DG.
[0285] In a third aspect, alone or in combination with one or more of the first and second aspects, each PUSCH of the plurality of PUSCHs is associated with a single TB.
[0286] In a fourth aspect, alone or in combination with one or more of the first to third aspects, each PUSCH of the plurality of PUSCHs is associated with a corresponding MCS and a corresponding number of RBs.
[0287] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, each CG opportunity is associated with a maximum number of PUSCHs.
[0288] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 2200 also includes sending (e.g., using communication manager 140 and / or sending component 2404) an indication associated with skipping one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity, and avoiding sending (e.g., using communication manager 140 and / or sending component 2404) during one or more PUSCHs.
[0289] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 2200 also includes sending (e.g., using communication manager 140 and / or sending component 2404) a request associated with adding one or more additional PUSCHs during at least one CG opportunity; receiving (e.g., using communication manager 140 and / or receiving component 2402) approval of the request; and sending (e.g., using communication manager 140 and / or sending component 2404) during one or more additional PUSCHs.
[0290] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 2200 also includes sending (e.g., using communication manager 140 and / or sending component 2404) a request associated with modifying characteristics of one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity; receiving (e.g., using communication manager 140 and / or receiving component 2402) approval of the request; and transmitting during one or more PUSCHs based on the modified characteristics (e.g., using communication manager 140 and / or sending component 2404).
[0291] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, process 2200 further comprises sending (e.g., using communications manager 140 and / or sending component 2404) a request for the configuration based at least in part on one or more traffic statistics associated with a plurality of packets.
[0292] although Fig. 22 An example block diagram of process 2200 is shown, but in some aspects, process 2200 may include Fig. 22 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 2200 may be performed in parallel.
[0293] Fig.23 2300 is a diagram illustrating an example process 2300 performed, for example, by a network entity according to the present disclosure. The example process 2300 is a diagram in which a network entity (e.g., network entity 1601 and / or Fig.25An example of a device 2500) performing operations associated with using multiple channels within a CG opportunity.
[0294] like Fig.23 As shown, in some aspects, process 2300 may include sending a configuration associated with the CG, the configuration indicating that the UE (e.g., UE 120 and / or Fig.24 For example, a network entity (e.g., using Fig.25 The depicted communications manager 150 and / or transmitting component 2504) may transmit a configuration associated with a CG indicating multiple PUSCHs within each CG opportunity for the UE, as described herein.
[0295] like Fig.23 As further shown, in some aspects, process 2300 may include receiving a plurality of packets across a plurality of PUSCHs within at least one CG opportunity of the UE (block 2320). For example, a network entity (e.g., using Fig.25 The depicted communication manager 150 and / or receiving component 2502) may receive multiple packets across multiple PUSCHs within at least one CG opportunity of the UE, as described herein.
[0296] Process 2300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in combination with one or more other processes described elsewhere herein.
[0297] In a first aspect, the plurality of packets include one or more XR packets, one or more VR packets, or a combination thereof.
[0298] In a second aspect, either alone or in combination with the first aspect, process 2300 also includes sending (e.g., using communication manager 150 and / or sending component 2504) a configuration associated with a DG for retransmitting one or more packets of a plurality of packets, and receiving (e.g., using communication manager 150 and / or receiving component 2502) one or more retransmissions of the one or more packets based on the DG.
[0299] In a third aspect, alone or in combination with one or more of the first and second aspects, each PUSCH of the plurality of PUSCHs is associated with a single TB.
[0300] In a fourth aspect, alone or in combination with one or more of the first to third aspects, each PUSCH of the plurality of PUSCHs is associated with a corresponding MCS and a corresponding number of RBs.
[0301] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, each CG opportunity is associated with a maximum number of PUSCHs.
[0302] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the process 2300 also includes receiving (e.g., using the communication manager 150 and / or the receiving component 2502) an indication associated with skipping one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity, and avoiding monitoring during the one or more PUSCHs (e.g., using Fig.25 Communications manager 150 and / or scheduling component 2508 as depicted).
[0303] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, process 2300 also includes receiving (e.g., using communication manager 150 and / or receiving component 2502) a request associated with adding one or more additional PUSCHs during at least one CG opportunity; sending (e.g., using communication manager 150 and / or sending component 2504) an approval of the request; and receiving (e.g., using communication manager 150 and / or receiving component 2502) during one or more additional PUSCHs.
[0304] In an eighth aspect, either alone or in combination with one or more of aspects 1 to 7, process 2300 also includes receiving (e.g., using communication manager 150 and / or receiving component 2502) a request associated with modifying characteristics of one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity; sending (e.g., using communication manager 150 and / or sending component 2504) approval of the request; and receiving (e.g., using communication manager 150 and / or receiving component 2502) during one or more PUSCHs based on the modified characteristics.
[0305] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the configuration indicates a periodicity of 16.67 ms or 8.33 ms.
[0306] although Fig.23 An example block diagram of process 2300 is shown, but in some aspects, process 2300 may include Fig.23 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 2300 may be performed in parallel.
[0307] Fig.242400. The apparatus 2400 may be a UE, or the UE may include the apparatus 2400. In some aspects, the apparatus 2400 includes a receiving component 2402 and a sending component 2404 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 2400 may communicate with another apparatus 2406 (such as a UE, a base station, or another wireless communication device) using the receiving component 2402 and the sending component 2404. As further shown, the apparatus 2400 may include a communication manager 140. The communication manager 140 may include a monitoring component 2408, etc.
[0308] In some aspects, the apparatus 2400 may be configured to perform Figures 4 to 7 Additionally or alternatively, the apparatus 2400 may be configured to perform one or more processes described herein, such as Fig. 20 The process of 2000, Fig. 22 In some aspects, Fig.24 The device 2400 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.24 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0309] The receiving component 2402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 2406. The receiving component 2402 may provide the received communications to one or more other components of the device 2400. In some aspects, the receiving component 2402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 2400. In some aspects, the receiving component 2402 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.
[0310] The transmitting component 2404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 2406. In some aspects, one or more other components of the device 2400 may generate communications and may provide the generated communications to the transmitting component 2404 for transmission to the device 2406. In some aspects, the transmitting component 2404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 2406. In some aspects, the transmitting component 2404 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 2404 can be co-located with the receive component 2402 in a transceiver.
[0311] In some aspects, receiving component 2402 may receive (e.g., from device 2406, such as a network entity) a configuration associated with SPS indicating multiple PDSCHs within each SPS opportunity of device 2400. Further, receiving component 2402 may receive multiple packets across multiple PDSCHs (e.g., from device 2406) within at least one SPS opportunity of device 2400. In some aspects, transmitting component 2404 may transmit (e.g., to device 2406) multiple acknowledgment signals associated with the multiple packets multiplexed into a single PUCCH.
[0312] In some aspects, receiving component 2402 may receive a configuration associated with a DG for retransmitting one or more packets of a plurality of packets (e.g., from device 2406). Thus, receiving component 2402 may receive one or more retransmissions of one or more packets according to the DG (e.g., from device 2406).
[0313] In some aspects, receiving component 2402 may receive (e.g., from device 2406) an indication associated with skipping one or more PDSCHs of a plurality of PDSCHs within at least one SPS opportunity. Accordingly, monitoring component 2408 may refrain from monitoring during one or more PDSCHs. Monitoring component 2408 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.
[0314] In some aspects, receiving component 2402 may receive an indication associated with adding one or more additional PDSCHs within at least one SPS opportunity (eg, from device 2406). Accordingly, monitoring component 2408 may monitor during the one or more additional PDSCHs.
[0315] In some aspects, receiving component 2402 may receive an indication associated with modifying a characteristic of one or more PDSCHs of a plurality of PDSCHs within at least one SPS opportunity (e.g., from device 2406). Accordingly, monitoring component 2408 may monitor during one or more PDSCHs based on the modified characteristic.
[0316] Additionally or alternatively, receiving component 2402 may receive (e.g., from device 2406, such as a network entity) a configuration associated with the CG indicating a plurality of PUSCHs within each CG opportunity of device 2400. Accordingly, sending component 2404 may send a plurality of packets across the plurality of PUSCHs (e.g., to device 2406) within at least one CG opportunity of device 2400. In some aspects, sending component 2404 may send (e.g., to device 2406) a request for the configuration based at least in part on one or more traffic statistics associated with the plurality of packets.
[0317] In some aspects, receiving component 2402 may receive a configuration associated with a DG for retransmitting one or more packets of a plurality of packets (eg, from device 2406). Accordingly, sending component 2404 may retransmit one or more packets according to the DG (eg, to device 2406).
[0318] In some aspects, transmitting component 2404 may transmit (e.g., to device 2406) an indication associated with skipping one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity. Thus, transmitting component 2404 may refrain from transmitting during one or more PUSCHs.
[0319] In some aspects, transmitting component 2404 may transmit (e.g., to device 2406) a request associated with adding one or more additional PUSCHs within at least one CG opportunity. Receiving component 2402 may receive (e.g., from device 2406) an approval of the request, causing transmitting component 2404 to transmit (e.g., to device 2406) during the one or more additional PUSCHs.
[0320] In some aspects, transmitting component 2404 may transmit (e.g., to device 2406) a request associated with modifying characteristics of one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity. Receiving component 2402 may receive (e.g., from device 2406) an approval of the request, causing transmitting component 2404 to transmit (e.g., to device 2406) during one or more PUSCHs based on the modified characteristics.
[0321] Fig.24 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.24Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.24 Two or more components shown may be implemented in a single component, or Fig.24 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.24 The illustrated set (one or more) of components may be described as being executable by Fig.24 Another group of components shown performs one or more functions.
[0322] Fig.25 2500. The apparatus 2500 may be a network entity, or the network entity may include the apparatus 2500. In some aspects, the apparatus 2500 includes a receiving component 2502 and a sending component 2504 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 2500 may communicate with another apparatus 2506 (such as a UE, a base station, or another wireless communication device) using the receiving component 2502 and the sending component 2504. As further shown, the apparatus 2500 may include a communication manager 150. The communication manager 150 may include one or more of a scheduling component 2508 and / or a determining component 2510, etc.
[0323] In some aspects, the apparatus 2500 may be configured to perform Figures 16 to 19 Additionally or alternatively, the apparatus 2500 may be configured to perform one or more of the processes described herein, such as Fig.21 Process 2100, Fig.23 In some aspects, Fig.25 The device 2500 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.25 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.
[0324] The receiving component 2502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 2506. The receiving component 2502 may provide the received communications to one or more other components of the device 2500. In some aspects, the receiving component 2502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 2500. In some aspects, the receiving component 2502 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described base stations.
[0325] The transmitting component 2504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 2506. In some aspects, one or more other components of the device 2500 may generate communications and may provide the generated communications to the transmitting component 2504 for transmission to the device 2506. In some aspects, the transmitting component 2504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 2506. In some aspects, the transmitting component 2504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described base stations. In some aspects, the transmit component 2504 can be co-located with the receive component 2502 in a transceiver.
[0326] In some aspects, the transmitting component 2504 may transmit (e.g., to the device 2506, such as a UE) a configuration associated with the SPS indicating a plurality of PDSCHs within each SPS opportunity of the device 2506. Thus, the transmitting component 2504 may transmit a plurality of packets across a plurality of PDSCHs within at least one SPS opportunity of the device 2506. In some aspects, the determining component 2510 may determine the configuration based at least in part on one or more traffic statistics associated with the plurality of packets. The determining component may include combining Figure 2 A MIMO detector, a receive processor, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of the described base station. In some aspects, the receiving component 2502 may receive (e.g., from the device 2506) multiple acknowledgement signals associated with multiple packets, multiplexed into a single PUCCH.
[0327] In some aspects, transmitting component 2504 may transmit a configuration associated with a DG for retransmitting one or more packets of the plurality of packets (e.g., to device 2506). Thus, transmitting component 2504 may retransmit one or more packets according to the DG (e.g., to device 2506).
[0328] In some aspects, transmitting component 2504 may transmit (e.g., to device 2506) an indication associated with skipping one or more PDSCHs of a plurality of PDSCHs within at least one SPS opportunity. Thus, scheduling component 2508 may refrain from transmitting during one or more PDSCHs. Scheduling component 2508 may include combining Figure 2 A modem, a demodulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of a base station is described.
[0329] In some aspects, transmitting component 2504 may transmit (e.g., to apparatus 2506) an indication associated with adding one or more additional PDSCHs within at least one SPS opportunity. Thus, transmitting component 2504 may transmit (e.g., to apparatus 2506) during one or more additional PDSCHs.
[0330] In some aspects, transmitting component 2504 may transmit (e.g., to apparatus 2506) an indication associated with modifying a characteristic of one or more PDSCHs of a plurality of PDSCHs within at least one SPS opportunity. Thus, transmitting component 2504 may transmit (e.g., to apparatus 2506) during one or more PDSCHs based on the modified characteristic.
[0331] Additionally or alternatively, the transmitting component 2504 can transmit (e.g., to the device 2506, such as a UE) a configuration associated with the CG, the configuration indicating multiple PUSCHs within each CG opportunity of the device 2506. Thus, the receiving component 2502 can receive multiple packets across multiple PUSCHs within at least one CG opportunity of the device 2506.
[0332] In some aspects, the sending component 2504 can send a configuration associated with a DG for retransmitting one or more packets of the plurality of packets (e.g., to the device 2506). Accordingly, the receiving component 2502 can receive one or more retransmissions of the one or more packets according to the DG (e.g., from the device 2506).
[0333] In some aspects, receiving component 2502 may receive an indication associated with skipping one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity (e.g., from device 2506). Accordingly, scheduling component 2508 may avoid monitoring during one or more PUSCHs.
[0334] In some aspects, receiving component 2502 may receive a request associated with adding one or more additional PUSCHs within at least one CG opportunity (e.g., from device 2506). Transmitting component 2504 may send (to device 2506) an approval of the request such that receiving component 2502 receives (e.g., from device 2506) during the one or more additional PUSCHs.
[0335] In some aspects, receiving component 2502 may receive (e.g., from device 2506) a request associated with modifying characteristics of one or more PUSCHs of a plurality of PUSCHs within at least one CG opportunity. Sending component 2504 may send (e.g., to device 2506) an approval of the request such that receiving component 2502 receives (e.g., from device 2506) during one or more PUSCHs based on the modified characteristics.
[0336] Fig.25 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.25 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.25 Two or more components shown may be implemented in a single component, or Fig.25 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.25 The illustrated set (one or more) of components may be described as being executable by Fig.25 Another group of components shown performs one or more functions.
[0337] The following provides an overview of some aspects of the disclosure:
[0338] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration associated with semi-persistent scheduling (SPS), the configuration indicating multiple physical downlink shared channels (PDSCHs) within each SPS opportunity of the UE; and receiving multiple packets across the multiple PDSCHs within at least one SPS opportunity of the UE.
[0339] Aspect 2: The method according to aspect 1, wherein the plurality of groups include one or more extended reality groups, one or more virtual reality groups, or a combination thereof.
[0340] Aspect 3: The method according to any one of Aspects 1 to 2 further includes: receiving a configuration associated with a dynamic grant (DG) for retransmitting one or more of the multiple packets; and receiving one or more retransmissions of the one or more packets based on the DG.
[0341] Aspect 4: The method according to any one of aspects 1 to 3, wherein each PDSCH of the plurality of PDSCHs is associated with a single transport block.
[0342] Aspect 5: The method according to any one of aspects 1 to 4, wherein each PDSCH of the plurality of PDSCHs is associated with a corresponding modulation and coding scheme, a corresponding redundancy version, and corresponding start and length indicator values.
[0343] Aspect 6: The method according to any one of aspects 1 to 5, wherein each SPS opportunity is associated with a maximum number of PDSCHs.
[0344] Aspect 7: The method according to any one of Aspects 1 to 6 also includes: receiving an indication associated with skipping one or more PDSCHs of the multiple PDSCHs within the at least one SPS opportunity; and avoiding monitoring during the one or more PDSCHs.
[0345] Aspect 8: The method according to any one of aspects 1 to 7 further includes: receiving an indication associated with adding one or more additional PDSCHs within the at least one SPS opportunity; and monitoring during the one or more additional PDSCHs.
[0346] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: receiving an indication associated with modifying characteristics of one or more PDSCHs among the multiple PDSCHs within the at least one SPS opportunity; and monitoring during the one or more PDSCHs based on the modified characteristics.
[0347] Aspect 10: The method according to any one of aspects 1 to 9 further comprises: sending a plurality of confirmation signals associated with the plurality of packets multiplexed into a single physical uplink control channel.
[0348] Aspect 11: The method according to any one of aspects 1 to 10, wherein the configuration indicates a periodicity of 16.67 milliseconds (ms) or 8.33 ms.
[0349] Aspect 12: A method of wireless communication performed by a network entity, comprising: sending a configuration associated with semi-persistent scheduling (SPS), the configuration indicating multiple physical downlink shared channels (PDSCHs) within each SPS opportunity of a user equipment (UE); and sending multiple packets across the multiple PDSCHs within at least one SPS opportunity of the UE.
[0350] Aspect 13: The method according to Aspect 12, wherein the plurality of groups include one or more extended reality groups, one or more virtual reality groups, or a combination thereof.
[0351] Aspect 14: The method according to any one of Aspects 12 to 13 further includes: sending a configuration associated with a dynamic grant (DG) for retransmitting one or more packets of the multiple packets; and retransmitting the one or more packets according to the DG.
[0352] Aspect 15: The method according to any one of aspects 12 to 14, wherein each PDSCH of the plurality of PDSCHs is associated with a single transport block.
[0353] Aspect 16: The method according to any one of aspects 12 to 15, wherein each PDSCH of the plurality of PDSCHs is associated with a corresponding modulation and coding scheme, a corresponding redundancy version, and corresponding start and length indicator values.
[0354] Aspect 17: A method according to any one of aspects 12 to 16, wherein each SPS opportunity is associated with a maximum number of PDSCHs.
[0355] Aspect 18: The method according to any one of Aspects 12 to 17 further includes: sending an indication associated with skipping one or more PDSCHs among the multiple PDSCHs within the at least one SPS opportunity; and avoiding sending during the one or more PDSCHs.
[0356] Aspect 19: The method according to any one of aspects 12 to 18 further includes: sending an indication associated with adding one or more additional PDSCHs within the at least one SPS opportunity; and sending during the one or more additional PDSCHs.
[0357] Aspect 20: The method according to any one of Aspects 12 to 19 further includes: sending an indication associated with modifying the characteristics of one or more PDSCHs among the multiple PDSCHs within the at least one SPS opportunity; and sending during the one or more PDSCHs based on the modified characteristics.
[0358] Aspect 21: The method according to any one of aspects 12 to 20 further comprises: receiving a plurality of confirmation signals associated with the plurality of packets multiplexed into a single physical uplink control channel.
[0359] Aspect 22: The method according to any one of aspects 12 to 21 further includes: determining the configuration based at least in part on one or more traffic statistics associated with the plurality of packets.
[0360] Aspect 23: A method of wireless communication performed by a user equipment (UE), comprising: receiving a configuration associated with a configuration grant (CG), the configuration indicating multiple physical uplink shared channels (PUSCHs) within each CG opportunity of the UE; and sending multiple packets across the multiple PUSCHs within at least one CG opportunity of the UE.
[0361] Aspect 24: The method according to Aspect 23, wherein the plurality of groups include one or more extended reality groups, one or more virtual reality groups, or a combination thereof.
[0362] Aspect 25: The method according to any one of Aspects 23 to 24 further includes: receiving a configuration associated with a dynamic grant (DG) for retransmitting one or more packets of the multiple packets; and retransmitting the one or more packets according to the DG.
[0363] Aspect 26: A method according to any one of aspects 23 to 25, wherein each PUSCH of the plurality of PUSCHs is associated with a single transport block.
[0364] Aspect 27: The method according to any one of aspects 23 to 26, wherein each PUSCH of the plurality of PUSCHs is associated with a corresponding modulation and coding scheme and a corresponding number of resource blocks.
[0365] Aspect 28: A method according to any one of Aspects 23 to 27, wherein each CG opportunity is associated with a maximum number of PUSCHs.
[0366] Aspect 29: The method according to any one of Aspects 23 to 28 further includes: sending an indication associated with skipping one or more PUSCHs among the multiple PUSCHs within the at least one CG opportunity; and avoiding sending during the one or more PUSCHs.
[0367] Aspect 30: The method according to any one of Aspects 23 to 29 further includes: sending a request associated with adding one or more additional PUSCHs within the at least one CG opportunity; receiving approval of the request; and sending during the one or more additional PUSCHs.
[0368] Aspect 31: The method according to any one of Aspects 23 to 30 further includes: sending a request associated with modifying the characteristics of one or more PUSCHs among the multiple PUSCHs within the at least one CG opportunity; receiving approval of the request; and sending during the one or more PUSCHs based on the modified characteristics.
[0369] Aspect 32: The method according to any one of Aspects 23 to 31, further comprising: sending a request for the configuration based at least in part on one or more traffic statistics associated with the plurality of packets.
[0370] Aspect 33: A method of wireless communication performed by a network entity, comprising: sending a configuration associated with a configuration grant (CG), the configuration indicating multiple physical uplink shared channels (PUSCHs) within each CG opportunity of a user equipment (UE); and receiving multiple packets across the multiple PUSCHs within at least one CG opportunity of the UE.
[0371] Aspect 34: The method according to Aspect 33, wherein the plurality of groups include one or more extended reality groups, one or more virtual reality groups, or a combination thereof.
[0372] Aspect 35: The method according to any one of Aspects 33 to 34 further includes: sending a configuration associated with a dynamic grant (DG) for retransmitting one or more of the multiple packets; and receiving one or more retransmissions of the one or more packets based on the DG.
[0373] Aspect 36: A method according to any one of aspects 33 to 35, wherein each PUSCH of the plurality of PUSCHs is associated with a single transport block.
[0374] Aspect 37: A method according to any one of aspects 33 to 36, wherein each PUSCH of the plurality of PUSCHs is associated with a corresponding modulation and coding scheme and a corresponding number of resource blocks.
[0375] Aspect 38: A method according to any one of Aspects 33 to 37, wherein each CG opportunity is associated with a maximum number of PUSCHs.
[0376] Aspect 39: The method according to any one of Aspects 33 to 38 further includes: receiving an indication associated with skipping one or more PUSCHs of the multiple PUSCHs within the at least one CG opportunity; and avoiding monitoring during the one or more PUSCHs.
[0377] Aspect 40: The method according to any one of Aspects 33 to 39 further includes: receiving a request associated with adding one or more additional PUSCHs within the at least one CG opportunity; sending an approval for the request; and receiving during the one or more additional PUSCHs.
[0378] Aspect 41: The method according to any one of Aspects 33 to 40 also includes: receiving a request associated with modifying the characteristics of one or more PUSCHs among the multiple PUSCHs within the at least one CG opportunity; sending an approval for the request; and receiving during the one or more PUSCHs based on the modified characteristics.
[0379] Aspect 42: A method according to any one of aspects 33 to 41, wherein the configuration indicates a periodicity of 16.67 milliseconds (ms) or 8.33 ms.
[0380] Aspect 43: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.
[0381] Aspect 44: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 11.
[0382] Aspect 45: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 1 to 11.
[0383] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.
[0384] Aspect 47: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 11.
[0385] Aspect 48: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 12 to 22.
[0386] Aspect 49: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 12 to 22.
[0387] Aspect 50: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 12 to 22.
[0388] Aspect 51: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 12 to 22.
[0389] Aspect 52: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, cause the device to perform one or more methods according to aspects 12 to 22.
[0390] Aspect 53: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 23 to 32.
[0391] Aspect 54: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 23 to 32.
[0392] Aspect 55: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 23 to 32.
[0393] Aspect 56: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 23 to 32.
[0394] Aspect 57: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform one or more of the methods described in aspects 23 to 32.
[0395] Aspect 58: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 33 to 42.
[0396] Aspect 59: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 33 to 42.
[0397] Aspect 60: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 33 to 42.
[0398] Aspect 61: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 33 to 42.
[0399] Aspect 62: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 33 to 42.
[0400] Aspect 63: A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication of a timing of a discontinuous reception (DRX) on duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream; and monitoring communication of the first data stream and the second data stream at the DRX on duration opportunity.
[0401] Aspect 64: A method according to aspect 63, wherein the indication identifies the first DRX cycle or the second DRX cycle as an anchor cycle, and wherein the DRX on-duration opportunity of the anchor cycle includes information indicating the on-duration opportunity of a non-anchor DRX cycle.
[0402] Aspect 65: The method according to Aspect 64, wherein the anchor cycle has a periodicity that is the minimum of the first periodicity and the second periodicity.
[0403] Aspect 66: The method according to Aspect 64, wherein the anchor cycle has a periodicity that is a maximum of the first periodicity and the second periodicity.
[0404] Aspect 67: A method according to any one of aspects 63 to 66, wherein the downlink control information in the DRX on-Duration opportunity of the first DRX cycle indicates the position of the DRX on-Duration opportunity of the second DRX cycle.
[0405] Aspect 68: A method according to any one of Aspects 63 to 67, wherein the timing is based at least in part on a first packet delay budget (PDB) of the first DRX cycle, the first periodicity, a second PDB of the second DRX cycle, and the second periodicity.
[0406] Aspect 69: A method according to Aspect 68, wherein the timing is based at least in part on the minimum value of the first PDB×the first periodicity and the second PDB×the second periodicity divided by a minimum PDB, the minimum PDB being the PDB of the flow minimum value of the first PDB×the first periodicity and the second PDB×the second periodicity.
[0407] Aspect 70: A method according to any one of aspects 63 to 69, wherein the timing of the DRX On-Duration opportunities comprises a non-uniform DRX cycle.
[0408] Aspect 71: A method according to any one of aspects 63 to 70, wherein the timing is specified for epochs of multiple connected mode DRX cycles.
[0409] Aspect 72: The method according to aspect 63, wherein one or more of the first DRX cycle or the second DRX cycle corresponds to the periodicity of extended reality traffic.
[0410] Aspect 73: The method according to any one of Aspects 63 to 72, wherein one or more of the first data stream or the second data stream comprises extended reality traffic.
[0411] Aspect 74: The method according to any one of aspects 63 to 73, further comprising monitoring communications in one or more time slots before or after the DRX On Duration opportunity.
[0412] Aspect 75: A method of wireless communication performed by a network entity, comprising: sending an indication of the timing of a discontinuous reception (DRX) on duration opportunity, the timing being associated with a combination of a first DRX cycle having a first periodicity for a first data stream and a second DRX cycle having a second periodicity for a second data stream; and sending communications of the first data stream and the second data stream at the DRX on duration opportunity.
[0413] Aspect 76: The method according to aspect 75, wherein the indication identifies the first DRX cycle or the second DRX cycle as an anchor cycle, and wherein the DRX on-duration opportunity of the anchor cycle indicates the on-duration opportunity of a non-anchor DRX cycle.
[0414] Aspect 77: The method according to Aspect 76, wherein the anchor cycle has a periodicity that is the minimum of the first periodicity and the second periodicity.
[0415] Aspect 78: A method according to any one of Aspects 75 to 77, wherein the downlink control information in the DRX On Duration opportunity of the first DRX cycle indicates the position of the DRX On Duration opportunity of the second DRX cycle.
[0416] Aspect 79: A method according to any one of Aspects 75 to 78, wherein the timing is based at least in part on a first packet delay budget (PDB) of the first DRX cycle, the first periodicity, a second PDB of the second DRX cycle, and the second periodicity.
[0417] Aspect 80: A method according to Aspect 79, wherein the timing is based at least in part on the minimum value of the first PDB×the first periodicity and the second PDB×the second periodicity divided by a minimum PDB, the minimum PDB being the PDB of the flow minimum value of the first PDB×the first periodicity and the second PDB×the second periodicity.
[0418] Aspect 81: A method according to any one of aspects 75 to 80, wherein the timing of the DRX On-Duration occasions comprises a non-uniform DRX cycle.
[0419] Aspect 82: A method according to any one of aspects 75 to 81, wherein the timing is specified for epochs of multiple connected mode DRX cycles.
[0420] Aspect 83: The method according to any one of aspects 75 to 82, wherein one or more of the first DRX cycle or the second DRX cycle corresponds to the periodicity of extended reality traffic.
[0421] Aspect 84: The method according to any one of Aspects 75 to 83, wherein one or more of the first data stream or the second data stream comprises extended reality traffic.
[0422] Aspect 85: A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication of a timing of a discontinuous reception (DRX) on duration opportunity, the timing being associated with the larger of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream; and monitoring communication of the first data stream and the second data stream at the DRX on duration opportunity.
[0423] Aspect 86: The method according to aspect 85, wherein one or more of the first DRX cycle or the second DRX cycle corresponds to the periodicity of extended reality traffic.
[0424] Aspect 87: The method according to aspect 85 or 86, wherein one or more of the first data stream or the second data stream includes extended reality traffic.
[0425] Aspect 88: A method according to any one of aspects 85 to 87, wherein the downlink control information in the DRX On Duration opportunity of the first DRX cycle indicates the position of the DRX On Duration opportunity of the second DRX cycle.
[0426] Aspect 89: A method of wireless communication performed by a network entity, comprising: sending an indication of the timing of a discontinuous reception (DRX) on duration opportunity, the timing being associated with the larger of a first periodicity of a first DRX cycle of a first data stream or a second periodicity of a second DRX cycle of a second data stream; and sending communications of the first data stream and the second data stream at the DRX on duration opportunity.
[0427] Aspect 90: The method according to aspect 89, wherein one or more of the first DRX cycle or the second DRX cycle corresponds to the periodicity of extended reality traffic.
[0428] Aspect 91: The method according to aspect 89 or 90, wherein one or more of the first data stream or the second data stream includes extended reality traffic.
[0429] Aspect 92: A method according to any one of aspects 89 to 91, wherein the downlink control information in the DRX On Duration opportunity of the first DRX cycle indicates a position of the DRX On Duration opportunity of the second DRX cycle.
[0430] Aspect 93: An apparatus for performing wireless communications at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 63 to 92.
[0431] Aspect 94: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 63 to 92.
[0432] Aspect 95: An apparatus for wireless communication, comprising: at least one means for performing the method according to one or more of aspects 63 to 92.
[0433] Aspect 96: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 63 to 92.
[0434] Aspect 97: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 63 to 92.
[0435] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of these aspects.
[0436] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.
[0437] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.
[0438] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claims. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).
[0439] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly described as such. In addition, as used herein, the articles "one" and "an" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said / the" is intended to include one or more items connected to the article "said / the", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you want to refer to only one project, use the phrase "only one" or similar terms. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving a configuration associated with a configuration grant (CG), the configuration indicating a plurality of physical uplink shared channels (PUSCHs) within each CG opportunity of the UE; and Multiple packets are sent across the multiple PUSCHs within at least one CG opportunity of the UE.
2. The apparatus of claim 1, wherein the plurality of groups comprises one or more extended reality groups, one or more virtual reality groups, or a combination thereof.
3. The apparatus of claim 1 , wherein the one or more processors are further configured to: receiving a configuration associated with a dynamic grant (DG) for retransmitting one or more packets of the plurality of packets; and The one or more packets are retransmitted according to the DG.
4. The apparatus of claim 1, wherein each PUSCH of the plurality of PUSCHs is associated with a single transport block.
5. The apparatus of claim 1, wherein each PUSCH of the plurality of PUSCHs is associated with a corresponding modulation and coding scheme and a corresponding number of resource blocks.
6. An apparatus according to claim 1, wherein each CG opportunity is associated with a maximum number of PUSCHs.
7. The apparatus of claim 1, wherein the one or more processors are further configured to: sending an indication associated with skipping one or more PUSCHs of the plurality of PUSCHs within the at least one CG opportunity; and Transmission is avoided during the one or more PUSCHs.
8. The apparatus of claim 1, wherein the one or more processors are further configured to: sending a request associated with adding one or more additional PUSCHs within the at least one CG opportunity; receiving approval of the request; and The transmission is performed during the one or more additional PUSCHs.
9. The apparatus of claim 1, wherein the one or more processors are further configured to: sending a request associated with modifying a characteristic of one or more PUSCHs of the plurality of PUSCHs within the at least one CG opportunity; receiving approval of the request; and Transmitting during the one or more PUSCHs is performed based on the modified characteristic.
10. The apparatus of claim 1, wherein the one or more processors are further configured to send the request for the configuration based at least in part on one or more traffic statistics associated with the plurality of packets.
11. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: sending a configuration associated with a configuration grant (CG), the configuration indicating a plurality of physical uplink shared channels (PUSCHs) within each CG opportunity of a user equipment (UE); and Multiple packets are received across the multiple PUSCHs within at least one CG opportunity of the UE.
12. The apparatus of claim 11, wherein each PUSCH of the plurality of PUSCHs is associated with a corresponding modulation and coding scheme and a corresponding number of resource blocks.
13. The apparatus of claim 11, wherein the one or more processors are further configured to: sending a configuration associated with a dynamic grant (DG) for retransmitting one or more packets of the plurality of packets; and The one or more packets are received according to the DG.
14. The apparatus of claim 11, wherein each CG opportunity is associated with a maximum number of PUSCHs.
15. An apparatus according to claim 11, wherein the one or more processors are further configured to receive an indication associated with skipping one or more PUSCHs of the plurality of PUSCHs within the at least one CG opportunity.
16. The apparatus of claim 11, wherein the one or more processors are further configured to: receiving a request associated with adding one or more additional PUSCHs within the at least one CG opportunity; sending approval of the request; and Reception is performed during the one or more additional PUSCHs.
17. The apparatus of claim 11, wherein the one or more processors are further configured to: receiving a request associated with modifying a characteristic of one or more PUSCHs of the plurality of PUSCHs within the at least one CG opportunity; sending approval of the request; and Reception is performed during the one or more PUSCHs based on the modified characteristic.
18. The apparatus of claim 11, wherein the one or more processors are further configured to receive the request for the configuration based at least in part on one or more traffic statistics associated with the plurality of packets.
19. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration associated with a configuration grant (CG), the configuration indicating a plurality of physical uplink shared channels (PUSCHs) within each CG opportunity of the UE; and Multiple packets are sent across the multiple PUSCHs within at least one CG opportunity of the UE.
20. The method according to claim 19, further comprising: receiving a configuration associated with a dynamic grant (DG) for retransmitting one or more packets of the plurality of packets; as well as The one or more packets are retransmitted according to the DG.
21. The method of claim 19, wherein each PUSCH of the plurality of PUSCHs is associated with a corresponding modulation and coding scheme and a corresponding number of resource blocks.
22. The method of claim 19, further comprising: sending an indication associated with skipping one or more PUSCHs of the plurality of PUSCHs within the at least one CG opportunity; as well as Transmission is avoided during the one or more PUSCHs.
23. The method of claim 19, further comprising: sending a request associated with adding one or more additional PUSCHs within the at least one CG opportunity; receiving approval of the request; as well as The transmission is performed during the one or more additional PUSCHs.
24. The method of claim 19, further comprising: sending a request associated with modifying a characteristic of one or more PUSCHs of the plurality of PUSCHs within the at least one CG opportunity; receiving approval of the request; as well as Transmitting during the one or more PUSCHs is performed based on the modified characteristic.
25. The method of claim 19, further comprising sending the request for the configuration based at least in part on one or more traffic statistics associated with the plurality of packets.
26. A method of wireless communication performed by a network entity, the method comprising: sending a configuration associated with a configuration grant (CG), the configuration indicating a plurality of physical uplink shared channels (PUSCHs) within each CG opportunity of a user equipment (UE); and Multiple packets are received across the multiple PUSCHs within at least one CG opportunity of the UE.
27. The method of claim 26, wherein each PUSCH of the plurality of PUSCHs is associated with a corresponding modulation and coding scheme and a corresponding number of resource blocks.
28. The method of claim 26, further comprising receiving an indication associated with skipping one or more of the multiple PUSCHs within the at least one CG opportunity.
29. The method of claim 26, further comprising: receiving a request associated with adding one or more additional PUSCHs within the at least one CG opportunity; sending approval of said request; as well as Reception is performed during the one or more additional PUSCHs.
30. The method of claim 26, further comprising: receiving a request associated with modifying a characteristic of one or more PUSCHs of the plurality of PUSCHs within the at least one CG opportunity; sending approval of said request; as well as Reception is performed during the one or more PUSCHs based on the modified characteristic.
