Patent Application
20250168864
Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for skipping downlink channel monitoring.
Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and/or other traffic. The services may include unicast, multicast, and/or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and/or device transmit power, among other examples). Examples of such multiple-access RATs 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, and time division synchronous code division multiple access (TD-SCDMA) systems.
The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR). NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (IoT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication), massive multiple-input multiple-output (MIMO), disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high-precision positioning, and/or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution.
In physical downlink control channel (PDCCH) skipping, a UE may stop PDCCH monitoring for a duration of time. The UE may perform PDCCH skipping based at least in part on a scheduling downlink control information (DCI) received from a network node. A PDCCH monitoring adaptation may increase power savings for the UE. The UE may override the PDCCH skipping with a transmission of a scheduling request (SR).
In some cases, the UE may receive, from the network node, a PDCCH monitoring resumption after negative acknowledgement (NACK) parameter. The PDCCH monitoring resumption after NACK parameter may be a radio resource control (RRC) parameter, which may be based at least in part on a UE capability. The UE may be configured to resume the PDCCH monitoring after transmitting a NACK to the network node. However, when the UE is configured with the PDCCH monitoring resumption after NACK parameter, the UE may not be properly configured for the monitoring of multicast DCIs. In other words, the UE may not be able to properly handle the monitoring of multicast DCIs when the UE is configured to resume the PDCCH monitoring after transmitting the NACK. As a result, uncertainty when monitoring the multicast DCIs may cause the UE to not receive multicast DCIs, thereby degrading an overall performance of the UE.
In some aspects, a UE may receive, from a network node, a configuration associated with PDCCH monitoring resumption after NACK. The UE may receive, from the network node, DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink bandwidth part (BWP) of a serving cell. The UE may transmit, to the network node, a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission. The UE may perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs, and skip, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs, starting from a beginning of a first slot that is after a last symbol of a physical uplink control channel (PUCCH) resource. The UE may transmit the NACK in a NACK-only feedback mode in a shared PUCCH resource due to an incorrect decoding of a group common PDSCH (GC-PDSCH) transmission scheduled by the DCI, and the UE may terminate the PDCCH skipping and resume the PDCCH monitoring for a group common PDCCH (GC-PDCCH) transmission and not for a unicast PDCCH. Alternatively, the UE may transmit the NACK in an acknowledgement (ACK)-NACK feedback mode on a UE-specific PUCCH resource due to an incorrect decoding of a GC-PDSCH transmission scheduled by the DCI or due to an incorrect decoding of a unicast PDSCH transmission, and the UE may terminate the PDCCH skipping and resume the PDCCH monitoring for at least one of a CG-PDCCH transmission or unicast DCIs.
In some aspects, the UE may separately resume monitoring the PDCCH for unicast and multicast after the UE reports the NACK and after the PDCCH skipping indication, and the resumption of the PDCCH monitoring may depend on which HARQ ACK MBS mode is configured, which may include mode 1 (ACK-NACK) or mode 2 (NACK-only). When the UE is configured with the PDCCH monitoring resumption after NACK parameter, the UE may be able to monitor multicast DCIs. The UE may be able to properly handle the monitoring of multicast DCIs when the UE is configured to resume the PDCCH monitoring after transmitting the NACK. As a result, the UE may not be subject to uncertainty when monitoring the multicast DCIs, thereby improving an overall performance of the UE.
In some aspects, by configuring the UE to perform PDCCH monitoring resumption after a NACK while considering the monitoring of multicast DCIs, the described techniques can be used to terminate PDCCH skipping and resume PDCCH monitoring depending on whether the UE operates in a NACK-only feedback mode or an ACK-NACK feedback mode. By accounting for the monitoring of multicast DCIs when the UE is capable of PDCCH monitoring resumption after NACK, the UE may properly receive multicast DCIs, thereby improving an overall performance of the UE.
In some implementations, an apparatus for wireless communication at a UE includes one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the UE to: receive a configuration associated with PDCCH monitoring resumption after NACK; receive DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; transmit a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein the feedback mode is a NACK-only feedback mode or an ACK-NACK feedback mode; perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs; and skip, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs, starting from a beginning of a first slot that is after a last symbol of a PUCCH resource.
In some implementations, an apparatus for wireless communication at a network node includes one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the network node to: transmit a configuration associated with PDCCH monitoring resumption after NACK; transmit DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; and receive a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped.
In some implementations, a method of wireless communication performed by a UE includes receiving a configuration associated with PDCCH monitoring resumption after NACK; receiving DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; transmitting a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein the feedback mode is a NACK-only feedback mode or an ACK-NACK feedback mode; performing, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs; and skipping, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs, starting from a beginning of a first slot that is after a last symbol of a PUCCH resource.
In some implementations, a method of wireless communication performed by a network node includes transmitting a configuration associated with PDCCH monitoring resumption after NACK; transmitting DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; and receiving a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped.
In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: receive a configuration associated with PDCCH monitoring resumption after NACK; receive DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; transmit a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein the feedback mode is a NACK-only feedback mode or an ACK-NACK feedback mode; perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs; and skip, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs.
In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit a configuration associated with PDCCH monitoring resumption after NACK; transmit DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; and receive a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped.
In some implementations, an apparatus for wireless communication includes means for receiving a configuration associated with PDCCH monitoring resumption after NACK; means for receiving DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; means for transmitting a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein the feedback mode is a NACK-only feedback mode or an ACK-NACK feedback mode; means for performing, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs; and means for skipping, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs.
In some implementations, an apparatus for wireless communication includes means for transmitting a configuration associated with PDCCH monitoring resumption after NACK; means for transmitting DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; and means for receiving a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped.
Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and/or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings.
The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings.
The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.
Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and/or functionalities in addition to or other than the structures and/or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
In physical downlink control channel (PDCCH) skipping, a UE may stop PDCCH monitoring for a duration of time. In search space set group (SSSG) switching, the UE may stop monitoring certain synchronization signal (SS) sets associated with certain SSSGs and instead monitor other SS sets associated with other SSSGs. The UE may perform PDCCH skipping and SSSG switching based at least in part on a scheduling downlink control information (DCI) received from a network node. A PDCCH monitoring adaptation may increase power savings for the UE. The UE may override the PDCCH skipping with a transmission of a scheduling request (SR).
In some cases, the UE may receive, from the network node, a PDCCH monitoring resumption after negative acknowledgement (NACK) parameter. The PDCCH monitoring resumption after NACK parameter may be a radio resource control (RRC) parameter, which may be based at least in part on a UE capability. The UE may be configured to resume the PDCCH monitoring after transmitting a NACK to the network node. However, when the UE is configured with the PDCCH monitoring resumption after NACK parameter, the UE may not be properly configured for the monitoring of multicast DCIs. In other words, the UE may not be able to properly handle the monitoring of multicast DCIs when the UE is configured to resume the PDCCH monitoring after transmitting the NACK. As a result, uncertainty when monitoring the multicast DCIs may cause the UE to not receive multicast DCIs, thereby degrading an overall performance of the UE.
Various aspects relate generally to skipping downlink channel monitoring. Some aspects more specifically relate to PDCCH skipping for a multicast broadcast service (MBS). In some examples, a UE may receive, from a network node, a configuration associated with PDCCH monitoring resumption after NACK. The UE may receive, from the network node, DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink bandwidth part (BWP) of a serving cell. The UE may initially perform PDCCH monitoring, and then skip (or terminate) PDCCH monitoring based at least in part on the PDCCH monitoring adaptation field. The UE may transmit, to the network node, a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission. The UE may perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs. In other words, the UE may resume PDCCH monitoring only for the PDCCH candidates carrying groupcast scheduling DCIs. The UE may skip, based at least in part on the NACK, PDCCH monitoring only for PDCCH candidates carrying unicast scheduling DCIs. The UE may perform/skip PDCCH monitoring starting from a beginning of a first slot that is after a last symbol of a physical uplink control channel (PUCCH) resource. The UE may transmit the NACK in a NACK-only feedback mode in a shared PUCCH resource due to an incorrect decoding of a group common PDSCH (GC-PDSCH) transmission scheduled by the DCI, and the UE may terminate the PDCCH skipping and resume the PDCCH monitoring for a group common PDCCH (GC-PDCCH) transmission and not for a unicast PDCCH. Alternatively, the UE may transmit the NACK in an acknowledgement (ACK)-NACK feedback mode on a UE-specific PUCCH resource due to an incorrect decoding of a GC-PDSCH transmission scheduled by the DCI or due to an incorrect decoding of a unicast PDSCH transmission, and the UE may terminate the PDCCH skipping and resume the PDCCH monitoring for at least one of a CG-PDCCH transmission or unicast DCIs.
In some aspects, the UE may separately resume monitoring the PDCCH for unicast and multicast after the UE reports the NACK and after the PDCCH skipping indication, and the resumption of the PDCCH monitoring may depend on which HARQ ACK MBS mode is configured, which may include mode 1 (ACK-NACK) or mode 2 (NACK-only). When the UE is configured with the PDCCH monitoring resumption after NACK parameter, the UE may be able to monitor multicast DCIs. The UE may be able to properly handle the monitoring of multicast DCIs when the UE is configured to resume the PDCCH monitoring after transmitting the NACK. As a result, the UE may not be subject to uncertainty when monitoring the multicast DCIs, thereby improving an overall performance of the UE.
Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by configuring the UE to perform PDCCH monitoring resumption after a NACK while considering the monitoring of multicast DCIs, the described techniques can be used to terminate PDCCH skipping and resume PDCCH monitoring depending on whether the UE operates in a NACK-only feedback mode or an ACK-NACK feedback mode. By accounting for the monitoring of multicast DCIs when the UE is capable of PDCCH monitoring resumption after NACK, the UE may properly receive multicast DCIs, thereby improving an overall performance of the UE.
Multiple-access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).
As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, and/or artificial intelligence or machine learning (AI/ML), among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and/or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and/or support one or more of the foregoing use cases.
The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and/or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular radio access technology (RAT) (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G/NR RAT, and/or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another.
Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHZ), FR2 (24.25 GHz through 52.6 GHZ), FR3 (7.125 GHz through 24.25 GHZ), FR4a or FR4-1 (52.6 GHz through 71 GHz), FR4 (52.6 GHz through 114.25 GHZ), and FR5 (114.25 GHz through 300 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz), which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz,” if used herein, may broadly refer to frequencies that are less than 6 GHZ, that are within FR1, and/or that are included in mid-band frequencies. Similarly, the term “millimeter wave,” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-a or FR4-1, or FR5, and/or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and/or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS), in which multiple RATs (for example, 4G/LTE and 5G/NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges.
A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP), a transmission reception point (TRP), a mobility element, a core, a network entity, a network element, a network equipment, and/or another type of device, component, or system included in a radio access network (RAN).
A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures). For example, a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack), or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture), meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.
Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 may implement a radio protocol stack that is physically distributed and/or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance), or in a virtualized radio access network (vRAN), also known as a cloud radio access network (C-RAN), to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.
The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and/or one or more radio units (RUs). A CU may host one or more higher layer control functions, such as RRC functions, packet data convergence protocol (PDCP) functions, and/or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and/or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT), an inverse FFT (iFFT), beamforming, physical random access channel (PRACH) extraction and filtering, and/or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120.
In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and/or one or more RUs. Additionally or alternatively, a network node 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and/or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and/or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment.
Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or a non-terrestrial network (NTN) network node).
The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and/or disaggregated network nodes, among other examples. In the example shown in
In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link). The radio access link may include a downlink and an uplink. “Downlink” (or “DL”) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL”) refers to a communication direction from a UE 120 to a network node 110. Downlink channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit DCI (for example, scheduling information, reference signals, and/or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more PDCCHs, and downlink data channels may include one or more PDSCHs. Uplink channels may similarly include one or more control channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and/or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more PUCCHs, and uplink data channels may include one or more physical uplink shared channels (PUSCHs). The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.
Downlink and uplink resources may include time domain resources (frames, subframes, slots, and/or symbols), frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and/or resource elements), and/or spatial domain resources (particular transmit directions and/or beam parameters). Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs). A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs). A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and/or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and/or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor), leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.
As described above, in some aspects, the wireless communication network 100 may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or “IAB-donor”). The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). An IAB network also generally includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply as IAB nodes (or “IAB-nodes”). Each non-anchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and/or spatial resources) may be shared between access links and backhaul links.
In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a “multi-hop network.” In the example shown in
communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, 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, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and/or smart jewelry, such as a smart ring or a smart bracelet), an entertainment device (for example, a music device, a video device, and/or a satellite radio), an extended reality (XR) device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and/or any other suitable device or function that may communicate via a wireless medium.
A UE 120 and/or a network node 110 may include one or more chips, system-on-chips (SoCs), chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) and/or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry”). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions.
The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-access memory (RAM) or read-only memory (ROM), or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry”). One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.
Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC), UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as “MTC UEs”). An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and/or a location tag. Some UEs 120 may be considered IoT devices and/or may be implemented as NB-IoT (narrowband IoT) devices. An IoT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and/or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100).
Some UEs 120 may be classified according to different categories in association with different complexities and/or different capabilities. UEs 120 in a first category may facilitate massive IoT in the wireless communication network 100, and may offer low complexity and/or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, and/or premium UEs that are capable of ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), and/or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and/or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability). A UE 120 of the third category may be referred to as a reduced capacity UE (“RedCap UE”), a mid-tier UE, an NR-Light UE, and/or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and/or eMTC UEs, and mission-critical IoT devices and/or premium UEs. RedCap UEs may include, for example, wearable devices, IoT devices, industrial sensors, and/or cameras that are associated with a limited bandwidth, power capacity, and/or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and/or smart city deployments, among other examples.
In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary). As an example, the UE 120a may directly transmit data, control information, or other signaling as a sidelink communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication. In various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and/or vehicle-to-pedestrian (V2P) protocols), and/or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and/or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and/or other operations for sidelink communications.
In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full-duplex operation in addition to half-duplex operation. A network node 110 or a UE 120 operating in a half-duplex mode may perform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods. Half-duplex operation may involve time-division duplexing (TDD), in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time). In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources). By operating in a full-duplex mode, network nodes 110 and/or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full-duplex operation may involve frequency-division duplexing (FDD), in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120.
In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. “MIMO” generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO). Some radio access technologies (RATs) may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time domain or the frequency domain, single-frequency-network (SFN) transmission, or non-coherent joint transmission (NC-JT).
In some aspects, a UE (e.g., the UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive a configuration associated with PDCCH monitoring resumption after NACK; receive DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; transmit a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission; perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs; and skip, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
In some aspects, a network node (e.g., the network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit a configuration associated with PDCCH monitoring resumption after NACK; transmit DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; and receive a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
As indicated above,
As shown in
The terms “processor,” “controller,” or “controller/processor” may refer to one or more controllers and/or one or more processors. For example, reference to “a/the processor,” “a/the controller/processor,” or the like (in the singular) should be understood to refer to any one or more of the processors described in connection with
In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with
For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data (“downlink data”) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue). In some examples, the transmit processor 214 may select one or more MCSs for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS(s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI)) and/or control information (for example, CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and/or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS), a demodulation reference signal (DMRS), or a channel state information (CSI) reference signal (CSI-RS)) and/or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS)).
The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for orthogonal frequency division multiplexing ((OFDM)) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.
A downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and/or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and/or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and/or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.
For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232), may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and/or may be further processed by the receive processor 238 to obtain decoded data and/or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and/or another type of data sink) and provide the decoded control information to a processor, such as the controller/processor 240.
The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and/or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and/or frequency domain resources that the UE 120 may use to transmit and/or receive communications using an RRC configuration (for example, a semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure a configured grant (CG) for the UE 120.
One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and/or the controller/processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and/or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110). In some aspects, the RF chain may be or may be included in a transceiver of the network node 110.
In some examples, the network node 110 may use the communication unit 244 to communicate with a core network and/or with other network nodes. The communication unit 244 may support wired and/or wireless communication protocols and/or connections, such as Ethernet, optical fiber, common public radio interface (CPRI), and/or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and/or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and/or an interface, such as a network interface.
The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r≥1), a set of modems 254 (shown as modems 254a through 254u, where a≥1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, a memory 282, and/or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller/processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and/or another component that facilitates communication with the network node 110 and/or another UE 120.
For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the respective demodulator component to condition (for example, filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and/or an application executed on the UE 120), and may provide decoded control information and system information to the controller/processor 280.
For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data (“uplink data”) from a data source 262 (such as a data pipeline, a data queue, and/or an application executed on the UE 120) and control information from the controller/processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and/or other types of control information. In some aspects, the receive processor 258 and/or the controller/processor 280 may determine, for a received signal (such as received from the network node 110 or another UE), one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, a channel quality indicator (CQI) parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and/or another parameter. The control information may facilitate parameter selection and/or scheduling for the UE 120 by the network node 110.
The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink SRS, and/or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM). The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain an uplink signal.
The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and/or another type of uplink channel. An uplink signal may carry one or more TBs of data. Sidelink data and control transmissions (that is, transmissions directly between two or more UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and/or a physical sidelink feedback channel (PSFCH).
One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of
In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and/or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam). For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range.
The amplitudes and/or phases of signals transmitted via antenna elements and/or sub-elements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and/or amplitude) to generate one or more beams, which is referred to as beamforming. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. “Beam” may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and/or a vertical direction), and/or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and/or a set of directional resources associated with the signal. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and/or phases of the signal(s) to form one or more beams. The shape of a beam (such as the amplitude, width, and/or presence of side lobes) and/or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and/or amplitudes of the multiple signals relative to each other.
Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements. Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing.
While blocks in
As indicated above,
Each of the components of the disaggregated base station architecture 300, including the CUS 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.
In some aspects, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 may be controlled by the corresponding DU 330.
The SMO Framework 360 may support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an O1 interface. For virtualized network elements, the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an O2 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and/or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and/or a 6G RAN, such as an open eNB (O-eNB) 380, via an O1 interface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective O1 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence and/or machine learning (AI/ML) workflows including model training and updates, and/or policy-based guidance of applications and/or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an A1 interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, and/or an O-eNB with the Near-RT RIC 370.
In some aspects, to generate AI/ML models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI/ML models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies).
The network node 110, the controller/processor 240 of the network node 110, the UE 120, the controller/processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other component(s) of
In some aspects, a UE (e.g., the UE 120) includes means for receiving a configuration associated with PDCCH monitoring resumption after NACK; means for receiving DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; means for transmitting a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission; means for performing, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs; and/or means for skipping, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs. The means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
In some aspects, a network node (e.g., the network node 110) includes means for transmitting a configuration associated with PDCCH monitoring resumption after NACK; means for transmitting DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell; and/or means for receiving a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped. The means for the network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.
As indicated above,
A PDCCH monitoring adaptation may increase power savings. The PDCCH monitoring adaptation may be based at least in part on a unified design of PDCCH skipping and SSSG switching. A UE may override the PDCCH skipping with a transmission of an SR. The PDCCH skipping and/or the SSSG switching may be applicable to both Type 3 common search space (CSS) and UE-specific search space (USS). The UE may apply the PDCCH skipping and/or the SSSG switching for PDCCH monitoring for both unicast downlink control information (DCI) and multicast DCI in the Type 3 CSS, which may be based at least in part on a dynamic PDCCH skipping and SSSG switching indication. Further, a UE behavior to reset a timer when detecting a multicast PDCCH may involve, similar to when detecting a unicast PDCCH, resetting the timer after a slot of an active downlink BWP of a serving cell when the UE detects DCI in a PDCCH reception in a slot for which a cyclic redundancy check (CRC) is scrambled by a cell radio network temporary identifier (RNTI) (C-RNTI), configured scheduling RNTI (CS-RNTI), MCS C-RNTI, MCS-C-RNTI, or a group RNTI (G-RNTI) for multicast.
A PDCCH monitoring resumption after an uplink negative acknowledgement (NACK) may be defined, which may be based at least in part on a PDCCH monitoring resumption after NACK (PdcchMornitoringResumptionAfterNack) RRC parameter and/or an optional UE capability. The PDCCH monitoring resumption after the NACK may affect a monitoring of multicast DCIs, which may depend on a mode of hybrid automatic repeat request (HARQ) acknowledgement (ACK) multicast broadcast service (MBS). The mode may be mode 1 (ACK/NACK) or mode 2 (NACK-only). In some cases, the UE may separately resume PDCCH monitoring for unicast and multicast after the UE reports the NACK, where the NACK may be reported after a PDCCH skipping indication, and the PDCCH monitoring resumption may depend on an MBS HARQ ACK mode 1 or 2.
In a DCI-based PDCCH monitoring adaptation, the unified design of PDCCH skipping and SSSG switching may be defined. The UE may be indicated a behavior by a scheduling DCI. For PDCCH skipping, the behavior may involve the PDCCH skipping not being activated/triggered. For PDCCH skipping, the behavior may involve stopping PDCCH monitoring for a duration X. For SSSG switching, the behavior may involve stopping monitoring SS sets associated with SSSG #1 and SSSG #2, and monitoring SS sets associated with SSSG #0. For SSSG switching, the behavior may involve stopping monitoring SS sets associated with SSSG #0 and SSSG #2, and monitoring SS sets associated with SSSG #1. For SSSG switching, the behavior may involve stopping monitoring SS sets associated with SSSG #0 and SSSG #1, and monitoring SS sets associated with SSSG #2. One such behavior may be mapped to a codepoint of an indication field in the scheduling DCI.
As shown in
As indicated above,
As shown in
As indicated above,
In SR overriding PDCCH skipping, when PDCCH skipping is configured for a UE, an SR transmission from the UE during a PDCCH skip duration may override a previous PDCCH skipping indication, and the UE may resume PDCCH monitoring. An SR overriding SSSG may also be possible. In a PDCCH termination with a pending NACK, the UE may terminate PDCCH skipping after a NACK transmission. A non-scheduling DCI (dummy grant) may be used to cause the UE to enter a low power mode after all packets have been acknowledged, but uplink data may interrupt PDCCH skipping.
As shown in
As indicated above,
Two HARQ-ACK feedback modes may be defined for multicast, which may include an ACK/NACK-based feedback and a NACK-only based HARQ-ACK feedback. For a dynamic grant multicast, the HARQ-ACK feedback mode may be configured per G-RNTI by unicast RRC signaling. For SPS multicast and for an SPS activation/deactivation, only ACK/NACK-based HARQ-ACK feedback may be used. For SPS multicast and SPS groupcast (GC)-PDSCH without PDCCH scheduling, the HARQ-ACK feedback mode may be configured per G-CS-RNTI by unicast RRC signaling. Two codebook types may be defined for multicast, which may include a semi-static (Type-1) codebook and a dynamic (Type-2) codebook. A PDSCH HARQ-ACK codebook and/or a PDSCH HARQ-ACK codebook list for multicast, which may be separate from unicast, may be configured and applied to all G-RNTIs per UE.
RRC connected UEs may be associated with a multicast reliability. A multiplexing of unicast and multicast feedback on a PUCCH may be defined. In a first example, unicast and multicast HARQ-ACK feedback may be multiplexed with a same codebook type but different priorities. Separate sub-codebooks may be generated for unicast and multicast, such that a unicast sub-codebook may be concatenated, which may be followed by a multicast codebook. Two non-overlapping slot-based PUCCHs may be supported for multicast/unicast with different priorities in a slot subject to UE capability. In a second example, multicast HARQ-ACK feedback may be multiplexed with different codebook types but the same priority. Separate sub-codebooks may be generated for unicast and multicast, such that the sub-codebooks may be concatenated by appending a sub-codebook for multicast to a sub-codebook for unicast in the same PUCCH. For a Type-3 HARQ-ACK codebook configured for unicast, HARQ-ACK feedback may be included per HARQ process identifier (HPID) without differentiating unicast or multicast. In a third example, multiplexing unicast and multicast HARQ-ACK feedback with different PUCCH structures may not be supported, which may be considered an error case (e.g., the UE may not be expected to be configured to multiplex unicast and multicast with different PUCCH structures in the same PUCCH slot).
A NACK-only feedback for multicast may be defined. In a PUCCH format for NACK-only based HARQ-ACK feedback, PUCCH format 0 and format 1 with cyclic shift 0 may be used for NACK-only based HARQ-ACK feedback for multicast. A PUCCH resource configuration for HARQ-ACK feedback from a per UE perspective may be separate from that of unicast. A PUCCH resource for NACK-only may be shared by UEs transmitting NACK-only based HARQ-ACK feedback. When a PUCCH for the NACK-only based feedback collides with a unicast PUCCH for HARQ-ACK feedback/CSI, or a PUSCH for the same priority, the NACK-only based feedback may be multiplexed in the PUCCH or a PUSCH by transforming a NACK-only into an ACK/NACK HARQ bit.
A multiplexing of unicast and multicast HARQ-ACK feedback may be supported, so a PUCCH resource may carry HARQ-ACKs corresponding to a group common PDSCH (GC-PDSCH) as well as an ACK/NACK for a PDSCH scheduled by DCI that includes a PDCCH skipping indication. A PUCCH may carry original NACK-only bits transformed into ACK/NACK when colliding with unicast. The DCI indicating the PDCCH skipping may be a dummy grant that schedules no valid PDSCH, but may only be used for the PDCCH indication (subsequent NACKs are for an earlier GC-PDSCH).
A multicast group scheduling for RRC connected UEs may be defined. A PDCCH configuration for multicast (PDCCH-Config-Multicast) may be associated with a control resource set (CORESET). A maximum number of CORESETs per BWP may not be increased for support of MBS. A network node may use the CORESET configured in PDCCH-Config-Multicast for unicast PDCCH. An initializing sequence generator of a GC-PDCCH and a DMRS of the GC-PDCCH may be configured in the CORESET. The PDCCH configuration for multicast may be associated with a search space multicast. A Type3 CSS may be configured for multicast using a common control channel element (CCE) index. A monitoring priority of CSS for multicast may be determined based at least in part on an SS set index, similar as a USS. The search space multicast may be associated with multicast DCI formats.
DCI format 4_1 and 4_2 may be used for multicast. A “3+1” DCI size budget may be kept for MBS. The size of DCI format 4_1 may be aligned with DCI format 1_0 with a CRC scrambled by a C-RNTI monitored in the CSS. The size of DCI format 4_2 may be configured per common frequency resource (CFR) for all G-RNTIs with a range of 20-140. The DCI format 2_x cannot be configured in the same CSS configuration with multicast DCI formats. The UE may be able to process a certain number of DCIs in a slot or span, where an MBS DCI may be treated as unicast DCI scheduling downlink.
The DCI format 4_1 with G-RNTI may be defined. An identifier for DCI formats field may be reserved. A frequency domain resource assignment field may be similar as DCI format 1_0 for unicast in CSS, except RBstart is a lowest RB of the CFR and for a resource indication value (RIV) of downlink resource allocation (RA) type 1, if NCFR>NBWPinitial, use a scaling factor K={1, 2, 4, 6, 8, 10, 12}, which satisfies K≤└NCFR/NBWPinitial┘; otherwise, K=1. A time domain resource assignment field may indicate 4 (common for all G-RNTIs/G-CS-RNTIs). A virtual resource block (VRB) to physical resource block (PRB) mapping field may indicate 1. An MCS field may indicate 5. A redundancy version (RV) field may indicate 2. A new data indicator (NDI) field may indicate 1. A hybrid automatic repeat request (HARQ) process number may indicate 4. A downlink assignment index (DAI) field may indicate 2. A PDSCH-to-HARQ feedback timing indicator may indicate 4. A PUCCH resource indicator field may indicate 3. A transmit power control (TPC) command for PUCCH field may be reserved.
The DCI format 4_2 with G-RNTI may be defined. An identifier for DCI formats field may be reserved. A frequency domain resource assignment field may be variable based at least in part on the CFR. A time domain resource assignment field may indicate 0, 1, 2, 3, or 4. A VRB to PRB mapping field may indicate 0 or 1. A PRB bundling field may indicate 0 or 1. A rate matching indicator field may indicate 0, 1, or 2. An MCS/RV/NDI for transport block 1 (TB1) field may indicate 5/2/1. An MCS/RV/NDI for transport block 2 (TB2) field may indicate 5/2/1 (optional). A HARQ process number may indicate 4. A DAI field may indicate 0 or 2. A PDSCH-to-HARQ feedback timing indicator may indicate 0, 1, 2, or 3. A PUCCH resource indicator field may indicate 3. A TPC command for PUCCH field may be reserved. An antenna port(s) field may indicate 4, 5, or 6. A transmission configuration indicator (TCI) field may indicate 0 or 3. A zero power (ZP) channel state information reference signal (CSI-RS) trigger may indicate 0, 1, or 2. A DMRS sequence initialization field may indicate 1. A priority indicator field may indicate 0 or 1. An enabling/disabling HARQ feedback indication field may indicate 0 or 1.
In PDCCH skipping, a UE may stop PDCCH monitoring for a duration of time. In SSSG switching, the UE may stop monitoring certain SS sets associated with certain SSSGs and instead monitor other SS sets associated with other SSSGs. The UE may perform PDCCH skipping and SSSG switching based at least in part on a scheduling DCI received from a network node. A PDCCH monitoring adaptation may increase power savings for the UE.
In some cases, the UE may receive, from the network node, a PDCCH
monitoring resumption after NACK parameter. The UE may be configured to resume the PDCCH monitoring after transmitting a NACK to the network node. However, when the UE is configured with the PDCCH monitoring resumption after NACK parameter, the UE may not be properly configured for the monitoring of multicast DCIs. In other words, the UE may not be able to properly handle the monitoring of multicast DCIs when the UE is configured to resume the PDCCH monitoring after transmitting the NACK. As a result, uncertainty when monitoring the multicast DCIs may cause the UE to not receive multicast DCIs, thereby degrading an overall performance of the UE.
In some aspects, a UE may receive, from a network node, a configuration associated with PDCCH monitoring resumption after NACK. The UE may receive, from the network node, DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell. The UE may transmit, to the network node, a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission. The UE may perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs and skip, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs, starting from a beginning of a first slot that is after a last symbol of a PUCCH resource. The UE may transmit the NACK in a NACK-only feedback mode in a shared PUCCH resource due to an incorrect decoding of a GC-PDSCH transmission scheduled by the DCI, and the UE may terminate the PDCCH skipping and resume the PDCCH monitoring for a GC-PDCCH transmission and not for a unicast PDCCH. Alternatively, the UE may transmit the NACK in an acknowledgement (ACK)-NACK feedback mode on a UE-specific PUCCH resource due to an incorrect decoding of a GC-PDSCH transmission scheduled by the DCI or due to an incorrect decoding of a unicast PDSCH transmission, and the UE may terminate the PDCCH skipping and resume the PDCCH monitoring for at least one of a CG-PDCCH transmission or unicast DCIs. In other words, the UE may separately resume monitoring the PDCCH for unicast and multicast after the UE reports the NACK and after the PDCCH skipping indication, and the resumption of the PDCCH monitoring may depend on which HARQ ACK MBS mode is configured, which may include mode 1 (ACK-NACK) or mode 2 (NACK-only).
In some aspects, by configuring the UE to perform PDCCH monitoring resumption after a NACK while considering the monitoring of multicast DCIs, PDCCH skipping may be terminated and PDCCH monitoring may be resumed depending on whether the UE operates in a NACK-only feedback mode or an ACK-NACK feedback mode. By accounting for the monitoring of multicast DCIs when the UE is capable of PDCCH monitoring resumption after NACK, the UE may properly receive multicast DCIs, thereby improving an overall performance of the UE.
As shown by reference number 702, the UE may receive, from the network node, a configuration associated with PDCCH monitoring resumption after NACK. The UE may be configured with a PDCCH monitoring resumption after NACK
(PdcchMonitoringResumptionAfterNack) parameter. The UE may be able to resume PDCCH monitoring after transmitting a NACK based at least in part on the PDCCH monitoring resumption after NACK parameter.
As shown by reference number 704, the UE may receive, from the network node, a downlink DCI associated with a DCI format that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell. The UE may detect DCI providing the PDCCH monitoring adaptation field, which may indicate to the UE to skip PDCCH monitoring for the duration on the active downlink BWP of the serving cell.
As shown by reference number 706, the UE may transmit, to the network node, a NACK based at least in part on an incorrectly decoded PDSCH transmission. The UE may transmit the NACK in accordance with a feedback mode. The feedback mode may be a NACK-only feedback mode or an ACK-NACK feedback mode. The UE may transmit the NACK in the NACK-only feedback mode in a shared PUCCH resource due to an incorrect decoding of a GC-PDSCH transmission scheduled by the DCI. The UE may transmit the NACK in the ACK-NACK feedback mode on a UE-specific PUCCH resource due to an incorrect decoding of the GC-PDSCH transmission scheduled by the DCI or due to an incorrect decoding of a unicast PDSCH transmission.
As shown by reference number 708, the UE may perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs, and skip, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs, based at least in part on the NACK, starting from a beginning of a first slot that is after a last symbol of a PUCCH resource. The PDCCH candidates carrying unicast scheduling DCIs may be associated with DCI format 4_x for MBS (e.g., DCIs transmitted via a GC-PDCCH). The UE may terminate the PDCCH skipping and resume the PDCCH monitoring for a GC-PDCCH transmission and not for a unicast PDCCH. The UE may terminate the PDCCH skipping and resume the PDCCH monitoring for at least one of a CG-PDCCH transmission or unicast DCIs. The UE may terminate the PDCCH skipping and resume the PDCCH monitoring based at least in part on a configuration.
In some aspects, when the UE is configured with the PDCCH monitoring resumption after NACK parameter, after the UE detects the DCI, and when the UE transmits the NACK in the NACK-only mode in the shared PUCCH resource (e.g., pucch-ConfigMulticast2 or pucch-ConfigurationListMulticast2 configured for a second reporting mode) due to incorrectly decoding the GC-PDSCH transmission scheduled by the DCI (which may be received before the PDCCH skipping indication), the UE may terminate the PDCCH skipping and/or resume PDCCH monitoring for only the GC-PDCCH (not for the unicast PDCCH), starting from the beginning of the first slot that is after the last symbol of the PUCCH.
In some aspects, when the UE is configured with the PDCCH monitoring resumption after NACK parameter, after the UE detects the DCI, and when the UE transmits the NACK in the ACK/NACK mode on the UE specific PUCCH (e.g., pucch-ConfigMulticast1 or pucch-ConfigurationListMulticast1 configured for a first reporting mode, or a pucch-Config or pucch-ConfigurationList) providing a NACK value due to incorrectly decoding a GC-PDSCH transmission scheduled by DCI received from the serving cell and/or due to incorrectly decoding a unicast PDSCH, the UE may terminate the PDCCH skipping and/or resume PDCCH monitoring for both GC-PDCCH and unicast DCIs, for only GC-PDCCH DCIs (assuming only point-to-multipoint (PTM) is configured), or for only unicast DCIs (assuming only point-to-point (PTP) is configured), starting from the beginning of the first slot that is after the last symbol of the PUCCH.
In some aspects, the UE may terminate the PDCCH skipping and/or resume PDCCH monitoring based at least in part on an implicit RRC configuration (e.g., from a PTP/PTM configuration) or an explicit RRC configuration. Further, a priority may be assigned such that the UE may start with searching for a unicast retransmission (reTx) DCI and then multicast (or vice versa).
In some aspects, the UE may transmit the NACK on the PUCCH resource or a PUSCH resource due to an incorrect decoding of a unicast PDSCH transmission scheduled by the DCI. The UE may terminate the PDCCH skipping and resume the PDCCH monitoring for the unicast PDCCH and not a multicast PDCCH.
In some aspects, a selective PDCCH monitoring resumption may be based at least in part on a unicast/multicast DCI reception. The UE may be configured with a PDCCH monitoring resumption after NACK (PdcchMonitoringResumptionAfterNack) parameter. The UE may detect DCI providing a PDCCH monitoring adaptation field, which may indicate to the UE to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell.
In some aspects, when the UE transmits a NACK on a PUCCH or a PUSCH due to incorrectly decoding a unicast PDSCH scheduled by DCI received from a serving cell, the UE may terminate PDCCH skipping and/or resume PDCCH monitoring for only unicast PDCCH (not multicast), starting from a beginning of a first slot that is after a last symbol of the PUCCH. In other words, the UE may not expect retransmissions for multicast based at least in part on a PTM retransmission associated with a G-RNTI/G-CS-RNTI or a PTP retransmission associated with a C-RNTI/CS-RNTI for an MBS PDSCH (where the PTP retransmission may have the same HPID or new data indicator (NDI) as an initial transmission of an MBS PDSCH). The UE may keep receiving a unicast DCI scheduling only unicast data. The UE may receive a unicast DCI scheduling unicast data or a unicast DCI scheduling the PTP retransmission for multicast data.
In some aspects, the UE may transmit an SR, a buffer status report (BSR), or a delay status report (DSR) in an attempt to exit a low power PDCCH skipping mode and resume PDCCH monitoring. The UE may monitor unicast DCIs and not multicast downlink DCIs based at least in part on radio network temporary identifiers (RNTIs) for unicast and MBS, common search spaces or UE-specific search spaces for unicast and MBS, and/or DCI formats for unicast and MBS.
In some aspects, when the UE transmits the SR, the BSR, or the DSR in an attempt to exit the low power PDCCH skipping mode and resume PDCCH monitoring, the UE may monitor unicast DCIs and not multicast downlink DCIs, which may be based at least in part on different RNTIs for unicast (e.g., C-RNTI/CS-RNTI/MCS-C-RNTI) and MBS (e.g., G-RNTI/G-CS-RNTI for multicast in RRC connected mode), different Type3-CSS/USS configured for unicast PDCCH and separate Type3-CSS configured for MBS PDCCH, and/or different DCI formats with different sizes (e.g., one size for DCI format 1_0/0_0 for unicast or DCI format 4_1 for multicast and a different size for DCI format 4_2 for multicast). The UE, by reducing PDCCH monitoring, may reduce power consumption. In some cases, the network node may use an active time after the SR to schedule downlink MBS, but such a case may be enabled or disabled via RRC signaling, and may also be based at least in part on whether low latency MBS traffic is configured.
In some aspects, the UE may transmit the SR, the BSR, or the DSR in the attempt to exit the low power PDCCH skipping mode and resume PDCCH monitoring. The UE may resume monitoring fallback uplink DCIs, fallback downlink DCIs, and non-fallback downlink DCIs. The UE may resume monitoring fallback DCIs. The UE may monitor uplink DCIs and not downlink DCIs. The UE may monitor downlink-to-uplink DCIs with a ratio alpha that scales a number of blind decodings toward a downlink direction.
In some aspects, when the UE transmits the SR, the BSR, or the DSR associated with exiting a low power PDCCH skipping mode and resume PDCCH monitoring, the UE may receive an uplink DCI and not downlink DCIs (or limited DL DCIs), such that the UE may skew the search to downlink DCIs. The UE may only resume monitoring fallback uplink DCIs and both fallback and non-fallback downlink DCIs. The UE may only resume monitoring fallback DCIs (e.g., DCI 0_0 and DCI 1_0, as they have same size). The UE may monitor uplink DCIs and not downlink DCIs, which may be based at least in part on a different Type3-CSS/USS, when separately configured for a downlink PDCCH (for unicast downlink data and MBS downlink data) and an uplink PDCCH (for unicast uplink data). The UE may monitor downlink-to-uplink DCIs with a certain ratio alpha that scales a number of blind decodings toward a downlink direction.
In some aspects, the UE may transmit the NACK due to an incorrect PDSCH decoding, the UE may be configured to monitor fallback DCI and non-fallback DCI, and the incorrect PDSCH decoding may be associated with a PDSCH scheduled by the fallback DCI. The UE may monitor downlink DCIs and not uplink DCIs. The UE may monitor downlink DCI for fallback and non-fallback, and fallback uplink DCIs. The UE may search for downlink DCIs based at least in part on an alpha factor.
In some aspects, when the UE transmits the NACK due to the incorrect PDSCH decoding, the UE is configured to monitor both fallback DCI (e.g., DCI 0_0 and CI 1_0) and non-fallback DCI (e.g., DCI 0_1/2 and DCI 1_1/2), and the UE fails decoding a PDSCH scheduled by the fallback DCI, the UE may monitor only downlink DCI and not uplink DCI. The UE not monitoring the uplink DCI may not be ideal in cases when the UE misses uplink DCIs as well. Alternatively, the UE may monitor downlink DCI (configured fallback and non-fallback), but only fallback uplink DCIs, or the UE may skew the search toward downlink DCI with an alpha factor.
In some aspects, the UE may be configured with an SSSG specific to unicast and an SSSG specific to MBS. The UE may switch to a non-MBS SSSG, such as the SSSG specific to unicast, based at least in part on an SR transmission, or the UE may switch to the SSSG specific to MBS based at least in part on a NACK transmission in a NACK-only shared PUCCH resource.
In some aspects, a NACK-only event based SSSG switch may be defined. In an SSSG switching, the UE may switch to the non-MBS SSSG when an SR is transmitted. The UE may be configured with SSSG specific to MBS and SSSG specific to unicast. When the UE reports a NACK in the NACK-only shared PUCCH resource, the UE may immediately switch into the MBS configured SSSG.
As indicated above,
As shown in
The network node may transmit, to the UE, a non-scheduling DCI (dummy grant) with a PDCCH skipping indication. The UE may transmit, to the network node and after the PDCCH skipping indication is received, a NACK in a NACK-only mode 2, after which the UE may resume monitoring only a GC-PDCCH for retransmissions. In this example, an MBS shared PUCCH resource used for mode 2 (NACK-only) may carry only multicast NACK-only feedback. The UE may resume monitoring of only the GC-PDCCH after reporting the NACK-only. The UE may save power by not searching over unicast DCIs.
As indicated above,
As shown in
As indicated above,
As shown in
As indicated above,
As shown in
As further shown in
As further shown in
As further shown in
Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
In a first aspect, process 1100 includes transmitting the NACK in the NACK-only feedback mode in a shared PUCCH resource due to incorrectly decoding a GC-PDSCH transmission scheduled by the DCI, and performing PDCCH monitoring is for a GC-PDCCH transmission and not for a unicast PDCCH.
In a second aspect, alone or in combination with the first aspect, process 1100 includes transmitting the NACK in the ACK-NACK feedback mode on a UE-specific PUCCH resource due to incorrectly decoding a GC-PDSCH transmission scheduled by the DCI or due to incorrectly decoding a unicast PDSCH, and performing PDCCH monitoring is for at least one of a CG-PDCCH transmission or unicast DCIs.
In a third aspect, alone or in combination with one or more of the first and second aspects, process 1100 includes performing PDCCH monitoring based at least in part on an RRC configuration.
In a fourth aspect, alone or in combination with one or more of the first through third aspects, process 1100 includes transmitting the NACK on the PUCCH resource or a PUSCH resource due to incorrectly decoding a unicast PDSCH scheduled by the DCI, and performing PDCCH monitoring is for a unicast PDCCH transmission and not a multicast PDCCH transmission.
In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process 1100 includes transmitting an SR, a BSR, or a DSR associated with exiting a low power PDCCH skipping mode and perform PDCCH monitoring.
In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process 1100 includes monitoring unicast DCIs and not multicast downlink DCIs based at least in part on one or more of RNTIs for unicast and MBS, common search spaces or UE-specific search spaces for unicast and MBS, or DCI formats for unicast and MBS.
In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 1100 includes monitoring fallback uplink DCIs, fallback downlink DCIs, and non-fallback downlink DCIs, monitoring fallback DCIs, monitoring uplink DCIs and not downlink DCIs, or monitoring downlink-to-uplink DCIs with a ratio alpha that scales a number of blind decodings toward a downlink direction.
In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process 1100 includes monitoring fallback DCI and non-fallback DCI, wherein the incorrectly decoded PDSCH transmission is a PDSCH transmission scheduled by the fallback DCI.
In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, process 1100 includes monitoring downlink DCIs and not uplink DCIs, monitoring downlink DCI for fallback and non-fallback, and fallback uplink DCIs, or searching for downlink DCIs based at least in part on an alpha factor.
In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the UE is configured with an SSSG specific to unicast and an SSSG specific to MBS, and process 1100 includes switching to the SSSG specific to unicast based at least in part on an SR transmission, or switching to the SSSG specific to MBS based at least in part on a NACK transmission in a NACK-only shared PUCCH resource.
Although
As shown in
As further shown in
As further shown in
Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
In a first aspect, the feedback mode is a NACK-only feedback mode, and the PDCCH monitoring is for a GC-PDCCH transmission and not for a unicast PDCCH.
In a second aspect, alone or in combination with the first aspect, the feedback mode is an ACK-NACK feedback mode, and the PDCCH monitoring is for at least one of a CG-PDCCH transmission or unicast DCIs.
In a third aspect, alone or in combination with one or more of the first and second aspects, process 1200 includes transmitting an RRC configuration associated with performing PDCCH monitoring.
Although
In some aspects, the apparatus 1300 may be configured to perform one or more operations described herein in connection with
The reception component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1308. The reception component 1302 may provide received communications to one or more other components of the apparatus 1300. In some aspects, the reception component 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1300. In some aspects, the reception component 1302 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with
The transmission component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1308. In some aspects, one or more other components of the apparatus 1300 may generate communications and may provide the generated communications to the transmission component 1304 for transmission to the apparatus 1308. In some aspects, the transmission component 1304 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1308. In some aspects, the transmission component 1304 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection with
The communication manager 1306 may support operations of the reception component 1302 and/or the transmission component 1304. For example, the communication manager 1306 may receive information associated with configuring reception of communications by the reception component 1302 and/or transmission of communications by the transmission component 1304. Additionally, or alternatively, the communication manager 1306 may generate and/or provide control information to the reception component 1302 and/or the transmission component 1304 to control reception and/or transmission of communications.
The reception component 1302 may receive a configuration associated with PDCCH monitoring resumption after NACK. The reception component 1302 may receive DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell. The transmission component 1304 may transmit a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission. The communication manager 1306 may perform, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs, and skip, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs.
The transmission component 1304 may transmit the NACK comprises transmitting the NACK in a NACK-only feedback mode in a shared PUCCH resource due to incorrectly decoding a group common PDSCH (GC-PDSCH) transmission scheduled by the DCI.
The communication manager 1306 may perform PDCCH monitoring for a GC-PDCCH transmission and not for a unicast PDCCH. The transmission component 1304 may transmit the NACK in an ACK-NACK feedback mode on a UE-specific PUCCH resource due to incorrectly decoding a GC-PDSCH transmission scheduled by the DCI or due to incorrectly decoding a unicast PDSCH.
The communication manager 1306 may perform PDCCH monitoring for at least one of a CG-PDCCH transmission or unicast DCIs. The transmission component 1304 may transmit the NACK on the PUCCH resource or a PUSCH resource due to incorrectly decoding a unicast PDSCH scheduled by the DCI.
The communication manager 1306 may perform PDCCH monitoring for a unicast PDCCH transmission and not a multicast PDCCH transmission. The transmission component 1304 may transmit an SR, a BSR, or a DSR associated with exiting a low power PDCCH skipping mode and perform PDCCH monitoring. The communication manager 1306 may monitor unicast DCIs and not multicast downlink DCIs based at least in part on one or more of: RNTIs for unicast and MBS, common search spaces or UE-specific search spaces for unicast and MBS, or DCI formats for unicast and MBS. The communication manager 1306 may monitor fallback uplink DCIs, fallback downlink DCIs, and non-fallback downlink DCIs. The communication manager 1306 may monitor fallback DCIs. The communication manager 1306 may monitor uplink DCIs and not downlink DCIs. The communication manager 1306 may monitor downlink-to-uplink DCIs with a ratio alpha that scales a number of blind decodings toward a downlink direction.
The number and arrangement of components shown in
In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein in connection with
The reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1408. The reception component 1402 may provide received communications to one or more other components of the apparatus 1400. In some aspects, the reception component 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1400. In some aspects, the reception component 1402 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network node described in connection with
The transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1408. In some aspects, one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1408. In some aspects, the transmission component 1404 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1408. In some aspects, the transmission component 1404 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the network node described in connection with
The communication manager 1406 may support operations of the reception component 1402 and/or the transmission component 1404. For example, the communication manager 1406 may receive information associated with configuring reception of communications by the reception component 1402 and/or transmission of communications by the transmission component 1404. Additionally, or alternatively, the communication manager 1406 may generate and/or provide control information to the reception component 1402 and/or the transmission component 1404 to control reception and/or transmission of communications.
The transmission component 1404 may transmit a configuration associated with PDCCH monitoring resumption after NACK. The transmission component 1404 may transmit DCI that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink BWP of a serving cell. The reception component 1402 may receive a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded PDSCH transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped. The transmission component 1404 may transmit an RRC configuration associated with performing PDCCH monitoring.
The number and arrangement of components shown in
The following provides an overview of some Aspects of the present disclosure:
Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving downlink control information (DCI) that includes a physical downlink control channel (PDCCH) monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink bandwidth part (BWP) of a serving cell; transmitting a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded physical downlink shared channel (PDSCH) transmission, wherein the feedback mode is a NACK-only feedback mode or an acknowledgement (ACK)-NACK feedback mode; and terminating PDCCH skipping, performing, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs; and skipping, based at least in part on the NACK, PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs.
Aspect 2: The method of Aspect 16, wherein: transmitting the NACK comprises transmitting the NACK in the NACK-only feedback mode in a shared physical uplink control channel (PUCCH) resource due to incorrectly decoding a group common PDSCH (GC-PDSCH) transmission scheduled by the DCI; and performing PDCCH monitoring is for a GC-PDCCH transmission and not for a unicast PDCCH.
Aspect 3: The method of any of Aspects 16-17, wherein: transmitting the NACK comprises transmitting the NACK in the ACK-NACK feedback mode on a UE-specific physical uplink control channel (PUCCH) resource due to incorrectly decoding a group common PDSCH (GC-PDSCH) transmission scheduled by the DCI or due to incorrectly decoding a unicast PDSCH; and performing PDCCH monitoring is for at least one of a CG-PDCCH transmission or unicast DCIs.
Aspect 4: The method of any of Aspects 16-18, wherein performing PDCCH monitoring is based at least in part on a radio resource control (RRC) configuration.
Aspect 5: The method of any of Aspects 16-19, wherein: transmitting the NACK comprises transmitting the NACK on the physical uplink control channel (PUCCH) resource or a PUSCH resource due to incorrectly decoding a unicast PDSCH scheduled by the DCI; and performing PDCCH monitoring is for a unicast PDCCH transmission and not a multicast PDCCH transmission.
Aspect 6: The method of any of Aspects 16-20, further comprising: transmitting a scheduling request, a buffer status report (BSR), or a delay status report (DSR) associated with exiting a low power PDCCH skipping mode and perform PDCCH monitoring.
Aspect 7: The method of Aspect 21, further comprising: monitoring unicast DCIs and not multicast downlink DCIs based at least in part on one or more of: radio network temporary identifiers (RNTIs) for unicast and MBS, common search spaces or UE-specific search spaces for unicast and MBS, or DCI formats for unicast and MBS.
Aspect 8: The method of Aspect 21, further comprising: monitoring fallback uplink DCIs, fallback downlink DCIs, and non-fallback downlink DCIs; monitoring fallback DCIs; monitoring uplink DCIs and not downlink DCIs; or monitoring downlink-to-uplink DCIs with a ratio alpha that scales a number of blind decodings toward a downlink direction.
Aspect 9: The method of any of Aspects 16-23, further comprising: monitoring fallback DCI and non-fallback DCI, wherein the incorrectly decoded PDSCH transmission is a PDSCH transmission scheduled by the fallback DCI.
Aspect 10: The method of Aspect 24, further comprising: monitoring downlink DCIs and not uplink DCIs; monitoring downlink DCI for fallback and non-fallback, and fallback uplink DCIs; or searching for downlink DCIs based at least in part on an alpha factor.
Aspect 11: The method of any of Aspects 16-25, wherein the UE is configured with a search space set group (SSSG) specific to unicast and an SSSG specific to MBS, and further comprising: switching to the SSSG specific to unicast based at least in part on a scheduling request transmission; or switching to the SSSG specific to MBS based at least in part on a NACK transmission in a NACK-only shared physical uplink control channel (PUCCH) resource.
Aspect 12: A method of wireless communication performed by a network node, comprising: transmitting a configuration associated with physical downlink control channel (PDCCH) monitoring resumption after negative acknowledgement (NACK); transmitting downlink control information (DCI) that includes a PDCCH monitoring adaptation field indicating to skip PDCCH monitoring for a duration on an active downlink bandwidth part (BWP) of a serving cell; and receiving a NACK, in accordance with a feedback mode, based at least in part on an incorrectly decoded physical downlink shared channel (PDSCH) transmission, wherein PDCCH monitoring for PDCCH candidates carrying groupcast scheduling DCIs is performed, and PDCCH monitoring for PDCCH candidates carrying unicast scheduling DCIs is skipped.
Aspect 13: The method of Aspect 27, wherein the feedback mode is a NACK-only feedback mode, and the PDCCH monitoring is for a group common PDSCH (GC-PDCCH) transmission and not for a unicast PDCCH transmission.
Aspect 14: The method of any of Aspects 27-28, wherein the feedback mode is an acknowledgement (ACK)-NACK feedback mode, and the PDCCH monitoring is for a group common PDSCH (GC-PDCCH) transmission and unicast DCIs, for a GC-PDCCH, or for unicast DCIs.
Aspect 15: The method of any of Aspects 27-29, further comprising: transmitting a radio resource control (RRC) configuration associated with performing PDCCH monitoring.
Aspect 16: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-11.
Aspect 17: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-11.
Aspect 18: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-11.
Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-11.
Aspect 20: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-11.
Aspect 21: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-11.
Aspect 22: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-11.
Aspect 23: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 12-15.
Aspect 24: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 12-15.
Aspect 25: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 12-15.
Aspect 26: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 12-15.
Aspect 27: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 12-15.
Aspect 28: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 12-15.
Aspect 29: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 12-15.
The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.
As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.
As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.
As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. 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, as well as any combination with multiples of the same element (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).
No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based on or otherwise in association with” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of”). It should be understood that “one or more” is equivalent to “at least one.”
Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.
