Physical downlink control channel (PDCCH) monitoring adaptation for two-stage downlink control information (DCI)

Abstract

Certain aspects of this disclosure provide techniques for adaptive monitoring of the Physical Downlink Control Channel (PDCCH). One method typically includes: receiving an indication in a downlink channel that instructs the cessation of monitoring of a plurality of PDCCH monitoring opportunities previously scheduled for monitoring by a monitoring device after an activation time for the indication, wherein the downlink channel or at least one of the plurality of PDCCH monitoring opportunities is associated with at least one of a first-level DCI or a second-level DCI in a two-level downlink control information (DCI); monitoring at least one of the plurality of PDCCH monitoring opportunities after the activation time based on the indication; and ceasing monitoring of one or more of the plurality of PDCCH monitoring opportunities after the activation time based on the indication.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to U.S. Patent Application Serial No. 18 / 519,916, filed November 27, 2023, entitled “PHYSICAL DOWNLINK CONTROLCHANNEL (PDCCH) MONITORING ADAPTATION FOR TWO STAGE DOWNLINK CONTROLINFORMATION (DCI)”, the entire contents of which are incorporated herein by reference.

[0003] introduction Technical Field

[0004] Various aspects of this disclosure relate to wireless communications, and more specifically to techniques for adaptive monitoring of the Physical Downlink Control Channel (PDCCH).

[0005] Related technical descriptions

[0006] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with several users by sharing available wireless communication system resources.

[0007] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0008] One aspect provides a method for wireless communication by a device. The method includes: receiving an indication in a downlink channel indicating, after an activation time for the indication, to cease monitoring of a plurality of physical downlink control channel (PDCCH) monitoring opportunities previously scheduled for monitoring by the device, wherein the downlink channel or at least one of the plurality of PDCCH monitoring opportunities is associated with at least one of a first-level DCI or a second-level DCI in a two-level downlink control information (DCI); monitoring at least one of the plurality of PDCCH monitoring opportunities after the activation time based on the indication; and ceasing monitoring of one or more of the plurality of PDCCH monitoring opportunities after the activation time based on the indication.

[0009] Other aspects provide: one or more means capable of operating to, configured to, or otherwise adapted to perform any part of any method described herein (e.g., such that it can be implemented by only one means or in a distributed manner across multiple means); one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of the one or more means, cause the one or more means to perform any part of any method described herein (e.g., such that the instructions can be included in only one computer-readable medium or in a distributed manner across multiple computer-readable media, such that the instructions can be executed by only one processor or by multiple processors in a distributed manner). Each of the one or more means may include one or more processors, and / or enable execution to be performed by only one means or in a distributed manner across multiple means; one or more computer program products embodied on one or more computer-readable storage media, the computer-readable storage media including code for performing any part of any method described herein (e.g., such that the code may be stored in only one computer-readable medium or in a distributed manner across computer-readable media); and / or one or more means, the one or more means including one or more components for performing any part of any method described herein (e.g., such that execution will be performed by only one means or by multiple means in a distributed manner). By way of example, an means may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks. An means may include: one or more memories; and one or more processors configured to enable the means to perform any part of any method described herein. In some examples, one or more processors may be pre-configured to perform the various functions or operations described herein without being configured by software.

[0010] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0011] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0012] Figure 1 An example wireless communication network is depicted.

[0013] Figure 2 An example decomposed base station architecture is described.

[0014] Figure 3 Various aspects of the example base station and example user equipment (UE) are described.

[0015] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0016] Figures 5A to 5C An example two-level downlink control information (DCI) use case is described.

[0017] Figures 6A to 6C An example physical downlink control channel (PDCCH) monitoring behavior of a UE adapted to immediately stop monitoring the PDCCH monitoring timing previously scheduled for monitoring by the UE is described.

[0018] Figure 7 An example issue is described that relates to the PDCCH monitoring behavior of a UE that is adapted to monitor both single-level DCI and two-level DCI.

[0019] Figure 8 An example PDCCH monitoring and adaptation for two-level DCI is described.

[0020] Figures 9A to 9B An example PDCCH monitoring behavior of a UE adapted to monitor at least the first PDCCH monitoring timing associated with the first level DCI in two levels of DCI after receiving a PDCCH monitoring adaptive indication is described.

[0021] Figures 10A to 10C An example PDCCH monitoring behavior of a UE adapted to monitor all PDCCH monitoring opportunities associated with the first level of the two-level DCI after receiving a PDCCH monitoring adaptive indication is described.

[0022] Figures 11A to 11BAn example PDCCH monitoring behavior of a UE adapted to monitor the timing of PDCCH monitoring associated with the first level of DCI in a two-level DCI after receiving a PDCCH monitoring adaptive indication is described.

[0023] Figure 12 An example of the UE's adaptive PDCCH monitoring behavior is described after receiving a PDCCH monitoring adaptive indication for Search Space Set Group (SSSG) switching.

[0024] Figure 13 A method for wireless communication is described.

[0025] Figure 14 Various aspects of the example communication device are described. Detailed Implementation

[0026] User equipment (UE) can be configured to monitor two levels of downlink control information (DCI). That is, a UE can be configured to monitor at least two DCIs (e.g., a first-level DCI and one or more second-level DCIs) to obtain scheduling information for a given downlink channel or uplink channel. Techniques for implementing PDCCH monitoring adaptive indications (also referred to herein as "adaptive indications") to adjust the PDCCH monitoring behavior of a UE configured to monitor at least two levels of DCI are still under exploration.

[0027] Therefore, various aspects of this disclosure provide apparatus, methods, processing systems, and computer-readable media for adapting UE PDCCH monitoring behavior to at least two levels of DCI. In some cases, adapting PDCCH monitoring behavior involves the UE monitoring at at least one PDCCH monitoring event where the UE has been instructed to stop monitoring via adaptive indication.

[0028] For example, a PDCCH monitoring adaptive indication can be used to trigger a UE to stop monitoring one or more PDCCH monitoring moments that the UE was previously scheduled to monitor. As used herein, a PDCCH monitoring moment is a time interval during which the UE is expected to monitor the PDCCH used for DCI, such as when it is in CONNECTED mode (e.g., having a Radio Resource Control (RRC) connection established with a network entity).

[0029] In some aspects, the adaptive indication includes a PDCCH skip command that instructs (e.g., the adaptively indicated) the receiving UE to skip PDCCH monitoring for a specific duration, until the next discontinuous reception (DRX) activation duration (e.g., a periodic duration during which the UE is expected to be in a "wake-up" / active state to monitor the downlink channel, while during other time periods the UE is in a "sleep" state where the downlink channel is not monitored) or during the current DRX activation duration (e.g., within a DRX cycle). In other words, an indication including a PDCCH skip command instructs the UE to stop monitoring PDCCH monitoring opportunities scheduled during the indicated time period.

[0030] In some other implementations, the adaptive indication includes a Search Space Set Group (SSSG) switching command that indicates (e.g., the adaptive indication) that the receiving UE wants to switch from monitoring a first SSSG to monitoring a second SSSG indicated in the PDCCH monitoring adaptive indication. An SSSG includes one or more Search Space Sets (SSSs). For example, the UE may be configured to monitor a first SSS included in a first SSSG (e.g., along with one or more other SSSs). The SSSG switching indication received by the UE may indicate a switch from monitoring the first SSSG to monitoring the second SSSG, where the second SSSG does not include the first SSS. Therefore, in response to receiving the adaptive indication, the UE may stop monitoring the PDCCH monitoring timing associated with the first SSS and correspondingly stop monitoring the first SSSG.

[0031] In some cases, in addition to UE power-saving features such as Bandwidth Partial (BWP) adaptation and / or Wake-up Signal (WUS) , the PDCCH monitoring adaptation techniques described above also help reduce power consumption at the UE. Furthermore, PDCCH monitoring adaptation techniques help support new use cases with short packet arrival intervals (e.g., by enabling short UE sleep), such as extended reality (XR) (including augmented reality (AR) applications and / or virtual reality (VR) applications).

[0032] Despite its advantages, the use of PDCCH monitoring adaptive indication technology in situations where the UE is configured to monitor two-level DCIs (as an alternative to or supplement to single-level DCIs) is still under exploration. Specifically, in some cases, the UE is configured to monitor only a single-level DCI. That is, the UE is configured to monitor a single DCI to obtain all scheduling information (e.g., DCI content) for a given downlink channel (e.g., Physical Downlink Shared Channel (PDSCH)) or uplink channel (e.g., Physical Uplink Shared Channel (PUSCH)), such as for subsequent uplink and / or downlink data transmissions. In such cases, the PDCCH monitoring adaptive indication can be carried in a single DCI, and the UE's PDCCH monitoring behavior can be adapted immediately after the activation time of the adaptive indication (e.g., the UE stops monitoring one or more PDCCHs). As used herein, the activation time can be the start application time for PDCCH skipping or SSSG handover triggered by the adaptive indication (e.g., such as an explicit symbol, subframe, frame, slot, etc.). Specifically, after receiving signaling including a PDCCH monitoring adaptation indication, the UE may need time to process the PDCCH monitoring adaptation indication, such as time to decode it and apply it to change its operation. For example, the UE may not immediately apply the PDCCH monitoring adaptation indication to stop monitoring PDCCH timings after receiving it, as it may process it first to apply it and stop monitoring PDCCH timings. Therefore, the activation time for the PDCCH monitoring adaptation indication can be based on the minimum amount of time required for the UE to process it after receiving it. The minimum time required to process the PDCCH monitoring adaptation can be uniform or variable across UEs. In cases where the minimum time for processing the PDCCH monitoring adaptation indication varies across UEs, a minimum processing time specific to the UE receiving the PDCCH monitoring adaptation indication can be communicated between the UE and the network entity that sent the PDCCH monitoring adaptation indication. In some cases, the communication of the minimum processing time occurs between the UE and the network entity before the transmission of the PDCCH monitoring adaptation. In some other cases, the communication of the minimum processing time occurs between the UE and the network entity after the transmission of PDCCH monitoring adaptation. In such cases, the activation time for the PDCCH monitoring adaptation indication may also be based on the minimum amount of time required to ensure that the UE and the network entity coordinate (e.g., synchronize) the activation time (e.g., the minimum amount of time for communication and agreeing on the activation time).

[0033] However, in some other cases, the UE is configured to monitor two-level DCIs as a supplement to or alternative to monitoring a single-level DCI. That is, the UE can be configured to monitor at least two DCIs (e.g., a first-level DCI and one or more second-level DCIs) to obtain all scheduling information (e.g., DCI content) for a given downlink or uplink channel. Currently, it is unknown which DCIs (e.g., a single-level DCI, a first-level DCI in a two-level DCI, and / or a second-level DCI in a two-level DCI) can carry an adaptive indication for PDCCH monitoring and its corresponding meaning, and how the UE should change its PDCCH monitoring behavior when an adaptive indication is received in a single-level DCI, a first-level DCI, and / or a second-level DCI. For example, whether the adaptive indication should affect both single-level DCI monitoring and two-level DCI monitoring, whether the UE should immediately stop monitoring after receiving a DCI, and how to handle scenarios where an adaptive indication is received after receiving a first-level DCI but before receiving the associated second-level DCI, etc., are still under investigation.

[0034] Therefore, when a UE is configured to monitor two-level DCI or both two-level DCI and single-level DCI, the aspects described herein provide techniques for: (1) communicating (e.g., transmitting and / or acquiring, such as sending and / or receiving) PDCCH monitoring adaptive indications; and (2) adapting PDCCH monitoring behavior based on such indications. For example, the aspects described herein provide techniques for carrying PDCCH monitoring adaptive indications using any scheduled DCI (such as a single-level DCI, the first-level DCI in a two-level DCI, and / or the second-level DCI in a two-level DCI). The PDCCH monitoring adaptive indication can be a PDCCH skip command or an SSSG handover command.

[0035] In some respects, in response to receiving an indication, the UE immediately adjusts its monitoring behavior based on the adaptive indication. For example, in the case of an adaptive indication for PDCCH skipping, the UE may immediately cease monitoring (e.g., after the activation time for the adaptive indication) of PDCCH monitoring timings associated with a single-level DCI (e.g., where the UE is configured to monitor both single-level and two-level DCIs), a first-level DCI, and / or a second-level DCI. As another example, in the case of an adaptive indication for SSSG handover (e.g., indicating a switch from monitoring from a first SSSG to a second SSSG), the UE may immediately cease monitoring (e.g., after the activation time for the adaptive indication) of PDCCH monitoring timings associated with the first SSSG.

[0036] Alternatively, in some aspects, in response to receiving an indication, the UE may monitor at least one PDCCH monitoring opportunity (e.g., for a second-level DCI or a first-level DCI) and cease monitoring other PDCCH monitoring opportunities that occur during the time period indicated in the adaptive indication (e.g., where the adaptive indication includes a PDCCH skip command) or are associated with an SSSG not indicated by the adaptive indication (e.g., where the adaptive indication includes an SSSG handover command). This behavior may include situations where the UE receives a first-level DCI in two-level DCIs and subsequently receives an adaptive indication (e.g., in a single-level DCI, in another first-level DCI in another two-level DCI, in a second-level DCI in that two-level DCI, or in another two-level DCI, etc.). Specifically, by monitoring at least one second-level DCI in a PDCCH monitoring opportunity where the UE has been instructed to cease monitoring after the activation of the adaptive indication, the UE may receive a second-level DCI associated with a previously received first-level DCI. Information from at least the first-level DCI and the second-level DCI may be used by the UE for data transmission scheduled by the first-level DCI and the second-level DCI. Therefore, data intended for use by the UE or expected to be sent by the UE can be conveyed without wasting the overhead incurred by sending the first-level DCI.

[0037] Some aspects of this article are discussed regarding the transmission of PDCCH monitoring adaptive indications via PDCCH. However, it should be noted that the techniques discussed herein are also applicable to the transmission of PDCCH monitoring adaptive indications via different channel types, such as the Physical Downlink Shared Channel (PDSCH) or another downlink channel.

[0038] The aspects described herein enable the use of PDCCH monitoring adaptive indications to reduce PDCCH monitoring behavior in UEs configured to monitor at least two levels of DCI. Therefore, power savings can be achieved when using PDCCH monitoring adaptive indications (e.g., as described above), along with the advantages of implementing two levels of DCI, including, for example, increased available downlink and / or uplink processing time for scheduled downlink and / or uplink data transmissions, reduced control overhead, robust and efficient transmission capabilities, and / or reduced blind decoding at the receiving UE, as described in detail below.

[0039] An introduction to wireless communication networks

[0040] The techniques and methods described herein can be used in a variety of wireless communication networks. Although aspects herein may be described using terms commonly associated with 3G, 4G, 5G, 6G and / or other generations of wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0041] Figure 1An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0042] Generally, wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of the BS, servers, etc.). Since such communication devices are part of wireless communication network 100 and facilitate wireless communication, they may be referred to as wireless communication devices. For example, various functions of the network and various devices associated with and interacting with the network may be considered network entities. Furthermore, wireless communication network 100 includes terrestrial aspects (such as terrestrial network entities (e.g., BS 102)) and non-terrestrial aspects (also referred to herein as non-terrestrial network entities) (such as satellite 140 and aircraft), which may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0043] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0044] Figure 1 Various example UEs 104 are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, data centers, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0045] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., transmitting or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to BS 102 and / or downlink (DL) (also known as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0046] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each of BS 102 provides communication coverage for a corresponding coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0047] Generally, a cell can refer to a portion, partition, or segment of wireless communication coverage served by a network entity within a wireless communication network. A cell may have geographical characteristics (such as a geographical coverage area) and radio frequency characteristics (such as time and / or frequency resources dedicated to the cell). For example, a specific geographical coverage area may be covered by multiple cells employing different frequency resources (e.g., bandwidth portions) and / or different time resources. As another example, a specific geographical coverage area may be covered by a single cell. In some contexts (e.g., carrier aggregation scenarios and / or multi-connectivity scenarios), the terms "cell" or "serving cell" may refer to or correspond to a specific carrier frequency (e.g., component carrier) used for wireless communication, and "cell group" may refer to or correspond to multiple carriers used for wireless communication. For example, in a carrier aggregation scenario, a UE may communicate on multiple component carriers corresponding to multiple (serving) cells in the same cell group, and in a multi-connectivity (e.g., dual-connectivity) scenario, a UE may communicate on multiple component carriers corresponding to multiple cell groups.

[0048] Although BS 102 is described as a single communication device in various aspects, it can be implemented in various configurations. For example, to give a few examples, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

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

[0050] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0051] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0052] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 may be the same or different.

[0053] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

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

[0055] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0056] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0057] The BM-SC 170 provides functionality for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, can be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS services to BS 102 belonging to a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

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

[0059] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0060] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides the UE with IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0061] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0062] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0063] Each of these units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of these units, or an associated processor or controller that provides instructions to the unit's communication interface, may be configured to communicate with one or more other units via transmission media. For example, these units may include a wired interface configured to receive signals or transmit signals to one or more other units via a wired transmission media. Additionally or alternatively, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission media or transmit signals to one or more other units, or both.

[0064] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling, as needed.

[0065] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0066] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, the RU240 controlled by the DU 230 may correspond to a logical node that is at least partially based on functional decomposition, such as lower-layer functional decomposition, to host RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) or both. In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration allows the DU 230 and CU210 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0067] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, SMO framework 205 may communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 211, via the O1 interface. Additionally, in some implementations, the SMO framework 205 may communicate directly with one or more DU 230s and / or one or more RU 240s via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0068] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0069] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0070] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0071] Generally, BS 102 includes various processors (e.g., 318, 320, 330, 338, and 340), antennas 334a to 334t (collectively referred to as 334), transceivers 332a to 332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 314). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various functions described herein related to wireless communication.

[0072] Generally, UE 104 includes various processors (e.g., 358, 364, 366, 370, and 380), antennas 352a to 352r (collectively referred to as 352), transceivers 354a to 354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieved from data source 362) and the wireless reception of data (e.g., provided to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various functions described herein related to wireless communication.

[0073] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. This control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

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

[0075] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a to 332t. Each modulator in transceivers 332a to 332t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a to 332t can be transmitted via antennas 334a to 334t, respectively.

[0076] To receive downlink transmissions, UE 104 includes antennas 352a to 352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a to 354r, respectively. Each demodulator in transceivers 354a to 354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0077] The RX MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a to 354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes (e.g., demodulates, deinterleaves, and decodes) the detected symbols, provides the decoded data for UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0078] Regarding the example uplink transmission, UE 104 further includes a transmission processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmission processor 364 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmission processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a to 354r (e.g., for SC-FDM), and transmitted to BS 102.

[0079] At BS 102, uplink signals from UE 104 can be received by antennas 334a to 334t, processed by demodulators in transceivers 332a to 332t, detected where applicable by RX MIMO detector 336, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 314 and the decoded control information to controller / processor 340.

[0080] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0081] Scheduler 344 can schedule UE to transmit data on the downlink and / or uplink.

[0082] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a to 332t, antennas 334a to 334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 334a to 334t, transceivers 332a to 332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0083] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a to 354t, antennas 352a to 352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 352a to 352t, transceivers 354a to 354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0084] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0085] In various aspects, artificial intelligence (AI) processors 318 and 370 may perform AI processing for BS 102 and / or UE 104, respectively. AI processor 318 may include AI accelerator hardware or circuitry, such as one or more neural processing units (NPUs), one or more neural network processors, one or more tensor processors, one or more deep learning processors, etc. AI processor 370 may also include AI accelerator hardware or circuitry. As an example, AI processor 370 may perform AI-based beam management, AI-based channel state feedback (CSF), AI-based antenna tuning, and / or AI-based positioning (e.g., Global Navigation Satellite System (GNSS) positioning). In some cases, AI processor 318 may use hardware-accelerated AI inference and / or AI training to process feedback (e.g., CSF) from UE 104. AI processor 318 may, for example, use hardware-accelerated AI inference associated with the CSF to decode compressed CSF from UE 104. In some cases, AI processor 318 may perform certain RAN-based functions, including, for example, network planning, network performance management, energy-efficient network operation, etc.

[0086] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0087] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0088] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0089] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0090] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 12 or 14 symbols, depending on the Cyclic Prefix (CP) type (e.g., 12 symbols per time slot for extended CP, or 14 symbols per time slot for normal CP). Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0091] In some respects, the number of time slots within a subframe (e.g., the time slot duration within a subframe) is based on a parameter set that defines the frequency-domain subcarrier spacing and symbol duration, as further described herein. In some respects, given a parameter set μ, each subframe has 2 μ The number of time slots is 1. Therefore, parameter sets (µ) 0 through 6 allow for 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. In some cases, extended CP (e.g., 12 symbols per time slot) can be used with specific parameter sets (e.g., parameter set 2, allowing 4 time slots per subframe). Subcarrier spacing and symbol length / duration are functions of the parameter sets. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. As an example, the parameter set... Corresponding to a subcarrier spacing of 15 kHz, and the parameter set This corresponds to a subcarrier spacing of 960 kHz. Symbol length / duration is negatively correlated with subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides a slot format with 14 symbols per slot (e.g., normal CP) and a parameter set with 4 slots per subframe. Example. In this case, the slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0092] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme, including, for example, quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM).

[0093] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0094] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0095] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0096] The secondary synchronization signal (SSS) can be located in symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identifier group number and radio frame timing.

[0097] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Blocks (SIBs)) not transmitted via the PBCH, and / or paging messages.

[0098] like Figure 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0099] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0100] Various aspects related to PDCCH monitoring and adaptation

[0101] The PDCCH may carry a DCI. The DCI may be transmitted on the PDCCH to a UE or a group of UEs. The DCI may contain: (1) scheduling information for uplink and / or downlink data channels, such as resource allocation for uplink and / or downlink data and control information; (2) instructions related to Hybrid Automatic Repeat Request (HARQ) (e.g., mechanisms for error detection and retransmission); (3) useful information for adjusting uplink power for power control; and / or (4) other signaling. Multiple different DCI formats may be defined, each serving a different purpose, such as uplink data scheduling (e.g., on the Physical Uplink Shared Channel (PUSCH)) and / or downlink data scheduling (e.g., on the PDSCH). In some respects, the DCI format specifies an ordered set of bit fields, where each field carries different transmission information, such as frequency resource allocation for data transmission, time resource allocation for data transmission, redundancy version (RV), and / or modulation and decoding (MCS) (e.g., specifying the modulation scheme and decoding rate to be used by the UE to decode downlink data).

[0102] DCI can be transmitted to the UE using resource elements (REs) within a control resource set (CORESET) (e.g., a physical resource set within a specific area of ​​a downlink resource grid), for example, via PDCCH. A UE intending to receive DCI can monitor PDCCH monitoring opportunities within a search space set (SSS) mapped to the CORESET in which DCI is transmitted, in order to detect and decode the DCI. For example, the UE can utilize up to 40 SSSs, each with an index from 0 to 39. In some aspects, each SSS configuration provides the UE with the SSS type (e.g., a common SSS (CSSS) or a UE-specific SSS (USSS)), the DCI format to be monitored, and / or the PDCCH monitoring opportunities used to monitor the reception of DCI (e.g., a monitoring mode for PDCCH monitoring opportunities).

[0103] PDCCH monitoring timing can be a specific time interval during which the UE is expected to monitor PDCCH, such as for DCI, when in CONNECTED mode. The frequency of PDCCH monitoring timing for DCI that the UE can monitor can be based on PDCCH monitoring periodicity. Different SSSs configured at the UE can have different PDCCH monitoring periodicities. For example, the PDCCH monitoring periodicity for a first SSS (e.g., belonging to a first SSSG that includes multiple SSSs and that first SSS) can be greater than the PDCCH monitoring periodicity for a second SSS (e.g., belonging to a second SSSG that includes multiple other SSSs and that second SSS), and therefore includes sparser PDCCH monitoring timing (e.g., fewer timings with longer intervals between timings).

[0104] The UE can be configured to monitor one or more PDCCH monitoring opportunities in each time slot in the time domain (e.g., based on information included in one or more SSSs configured at the UE) to decode the PDCCH in each time slot. More specifically, utilizing the received information included in the configured SSS at the UE, the UE can apply blind decoding (e.g., the UE attempts to decode a candidate set to identify whether one of these candidates retains its control information) to detect the corresponding DCI in each time slot, which may include scheduling information for uplink data and / or downlink data. Based on the received DCI, the UE may have sufficient information to continue receiving and / or transmitting on other channels, such as PDSCH and / or PUSCH.

[0105] The requirement for the UE to monitor the PDCCH used for DCI in each time slot is a contributing factor to power consumption at the UE. Therefore, several power-saving techniques have been introduced, such as BWP-based bandwidth adaptation (e.g., reduced PDCCH monitoring, MIMO layer adaptation, secondary cell (SCell) sleep, and cross-time slot scheduling), wake-up signals (WUS) for Connected mode discontinuous reception (C-DRX), and UE assistance information (UAI). Another power-saving technique involves using PDCCH monitoring adaptive indications as discussed herein.

[0106] Specifically, a PDCCH monitoring adaptive indication may be transmitted to the UE, such as in the DCI and more specifically in the scheduling DCI used for scheduling unicast and / or multicast data. The adaptive indication can be used to trigger PDCCH skipping and / or SSSG handover at the UE to reduce PDCCH monitoring at the UE. When the PDCCH skipping and / or SSSG handover indication is transmitted, the power used for data channel demodulation can be adjusted accordingly.

[0107] For example, an adaptive indication for triggering PDCCH skipping can trigger the UE receiving the corresponding adaptive indication to skip (e.g., stop) monitoring one or more PDCCH monitoring opportunities that the UE was previously scheduled to monitor. One or more PDCCH monitoring opportunities may occur temporally during a time period following the activation time of the adaptive indication. On the other hand, an adaptive indication for triggering SSSG switching can trigger the UE receiving the indication to stop monitoring PDCCH monitoring opportunities associated with the current SSSG and begin monitoring PDCCH monitoring opportunities associated with a target (e.g., the indicated) SSSG (e.g., switching from the current SSSG to the target SSSG after the activation time of the adaptive indication received by the UE). In some cases, such SSSG switching is used to enable the UE to monitor fewer PDCCH monitoring opportunities by switching from an SSSG associated with more intensive PDCCH monitoring opportunities (e.g., a larger number of opportunities with smaller periodicity) to an SSSG associated with sparser PDCCH monitoring opportunities (e.g., a smaller number of opportunities with larger periodicity). Therefore, using any indication, the UE can monitor fewer PDCCH monitoring opportunities than the PDCCH monitoring opportunities initially scheduled for monitoring by the UE, thereby reducing power consumption at the UE. Furthermore, the UE can switch between different PDCCH monitoring intensities at different times based on one or more adaptive indications to achieve power savings.

[0108] Various aspects related to single-level DCI and two-level DCI

[0109] In some implementations, the UE is configured to monitor only a single-level DCI. That is, the UE is configured to monitor a single DCI to obtain all scheduling information (e.g., DCI content) for either the downlink or uplink channel. In some cases, the single-level DCI design provides the flexibility to schedule various services with different Quality of Service (QoS) requirements.

[0110] In some other implementations, the UE is configured to monitor two-level DCIs as a supplement to or alternative to monitoring a single-level DCI. Unlike a single-level DCI, with a two-level DCI, the UE is configured to monitor at least two DCIs (e.g., a first-level DCI and one or more second-level DCIs) to obtain all scheduling information (e.g., DCI content) for a downlink or uplink channel. For example, a network entity may send the first-level DCI and the second-level DCI associated with the first-level DCI to the UE (e.g., they together constitute a two-level DCI). The second-level DCI may be “associated” with the first-level DCI because both the first-level DCI and the second-level DCI may each contain scheduling information associated with a single downlink or uplink channel (such as a single downlink or uplink data transmission). The UE may be configured to monitor two-level DCIs, and therefore may monitor both the first-level DCI and the second-level DCI sent by the network entity. Based on this monitoring, the UE can detect and decode both the first-level DCI and the second-level DCI, and use the information contained in the first-level DCI and the second-level DCI together to receive downlink data from network entities or send uplink data to network entities.

[0111] Configure the UE to monitor two levels of DCI in various situations (including, for example) Figures 5A to 5C This may be useful in the cases illustrated in the example.

[0112] For example, in Figure 5A In this context, a two-stage DCI can be used to provide additional downlink processing time for upcoming downlink data transmissions. Specifically, as shown in the figure, network entity 502 (e.g., such as...) Figure 1 and Figure 3 BS 102 in the middle) to UE 504 (e.g., such as Figure 1 and Figure 3UE 104 in the example sends a first-level DCI 510 and a second-level DCI 514 (e.g., associated with the first-level DCI 510). Both the first-level DCI 510 and the second-level DCI 514 can be used to schedule resources for downlink data transmission (e.g., PDSCH 516). The first-level DCI 510 may be sent earlier in time than the second-level DCI 514, which is sent closer in time to the time when the downlink data transmission (e.g., PDSCH 516) is scheduled. For example, the first-level DCI 510 may be sent before the time when UE 504 is expected to send a HARQ report 512 (e.g., HARQ ACK / NACK feedback) for previous data transmission (e.g., previous data transmitted via PDSCH). By scheduling downlink resources for downlink data transmission before receiving HARQ feedback for previous data transmissions, UE 504 can begin demodulation reference signal (DMRS) processing and channel estimation before receiving the second-level DCI 514.

[0113] Figure 5B The text further describes how utilizing a two-stage DCI could be useful for reducing control overhead. Specifically, such as... Figure 5B As shown, network entity 502 sends a first-level DCI 510 and multiple second-level DCIs (e.g., second-level DCI 514 and second-level DCI 518) to UE 504. The first-level DCI 510 provides common scheduling information for multiple transmissions (e.g., PDSCH 516 and PDSCH 522), while each second-level DCI 514, 518 provides link-adaptive scheduling information. By using the first-level DCI 510 to carry scheduling information for multiple transmissions, multiple DCI transmissions carrying similar information are avoided, thereby reducing control information transmission overhead.

[0114] Figure 5C This further illustrates how utilizing a two-stage DCI can allow for more robust transmission with the first-stage DCI and more spectrally efficient transmission with the second-stage DCI. For example, as... Figure 5CAs shown, network entity 502 sends a first-level DCI 510 and a second-level DCI 514 to UE 504. Both the first-level DCI 510 and the second-level DCI 514 can be used to schedule resources for downlink data transmission (e.g., PDSCH 516). The first-level DCI 510 may be sent to UE 504 via a first beam or a wide beam (e.g., an unrefined beam or a beamwidth that meets a first threshold), while the second-level DCI 514 may be sent to UE 504 via a second beam or a narrow beam (e.g., a refined beam or a beamwidth that meets both a second threshold and a first threshold). The references to wide and narrow beams can be relative to each other, such that a wide beam has a relatively wide beamwidth, and a narrow beam has a relatively narrow beamwidth.

[0115] Apart from Figures 5A to 5C Beyond the use cases illustrated, utilizing a two-level DCI can also increase uplink processing time at the UE receiving both the first-level and second-level DCIs. For example, the UE can begin preparing uplink data for transmission immediately after receiving the first-level DCI with minimal information. Therefore, the uplink data can be transmitted directly after the UE decodes the second-level DCI. Utilizing a two-level DCI can also help reduce blind decoding at the UE. Specifically, the DCI sizes can be aligned between different first-level DCI formats that require blind decoding.

[0116] Implementing both single-level DCI (e.g., NR single-level DCI) and two-level DCI designs, allowing the UE to be configured to monitor both single-level and two-level DCI, enables the realization of the advantages associated with both specific implementations, as described above. However, techniques for building two-level DCI designs (including techniques for enabling the use of adaptive indications for PDCCH monitoring) based on single-level DCI designs (e.g., including CORESET, SSS, PDCCH monitoring timing, PDCCH candidates, various DCI formats, DCI size alignment, blind decoding constraints, control channel element (CCE) constraints, PDCCH monitoring skip conditions, etc.) are still under exploration.

[0117] For example, when a UE is configured to monitor only a single-level DCI, a PDCCH monitoring adaptive indication can be carried in the single-level DCI to initiate PDCCH skipping and / or SSSG handover by one or more receiving UEs. The PDCCH monitoring adaptive indication allows the receiving UE to immediately cease monitoring PDCCH monitoring events such as those used for DCI (e.g., within a specified time period or not associated with the indicated target SSSG) after the activation time of the adaptive indication.

[0118] However, when the UE is configured to monitor single-level DCI and two-level DCI, it is unclear whether the PDCCH monitoring adaptive indication should be carried in the first level DCI of the single-level DCI, the first level DCI of the two-level DCI, or the second level DCI of the two-level DCI, and what its meaning is for each scenario. Furthermore, it is being explored how the UE should operate when it receives a PDCCH monitoring adaptive indication carried in a single-level DCI, the first level DCI, or the second level DCI. For example, should the adaptive indication affect both single-level DCI monitoring and two-level DCI monitoring? Should the UE immediately stop monitoring after receiving the DCI? How should scenarios where the adaptive indication is received after receiving the first level DCI but before receiving the associated second level DCI be handled?

[0119] Therefore, a technology is desired for PDCCH monitoring and adaptation when the UE is configured to monitor at least two levels of DCI.

[0120] Example aspects related to PDCCH monitoring for two-level DCI

[0121] The aspects described herein provide techniques for adapting PDCCH monitoring for single-level DCI and / or two-level DCI using PDCCH monitoring adaptive indications. As described above, PDCCH monitoring adaptive indications can be transmitted in downlink channels (e.g., PDCCH, PDSCH, etc.) such as in scheduled DCI and are used to trigger PDCCH skipping and / or SSSG switching at the receiving UE. More specifically, adaptive indications that trigger PDCCH skipping and / or SSSG switching (e.g., switching to an SSSG associated with sparser PDCCH monitoring timings) can trigger the UE to stop monitoring (e.g., after the activation time of the adaptive indication) one or more PDCCH monitoring timings that the UE was previously scheduled to monitor (e.g., after the activation time of the adaptive indication), thereby adapting the monitoring behavior (e.g., reducing monitoring performed by the UE) and improving power consumption at the UE. In some other cases, an adaptive indication that triggers an SSSG handover (e.g., a handover to an SSSG associated with more intensive PDCCH monitoring timing) can trigger the UE to stop monitoring (e.g., after the activation time for the adaptive indication) sparser (e.g., less frequent) PDCCH monitoring timings associated with the first SSSG and begin monitoring intensive (e.g., more frequent) PDCCH monitoring timings associated with the second SSSG, thereby adapting the monitoring behavior (e.g., increasing the frequency of monitoring by the UE) and improving the reliability of communication between the UE and the network entity that sent the adaptive indication.

[0122] According to some implementations described herein, the PDCCH monitoring adaptive indication may be carried in the scheduling DCI (such as a single-level DCI, the first-level DCI in a two-level DCI, or the second-level DCI in a two-level DCI). For example, when the UE is configured to monitor only two-level DCI, the PDCCH monitoring adaptive indication may be carried in one of the following: (1) only the first-level DCI in a two-level DCI; (2) only the second-level DCI in a two-level DCI; or (3) both the first-level DCI and the second-level DCI. Alternatively, when the UE is configured to monitor both a single-level DCI and a two-level DCI, the PDCCH monitoring adaptive indication may be carried in one of the following: (1) only the single-level DCI; (2) only the first-level DCI in a two-level DCI; (3) only the second-level DCI in a two-level DCI; (4) both the first-level DCI and the second-level DCI; or (5) each of the single-level DCI, the first-level DCI, and the second-level DCI.

[0123] Besides carrying the adaptive indication in a single-level DCI, it can also be beneficial to carry the adaptive indication in the first-level DCI, the second-level DCI, or both (e.g., where the UE is configured to monitor both levels of DCI). For example, using the first-level DCI to carry the adaptive indication allows the receiving UE to immediately begin the indicated PDCCH monitoring adaptive behavior triggered by the adaptive indication. Skipping monitoring one or more PDCCH monitoring opportunities in advance without expecting any control information can further increase power savings at the UE. Furthermore, switching to the DCI in the SSSG associated with more intensive / frequent PDCCH monitoring opportunities in advance based on receiving the adaptive indication in the first-level DCI can help minimize handover latency at the UE. Alternatively, using the second-level DCI instead of the first-level DCI to carry the adaptive indication allows the network entity sending the DCI to fine-tune the PDCCH monitoring adaptive timing. For example, if a first-level DCI is associated with multiple second-level DCIs to be transmitted during sequential PDCCH monitoring, the network entity can transmit the adaptive indication in the first, second, and third time-time-time second-level DCIs, etc. Therefore, the network entity can select the timing for when the adaptive indication should be transmitted to the UE, and thus the UE applies it upon receiving the second-level DCI carrying the adaptive indication. Finally, using both the first-level and second-level DCIs to carry the adaptive indication helps to achieve the advantages associated with carrying the adaptive indication in the first-level DCI as well as the advantages associated with carrying the adaptive indication in the second-level DCI; however, this incurs additional overhead.

[0124] In some respects, upon receiving a DCI that includes an adaptive indication (e.g., a single-level DCI, a first-level DCI in a two-level DCI, and / or a second-level DCI in a two-level DCI), the UE immediately adjusts its monitoring behavior based on the adaptive indication. For example, in the case where the adaptive indication is used for PDCCH skipping, the UE may immediately cease monitoring (e.g., after the activation time for the adaptive indication) the PDCCH monitoring timing associated with one or more single-level DCIs, one or more first-level DCIs, and / or one or more second-level DCIs (e.g., regardless of where the adaptive indication is received, such as in a single-level DCI, a first-level DCI, or a second-level DCI). Alternatively, when the adaptive indication is used for SSSG handover, the indication switches from monitoring the PDCCH monitoring timing associated with the first SSSG to monitoring the PDCCH monitoring timing associated with the second SSSG. The UE may immediately stop monitoring (e.g., after the activation time for the adaptive indication) the PDCCH monitoring timing associated with the first SSSG (e.g., and associated with one or more single-level DCIs, one or more first-level DCIs and / or one or more second-level DCIs), and begin monitoring the PDCCH monitoring timing associated with the second SSSG (e.g., and associated with one or more single-level DCIs, one or more first-level DCIs and / or one or more second-level DCIs).

[0125] Figures 6A to 6C An example PDCCH monitoring behavior of a UE that is adapted to immediately stop monitoring the PDCCH monitoring timing that the UE was previously scheduled to monitor. Figures 6A to 6C An example scenario is depicted where a PDCCH monitoring adaptive indication (e.g., indication 606) is carried (e.g., via PDCCH) in a single-level DCI 610, a first-level DCI 612, and a second-level DCI 614, respectively. The adaptive indication can be used to trigger PDCCH skipping or SSSG switching.

[0126] like Figure 6A As shown, network entity 602 (e.g., such as...) Figure 1 and Figure 3 BS 102 in the middle) to UE 604 (e.g., such as Figure 1 and Figure 3UE 604 sends a single-level DCI 610. UE 604 can be configured to monitor both single-level DCI and two-level DCI, and therefore monitors and receives / detects single-level DCI 610 based on this configuration. UE 604 may receive single-level DCI 610 before the first and second level DCIs of the next two-level DCIs at the received time (e.g., the DCIs of the previous two levels DCIs may have been transmitted before receiving single-level DCI 610), such as during one or more PDCCH monitoring opportunities 620 previously scheduled for monitoring by UE 604. Single-level DCI 610 includes an indication 606 that triggers PDCCH skipping or SSSG switching for PDCCH monitoring at UE 604. Therefore, in response to receiving indication 606 and after the activation time 605 of indication 606, UE 604 stops monitoring the PDCCH monitoring opportunities 620 previously scheduled for monitoring by UE 604. In some cases, PDCCH monitoring timing 620 is a monitoring timing that falls within a time period following the activation time 605 of indication 606, where indication 606 is a PDCCH skip command for that time period. These PDCCH monitoring timings 620 can be monitoring timings used by UE 604 to monitor single-level DCI, first-level DCI, and / or second-level DCI. Although in Figure 6A Not shown, but after this time period ends, UE 604 may resume monitoring the PDCCH monitoring timing that UE 604 was scheduled to monitor. In some other cases, PDCCH monitoring timing 620 is a monitoring timing associated with an SSSG that UE 604 previously monitored before receiving indication 606.

[0127] and Figure 6A The difference lies in Figure 6B In this context, indication 606 is carried within the first-level DCI 612 (e.g., not in the single-level DCI 610). In some cases, after sending the single-level DCI 610 to UE 604, network entity 602 sends the first-level DCI 612, including indication 606, to UE 604. Similar to... Figure 6A ,exist Figure 6BIn response to receiving indication 606 and after the activation time 607 of indication 606, UE 604 ceases monitoring the PDCCH monitoring timing 630 that UE 604 was previously scheduled to monitor. PDCCH monitoring timing 630 can be a monitoring timing occurring during a time period after the activation time 607 of indication 606, or a monitoring timing associated with an SSSG that UE 604 was previously scheduled to monitor (e.g., before the activation time 607 of indication 606). These PDCCH monitoring timings 630 can be monitoring timings used by UE 604 to monitor single-level DCI, first-level DCI, and / or second-level DCI. In some aspects, indication 606 carried in first-level DCI 612 can indicate the monitoring behavior of UE 604 when monitoring two-level DCI instead of single-level DCI. Therefore, PDCCH monitoring timing 630 can be monitoring timings used by UE 604 to monitor first-level DCI and / or second-level DCI, while monitoring of PDCCH monitoring timings used for single-level DCI remains unchanged.

[0128] and Figure 6A and Figure 6B The difference lies in Figure 6C In this context, indication 606 is carried in the second-level DCI 614 (e.g., not in the single-level DCI 610 and / or the first-level DCI 612). The second-level DCI 614 is sent to the UE 604 by network entity 602 after the first-level DCI 612 is sent to the UE 604 (e.g., where the second-level DCI 614 is associated with the first-level DCI 612). Additionally, in some cases, the second-level DCI 614, including indication 606, is sent to the UE 604 by network entity 602 after the single-level DCI 610 is sent to the UE 604 before or after the first-level DCI 612. Similar to... Figure 6A and Figure 6B ,exist Figure 6C In response to receiving indication 606 and after the activation time 609 of indication 606, UE 604 stops monitoring the PDCCH monitoring opportunity 640 that UE 604 was previously scheduled to monitor. PDCCH monitoring opportunity 640 can be a monitoring opportunity occurring during a time period after the activation time 609 of indication 606, or a monitoring opportunity associated with an SSSG that UE 604 was previously scheduled to monitor after the activation time 609 of indication 606. These PDCCH monitoring opportunities 640 can be monitoring opportunities used by UE 604 to monitor single-level DCI, other first-level DCI, and / or second-level DCI.

[0129] In some cases, the PDCCH monitoring adaptive indication is carried in a single-level DCI, which is transmitted later in time than the first-level DCI but earlier in time than the second-level DCI. For example, as Figure 7 As shown, network entity 702 (e.g., such as Figure 1 and Figure 3 BS 102 in the middle) to UE 704 (e.g., such as Figure 1 and Figure 3 The single-level DCI 710 sent by UE 104 is used to carry indication 706 (e.g., for PDCCH skipping or SSSG handover). UE 704 may receive the single-level DCI 710 after receiving the first-level DCI 712, but before receiving the second-level DCI associated with the first-level DCI 712. Based on receiving indication 706 in the single-level DCI 710 and after the activation time 705 of indication 706, UE 704 immediately stops monitoring the PDCCH monitoring timing 720. However, if UE 704 immediately stops monitoring the PDCCH monitoring timing 720 after the activation time 705 of indication 706 (and after receiving the first-level DCI 712), UE 704 may not receive any second-level DCI associated with the first-level DCI 712 (e.g., may not receive...). Figure 7 The diagram shows the second-level DCI 714 and the second-level DCI 718 associated with the first-level DCI 712. In other words, if one or more PDCCH monitoring opportunities 720 are used to monitor the second-level DCI and UE 704 immediately stops monitoring the PDCCH monitoring opportunity 720 after the activation time 705 of indication 706, then UE 704 may not receive the second-level DCI associated with the already received first-level DCI 712 (e.g., scheduling downlink or uplink data transmissions). Therefore, UE 704 may not have all the necessary information to receive downlink data transmissions or transmit uplink data transmissions (at least partially scheduled by the first-level DCI 712). Furthermore, transmitting previously received first-level DCI 712 may be unnecessary (e.g., a waste of resources).

[0130] Similar problems may arise when the PDCCH monitoring adaptive indication is carried in the following: (1) a Level 1 DCI; (2) a single-level DCI transmitted concurrently with the transmission of the Level 1 DCI (e.g., transmitted during the same PDCCH monitoring time associated with the Level 1 DCI); or (3) a Level 1 or Level 2 DCI that is later in time than or concurrently transmitted with the Level 1 DCI. In other words, similar problems may arise when the PDCCH monitoring adaptive indication is transmitted before the PDCCH monitoring time associated with the Level 2 DCI, which is associated with the previously transmitted Level 1 DCI in the two-level DCI sequence.

[0131] To overcome the problems associated with receiving PDCCH monitoring adaptive indications at or after receiving the first-level DCI and before receiving the second-level DCI (e.g., as regarding... Figure 7 As depicted and described, in some respects, the UE may monitor at least one PDCCH monitoring opportunity associated with the second level DCI in a two-level DCI after the activation time of the PDCCH monitoring adaptive indication, which indicates that DCI should not be monitored during that at least one PDCCH monitoring opportunity. In other words, the adaptive indication may trigger the UE to stop monitoring multiple monitoring opportunities; however, the UE may continue to monitor at least one of these monitoring opportunities associated with the second level DCI, which is associated with the previously received first level DCI (e.g., regardless of what the adaptive indication is instructing the UE to do).

[0132] Figure 8 This describes such PDCCH monitoring adaptation after receiving a PDCCH monitoring adaptation indication. As shown in the figure, network entity 802 (e.g., such as...) Figure 1 and Figure 3 BS 102 in the middle) to UE 804 (e.g., such as Figure 1 and Figure 3 UE104 in the system sends scheduled data transmissions (e.g., uplink data transmissions or downlink data transmissions). Figure 8 DCI 808 (not shown in the image). DCI 808 can be a single-level DCI, a first-level DCI, or a second-level DCI. In some cases, DCI 808 is a single-level DCI received by UE804 after receiving the first-level DCI but before receiving the second-level DCI associated with the first-level DCI.

[0133] DCI 808 includes an indication 806 (e.g., a PDCCH skip indication or SSSG handover indication) indicating the cessation of monitoring multiple PDCCH monitoring opportunities, such as PDCCH monitoring opportunities 820 previously scheduled for monitoring by UE 804 (e.g., an indication to stop monitoring PDCCH monitoring opportunities 820(1) to 820(4)). Based on receiving DCI 808 (e.g., via PDCCH), UE 804 (1) monitors at least one PDCCH monitoring opportunity 820, and (2) stops monitoring one or more of the PDCCH monitoring opportunities 820. Specifically, in this example, UE 804 monitors PDCCH monitoring opportunity 820(1) (e.g., the opportunity associated with the second-level DCI), and stops monitoring PDCCH monitoring opportunities 820(2) to 820(4) after the activation time 805 of indication 806. In some other examples, UE 804 additionally monitors PDCCH monitoring events 820(2), 820(3), and / or 820(4), and stops monitoring PDCCH monitoring events 820(3) and / or 820(4). In some other examples, UE 804 may simultaneously monitor at least one PDCCH monitoring event that indication 806 indicates to stop monitoring, and stop monitoring other PDCCH monitoring events that indication 806 indicates to stop monitoring. Monitoring at least one PDCCH monitoring event 820 in which UE 804 was instructed to stop monitoring (e.g., based on receiving indication 806 and after the activation time 805 of indication 806) when indication 806 is received in a single-level DCI after receiving a first-level DCI, or when indication 806 is received in an associated first-level DCI, enables UE 804 to receive a second-level DCI. The following is about Figures 9A to 9B , Figures 10A to 10C , Figures 11A to 11B and Figure 12 Additional details are provided regarding monitoring at least one PDCCH monitoring time after being instructed to stop monitoring multiple PDCCH monitoring times, including at least one PDDCH monitoring time.

[0134] For example, in some aspects, at least one PDCCH monitoring opportunity monitored by the UE after the activation time of the PDCCH monitoring adaptive indication is a PDCCH monitoring opportunity associated with (e.g., at the UE) a previously received first-level DCI, which occurs first in time after the adaptive indication is received. For example, at least one PDCCH monitoring opportunity is scheduled to carry a second-level DCI associated with the first-level DCI. Figures 9A to 9BAn example PDCCH monitoring behavior of a UE adapted to monitor at least the first PDCCH monitoring timing associated with the first level DCI in two levels of DCI after the activation time of the PDCCH monitoring adaptive indication received by the UE. Figure 9A A single-level DCI carrying adaptive indications is described, while Figure 9B The first-level DCI carrying adaptive indications is described.

[0135] like Figure 9A As shown, network entity 902 (e.g., such as Figure 1 and Figure 3 BS 102 in the middle) to UE 904 (e.g., such as Figure 1 and Figure 3 The single-level DCI 910 sent by UE 904 is used to carry indication 906. UE 904 may receive the single-level DCI 910 after receiving the first-level DCI 912 but before receiving the second-level DCI associated with the first-level DCI 912. The indication 906 included in the single-level DCI 910 indicates that UE 904 should stop monitoring PDCCH monitoring times 920(1) to 920(3) that UE 904 was previously scheduled to monitor. Based on receiving the indication 906 in the single-level DCI 910 and after the activation time 905 of the indication 906, UE 904 monitors at least PDCCH monitoring times 920(1), and in some cases, stops monitoring PDCCH monitoring times 920(2) and 920(3), or monitors one or more of PDCCH monitoring times 920(2) and 920(3).

[0136] For example, indication 906 may include a PDCCH skip command for a period of time following the activation time 905 of indication 906; therefore, the PDCCH monitoring opportunities 920(1) to 920(3) for which UE 904 is instructed to stop monitoring may be PDCCH monitoring opportunities scheduled during the period of time following the activation time 905 of indication 906. Based on receiving indication 906 in single-level DCI 910, UE 904 monitors at least PDCCH monitoring opportunity 920(1) occurring during that period of time (e.g., associated with second-level DCI), and in some cases, stops monitoring PDCCH monitoring opportunities 920(2) and 920(3), or monitors one or more of PDCCH monitoring opportunities 920(2) and 920(3) that also occur during that period of time.

[0137] As another example, instruction 906 may include an SSSG handover command indicating a switch from a first SSSG to a second SSSG; therefore, the PDCCH monitoring timings 920(1) to 920(3) for which UE 904 is instructed to stop monitoring may be PDCCH monitoring timings associated with the first SSSG. Based on receiving instruction 906 in single-level DCI 910 and after the activation time 905 of instruction 906, UE 904 monitors PDCCH monitoring timings 920(1) associated with the first SSSG (e.g., associated with the second-level DCI), and in some cases, stops monitoring PDCCH monitoring timings 920(2) and 920(3), or monitors one or more of PDCCH monitoring timings 920(2) and 920(3) that are also associated with the first SSSG.

[0138] In some cases, the PDCCH monitoring timing 920(1) is associated with a second-level DCI, which is associated with a first-level DCI 912. Therefore, by continuing to monitor at least the PDCCH monitoring timing 920(1), the UE 904 may be able to receive at least one second-level DCI associated with the previously received first-level DCI 912.

[0139] and Figure 9A The difference lies in Figure 9B In this context, indication 906 is sent to UE 904 via first-level DCI 912 (instead of single-level DCI 910). In some cases, UE 904 receives first-level DCI 912 including indication 906 after receiving single-level DCI 910. Although indication 906 is received in first-level DCI instead of single-level DCI 910 (e.g., as...), Figure 9A (as shown), but the UE behavior in response to receiving instruction 906 can be compared with... Figure 9A The same applies. Specifically, based on receiving instruction 906 and after the activation time 907 of instruction 906, UE 904 monitors at least one PDCCH monitoring opportunity 930 for which UE 904 is instructed to stop monitoring via instruction 906. In one example, UE 904 monitors at least PDCCH monitoring opportunity 930 (1) and stops monitoring one or more PDCCH monitoring opportunities 930 (2) to 920 (3) for which UE 904 is instructed to stop monitoring via instruction 906.

[0140] In some cases, the PDCCH monitoring timing 930(1) is associated with a second-level DCI, which is associated with a first-level DCI 912. Therefore, by continuing to monitor at least the PDCCH monitoring timing 930(1), the UE 904 may be able to receive at least one second-level DCI associated with the previously received first-level DCI 912.

[0141] In some other implementations, at least one PDCCH monitoring event is monitored by the UE after receiving the PDCCH monitoring adaptive indication (e.g., as...). Figure 8 (As shown) This includes all PDCCH monitoring opportunities that are associated with (e.g., at the UE) the previously received first-level DCI and occur after the activation time indicated by the adaptive. Figures 10A to 10C An example PDCCH monitoring behavior of a UE adapted to monitor all PDCCH monitoring timings associated with the first level DCI in a two-level DCI after the activation time of the PDCCH monitoring adaptive indication received by the UE.

[0142] like Figure 10A As shown, network entity 1002 (e.g., such as Figure 1 and Figure 3 BS 102 in the middle) to UE 1004 (e.g., such as Figure 1 and Figure 3 The single-level DCI 1010 sent by UE 1004 carries an indication 1006. UE 1004 may receive the single-level DCI 1010 after receiving the first-level DCI 1012, but before receiving the second-level DCI associated with the first-level DCI 1012. The indication 1006 included in the single-level DCI 1010 indicates that UE 1004 should stop monitoring the PDCCH monitoring events 1020(1) to 1020(4) that UE 1004 was previously scheduled to monitor. Based on receiving indication 1006 in single-level DCI 1010 and after the activation time 1005 of indication 1006, UE 1004 monitors all PDCCH monitoring opportunities 1020(1) to 1020(3) associated with first-level DCI 1012 (and occurring in time after the activation time 1005 of indication 1006), and stops monitoring any PDCCH monitoring opportunity 1020(4) not associated with first-level DCI 1012 (and occurring in time after the activation time 1005 of indication 1006).

[0143] For example, indication 1006 may include a PDCCH skip command for a period of time following the activation time 1005 of indication 1006; therefore, the PDCCH monitoring times 1020(1) to 1020(4) for which UE 1004 is instructed to stop monitoring may be PDCCH monitoring times scheduled during the period of time following the activation time 1005 of indication 1006. PDCCH monitoring times 1020(1) to 1020(3) may be monitoring times associated with the first-level DCI 1012, but monitoring time 1020(4) may not be associated with the first-level DCI 1012. In other words, PDCCH monitoring times 1020(1) to 1020(3) may be monitoring times for receiving multiple second-level DCIs associated with a single first-level DCI 1012. Based on receiving indication 1006 in single-level DCI 1010 and after the activation time 1005 of indication 1006, UE 1004 monitors PDCCH monitoring opportunities 1020(1) to 1020(3) that occur during this time period and are associated with first-level DCI 1012 (e.g., all PDCCH monitoring opportunities associated with first-level DCI 1012 that occur after the activation time 1005 of indication 1006), and stops monitoring that also occurs during this time period but is not associated with first-level DCI 1012 PDCCH monitoring opportunity 1020(4).

[0144] As another example, instruction 1006 may include an SSSG handover command indicating a switch from a first SSSG to a second SSSG; therefore, the PDCCH monitoring timings 1020(1) to 1020(4) for which UE 1004 is instructed to stop monitoring may be PDCCH monitoring timings associated with the first SSSG. Furthermore, PDCCH monitoring timings 1020(1) to 1020(3) may be monitoring timings associated with the first-level DCI 1012, but monitoring timing 1020(4) may not be associated with the first-level DCI 1012. Based on receiving indication 1006 in single-level DCI 1010 and after the activation time 1005 of indication 1006, UE 1004 monitors PDCCH monitoring opportunities 1020(1) to 1020(3) associated with the first SSSG and associated with the first-level DCI 1012 (e.g., all PDCCH monitoring opportunities associated with the first-level DCI 1012 that occur after the activation time 1005 of indication 1006), and stops monitoring PDCCH monitoring opportunities 1020(4) that are also associated with the first SSSG but not associated with the first-level DCI 1012.

[0145] By continuing to monitor all PDCCH monitoring moments 1020(1) to 1020(3) that are associated with the first-level DCI and occur in time after the activation time 1005 of indication 1006, UE 1004 may be able to receive all second-level DCIs associated with the previously received first-level DCI 1012.

[0146] and Figure 10A The difference lies in Figure 10B In this context, indication 1006 is sent to UE 1004 via first-level DCI 1012 (instead of single-level DCI 1010). In some cases, UE 1004 receives first-level DCI 1012 including indication 1006 after receiving single-level DCI 1010. Although indication 1006 is received in first-level DCI 1012 instead of single-level DCI 1010 (e.g., as...), Figure 10A (as shown), but the UE behavior in response to receiving instruction 1006 can be compared with... Figure 10A The same applies. Specifically, instruction 1006 included in the first-level DCI 1012 instructs UE 1004 to stop monitoring PDCCH monitoring opportunities 1030(1) to 1030(4) that UE 1004 was previously scheduled to monitor. Based on receiving instruction 1006 in the first-level DCI 1012, UE 1004 monitors all PDCCH monitoring opportunities 1030(1) to 1030(3) associated with the first-level DCI 1012 (and occurring after the activation time 1007 of instruction 1006 in time), and stops monitoring any PDCCH monitoring opportunity 1030(4) not associated with the first-level DCI 1012 (and occurring after the activation time 1007 of instruction 1006 in time).

[0147] Similarly, by continuing to monitor all PDCCH monitoring moments 1030(1) to 1030(3) associated with the first-level DCI 1012 and occurring after the activation time 1007 of indication 1006, UE 1004 may be able to receive all second-level DCIs associated with the previously received first-level DCI 1012.

[0148] and Figure 10A and Figure 10B The difference lies in Figure 10CIn this configuration, indication 1006 is sent to UE 1004 via second-level DCI 1014 (instead of single-level DCI 1010 or first-level DCI 1012). After receiving first-level DCI 1012, UE 1004 receives second-level DCI 1014 including indication 1006 (e.g., where the second-level DCI is associated with first-level DCI 1012). In some cases, UE 1004 receives second-level DCI 1014 including indication 1006 after receiving single-level DCI 1010. Although indication 1006 is in second-level DCI 1014 instead of single-level DCI 1010 (e.g., as...), Figure 10A (as shown) or Level 1 DCI 1012 (e.g., as shown) Figure 10B Received as shown, but the UE behavior in response to receiving instruction 1006 can be compared with Figure 10A and Figure 10B Same, or similar Figure 9A and Figure 9B Specifically, instruction 1006 included in the first-level DCI 1012 instructs UE 1004 to stop monitoring PDCCH monitoring opportunities 1040(1) to 1040(3) that UE 1004 was previously scheduled to monitor. Based on receiving instruction 1006 in the second-level DCI 1012 (e.g., in this example, the second-level DCI that is time-first associated with the first-level DCI 1014), UE 1004 monitors one or more (e.g., all) PDCCH monitoring opportunities 1040(1) to 1040(2) that are associated with the first-level DCI 1012 and that occur time-wise after receiving instruction 1006, and stops monitoring any PDCCH monitoring opportunity 1040(3) that is not associated with the first-level DCI 1012 and that occurs time-wise after the activation time 1009 of instruction 1006. In this example, one or more of the PDCCH monitoring times 1040(1) to 1040(2) may be used to receive an additional second-level DCI associated with the first-level DCI (e.g., excluding the second-level DCI that is time-first associated with the first-level DCI 1012, e.g., the second-level DCI 1014).

[0149] Similarly, by continuing to monitor one or more (e.g., all) PDCCH monitoring moments 1040(1) to 1040(2) associated with the first-level DCI 1012 and occurring in time after the activation time 1009 of indication 1006, UE 1004 may be able to receive the second-level DCI associated with the previously received first-level DCI 1012.

[0150] In some respects, other UE behaviors can be considered when the PDCCH monitoring adaptive indication is carried by either the first or second level DCI in a two-level DCI system, and the first level DCI is associated with multiple second level DCIs. For example, such as... Figure 11A and Figure 11B As shown, after the activation time of the PDCCH monitoring adaptive indication received by the UE, the UE may (1) stop monitoring one or more PDCCH monitoring opportunities associated with the first-level DCI, which are time-scheduled after the time of receiving and activating the adaptive indication, but (2) resume PDCCH monitoring to monitor PDCCH monitoring opportunities associated with at least another first-level DCI in another two-level DCI.

[0151] Specifically, such as Figure 11A As shown, network entity 1102 (e.g., such as Figure 1 and Figure 3 BS 102 in the middle) to UE1104 (e.g., such as Figure 1 and Figure 3 The first level DCI 1112 of the two-level DCI sent by UE 1004 is used to carry indication 1106. Although not shown, in some cases, UE 1104 receives the first level DCI 1112 after receiving the single level DCI. Indication 1106 included in the first level DCI 1112 instructs UE 1104 to stop monitoring PDCCH monitoring times 1120(1) to 1120(4) that UE 1004 was previously scheduled to monitor after the activation time 1105 of indication 1106. For example, indication 1106 may be a PDCCH skip command instructing UE 1104 to stop monitoring PDCCH monitoring times 1120(1) to 1120(4) because these monitoring times occur during the time period after the activation time 1105 of indication 1106. In this example, PDCCH monitoring timings 1120(1) to 1120(3) are associated with the second level DCI in the two-level DCI (e.g., associated with the first level DCI 1112), and PDCCH monitoring timing 1120(4) is associated with another first level DCI in another two-level DCI.

[0152] Based on receiving indication 1106 in the first-level DCI 1112 and after the activation time 1105 of indication 1106, UE 1104 skips monitoring PDCCH monitoring opportunities 1120(1) to 1120(3) (e.g., PDCCH monitoring opportunities associated with the second-level DCI in the two-level DCI and scheduled after the activation time 1105 of indication 1106), but monitors PDCCH monitoring opportunity 1120(4) because this PDCCH monitoring opportunity 1120(4) is associated with another first-level DCI in another two-level DCI (e.g., the next first-level DCI in time in another two-level DCI). In other words, the periodic duration pattern of the two-level DCI monitoring can be used to implicitly indicate the duration of PDCCH monitoring opportunity skipping for UE 1104.

[0153] and Figure 11A The difference lies in Figure 11B In this configuration, indication 1106 is sent to UE 1104 via PDCCH in the second-level DCI 1114 (instead of the first-level DCI 1112). After receiving the first-level DCI 1112, UE 1004 receives the second-level DCI 1114 including indication 1106 (e.g., where the second-level DCI 1114 is associated with the first-level DCI 1112, and the two DCIs belong to the same two-level DCI). In some cases, UE 1104 receives the second-level DCI 1114 including indication 1106 after receiving the single-level DCI. Figure 11B (Not shown in the image). Although indication 1106 is received in the second-level DCI 1114 rather than the first-level DCI 1112 (e.g., as shown in the image). Figure 11A (as shown), but the UE behavior in response to receiving instruction 1106 can be compared with... Figure 11A The same applies. Specifically, after the activation time 1107 of indication 1106, UE 1104 may skip monitoring the PDCCH monitoring timing associated with the second level DCI in the two-level DCI (e.g., where the first level DCI 1112 in the two-level DCI is associated with multiple second level DCIs), but monitor the PDCCH monitoring timing for the next first level DCI in another two-level DCI. For example, based on receiving indication 1106 in the second level DCI 1114 and after the activation time 1107 of indication 1106, UE 1104 skips monitoring PDCCH monitoring timings 1130(1) to 1130(3) (e.g., PDCCH monitoring timings associated with the second level DCI in the two-level DCI and scheduled after the activation time of indication 1106), but monitors PDCCH monitoring timing 1120(4) because this PDCCH monitoring timing 1120(4) is associated with another first level DCI in another two-level DCI.

[0154] exist Figure 11A and Figure 11B The adaptive behavior of UE 1104 illustrated in the diagram may be useful if UE 1104 is not configured using Connected Mode Discontinuous Reception (C-DRX). C-DRX is a technique used to improve UE battery consumption by allowing the UE to periodically enter a "sleep" state (e.g., during the DRX off duration), during which PDCCH monitoring is not required. To monitor the PDCCH, when configured using C-DRX, the UE is allowed to periodically transition to a "wake-up" state and remain "wake-up" for a certain period of time (e.g., the DRX on duration) before returning to the "sleep" state.

[0155] In some cases, the UE may (1) stop monitoring all PDCCH monitoring opportunities scheduled after the time of receiving and activating the adaptive indication (e.g., including PDCCH monitoring opportunities associated with two-level DCI and single-level DCI), and (2) resume PDCCH monitoring to monitor PDCCH monitoring opportunities associated with at least another first-level DCI in another two-level DCI. This is similar to Figure 11A and Figure 11B The example illustrated herein; however, all PDCCHs scheduled for user data (and time-scheduled after the time of receiving and activating the adaptive indication) can be skipped, rather than only the PDCCH monitoring timing associated with the second-level DCI in a two-level DCI. In such cases, the UE stops monitoring any PDCCHs affected by the adaptive indication (e.g., a PDCCH skip command) scheduled during the time period after the activation of the adaptive indication but before the PDCCH monitoring timing for the next first-level DCI in another two-level DCI. This can be particularly useful when monitoring of the first-level DCI is aligned with the start of a data cycle for periodic services, when C-DRX is not enabled.

[0156] In some cases, the first and second level DCIs in a two-level DCI can be associated with different SSSs. For example, the first level DCI can be scheduled during the PDCCH monitoring period of the first SSS, while the second level DCI can be scheduled during the PDCCH monitoring period of the second SSS. Certain aspects of this document ensure that when a UE is configured to monitor the SSS of either the first or second level DCI in a two-level DCI, it is also configured to monitor the SSS of the other of the first or second level DCI in a two-level DCI, such that the UE receives both the first and second level DCIs. For example, if the UE is configured to monitor the first SSS, the UE is also configured to monitor the second SSS, and vice versa (if the UE is configured to monitor the second SSS, the UE is also configured to monitor the first SSS).

[0157] In some aspects, the SSS for both Level 1 DCI and Level 2 DCI is configured within the same SSSG, such that the PDCCH monitoring adaptive indication explicitly switches the SSS for both Level 1 DCI and Level 2 DCI simultaneously. For example, both the first SSS and the second SSS will be part of the same SSSG.

[0158] In some aspects, the SSS associated with the first-level DCI and the SSS associated with the second-level DCI may not be part of the same SSSG. For example, an SSSG may include the first SSS but not the second SSS. As another example, an SSSG may include the second SSS but not the first SSS. In some such aspects, if the UE is configured (e.g., switched to that specific SSSG) using a particular SSSG and that SSSG includes the SSS of one of the first-level DCI and the second-level DCI but not the other, the UE may implicitly monitor the other of the first-level DCI and the second-level DCI. For example, the UE may still monitor the second SSS even if the SSSG includes the first SSS but not the second SSS. Furthermore, the UE may still monitor the first SSS even if the SSSG includes the second SSS but not the first SSS.

[0159] Therefore, in some respects, when a UE switches away from such an SSSG, the UE can stop monitoring both the SSS of the two DCI levels included in the SSSG and the SSS of the two DCI levels not included in the SSSG. For example, if the SSSG includes a first SSS but not a second SSS, the UE can stop monitoring both the first and second SSS. Furthermore, if the SSSG includes a second SSS but not a first SSS, the UE can stop monitoring both the first and second SSS.

[0160] Figure 12This describes an example of the UE's adaptive PDCCH monitoring behavior after the activation time of the PDCCH monitoring adaptive indication received by the UE for SSSG handover. As shown in the figure, network entity 1202 (e.g., such as...) Figure 1 and Figure 3 BS102 in the middle) to UE 1204 (e.g., such as Figure 1 and Figure 3 UE 104 in the middle sends scheduled data transmission (e.g., uplink data transmission or downlink data transmission). Figure 12 DCI 1208 (not shown in the image). DCI 1208 can be a single-level DCI, a first-level DCI, or a second-level DCI. In some cases, DCI 1208 is a single-level DCI received by UE 1204 after receiving the first-level DCI but before receiving the second-level DCI associated with the previously received first-level DCI.

[0161] DCI 1208 includes indication 1206, which includes an SSSG handover indication that instructs UE 1204 (e.g., after the activation time 1205 of indication 1206) to switch from the first SSSG (SSSG1) to the second SSSG (SSSG2), or in other words, to stop monitoring the PDCCH monitoring timing associated with SSSG1.

[0162] In this example, prior to receiving indication 1206, UE 1204 is configured to monitor the first level DCI in a first SSS (SSS1) and the second level DCI in a third SSS (SSS3). SSSS1 includes SSS1 (e.g., corresponding to the first level DCI) but does not include SSS3.

[0163] According to the aspects described herein, indication 1206, which indicates a switch from SSSG1 to SSSG2 (e.g., excluding SSS1 or SSS3 but including SSS2), enables UE 1204 to not only cease monitoring PDCCH monitoring opportunities associated with SSS1 belonging to SSSG1 (e.g., 1220(2) to 1220(4)), but also cease monitoring PDCCH monitoring opportunities associated with SSS3. In some cases, UE 1204 may immediately cease monitoring such PDCCH monitoring opportunities associated with both SSS1 and SSS3. In some cases, as discussed, UE 1204 may monitor at least one PDCCH monitoring opportunity 1220(1) associated with SSS3 after the activation time 1205 of indication 1206. In some cases, this involves UE 1204 monitoring all PDCCH monitoring opportunities associated with SSS3 and associated with previously received Level 1 DCI (although in Figure 12(not explicitly shown in the document) to receive all second-level DCIs associated with the previously received first-level DCI (e.g., also associated with SSS3).

[0164] Example operation of user equipment

[0165] Figure 13 It shows a device (such as) Figure 1 and Figure 3 Method 1300 for wireless communication of UE 104.

[0166] Method 1300 begins at step 1305, wherein an indication is received in the downlink channel indicating that monitoring of multiple PDCCH monitoring opportunities previously scheduled for monitoring by the device should cease after an activation time for the indication. For example, as per [reference to...] Figure 8 , Figures 9A to 9B , Figures 10A to 10C , Figures 11A to 11B and Figure 12 The discussed UEs (e.g., UEs 804, 904, 1004, 1104, and 1204) receive indications (e.g., indications 806, 906, 1006, 1106, and 1206, respectively) in the PDCCH. This indication can be a PDCCH skip command instructing the UE to skip PDCCH monitoring for a specific duration after the activation time of the indication (e.g., activation times 805, 905, 907, 1005, 1007, 1009, 1105, 1107, and 1205, respectively), or an SSSG command instructing the UE to switch from monitoring the first SSSG to monitoring the second SSSG after the activation time. In other words, the indication can be a command that instructs the UE to stop monitoring PDCCH monitoring opportunities after the activation time specified in the indication (e.g., PDCCH monitoring opportunities 820(1) to 820(4), 920(1) to 920(3), 930(1) to 930(3), 1020(1) to 1020(4), 1030(1) to 1030(4), 1040(1) to 1040(3), 1120(1) to 1120(4), 1130(1) to 1130(4), 1220(1) to 1220(4) respectively), which are scheduled during the indicated time period or are not associated with a second SSSG. At least one of the downlink channel or multiple PDCCH monitoring opportunities may be associated with at least one of the first level DCI or the second level DCI in a two-level DCI. For example, as per the information regarding... Figure 9B , Figure 10B and Figure 11A The downlink channels discussed can be associated with Level 1 DCIs 912, 1012, and 1112, respectively. Additionally, as regarding... Figure 10Cand Figure 11B The downlink channels discussed can be associated with the second-level DCIs 1014 and 1114, respectively. Additionally, as regarding... Figure 8 , Figures 9A to 9B , Figures 10A to 10C , Figures 11A to 11B and Figure 12 The PDCCH monitoring times of 820(1) to 820(4), 920(1) to 920(3), 930(1) to 930(3), 1020(1) to 1020(4), 1030(1) to 1030(4), 1040(1) to 1040(3), 1120(1) to 1120(4), 1130(1) to 1130(4), and 1220(1) to 1220(4) can be associated with at least one of the first-level DCI or the second-level DCI in the two-level DCI.

[0167] Then, method 1300 proceeds to step 1310, wherein, based on an indication, at least one of a plurality of PDCCH monitoring opportunities is monitored after the activation time. For example, as per [reference to...] Figure 8 , Figures 9A to 9B , Figures 10A to 10C , Figures 11A to 11B and Figure 12 The discussed UEs 804, 904, 1004, 1104, and 1204 are respectively instructed to stop monitoring PDCCH at the following times: 820(1) to 820(4), 920(1) to 920(3), 930(1) to 930(3), 1020(1) to 1020(4), 1030(1) to 1030(4), and 1040(1) to 1040(3), based on instructions 806, 906, 1006, 1106, and 1206. ), 1120(1) to 1120(4), 1130(1) to 1130(4), 1220(1) to 1220(4), but continue to monitor PDCCH monitoring times at 820(1), 920(1), 930(1), 1020(1) to 1020(3), 1030(1) to 1030(3), 1040(1) to 1040(2), 1120(4), 1130(4), 1220(4).

[0168] Then, method 1300 proceeds to step 1315, where, based on an instruction, monitoring of one or more of the multiple PDCCH monitoring opportunities is stopped after the activation time. For example, as per the... Figure 8 , Figures 9A to 9B , Figures 10A to 10C , Figures 11A to 11B and Figure 12The discussed UEs 804, 904, 1004, 1104, and 1204 are respectively instructed to stop monitoring PDCCH at the following times: 820(1) to 820(4), 920(1) to 920(3), 930(1) to 930(3), 1020(1) to 1020(4), 1030(1) to 1030(4), 1040(1) to 1040(3), and 1120(1) to 1206. 120(4), 1130(1) to 1130(4), 1220(1) to 1220(4), and stop monitoring PDCCH monitoring at 820(2) to 820(4), 920(2) to 920(3), 930(2) to 930(3), 1020(4), 1030(4), 1040(3), 1120(1) to 1120(3), 1130(1) to 1130(3), 1220(2) to 1220(4).

[0169] In some respects, the indication includes a PDCCH skip command for a time period during which multiple PDCCH monitoring events are scheduled.

[0170] In some respects, the indication includes an SSSG switching command that indicates a switch from a first SSSG to a second SSSG, the multiple PDCCH monitoring timings being associated with the first SSSG.

[0171] In some respects, the first SSSG includes the first SSS, the second SSSG does not include the first SSS, and the multiple PDCCH monitoring timings are associated with the first SSS.

[0172] In some respects, the first SSSG includes a first SSS corresponding to one of the first-level DCI or the second-level DCI and does not include a second SSS corresponding to the other of the first-level DCI or the second-level DCI, and wherein the SSSG switching command instructs to stop monitoring the PDCCH monitoring timing associated with the first SSS and the PDCCH monitoring timing associated with the second SSS.

[0173] In some respects, method 1300 also includes receiving a first-level DCI.

[0174] In some respects, monitoring at least one of the plurality of PDCCH monitoring opportunities includes monitoring at least one PDCCH monitoring opportunity scheduled after receiving the instruction for the second-level DCI associated with the first-level DCI.

[0175] In some respects, the at least one PDCCH monitoring timing associated with the first-level DCI includes all PDCCH monitoring timings scheduled after the instruction is received for the second-level DCI associated with the first-level DCI.

[0176] In some aspects, receiving the indication includes receiving the indication in the first-level DCI or the second-level DCI; monitoring at least one of the plurality of PDCCH monitoring opportunities includes monitoring a PDCCH monitoring opportunity associated with another first-level DCI in another two-level DCI; and stopping monitoring the one or more PDCCH monitoring opportunities includes stopping monitoring the one or more PDCCH monitoring opportunities associated with the first-level DCI that are scheduled after the activation time for the indication and before the second time when the other first-level DCI is scheduled.

[0177] In some aspects, method 1300 also includes receiving an indication in a first-level DCI or a second-level DCI, wherein monitoring at least one of a plurality of PDCCH monitoring opportunities includes monitoring a PDCCH monitoring opportunity associated with a single-level DCI.

[0178] In some respects, receiving the instruction includes receiving the instruction in at least one of the following: the first-level DCI, the second-level DCI.

[0179] In some respects, method 1300 or any aspect thereof may be made possible by means of a device (such as...) Figure 14 The communication device 1400 is used to perform the method 1300, which includes various components capable of operating, being configured, or adapted to perform the method. The communication device 1400 is described in further detail below.

[0180] It should be noted that Figure 13 This is merely one example of a method, and other methods that include fewer, additional, or alternative steps may also be consistent with this disclosure.

[0181] Example communication device

[0182] Figure 14 Various aspects of the example communication device 1400 are described. In some aspects, the communication device 1400 is user equipment, such as those described above. Figure 1 and Figure 3 The UE 104 described.

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

[0184] Processing system 1405 includes one or more processors 1410. In various aspects, the one or more processors 1410 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...]. Figure 3 As described. One or more processors 1410 are coupled to a computer-readable medium / memory 1430 via a bus 1450. In some aspects, the computer-readable medium / memory 1430 is configured to store instructions (e.g., computer-executable code) that, when executed by one or more processors 1410, enable one or more processors 1410 to execute and cause the one or more processors to perform actions related to... Figure 13 The described method 1300 or any aspect related to the method, including regarding Figure 13 Any additional steps or sub-steps described. Note that references to processors performing the functions of communication device 1400 may include one or more processors, such as performing the functions of communication device 1400 in a distributed manner.

[0185] In the depicted example, computer-readable medium / memory 1430 stores code 1435 for receiving, code 1440 for monitoring, and code 1445 for stopping. Processing of codes 1435 to 1445 enables communication device 1400 to execute and cause the communication device to perform actions related to... Figure 13 The described method 1300 or any aspect related to that method.

[0186] One or more processors 1410 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1430, the circuitry including circuitry 1415 for receiving, circuitry 1420 for monitoring, and circuitry 1425 for stopping. Processing using circuitry 1415 to 1425 enables communication device 1400 to perform and allow the communication device to perform actions related to... Figure 13 The described method 1300 or any aspect related to that method.

[0187] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include Figure 3The UE104 illustrated includes a transceiver 354, an antenna 352, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380. Figure 14 The transceiver 1455 and / or antenna 1460 of the communication device 1400 and / or Figure 14 One or more processors 1410 of the communication device 1400. Components for transmitting, receiving, or acquiring may include... Figure 3 The UE 104 illustrated includes a transceiver 354, an antenna 352, a receiver processor 358, and / or a controller / processor 380. Figure 14 The transceiver 1455 and / or antenna 1460 of the communication device 1400 and / or Figure 14 One or more processors 1410 of the communication device 1400 in the middle.

[0188] Example Terms

[0189] Specific implementation examples are described in the following numbered clauses: Clause 1: A method for wireless communication by a device, the method comprising: receiving an indication in a downlink channel, the indication indicating to stop monitoring a plurality of PDCCH monitoring opportunities previously scheduled for monitoring by the device after an activation time for the indication, wherein the downlink channel or at least one of the plurality of PDCCH monitoring opportunities is associated with at least one of a first-level DCI or a second-level DCI of two-level DCIs; monitoring at least one of the plurality of PDCCH monitoring opportunities after the activation time based on the indication; and stopping monitoring one or more of the plurality of PDCCH monitoring opportunities after the activation time based on the indication.

[0190] Clause 2: The method according to Clause 1, wherein: the indication includes a PDCCH skip command for a time period; and the plurality of PDCCH monitoring events are scheduled during the time period.

[0191] Clause 3: The method according to Clause 1, wherein: the indication includes an SSSG switching command indicating a switch from a first SSSG to a second SSSG; and the plurality of PDCCH monitoring timings are associated with the first SSSG.

[0192] Clause 4: The method according to Clause 3, wherein: the first SSSG includes the first SSS; the second SSSG does not include the first SSS; and the multiple PDCCH monitoring timings are associated with the first SSS.

[0193] Clause 5: The method according to Clause 3, wherein the first SSSG includes a first SSS corresponding to one of the first level DCI or the second level DCI and does not include a second SSS corresponding to the other of the first level DCI or the second level DCI, and wherein the SSSG switching command indicates to stop monitoring the PDCCH monitoring timing associated with the first SSS and the PDCCH monitoring timing associated with the second SSS.

[0194] Clause 6: The method described in any one of Clauses 1 to 5 further includes receiving the first-level DCI.

[0195] Clause 7: The method according to Clause 6, wherein monitoring at least one of the plurality of PDCCH monitoring opportunities includes monitoring at least one PDCCH monitoring opportunity scheduled after receiving the indication for a second-level DCI associated with the first-level DCI.

[0196] Clause 8: The method according to Clause 7, wherein the at least one PDCCH monitoring timing associated with the first-level DCI includes all PDCCH monitoring timings for the second-level DCI associated with the first-level DCI, scheduled after the instruction is received.

[0197] Clause 9: The method according to any one of Clauses 1 to 6, wherein receiving the indication includes receiving the indication in the first level DCI or the second level DCI; monitoring at least one PDCCH monitoring opportunity of the plurality of PDCCH monitoring opportunities includes monitoring a PDCCH monitoring opportunity associated with another first level DCI in another two levels DCI; and stopping monitoring the one or more PDCCH monitoring opportunities includes stopping monitoring the one or more PDCCH monitoring opportunities associated with the first level DCI that are scheduled after the activation time for the indication and before the second time when the other first level DCI is scheduled.

[0198] Clause 10: The method according to any one of Clauses 1 to 9 further includes: receiving the indication in the first level DCI or the second level DCI, wherein monitoring at least one of the plurality of PDCCH monitoring opportunities includes monitoring a PDCCH monitoring opportunity associated with a single level DCI.

[0199] Clause 11: The method according to any one of Clauses 1 to 10, wherein receiving the instruction includes receiving the instruction in at least one of: the first level DCI; or the second level DCI.

[0200] Clause 12: One or more means comprising: one or more memories (e.g., including executable instructions); and one or more processors (e.g., coupled to the one or more memories), the one or more processors being configured to (e.g., execute the executable instructions and) cause the one or more means to perform the method according to any one of Clauses 1 to 11.

[0201] Clause 13: One or more apparatuses, said one or more apparatuses comprising components for performing the method according to any one of Clauses 1 to 11.

[0202] Clause 14: One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media comprising executable instructions that, when executed by one or more processors of one or more devices, cause the one or more devices to perform the method according to any one of Clauses 1 to 11.

[0203] Clause 15: One or more computer program products embodied on one or more computer-readable storage media, the one or more computer-readable storage media including code for performing the method according to any one of Clauses 1 to 11.

[0204] Additional Notes

[0205] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described in some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Moreover, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0206] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, AI processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic element, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0207] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. For example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0208] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Furthermore, "determine" can include parsing, selecting, picking, building, etc.

[0209] As used herein, unless otherwise stated, “coupled to” and “coupled with” generally encompass both direct and indirect coupling (e.g., including intermediate aspects of coupling). For example, stating that a processor is coupled to memory allows for direct coupling or coupling via an intermediate aspect such as a bus.

[0210] The methods disclosed herein include one or more actions for implementing the methods. These actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above may be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0211] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. References to singular elements are not intended to mean “only one” (unless specifically stated as “only one”), but rather “one or more”. Unless otherwise expressly stated, definite articles (e.g., “the” or “described”) subsequently used with elements (e.g., “processor”) are not intended to introduce a singular meaning (e.g., “only one”) for that element. For example, unless specifically stated otherwise, references to elements (e.g., “processor”, “controller”, “memory”, “transceiver”, “antenna”, “the processor”, “the controller”, “the memory”, “the transceiver”, “the antenna”, etc.) should be understood to refer to one or more elements (e.g., “one or more processors”, “one or more controllers”, “one or more memories”, “one or more transceivers”, etc.). The terms “set” and “group” are intended to include one or more elements and are used interchangeably with “one or more”. In the case of references to one or more elements performing a function (e.g., steps of a method), one element may perform all the functions, or more than one element may collectively perform those functions. When more than one element performs these functions together, each function does not need to be performed by every single element (e.g., different functions can be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements can perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform a function, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions. Unless otherwise specifically stated, the term "some" refers to one or more. All structural and functional equivalents of the various aspects described throughout this disclosure that are currently or hereafter known to those skilled in the art are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors being coupled to said one or more memories and configured to cause the device to: An indication is received in a downlink channel, the indication indicating that monitoring of a plurality of physical downlink control channels (PDCCHs) previously scheduled for monitoring by the device shall cease after an activation time for the indication, wherein the downlink channel or at least one of the plurality of PDCCH monitoring opportunities is associated with at least one of a first-level DCI or a second-level DCI in a two-level downlink control information (DCI). Based on the indication, at least one of the plurality of PDCCH monitoring opportunities is monitored after the activation time; as well as Based on the instruction, monitoring of one or more of the plurality of PDCCH monitoring times will cease after the activation time.

2. The apparatus according to claim 1, wherein: The instruction includes a PDCCH skip command for a time period; and The multiple PDCCH monitoring opportunities are scheduled during the time period.

3. The apparatus according to claim 1, wherein: The instruction includes an SSSG switching command indicating a switch from a first search space set group (SSSG) to a second SSSG; and The timing of the multiple PDCCH monitoring is associated with the first SSSG.

4. The apparatus according to claim 3, wherein: The first SSSG includes the first search space set (SSS); The second SSSG does not include the first SSS; and The timing of the multiple PDCCH monitoring events is associated with the first SSS.

5. The apparatus of claim 3, wherein the first SSSG includes a first search space set (SSS) corresponding to one of the first level DCI or the second level DCI and does not include a second SSS corresponding to the other of the first level DCI or the second level DCI, and wherein the SSSG switching command instructs to stop monitoring of PDCCH monitoring timings associated with the first SSS and PDCCH monitoring timings associated with the second SSS.

6. The apparatus of claim 1, wherein the one or more processors are configured to cause the apparatus to receive the first-level DCI.

7. The apparatus of claim 6, wherein, in order to monitor at least one of the plurality of PDCCH monitoring opportunities, the one or more processors are configured to cause the apparatus to monitor at least one PDCCH monitoring opportunity scheduled after receiving the instruction for a second-level DCI associated with the first-level DCI.

8. The apparatus of claim 7, wherein the at least one PDCCH monitoring timing associated with the first-level DCI includes all PDCCH monitoring timings for the second-level DCI associated with the first-level DCI, scheduled after receiving the instruction.

9. The apparatus according to claim 1, wherein In order to receive the instruction, the one or more processors are configured to cause the device to receive the instruction in the first level DCI or the second level DCI; In order to monitor at least one of the plurality of PDCCH monitoring opportunities, the one or more processors are configured to cause the device to monitor a PDCCH monitoring opportunity associated with another first-level DCI in another two-level DCI; and In order to stop monitoring the one or more PDCCH monitoring opportunities, the one or more processors are configured to cause the device to stop monitoring the one or more PDCCH monitoring opportunities associated with the first-level DCI that are scheduled after the activation time indicated and before the second time when the other first-level DCI is scheduled.

10. The apparatus according to claim 1, wherein: The one or more processors are configured to cause the device to receive the instruction in the first level DCI or the second level DCI; and In order to monitor at least one of the plurality of PDCCH monitoring opportunities, the one or more processors are configured to enable the device to monitor PDCCH monitoring opportunities associated with a single-level DCI.

11. The apparatus of claim 1, wherein, in order to receive the instruction, the one or more processors are configured to cause the apparatus to receive the instruction in at least one of the following: Level 1 DCI; or The second level of DCI.

12. A method for wireless communication by a device, the method comprising: An indication is received in a downlink channel, the indication indicating that monitoring of a plurality of physical downlink control channels (PDCCHs) previously scheduled for monitoring by the device shall cease after an activation time for the indication, wherein the downlink channel or at least one of the plurality of PDCCH monitoring opportunities is associated with at least one of a first-level DCI or a second-level DCI in a two-level downlink control information (DCI). Based on the indication, at least one of the plurality of PDCCH monitoring opportunities is monitored after the activation time; as well as Based on the instruction, monitoring of one or more of the plurality of PDCCH monitoring times will cease after the activation time.

13. The method according to claim 12, wherein: The instruction includes a PDCCH skip command for a time period; and The multiple PDCCH monitoring opportunities are scheduled during the time period.

14. The method according to claim 12, wherein: The instruction includes an SSSG switching command indicating a switch from a first search space set group (SSSG) to a second SSSG; and The timing of the multiple PDCCH monitoring is associated with the first SSSG.

15. The method of claim 14, wherein: The first SSSG includes the first search space set (SSS); The second SSSG does not include the first SSS; and The timing of the multiple PDCCH monitoring events is associated with the first SSS.

16. The method of claim 14, wherein the first SSSG includes a first search space set (SSS) corresponding to one of the first level DCI or the second level DCI and does not include a second SSS corresponding to the other of the first level DCI or the second level DCI, and wherein the SSSG switching command instructs to stop monitoring of PDCCH monitoring timings associated with the first SSS and PDCCH monitoring timings associated with the second SSS.

17. The method according to claim 12, further comprising: Receive the first-level DCI.

18. The method of claim 17, wherein monitoring at least one of the plurality of PDCCH monitoring opportunities comprises monitoring at least one PDCCH monitoring opportunity scheduled after receiving the indication for a second-level DCI associated with the first-level DCI.

19. The method of claim 18, wherein the at least one PDCCH monitoring timing associated with the first-level DCI includes all PDCCH monitoring timings for the second-level DCI associated with the first-level DCI, scheduled after receiving the indication.

20. The method of claim 12, wherein: Receiving the instruction includes receiving the instruction in either the first-level DCI or the second-level DCI; Monitoring at least one of the plurality of PDCCH monitoring opportunities includes monitoring a PDCCH monitoring opportunity associated with another first-level DCI in another two-level DCI; and Stopping monitoring of the one or more PDCCH monitoring opportunities includes stopping monitoring of the one or more PDCCH monitoring opportunities associated with the first-level DCI that are scheduled after the activation time indicated and before the second time when the other first-level DCI is scheduled.

21. The method according to claim 12, further comprising: The indication is received in either the first-level DCI or the second-level DCI, wherein monitoring at least one of the plurality of PDCCH monitoring opportunities includes monitoring a PDCCH monitoring opportunity associated with a single-level DCI.

22. The method of claim 12, wherein receiving the instruction comprises receiving the instruction in at least one of the following: Level 1 DCI; or The second level of DCI.

23. An apparatus configured for wireless communication, the apparatus comprising: Components for receiving an indication in a downlink channel, the indication indicating the cessation of monitoring of a plurality of physical downlink control channel (PDCCH) monitoring opportunities previously scheduled for monitoring by the device after an activation time for the indication, wherein the downlink channel or at least one of the plurality of PDCCH monitoring opportunities is associated with at least one of a first-level DCI or a second-level DCI in a two-level downlink control information (DCI). Components for monitoring at least one of the plurality of PDCCH monitoring times based on the indication after the activation time; and A component for stopping monitoring one or more of the plurality of PDCCH monitoring times after the activation time based on the indication.

24. The apparatus according to claim 23, wherein: The instruction includes a PDCCH skip command for a time period; and The multiple PDCCH monitoring opportunities are scheduled during the time period.

25. The apparatus according to claim 23, wherein: The instruction includes an SSSG switching command indicating a switch from a first search space set group (SSSG) to a second SSSG; and The timing of the multiple PDCCH monitoring is associated with the first SSSG.

26. The apparatus according to claim 25, wherein: The first SSSG includes the first search space set (SSS); The second SSSG does not include the first SSS; and The timing of the multiple PDCCH monitoring events is associated with the first SSS.

27. The apparatus of claim 25, wherein the first SSSG includes a first search space set (SSS) corresponding to one of the first level DCI or the second level DCI and does not include a second SSS corresponding to the other of the first level DCI or the second level DCI, and wherein the SSSG switching command instructs to stop monitoring of PDCCH monitoring timings associated with the first SSS and PDCCH monitoring timings associated with the second SSS.

28. The apparatus of claim 23, further comprising a component for receiving the first-level DCI.

29. The apparatus of claim 28, wherein the component for monitoring at least one of the plurality of PDCCH monitoring opportunities includes a component for monitoring at least one PDCCH monitoring opportunity scheduled after receiving the instruction for a second-level DCI associated with the first-level DCI.

30. One or more non-transitory computer-readable media, the non-transitory computer-readable media comprising executable instructions that, when executed by one or more processors of one or more devices, cause the one or more devices to perform operations, the operations including: An indication is received in a downlink channel, the indication indicating that monitoring of a plurality of physical downlink control channel (PDCCH) monitoring opportunities previously scheduled for monitoring by the one or more devices shall cease after the activation time of the indication, wherein the downlink channel or at least one of the plurality of PDCCH monitoring opportunities is associated with at least one of a first-level DCI or a second-level DCI in a two-level downlink control information (DCI). Based on the indication, at least one of the plurality of PDCCH monitoring opportunities is monitored after the activation time; as well as Based on the instruction, monitoring of one or more of the plurality of PDCCH monitoring times will cease after the activation time.

Images