Dynamic indication of physical downlink control channel monitoring locations

Abstract

In summary, various aspects of the present disclosure relate to wireless communications. In some aspects, a UE may monitor a set of operating conditions associated with the UE. Based on the monitoring, the UE may send a request for an indication of a PDCCH monitoring location associated with receiving a next DCI communication. A base station may receive the request and determine whether to grant the request. Based on the determination, the base station may selectively send an indication to the UE. If an indication in response to the request is received, the UE may monitor in the PDCCH monitoring location.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] Pursuant to 35 U.S.C. §119, this patent application claims priority to Greek Patent Application No. 20190100432, entitled “DYNAMIC INDICATION OF PHYSICAL DOWNLINK CONTROL CHANNEL MONITORING LOCATION,” filed with the Hellenic Patent and Trademark Office on October 3, 2019, and U.S. Non-Provisional Patent Application No. 16 / 923,993, entitled “DYNAMIC INDICATION OF PHYSICAL DOWNLINK CONTROL CHANNEL MONITORING LOCATION,” filed on July 8, 2020, both of which are assigned to the assignee of this application, and the entire contents of which are hereby expressly incorporated herein by reference. Technical Field

[0003]

[0006] Generally speaking, various aspects of the disclosure relate to wireless communications and to techniques and apparatus for dynamic indication of physical downlink control channel (PDCCH) monitoring location. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard released by the Third Generation Partnership Project (3GPP).

[0005] A wireless communication network may include multiple base stations (BSs) that can support communications for multiple user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to a communication link from a BS to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user devices to communicate at the city, country, region and even global level. New Radio (NR) (which may also be referred to as 5G) is a set of enhancements to the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also referred to as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0007] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an extensive overview of all expected aspects, and is neither intended to identify the key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0008] In a wireless communication system such as an NR system, a downlink control information (DCI) communication may include control information, such as information associated with resource allocation (e.g., a set of resources to be used for a downlink shared channel, a set of resources to be used for an uplink shared channel, etc.), a transport format, and / or one or more other control information items. Such DCI communication is carried in a physical downlink control channel (PDCCH), which is transmitted in one or more control resource sets (CORESET).

[0009] The UE may be configured to monitor the PDCCH so that the UE may detect DCI communications intended for the UE. In a typical communication scenario, the UE performs a blind search for DCI communications in each time slot (e.g., by attempting to decode the PDCCH in one or more CORESETs). However, this so-called blind decoding results in significant power consumption at the UE. For example, in the typical communication scenario described above, without any scheduling grant, the UE monitoring the PDCCH may consume more than 40% of the total UE power.

[0010] Even in scenarios where the UE does not obviously need to monitor DCI communications frequently, such as when the UE is configured with semi-persistent scheduling (SPS) or configured grants, the power consumption problem still exists. For example, the UE may need to monitor DCI communications in association with activating SPS / configured grants. As another example, the UE may need to monitor DCI communications after a beam quality problem causes a UE configured with SPS / configured grants to fail to receive downlink communications (e.g., physical downlink shared channel (PDSCH) communications). Here, after failing to receive (e.g., failing to decode) downlink communications, the UE may send a negative acknowledgement (NACK) indicating a beam quality problem. After sending the NACK, the UE may monitor (within one or more CORESETs) DCI communications associated with initiating beam scanning for beam reselection / adaptation and retransmissions of downlink communications. This problem is particularly prevalent when operating in a high frequency range, such as frequency range 2 (FR2), where beam quality problems are more likely. Therefore, even in cases where the UE does not obviously need to monitor DCI communications frequently, monitoring DCI communications may result in UE power waste.

[0011] Some aspects of the present disclosure relate to various triggering mechanisms for sending an indication of PDDCH monitoring locations.For example, selectively triggering a request for an indication of PDDCH monitoring locations may facilitate reduced power consumption, less system interference, and less system overhead at a UE.

[0012] In one aspect of the present disclosure, a method, a computer-readable medium, and an organization are provided. The device may be a UE. The UE may monitor a set of operating conditions associated with the UE. The UE may also send a request for an indication of a physical downlink control channel (PDCCH) monitoring location associated with receiving a next downlink control information (DCI) communication based on the monitoring. If the indication is received in response to the request, the UE may monitor in the PDCCH monitoring location.

[0013] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a base station. The base station may receive from a user equipment (UE) a request for an indication of a physical downlink control channel (PDCCH) monitoring location associated with sending a next downlink control information (DCI) communication. The base station may also determine whether to grant the request.

[0014] In summary, aspects include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings, appendices, and descriptions and as illustrated thereby.

[0015] The foregoing has been fairly extensively summarized according to the features and technical advantages of the examples of the present disclosure so that the detailed description below can be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as the basis for modifying or designing other structures for the same purpose of performing the present disclosure. Such equivalent constructions do not depart from the scope of the attached claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the description below. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and is not intended to be a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] A more detailed description of the above brief summary may be obtained by reference to various aspects (some of which are shown in the accompanying drawings) so that the above-mentioned features of the present disclosure may be understood in detail. However, it is to be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope of the present disclosure, as the description may recognize other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0017] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0018] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a UE in a wireless communication network according to various aspects of the present disclosure.

[0019] Figure 3 is a diagram illustrating an example of downlink (DL)-centric time slots according to various aspects of the present disclosure.

[0020] Figure 4is a diagram illustrating an example of uplink (UL)-centric time slots in accordance with various aspects of the present disclosure.

[0021] Figures 5A-5C is a diagram illustrating an example of dynamic indication of PDCCH monitoring locations in accordance with various aspects of the present disclosure.

[0022] Figure 6 is a diagram illustrating an example process performed, for example, by a user device, according to various aspects of the present disclosure.

[0023] Figure 7 is a diagram illustrating example processes performed, for example, by a base station in accordance with various aspects of the present disclosure.

[0024] Figure 8 is a diagram illustrating example processes performed, for example, by a UE, according to various aspects of the present disclosure.

[0025] Fig. 9 is a diagram illustrating example processes performed, for example, by a base station in accordance with various aspects of the present disclosure.

[0026] Fig.10 An embodiment according to the present disclosure is shown. Figure 8-9 An example implementation of the process.

[0027] Fig.11 is a conceptual data flow diagram illustrating the data flow between different units / components in an exemplary apparatus according to one embodiment of the present disclosure.

[0028] Fig.12 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0029] Fig.13 is a diagram illustrating another example of a hardware implementation for an apparatus employing a processing system. DETAILED DESCRIPTION

[0030] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be comprehensive and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings of this article, it should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, using any number of aspects set forth herein, a device can be implemented or a method can be practiced. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0031] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the detailed description below by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements") and illustrated in the accompanying drawings. These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] It should be noted that although terms commonly associated with 3G and / or 4G wireless technologies may be used herein to describe various aspects, various aspects of the present disclosure may be applicable to communication systems based on other generations, such as 5G and beyond (including NR technologies).

[0033] Figure 11 is a schematic diagram showing a wireless network 100 in which various aspects of the present disclosure may be implemented. The wireless network 100 may be an LTE network or some other wireless network (such as a 5G or NR network). The wireless network 100 may include a plurality of BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0034] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0035] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces, such as direct physical connections, virtual networks, and / or similar interfaces using any suitable transport networks.

[0036] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that is capable of relaying transmissions for other UEs. Figure 1 In the example shown in FIG. 1 , a relay station 110 d may communicate with a macro BS 110 a and a UE 120 d to facilitate communication between the BS 110 a and the UE 120 d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0037] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0038] The network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other via a wireless or wired backhaul (eg, directly or indirectly).

[0039] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or apparatus, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), an entertainment device (e.g., a music or video device, or a satellite radio unit, etc.), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0040] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide a connection to or to a network (e.g., a wide area network such as the Internet or a cellular network) via, for example, a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as user premises equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120 (such as a processor component, a memory component, etc.).

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

[0042] In some aspects, two or more UEs 120 (e.g., illustrated as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In such cases, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0043] As noted above, Figure 1 is provided as an example. Other examples may differ from those described above. Figure 1 Examples described.

[0044] Figure 2 Base station 110 and UE 120 (which may be Figure 11. Block diagram of a design 200 of a base station 110 and a UE 120. Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general, T≥1 and R≥1.

[0045] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, a synchronization signal may be generated using position coding to convey additional information.

[0046] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0047] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide decoded data to a data sink 239 and decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0048] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components in the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Figure 6 The process of 600 Figure 7 The operations of process 700 and / or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120, may perform or direct, for example, Figure 6 The process of 600 Figure 7 The scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0049] In some aspects, UE 120 may include: means for receiving an indication identifying a PDCCH monitoring location associated with receiving a next DCI communication; means for monitoring in the PDCCH monitoring location based at least in part on the indication, wherein the indication is valid at least until the PDCCH monitoring location without regard to an amount of time between receiving the indication and monitoring in the PDCCH monitoring location; etc. In some aspects, such means may include combining Figure 2 One or more components of UE 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, and the like.

[0050] In some aspects, base station 110 may include: means for sending an indication identifying a PDCCH monitoring location associated with sending a next DCI communication, wherein the indication is valid at least until the PDCCH monitoring location, regardless of the amount of time between receiving the indication and monitoring in the PDCCH monitoring location; means for sending the next DCI communication after sending the indication; and so on. In some aspects, such means may include in conjunction with Figure 2One or more components of the base station 110 are depicted, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and the like.

[0051] As pointed out above, Figure 2 is provided as an example. Other examples may differ from those described above. Figure 2 Examples described.

[0052] Figure 3 300 is a diagram illustrating an example of a DL-centric time slot or wireless communication structure. The DL-centric time slot may include a control portion 302. The control portion 302 may be present in an initial or beginning portion of the DL-centric time slot. The control portion 302 may include various scheduling information or control information corresponding to various portions of the DL-centric time slot. In some configurations, the control portion 302 may be a physical DL control channel (PDCCH), such as in Figure 3 In some aspects, the control portion 302 may include legacy PDCCH information, shortened PDCCH (sPDCCH) information, a control format indicator (CFI) value (e.g., carried on a physical control format indicator channel (PCFICH)), one or more grants (e.g., downlink grant, uplink grant, etc.), etc.

[0053] The DL-centric time slot may also include a DL data portion 304. The DL data portion 304 may sometimes be referred to as the payload of the DL-centric time slot. The DL data portion 304 may include communication resources for transmitting DL data from a scheduling entity (e.g., a UE or BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 304 may be a physical DL shared channel (PDSCH).

[0054] The DL-centric time slot may also include a UL short burst portion 306. The UL short burst portion 306 may sometimes be referred to as a UL burst, a UL burst portion, a common UL burst, a short burst, a UL short burst, a common UL short burst, a common UL short burst portion, and / or various other appropriate terms. In some aspects, the UL short burst portion 306 may include one or more reference signals. Additionally or alternatively, the UL short burst portion 306 may include feedback information corresponding to various other portions of the DL-centric time slot. For example, the UL short burst portion 306 may include feedback information corresponding to the control portion 302 and / or the data portion 304. Non-limiting examples of information that may be included in the UL short burst portion 306 include an ACK signal (e.g., a physical uplink control channel (PUCCH) ACK, a physical uplink shared channel (PUSCH) ACK, an immediate ACK), a NACK signal (e.g., a PUCCH NACK, a PUSCH NACK, an immediate NACK), a scheduling request (SR), a buffer status report (BSR), a hybrid automatic repeat request (HARQ) indicator, a channel state indication (CSI), a channel quality indicator (CQI), a sounding reference signal (SRS), a demodulation reference signal (DMRS), PUSCH data, and / or various other suitable types of information. The UL short burst portion 306 may include additional or alternative information, such as information related to a random access channel (RACH) procedure, a scheduling request, and various other suitable types of information.

[0055] like Figure 3 As shown in , the end of the DL data portion 304 can be separated in time from the beginning of the UL short burst portion 306. Such time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other appropriate terms. Such separation provides time for switching from DL communication (e.g., a receive operation performed by a slave entity (e.g., a UE)) to UL communication (e.g., a transmit operation performed by a slave entity (e.g., a UE)). The foregoing is an example of a DL-centric wireless communication structure, and alternative structures with similar features may exist without necessarily departing from the aspects described herein.

[0056] As noted above, Figure 3 is provided as an example. Other examples may differ from those described above. Figure 3 Examples described.

[0057] Figure 4 4 is a schematic diagram showing an example of a UL-centric time slot or wireless communication structure. The UL-centric time slot may include a control portion 402. The control portion 402 may be present at the beginning or the start of the UL-centric time slot. Figure 4The control portion 402 in the embodiment may be similar to that described in the above reference Figure 3 The control portion 302 described above. The UL-centric time slot may also include a UL long burst portion 404. The UL long burst portion 404 may sometimes be referred to as the payload of the UL-centric time slot. The UL portion may refer to a communication resource utilized to transmit UL data from a subordinate entity (e.g., a UE) to a scheduling entity (e.g., a UE or a BS). In some configurations, the control portion 402 may be a physical DL control channel (PDCCH).

[0058] like Figure 4 As shown in , the end of the control portion 402 can be separated in time from the beginning of the UL long burst portion 404. This time separation may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other appropriate terms. This separation provides time for switching from DL communication (e.g., receiving operations performed by the scheduling entity) to UL communication (e.g., transmissions performed by the scheduling entity).

[0059] The UL-centric timeslot may also include a UL short burst portion 406. Figure 4 The UL short burst portion 406 in the embodiment may be similar to that described above with reference to Figure 3 The UL short burst portion 306 described above and may include the Figure 3 Any of the information described. The foregoing is merely one example of a UL-centric wireless communication structure, and alternative structures with similar features may exist without necessarily departing from the various aspects described herein.

[0060] In some cases, two or more slave entities (e.g., UEs) can communicate with each other using sidelink signals. Real-life applications of such sidelink communications may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh networks, and / or various other appropriate applications. Generally, a sidelink signal may refer to a signal transmitted from one slave entity (e.g., UE1) to another slave entity (e.g., UE2) without the need for the communication to be relayed by a scheduling entity (e.g., UE or BS), even though the scheduling entity may be used for scheduling and / or control purposes. In some aspects, licensed spectrum may be used to transmit sidelink signals (unlike wireless local area networks that typically use unlicensed spectrum).

[0061] In one example, a wireless communication structure (such as a frame) may include both UL-centric time slots and DL-centric time slots. In this example, the ratio of UL-centric time slots to DL-centric time slots in a frame may be dynamically adjusted based at least in part on the amount of UL data and the amount of DL data transmitted. For example, if there is more UL data, the ratio of UL-centric time slots to DL-centric time slots may be increased. Conversely, if there is more DL data, the ratio of UL-centric time slots to DL-centric time slots may be reduced.

[0062] As noted above, Figure 4 is provided as an example. Other examples may differ from those described above. Figure 4 Examples described.

[0063] In a wireless communication system such as an NR system, a downlink control information (DCI) communication may include control information, such as information associated with resource allocation (e.g., a set of resources to be used for a downlink shared channel, a set of resources to be used for an uplink shared channel, etc.), a transport format, and / or one or more other control information items. Such a DCI communication is carried in a physical downlink control channel (PDCCH), which is transmitted in one or more control resource sets (CORESET).

[0064] A UE (e.g., UE 120) may be configured to monitor the PDCCH so that the UE may detect DCI communications intended for the UE. In a typical communication scenario, the UE performs a blind search for DCI communications in each time slot (e.g., by attempting to decode the PDCCH in one or more CORESETs). However, this so-called blind decoding results in high power consumption at the UE. For example, in the typical communication scenario described above, without any scheduling grant, the UE monitoring the PDCCH may consume more than 40% of the total UE power.

[0065] Even in scenarios where the UE does not obviously need to monitor DCI communications frequently, such as when the UE is configured with semi-persistent scheduling (SPS) or configured grants, the power consumption problem still exists. For example, the UE may need to monitor DCI communications in association with activating SPS / configured grants. As another example, the UE may need to monitor DCI communications after a beam quality problem causes a UE configured with SPS / configured grants to fail to receive downlink communications (e.g., physical downlink shared channel (PDSCH) communications). Here, after failing to receive (e.g., failing to decode) downlink communications, the UE may send a negative acknowledgement (NACK) indicating a beam quality problem. After sending the NACK, the UE may monitor (within one or more CORESETs) DCI communications associated with initiating beam scanning for beam reselection / adaptation and retransmissions of downlink communications. This problem is particularly prevalent when operating in a high frequency range, such as frequency range 2 (FR2), where beam quality problems are more likely. Therefore, even in cases where the UE does not obviously need to monitor DCI communications frequently, monitoring DCI communications may result in UE power waste.

[0066] A technique for solving the power consumption problem caused by monitoring DCI communication is to allow the base station to signal the location of the PDCCH that can carry the DCI communication for a given UE (referred to as the PDCCH monitoring location herein). According to this technique, the PDCCH monitoring location is valid within a specific number of time slots, and the PDCCH monitoring location signaled expires after a specific number of time slots. Here, the content of the DCI communication in terms of resource block allocation can be different between the occurrences of the PDCCH monitoring location signaled, and the beam used for the DCI communication can be different between the occurrences of the PDCCH monitoring location signaled. However, this technique limits the flexibility associated with receiving and sending DCI communications. For example, from the perspective of the UE, lack of flexibility means that the UE must always search for the same PDCCH monitoring location on the same part of the bandwidth (for example, even if the UE is using another part of the bandwidth to send or receive other communications). As another example, from the perspective of the base station, the base station must reserve resources for the PDCCH monitoring opportunity signaled within the time period in which the PDCCH monitoring opportunity signaled is valid, which may reduce resource utilization and / or efficiency of use.

[0067] Some aspects of this document provide techniques and apparatus for dynamic indication of a PDCCH monitoring location. In some aspects, a base station may send an indication identifying a PDCCH monitoring location associated with a next DCI communication, and a UE may receive the indication. In some aspects, the indication may be valid at least until the PDCCH monitoring location, without regard to the amount of time between receiving the indication and monitoring in the PDCCH monitoring location.

[0068] Figure 5A , 5B 5 and 5C are diagrams illustrating examples 500, 520, and 560, respectively, of dynamic indication of PDCCH monitoring locations in accordance with various aspects of the present disclosure.

[0069] As in Figure 5A As shown by reference numeral 505 in the figure, a base station (e.g., base station 110) can send an indication to a UE (e.g., UE 120) for identifying a PDCCH monitoring location associated with a next DCI communication. In other words, the base station can send an indication for identifying a PDCCH monitoring location to be monitored by the UE in association with receiving the next DCI communication. In some aspects, the indication is valid at least until the PDCCH monitoring location, without regard to the amount of time between the time of the indication and the time of the PDCCH monitoring location. In other words, the validity of the indicated PDCCH monitoring location is not defined by a specific time period (i.e., the indicated PDCCH monitoring location does not expire after a specific time period). Instead, the indication can be valid at least until the next occurrence of the PDCCH monitoring location.

[0070] In some aspects, the indication identifying the PDCCH monitoring position may include one or more parameters defining the PDCCH monitoring position. For example, the indication may include information identifying the position of the PDCCH monitoring in the frequency domain and / or information identifying the position of the PDCCH monitoring position in the time domain. As another example, the indication may include information identifying the search space in which the PDCCH monitoring position is located. As another example, the indication may include information identifying the CORESET in which the PDCCH monitoring position is located (e.g., the identified CORESET may correspond to a new or different CORESET, as will be discussed in more detail below). As another example, the indication may include information identifying the periodicity and / or offset for defining the PDCCH monitoring position. As another example, the indication may include information identifying the duration of the PDCCH monitoring position. As another example, the indication may include information identifying the number of symbols associated with the PDCCH monitoring position (e.g., the number of symbols to be monitored). As another example, the indication may include information identifying the number of PDCCH candidates.

[0071] In some aspects, the indication identifying the PDCCH monitoring position may be associated with at least one subsequent DCI communication after the next DCI communication. That is, in some aspects, the indication may identify multiple PDCCH monitoring positions, each PDCCH monitoring position being associated with a corresponding DCI communication in a plurality of subsequent DCI communications. In general, the indication may identify N (N≥1) PDCCH monitoring positions, each PDCCH monitoring position being associated with a corresponding DCI communication in the next N DCI communications.

[0072] In some aspects, the base station may send the indication in a DCI communication (e.g., in a DCI communication sent in a previously indicated PDCCH monitoring location). In some aspects, the base station may send the indication via radio resource control (RRC) signaling. In some aspects, the base station may send the indication in a medium access control (MAC) control element (CE). In this case, the MAC CE may identify a single logical channel identifier and a single PDCCH monitoring location, or may identify multiple logical channel identifiers and corresponding multiple PDCCH monitoring locations.

[0073] As further indicated by reference numeral 505, the UE may receive an indication identifying a PDCCH monitoring location. Example operations in a scenario where the UE receives the indication are described below, followed by example operations in a scenario where the UE does not receive the indication.

[0074] In some aspects, as noted above, the UE may receive the indication in a DCI communication, via RRC signaling, or in a MAC CE.

[0075] In some aspects, the UE may send an acknowledgment (ACK) indicating that the indication has been received. For example, if the indication is carried in a DCI communication and the DCI communication is sent together with a PDSCH communication, the UE may attempt to decode the DCI communication and the PDSCH communication. Here, if the UE successfully decodes the DCI communication and the PDSCH communication, the UE may send (e.g., in a PUCCH) an ACK indicating that the UE has received the indication and the PDSCH communication. Conversely, in some aspects, the UE may send a negative ACK (NACK) indicating that the indication has been received. For example, if the indication is carried in a DCI communication and the DCI communication is sent together with a PDSCH communication, the UE may attempt to decode the DCI communication and the PDSCH communication. Here, if the UE successfully decodes the DCI communication but does not successfully decode the PDSCH communication, the UE may send (e.g., in a PUCCH) a NACK indicating that the UE has received the indication but has not received the PDSCH communication. Therefore, in some aspects, the base station may receive an ACK or NACK indicating that the UE has received the indication.

[0076] As indicated by reference numeral 510, the base station may send the next DCI communication after sending the indication. In some aspects, the base station may send the next DCI communication in the indicated PDCCH monitoring position. For example, as described above, the UE may receive the indication and may send an ACK or NACK to the base station indicating that the UE has received the indication. Here, the base station may send the next DCI communication in the PDCCH monitoring position based at least in part on the ACK or NACK indicating receipt of the indication.

[0077] In some aspects, the UE may monitor in the PDCCH monitoring locations based at least in part on the indication, as indicated by reference numeral 515. For example, after receiving the indication, the UE may monitor in the identified PDCCH monitoring locations in association with receiving a next DCI communication.

[0078] In some aspects, the UE may receive the next DCI communication based at least in part on monitoring in a PDCCH monitoring position. In some aspects, the next DCI communication may include another indication for identifying another PDCCH monitoring position associated with sending a subsequent DCI communication. That is, the base station may indicate another PDCCH monitoring position associated with a subsequent DCI communication to be received by the UE (e.g., a DCI communication after the next DCI communication previously sent / received). Here, the UE may monitor in the other PDCCH monitoring position based at least in part on another indication. In this way, the indication of the PDCCH monitoring position may be repeated over time, which allows the PDCCH monitoring position to be dynamically indicated to the UE, thereby providing flexibility in terms of the PDCCH monitoring position while also reducing power consumption at the UE.

[0079] In some aspects, the UE may send an ACK or NACK to indicate that the next DCI communication has been received. For example, the next DCI communication may be sent together with a PDSCH communication, and the UE may attempt to decode the next DCI communication and the PDSCH communication. Here, if the UE successfully decodes the next DCI communication and the PDSCH communication, the UE may send (e.g., in the PUCCH) an ACK to indicate that the UE has received the next DCI communication and the PDSCH communication. Conversely, if the UE successfully decodes the next DCI communication but does not successfully decode the PDSCH communication, the UE may send (e.g., in the PUCCH) a NACK to indicate that the UE has received the next DCI communication but has not received the PDSCH communication. Therefore, in some aspects, the base station may receive an ACK or NACK to indicate that the UE has received the next DCI communication.

[0080] In some aspects, the UE may fail to receive the next DCI communication based at least in part on monitoring in the PDCCH monitoring location, and may send a NACK indicating that the next DCI communication was not received. For example, if the UE does not successfully decode the next DCI communication, the UE may send (e.g., in the PUCCH) a NACK indicating that the UE failed to receive the next DCI communication. Thus, in some aspects, the base station may receive a NACK indicating that the UE did not receive the next DCI communication.

[0081] In some aspects, based at least in part on the failure to receive the next DCI communication, the UE may monitor in the PDCCH monitoring position in association with receiving a subsequent DCI communication (e.g., a DCI communication after the next DCI communication). For example, upon failure to receive the next DCI communication, the UE may send a NACK indicating that the next DCI communication has not been received. Here, the UE may be configured to monitor in a previously indicated PDCCH monitoring position (e.g., a PDCCH monitoring position that is the same as the PDCCH monitoring position monitored for the next DCI communication that the UE has not received). In some aspects, the base station may be configured to send a subsequent DCI communication in the PDCCH monitoring position based at least in part on the receipt of a NACK indicating that the next DCI communication has not been received. In other words, in some aspects, when the UE does not receive the next DCI communication, the previously indicated PDCCH monitoring position may be reused for subsequent DCI communications.

[0082] In some aspects, based at least in part on a failure to receive a next DCI communication, the UE may monitor multiple PDCCH monitoring locations in association with receiving a subsequent DCI communication (e.g., a DCI communication after the next DCI communication). For example, upon failure to receive the next DCI communication, the UE may send a NACK indicating that the next DCI communication was not received. Here, the UE may be configured to monitor multiple PDCCH monitoring locations (e.g., multiple PDCCH monitoring locations configured for the UE, which are candidate locations for carrying a PDCCH for the UE). In some aspects, the base station may be configured to send a subsequent DCI communication in one of the multiple PDCCH monitoring locations based at least in part on receiving a NACK indicating that the next DCI communication was not received.

[0083] In some aspects, the base station may not receive an indication as to whether the next DCI communication is received. For example, this may be the case when the UE does not send an ACK or NACK, or when the base station does not receive an ACK or NACK sent by the UE (e.g., due to beam quality issues). In some aspects, the base station may be configured to send subsequent DCI communications in a PDCCH monitoring position based at least in part on not receiving an indication as to whether the next DCI communication is received. In other words, in some aspects, when the base station does not receive any indication as to whether the UE has received the next DCI communication, the previously indicated PDCCH monitoring position may be reused for subsequent DCI communications. Alternatively, the base station may be configured to send subsequent DCI in one of a plurality of PDCCH monitoring positions based at least in part on not receiving an indication as to whether the next DCI communication is received.

[0084] Figure 5BA diagram illustrating an example sequence of operations associated with dynamic indication of PDCCH monitoring locations.

[0085] As indicated by reference numeral 522, the base station uses a first beam (at Figure 5B As indicated by reference numeral 524, the first DCI communication includes an indication of a PDCCH monitoring position associated with a second DCI communication (i.e., a next DCI communication associated with the UE). As indicated by reference numeral 526, the UE receives the first DCI communication and the first PDSCH communication, and sends an ACK to the base station indicating that the UE received the first DCI communication and the first PDSCH communication.

[0086] As indicated by reference numeral 528, the base station uses the first beam to send a second DCI communication and a second PDSCH communication to the UE. Here, the base station sends the second DCI communication in the PDCCH monitoring position indicated by the first DCI communication. The UE monitors the PDCCH monitoring position indicated by the first DCI communication and receives the second DCI communication accordingly. As indicated by reference numeral 530, the second DCI communication includes an indication of the PDCCH monitoring position associated with the third DCI communication (i.e., the next DCI communication associated with the UE). Here, the UE also receives the second PDSCH communication. Next, as shown by reference numeral 532, the UE sends an ACK to the base station indicating that the UE has received the second DCI communication and the second PDSCH communication.

[0087] As indicated by reference numeral 534, the base station uses the first beam to send a third DCI communication and a third PDSCH communication to the UE. Here, the base station sends the third communication in the PDCCH monitoring position indicated by the second DCI communication. The UE monitors the PDCCH monitoring position indicated by the second DCI communication, and receives the second DCI communication accordingly. As indicated by reference numeral 536, the third DCI communication includes an indication of the PDCCH monitoring position associated with the fourth DCI communication (i.e., the next DCI communication associated with the UE). However, in this example, as indicated by reference numeral 537, when the UE receives the third DCI communication, the UE does not receive (e.g., fails to decode) the third PDSCH communication. In this example, the failure to receive the third PDSCH is caused by a beam quality problem. Therefore, as indicated by reference numeral 538, the UE sends a NACK to the base station, which indicates that the third DCI communication is received and the third PDSCH communication is not received due to a beam quality problem.

[0088] As indicated by reference numeral 540, based at least in part on the NACK, the base station and the UE perform a beam reselection procedure. For example, the base station transmits a channel state information reference signal (CSI-RS) on a set of beams (e.g., including a second beam identified as "b", a third beam identified as "c", a fourth beam identified as "d", and a fifth beam identified as "e"). The UE receives the CSI-RS and provides PUCCH communications associated with each beam in the set of beams in association with identifying a suitable beam to be used for further communications with the base station. In this example, the fourth beam is selected as the suitable beam.

[0089] As indicated by reference numeral 542, after beam reselection, the base station uses the fourth beam to send a fourth DCI communication and a fourth PDSCH communication (e.g., a retransmission of the third PDSCH) to the UE. Here, the base station sends the fourth DCI communication in the PDCCH monitoring position indicated by the third DCI communication. The UE monitors the PDCCH monitoring position indicated by the third DCI communication and receives the fourth DCI communication accordingly. As indicated by reference numeral 544, the fourth DCI communication includes an indication of the PDCCH monitoring position associated with the fifth DCI communication (i.e., the next DCI communication associated with the UE). It is worth noting that the indication of the PDCCH monitoring position included in the third DCI communication is still valid for receiving the fourth DCI communication, even if a beam reselection process is performed between the transmission of the NACK and the fourth DCI communication. In other words, the indication in the third DCI communication is valid at least until the indicated PDCCH monitoring position, regardless of the amount of time between the indication and the indicated PDCCH monitoring position (or the execution of other operations). Here, the UE also receives the fourth PDSCH communication. Therefore, as indicated by reference numeral 546, the UE transmits to the base station an ACK indicating that the UE receives the fourth DCI communication and the fourth PDSCH communication.

[0090] As indicated by reference numeral 548, after the UE sends an ACK, the UE sends a sounding reference signal (SRS) for a beam set based on which beam reselection is performed. As indicated by reference numeral 550, after sending the SRS, the base station uses the fourth beam to send the fifth DCI communication and the fifth PDSCH communication to the UE. Here, the base station sends the fifth DCI communication in the PDCCH monitoring position indicated by the fourth DCI communication. The UE monitors the PDCCH monitoring position indicated by the fourth DCI communication and receives the fifth DCI communication accordingly. As indicated by reference numeral 552, the fifth DCI communication includes an indication of the PDCCH monitoring position associated with the sixth DCI communication (i.e., the next DCI communication associated with the UE (not shown)). It is worth noting that the indication of the PDCCH monitoring position included in the fourth DCI communication is still valid for receiving the fifth DCI communication, even if the UE sent an SRS between the base station transmissions of the previous ACK and the fifth DCI communication. In other words, the indication in the fourth DCI communication is valid at least until the indicated PDCCH monitoring position, regardless of the amount of time between the indication and the indicated PDCCH monitoring position (or the performance of other operations). Here, the UE also receives the fifth PDSCH communication. Next, as shown by reference numeral 554, the UE sends an ACK to the base station indicating the receipt of the fifth DCI communication and the fifth PDSCH communication. Further operations of the base station and the UE may continue in a similar manner.

[0091] In some aspects, the indication identifying the PDCCH monitoring location may be valid for a specific time period. For example, the indication identifying the PDCCH monitoring location may be valid for a specific number of time slots, a specific number of milliseconds, etc. In this case, the PDCCH monitoring location identified by the indication may be the same for all DCI communications arriving within the specific time period.

[0092] Figure 5C A diagram illustrating another example sequence of operations associated with dynamic indication of PDCCH monitoring locations.

[0093] As indicated by reference numeral 562, the base station uses the first beam (at Figure 5CAs indicated by reference numeral 564, the first DCI communication includes an indication of a PDCCH monitoring position. Here, as indicated by the dotted arrow in reference numeral 564, the PDCCH monitoring position is valid for a specific time period (six time slots). That is, in the next six time slots, the PDCCH monitoring position identified in the indication will be used by the UE in association with receiving the DCI communication. As indicated by reference numeral 566, the UE receives the first DCI communication and the first PDSCH communication, and sends an ACK to the base station indicating that the UE has received the first DCI communication and the first PDSCH communication.

[0094] As indicated by reference numeral 568, the base station uses the first beam to send a second DCI communication and a second PDSCH communication to the UE. Here, the base station sends the second DCI communication in the PDCCH monitoring position indicated by the first DCI communication (e.g., the indication is still valid because the second DCI communication is being sent in the second time slot since the indication). The UE monitors the PDCCH monitoring position indicated by the first DCI communication and receives the second DCI communication and the second PDSCH communication accordingly. Next, as indicated by reference numeral 570, the UE sends an ACK to the base station indicating that the UE receives the second DCI communication and the second PDSCH communication.

[0095] As indicated by reference numeral 572, the base station uses the first beam to send a third DCI communication and a third PDSCH communication to the UE. Here, the base station sends the third DCI communication in the PDCCH monitoring position indicated by the first DCI communication (e.g., the indication is still valid because the third DCI communication is being sent in the fifth time slot since the indication). The UE monitors the PDCCH monitoring position indicated by the first DCI communication and receives the third DCI communication and the third PDSCH communication accordingly. Next, as shown by reference numeral 574, the UE sends an ACK to the base station indicating that the UE receives the third DCI communication and the third PDSCH communication.

[0096] As indicated by reference numeral 576, the base station uses the first beam to send a fourth DCI communication and a fourth PDSCH communication to the UE. Here, the base station sends a fourth DCI communication in the PDCCH monitoring position indicated by the first DCI communication (e.g., the indication is still valid because the fourth DCI communication is being sent in the sixth time slot since the indication). As indicated by reference numeral 578, the fourth DCI communication includes an indication of another PDCCH monitoring position. Here, as indicated by the dotted arrow in reference numeral 578, the PDCCH monitoring position is valid in the next five time slots. That is, in the next five time slots, the PDCCH monitoring position identified in another indication will be used by the UE in association with receiving the DCI communication. As indicated by reference numeral 580, the UE receives the fourth DCI communication and the fourth PDSCH communication, and sends an ACK to the base station indicating that the UE has received the fourth DCI communication and the fourth PDSCH communication.

[0097] As indicated by reference numeral 582, the base station uses the first beam to send a fifth DCI communication and a fifth PDSCH communication to the UE. Here, the base station sends the fifth DCI communication in the PDCCH monitoring position indicated by the fourth DCI communication (e.g., the indication is still valid because the fourth DCI communication is being sent in the second time slot since the indication). The UE monitors the PDCCH monitoring position indicated by the fourth DCI communication and receives the fifth DCI communication and the fifth PDSCH communication accordingly. Next, as indicated by reference numeral 584, the UE sends an ACK to the base station indicating that the UE receives the fifth DCI communication and the fifth PDSCH communication.

[0098] As indicated by reference numeral 586, the base station uses the first beam to send a sixth DCI communication and a sixth PDSCH communication to the UE. Here, the base station sends the sixth DCI communication in the PDCCH monitoring position indicated by the fourth DCI communication (e.g., the indication is still valid because the sixth DCI communication is being sent in the fourth time slot since the indication). The UE monitors the PDCCH monitoring position indicated by the fourth DCI communication and receives the sixth DCI communication and the sixth PDSCH communication accordingly. Next, as shown by reference numeral 588, the UE sends an ACK to the base station indicating that the UE receives the sixth DCI communication and the sixth PDSCH communication.

[0099] As noted above, Figures 5A-5C is provided as an example. Other examples may differ from those described above. Figures 5A-5C Examples described.

[0100] Figure 66 is a diagram illustrating an example process 600, performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 600 is an example of operations in which a UE (eg, UE 120, etc.) performs operations associated with dynamic indication of PDCCH monitoring locations.

[0101] like Figure 6 As shown, in some aspects, process 600 may include receiving an indication identifying a PDCCH monitoring location associated with receiving a next DCI communication (block 610). For example, as described above, the UE (e.g., using receive processor 258, controller / processor 280, memory 282, etc.) may receive an indication identifying a PDCCH monitoring location associated with receiving a next DCI communication.

[0102] like Figure 6 As further shown, in some aspects, process 600 may include monitoring in a PDCCH monitoring location based at least in part on the indication, wherein the indication is valid at least until the PDCCH monitoring location, without regard to the amount of time between receiving the indication and monitoring in the PDCCH monitoring location (block 620). For example, as described above, the UE (e.g., using receive processor 258, controller / processor 280, memory 282, etc.) may monitor in the PDCCH monitoring location based at least in part on the indication. In some aspects, the indication is valid at least until the PDCCH monitoring location, without regard to the amount of time between receiving the indication and monitoring in the PDCCH monitoring location.

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

[0104] In a first aspect, the indication identifying the PDCCH monitoring location comprises information associated with at least one of: a frequency domain location, a time domain location, a search space identifier, a CORESET identifier, a periodicity, an offset, a duration, a number of symbols to monitor, or a number of PDCCH candidates.

[0105] In a second aspect (alone or in combination with the first aspect), the indication identifying the PDCCH monitoring location is further associated with receiving at least one subsequent DCI communication after the next DCI communication.

[0106] In a third aspect (alone or in combination with one or more of the first and second aspects), the indication is received in a DCI.

[0107] In a fourth aspect (alone or in combination with one or more of the first to third aspects), the indication is received via RRC signaling.

[0108] In a fifth aspect (alone or in combination with one or more of the first to fourth aspects), the indication is received in a MAC CE.

[0109] In a sixth aspect (in combination with the fifth aspect), a MAC CE identifies a single logical channel identifier and a single PDCCH monitoring location.

[0110] In a seventh aspect (combined with the fifth aspect), the MAC CE identifies multiple logical channel identifiers and corresponding multiple PDCCH monitoring locations.

[0111] In an eighth aspect (alone or in combination with one or more of the first to seventh aspects), process 600 includes sending an ACK or a NACK to indicate receipt of the indication.

[0112] In a ninth aspect (alone or in combination with one or more of aspects 1 to 8), process 600 includes receiving a next DCI communication based at least in part on monitoring in a PDCCH monitoring location, wherein the next DCI communication includes another indication for identifying another PDCCH monitoring location associated with receiving a subsequent DCI communication; and monitoring in another PDCCH monitoring location based at least in part on the other indication.

[0113] In a tenth aspect (alone or in combination with one or more of the first to ninth aspects), process 600 includes receiving a next DCI communication based at least in part on monitoring in a PDCCH monitoring location; and sending an ACK or NACK to indicate receipt of the next DCI communication.

[0114] In an eleventh aspect (alone or in combination with one or more of the first to tenth aspects), process 600 includes failing to receive a next DCI communication based at least in part on monitoring in a PDCCH monitoring location; and sending a NACK indicating that the next DCI communication was not received.

[0115] In a twelfth aspect (in combination with the eleventh aspect), process 600 includes monitoring in the PDCCH monitoring location in association with receiving a subsequent DCI communication based at least in part on a failure to receive a next DCI communication.

[0116] In a thirteenth aspect (alone or in combination with one or more of the first to twelfth aspects), process 600 includes monitoring in a plurality of PDCCH monitoring locations associated with receiving a subsequent DCI communication based at least in part on a failure to receive a next DCI communication.

[0117] In a fourteenth aspect (alone or in combination with one or more of the first to thirteenth aspects), the indication identifying the PDCCH monitoring position is valid for a specific time period.

[0118] although Figure 6 Example blocks of process 600 are shown, but in some aspects process 600 may include Figure 6 The blocks depicted in the process 600 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 600. Additionally or alternatively, two or more blocks in the blocks of process 600 may be executed in parallel.

[0119] Figure 7 is a diagram illustrating an example process 700, performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process 700 is an example of operations in which a base station (eg, base station 110, etc.) performs dynamic indication of PDCCH monitoring locations.

[0120] like Figure 7 As shown, in some aspects, process 700 may include sending an indication for identifying a PDCCH monitoring location associated with sending a next DCI communication, wherein the indication is valid at least until the PDCCH monitoring location, regardless of the amount of time between receiving the indication and monitoring in the PDCCH monitoring location (block 710). For example, as described above, a base station (e.g., using transmit processor 220, controller / processor 240, memory 242, etc.) may send an indication for identifying a PDCCH monitoring location associated with sending a next DCI communication. In some aspects, the indication is valid at least until the PDCCH monitoring location, regardless of the amount of time between receiving the indication and monitoring in the PDCCH monitoring location.

[0121] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include sending a next DCI communication after sending the indication (block 720). For example, as described above, the base station (e.g., using transmit processor 220, controller / processor 240, memory 242, etc.) may send the next DCI communication after sending the indication.

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

[0123] In a first aspect, the indication identifying the PDCCH monitoring location comprises information identifying at least one of: a frequency domain location, a time domain location, a search space identifier, a CORESET identifier, a periodicity, an offset, a duration, a number of symbols to monitor, or a number of PDCCH candidates.

[0124] In a second aspect (alone or in combination with the first aspect), the indication identifying the PDCCH monitoring location is further associated with transmitting at least one subsequent DCI communication after the next DCI communication.

[0125] In a third aspect (alone or in combination with one or more of the first and second aspects), the indication is sent in a DCI.

[0126] In a fourth aspect (alone or in combination with one or more of the first to third aspects), the indication is sent via RRC signaling.

[0127] In a fifth aspect (alone or in combination with one or more of the first to fourth aspects), the indication is sent in a MAC CE.

[0128] In a sixth aspect (in combination with the fifth aspect), a MAC CE identifies a single logical channel identifier and a single PDCCH monitoring location.

[0129] In a seventh aspect (combined with the fifth aspect), the MAC CE identifies multiple logical channel identifiers and corresponding multiple PDCCH monitoring locations.

[0130] In an eighth aspect (alone or in combination with one or more of the first to seventh aspects), process 700 includes receiving an ACK or NACK indicating receipt of the indication.

[0131] In a ninth aspect (in combination with the eighth aspect), the next DCI communication is sent in the PDCCH monitoring position based at least in part on an ACK or NACK indicating receipt of the indication.

[0132] In a tenth aspect (alone or in combination with one or more of the first to ninth aspects), the next DCI communication includes another indication for identifying another PDCCH monitoring location associated with sending the subsequent DCI communication.

[0133] In an eleventh aspect (alone or in combination with one or more of the first to tenth aspects), process 700 includes receiving an ACK or NACK indicating receipt of a next DCI communication.

[0134] In a twelfth aspect (alone or in combination with one or more of the first to eleventh aspects), the process 700 includes receiving a NACK indicating that a next DCI communication was not received.

[0135] In a thirteenth aspect (in combination with the twelfth aspect), process 700 includes sending a subsequent DCI communication in a PDCCH monitoring position based at least in part on the NACK.

[0136] In a fourteenth aspect (in combination with the twelfth aspect), the process 700 includes sending a subsequent DCI communication in one of a plurality of PDCCH monitoring locations based at least in part on the NACK.

[0137] In the fifteenth aspect (alone or in combination with one or more of the first to fourteenth aspects), process 700 includes not receiving an indication as to whether a next DCI communication is received; and sending a subsequent DCI in a PDCCH monitoring position based at least in part on not receiving an indication as to whether a next DCI communication is received.

[0138] In the sixteenth aspect (alone or in combination with one or more of the first to fifteenth aspects), process 700 includes not receiving an indication as to whether a next DCI communication is received; and sending a subsequent DCI in one of a plurality of PDCCH monitoring locations based at least in part on not receiving an indication as to whether a next DCI communication is received.

[0139] although Figure 7 Example blocks of process 700 are shown, but in some aspects process 700 may include Figure 7 The blocks depicted in the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks in the blocks of process 700 may be executed in parallel.

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

[0141] Although the above Figure 5A-7 The described embodiments focus primarily on various mechanisms and protocols associated with the transmission of an indication of a PDDCH monitoring location, but other aspects of the present disclosure relate to various triggering mechanisms for sending an indication of a PDDCH monitoring location, as will be described below with respect to Figure 8-13For example, selectively triggering a request for an indication of a PDDCH monitoring location may facilitate reduced power consumption, less system interference, and less system overhead at the UE.

[0142] Figure 8 is a diagram illustrating an example process 800, performed, for example, by a UE, in accordance with various aspects of the present disclosure. Example process 800 is an example of operations in which a UE (eg, UE 120 and / or similar devices) performs operations associated with triggering a dynamic indication of a PDCCH monitoring location.

[0143] like Figure 8 As shown, in some aspects, process 800 may include monitoring a set of operating conditions associated with the UE (block 802). For example, the UE (e.g., using the receive processor 258, the controller / processor 280, the memory 282, etc.) may monitor the set of operating conditions. In some designs, the set of operating conditions may include at least one operating condition associated with a channel (e.g., PUSCH) between the UE and a base station (e.g., whether SPS / configured grants are configured on the channel, an estimated amount of traffic on the channel, characteristics of a traffic pattern on the channel, an error rate on the channel, etc.). In some designs, the set of operating conditions may include at least one operating condition associated with a state of the UE (e.g., a power state of the UE, such as a battery charge level of the UE or a charging state of the UE).

[0144] like Figure 8 As further shown in , in some aspects, process 800 may optionally include sending a request for uplink resources to a base station (e.g., via antenna 252a ... 252r, TX MIMO processor 266, modulator 254a ... 254r, TX processor 264) (block 804). In one example, the request at block 804 may be triggered by monitoring from block 802 in one example. For example, monitoring of the set of operating conditions at block 802 may cause the UE to determine to send a request for an indication for identifying a PDCCH monitoring location associated with receiving a next DCI communication. In this case, if the UE does not already have sufficient uplink resources to send a request for the indication, the request for uplink resources at block 804 may be performed. In one example, the requested uplink resources may be associated with a physical uplink control channel (PUCCH) or a medium access control (MAC) command element (CE).

[0145] like Figure 8As further shown in FIG. 8 , in some aspects, process 800 may optionally include receiving a grant of uplink resources (e.g., via antennas 252a ... 252r, demodulators 254a ... 254r, MIMO detector 256, RX processor 258) (block 806). For example, the grant received at block 806 may be received in response to the request sent at block 804. As described above, block 804 is optional, and if block 804 is not performed, block 806 may also not be performed. In one example, the granted uplink resources may be associated with a PUCCH or a MAC CE.

[0146] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending a request for an indication of a PDCCH monitoring location associated with receiving a next DCI communication based on the monitoring (e.g., via antennas 252a ... 252r, TX MIMO processor 266, modulators 254a ... 254r, TX processor 264) (block 808). In one example, the request of block 808 may be transmitted using uplink resources associated with a grant from optional block 806. Alternatively, the request of block 808 may be transmitted using other uplink resources. The monitoring of block 802 triggering the transmission of block 808 may occur in a variety of ways, as will be discussed in more detail below.

[0147] like Figure 8 As further shown in , in some aspects, process 800 may optionally include (e.g., antenna 252a ... 252r, demodulator 254a ... 254r, MIMO detector 256, RX processor 258) receiving an indication for identifying a PDCCH monitoring location in response to the request (block 810). In one example, receiving the indication at block 810 may be optional for various reasons, such as the transmission of block 808 failing to reach the base station, or alternatively, the base station may receive the transmission of block 808 and then decide to deny the UE's request for an indication identifying a PDCCH monitoring location. In some designs, the indication of block 810 may be received via a DCI communication or a MAC CE. In one example, the identified PDCCH monitoring location may be associated with a CORESET change. In this case, the request from block 808 may be characterized as a CORESET change request.

[0148] like Figure 8As further shown in , in some aspects, process 800 may optionally include (e.g., antenna 252a ... 252r, demodulator 254a ... 254r, MIMO detector 256, RX processor 258) receiving a notification from a base station that a UE's request for an indication identifying a PDCCH monitoring location has been denied (block 812). There are various reasons (e.g., various network criteria, such as load, etc.) that may cause a base station to deny a UE's request for an indication identifying a PDCCH monitoring location, as will be discussed in more detail below. In other designs, the base station may deny the UE's request for an indication identifying a PDCCH monitoring location without sending any notification to the UE. In such a system, the UE may interpret the lack of an indication as an implicit denial of the request, or alternatively may retransmit the request of block 808 to the base station.

[0149] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include: if an indication is received in response to the request, then (e.g., antenna 252a ... 252r, demodulator 254a ... 254r, MIMO detector 256, RX processor 258) monitors in the PDCCH monitoring positions (block 814). In some designs, if an indication is received to identify the PDCCH monitoring positions in accordance with block 810, then monitoring in the PDCCH monitoring positions is performed at block 814. In some designs, if an indication is not received to identify the PDCCH monitoring positions (or is completely rejected as in block 812), then monitoring in the PDCCH monitoring positions is not performed at block 814.

[0150] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may optionally include detecting (e.g., antennas 252a ... 252r, demodulators 254a ... 254r, MIMO detector 256, RX processor 258) a next DCI communication based on monitoring in the PDCCH monitoring position (block 816). The detection of block 814 is optional for various reasons (e.g., the base station may not send a DCI communication in the PDCCH monitoring position despite the indication, or may not receive the indication based on a rejection or for some other reason).

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

[0152] In a first aspect, at least one operating condition in the set of operating conditions monitored at block 802 is associated with a channel between the UE and the base station. In some designs, the channel may include a physical uplink shared channel (PUSCH) including one or more uplink resources allocated to the UE.

[0153] In a first example of the first aspect, the set of operating conditions may include whether the channel includes one or more uplink resources allocated to the UE according to an SPS or a configured grant (CG) protocol. For example, if the one or more uplink resources are not allocated using an SPS or CG protocol, the sending of the request at block 808 may be triggered.

[0154] In a second example of the first aspect, the set of operating conditions may include an estimated traffic volume of the UE on one or more uplink resources of the channel. For example, if the estimated traffic volume exceeds a traffic volume threshold, sending the request at block 808 may be triggered.

[0155] In a third example of the first aspect, the set of operating conditions may include a traffic pattern characteristic performed by the UE on one or more uplink resources of the channel. For example, if the traffic pattern characteristic on the channel is associated with non-periodic traffic, periodic traffic at an interval exceeding an interval threshold, or a combination thereof, the sending of the request at block 808 may be triggered.

[0156] In a fourth example of the first aspect, the set of operating conditions may include an error rate on the channel. For example, the error rate may correspond to a block error rate (BLER). For example, if the error rate on the channel is lower than an error rate threshold (e.g., .01%), the sending of the request at block 808 may be triggered.

[0157] In a second aspect, at least one operating condition in the set of operating conditions monitored at block 802 is associated with a state of the UE. In some designs, the state of the UE may include a power state of the UE. For example, if the power state of the UE indicates a low power condition, then in some cases the UE may benefit from skipping decoding of the PDCCH entirely. In one example, the power state of the UE may be a battery charge level of the UE, a charging state of the UE, or a combination thereof. In one example, if the battery charge level of the UE is above a charging threshold, if the charging state of the UE indicates that the UE is charging, or a combination thereof, then the sending of a request at block 808 may be triggered. Conversely, in other designs, if the battery charge level of the UE is less than a charging threshold, if the charging state of the UE indicates that the UE is not charging, or a combination thereof, then the sending of a request at block 808 may be triggered.

[0158] In the third aspect, in some designs, the set of operating conditions may include various combinations of exemplary operating conditions (e.g., if there is no SPS / CG configuration for PUSCH, the estimated traffic on PUSCH is above a traffic threshold, the UE is not charging and its battery charge level is low, then a request for an indication of a PDCCH monitoring location is triggered).

[0159] In a fourth aspect, in some designs, the request sent at block 808 may not convey a reason for sending (e.g., a monitoring operating condition prompting the sending). However, in other designs, the request sent at block 808 may include some information based on the monitoring from block 802. For example, if a particular monitoring operating condition is a condition that triggers the request sent at block 808, then information associated with the particular monitoring operating condition may be sent with the request (e.g., in the same message or a different message). If one or more monitoring operating conditions do not contribute to the decision at the UE regarding triggering the request sent at block 808, then in some designs, information associated with those non-contributing monitoring operating conditions need not be sent to the base station. As will be discussed in more detail below, in some designs, the base station may optionally consider at least some portion of the information based on the monitoring from block 802 in its decision regarding whether to grant or deny the request sent at block 808.

[0160] although Figure 8 Example blocks of process 800 are shown, but in some aspects process 800 may include Figure 8 The blocks depicted in the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks in the blocks of process 800 may be executed in parallel.

[0161] Fig. 9 is a diagram illustrating an example process 900, performed, for example, by a base station, in accordance with various aspects of the present disclosure. Example process 900 is an example of operations in which a base station (eg, base station 110, etc.) performs operations associated with triggering a dynamic indication of a PDCCH monitoring location.

[0162] like Fig. 9 As shown, in some aspects, process 900 may include receiving (e.g., via antennas 234a ... 234r, demodulators 232a ... 232r, RX MIMO processor 236, RX processor 238) a request from a UE for an indication of a PDCCH monitoring location associated with sending a next DCI communication (block 902). For example, block 902 may be performed by Figure 8 The transmission of block 808 results. In some designs, the request at block 902 may be transmitted via a PUCCH or a MAC CE.

[0163] like Fig. 9 As further shown, in some aspects, process 900 may include determining (e.g., via controller / processor 240) whether to grant the request (block 904). In one example, the determination of block 904 may be based at least in part on one or more network criteria (e.g., current loading conditions of the base station, operator policy, UE permissions, etc.). For example, a particular UE (e.g., a low priority UE) may not have sufficient authority to request a PDCCH monitoring position, wherein a request from such a UE is automatically rejected. In contrast, another UE (e.g., a high priority UE) may have sufficient authority to request a PDCCH monitoring position, wherein a request from such a UE is automatically accepted. In another example, the current loading condition of the base station may be compared to a loading threshold, and if the current loading condition is below the loading threshold, the request at block 904 may be granted, or if the current loading condition is not below the loading threshold, the request is rejected. In another example, the determination of block 904 may be based on an operator policy (e.g., the on-demand PDCCH monitoring position is turned off or on according to the operator policy, wherein block 904 rejects the request when turned off or grants the request when turned on). In other designs, the various network criteria described above and / or other network criteria may be used in combination with each other and / or in combination with operating conditions monitored at the UE. In another example, the request of block 902 may be received in association with information based on the UE's monitoring of a set of operating conditions, as described above with respect to Figure 8 If such information is received in association with the request of block 902, the information may optionally be taken into account in the determination of block 904 (e.g., if the estimated traffic volume at the UE is very high and is communicated to the base station, this may bias the base station to grant the request from block 902, etc.). The set of operating conditions for which information may be received in association with the request may correspond to the above with respect to Figure 8 Any combination of the described operating conditions (e.g., BLER, estimated traffic volume, UE charging state, etc.).

[0164] like Fig. 9As further shown in FIG. 9 , in some aspects, process 900 may optionally include sending an indication (e.g., via antennas 234a ... 234r, TX MIMO processor 230, modulators 232a ... 232r, TX processor 220) to the UE identifying a PDCCH monitoring location associated with sending a next DCI communication (block 906). In one example, block 906 is optional, and if the base station determines at block 904 not to grant the request, block 906 need not be performed. In one example, the optional transmission at block 906 may occur via a DCI communication or a MAC CE. In one example, the identified PDCCH monitoring location may be associated with a CORESET change. In this case, the request from block 902 may be characterized as a CORESET change request, and the determination from block 904 may be characterized as a determination as to whether to change the CORESET.

[0165] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may optionally include sending a notification to the UE (e.g., via antennas 234a ... 234r, TX MIMO processor 230, modulators 232a ... 232r, TX processor 220) that the base station has rejected the UE's request from block 902 (block 908). In one example, block 908 is optional and need not be performed if the base station determines at block 904 that the request is granted.

[0166] Process 900 may include additional aspects, such as any single aspect or any combination of the aspects described below and / or in conjunction with one or more other processes described elsewhere herein. Fig. 9 Example blocks of process 900 are shown, but in some aspects process 900 may include Fig. 9 The blocks depicted in the process 900 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more blocks in the blocks of process 900 may be executed in parallel.

[0167] Fig.10 An embodiment according to the present disclosure is shown. Figure 8-9 An example implementation 1000 of the processes 800-900 is provided. Specifically, Fig.10 Depicted Figure 8-9 8. Different implementations of at least some portion of processes 800-900 with respect to each of UEs 1, 2, and 3 (and their communication interactions with the corresponding serving base station 110).

[0168] refer to Fig.10 , UE 1-3 each in blocks 1002-1006 (e.g., as in Figure 8The respective operating condition sets being monitored by UEs 1-3 may be the same or different (or may partially overlap). The monitoring of blocks 1002-1004 results in UEs 1 and 2 each sending a request for an indication of a PDCCH monitoring location to base station 110 at blocks 1008-1010 (e.g., as in Figure 8 Box 808 or Fig. 9 In this example, UE 1's request at block 1008 is supplemented with monitored operating condition information, while UE 2's request at block 1010 is not supplemented with monitored operating condition information. At block 1012, UE 3 determines not to send a request for an indication of a PDCCH monitoring location.

[0169] refer to Fig.10 At block 1014, BS 110 determines to deny UE 1's request and grant UE 2's request (e.g., as in Fig. 9 At block 1016, BS 110 sends a rejection notification to UE 1 (e.g., as in Figure 8 Box 812 or Fig. 9 At block 1018, BS 110 sends an indication of a PDCCH monitoring location associated with sending the next DCI communication (e.g., as in Figure 8 Box 810 or Fig. 9 At block 1020, BS 110 sends the next DCI in the PDCCH monitoring position according to the instructions from block 1018. At block 1022, UE 2 monitors in the PDCCH monitoring position according to the instructions from block 1018 and detects the DCI contained therein (e.g., as in Figure 8 814-816 of FIG. 10 ).

[0170] Fig.11 1 is a conceptual data flow diagram 1100 illustrating data flow between different units / components in exemplary apparatuses 1102 and 1180 according to an embodiment of the present disclosure. Apparatus 1102 may be a UE (e.g., UE 120) communicating with apparatus 1180, which may be a base station (e.g., base station 110).

[0171] The apparatus 1102 includes a sending component 1104, which may correspond to Figure 2 The transmitter circuit in the UE 120 depicted in FIG. 1 includes a controller / processor 280, antennas 252a ... 252r, modulators 254a ... 254r, TX MIMO processor 266, and TX processor 264. The device 1106 also includes a condition monitoring component 1106, which may correspond to the condition monitoring component 1106 as shown in FIG. Figure 2 The processor circuit in the UE 120 depicted in FIG. 1 includes the controller / processor 280, etc. The device 1102 also includes a receiving component 1108, which may correspond to the processor circuit in FIG. Figure 2 The receiver circuitry in UE 120 depicted in FIG. 1 includes a controller / processor 280 , antennas 252 a . . . 252 r , demodulators 254 a . . . 254 r , a MIMO detector 256 , and an RX processor 258 .

[0172] The apparatus 1180 includes a receiving component 1182, which may correspond to Figure 2 The receiver circuit in BS 110 shown includes a controller / processor 240, antennas 234a...234r, demodulators 232a...232r, MIMO detector 236, RX processor 238, and communication unit 244. The device 1180 also includes a request determination component 1184, which may correspond to the example in Figure 2 The processor circuit in BS 110 depicted in FIG. 1 includes controller / processor 240. Device 1180 also includes a sending component 1186, which may correspond to the processor circuit in FIG. Figure 2 The transmitting circuit in BS 110 depicted in FIG. 1 includes, for example, a controller / processor 240, antennas 234a . . . 234r, modulators 232a . . . 232r, a Tx MIMO processor 230, a Tx processor 220, and a communication unit 244.

[0173] refer to Fig.11 , condition monitoring component 1106 monitors various operating conditions associated with device 1102 to selectively trigger sending component 1104 to send a request for a PDCCH monitoring position from device 1180. In some cases, the sending of the request for a PDCCH monitoring position may optionally involve a request / grant process for uplink resources. In this case, sending component 1104 sends a request for uplink resources to receiving component 1182 at device 1180. Request determination component 1184 determines to grant the request for uplink resources, and signals sending component 1186 to transmit the grant of the requested uplink resources back to receiving component 1108 of device 1102.

[0174] refer to Fig.11, the sending component 1104 sends a request for an indication of the PDCCH monitoring location to the receiving component 1182 at the device 1180. The request determining component 1184 determines whether to grant the request for the indication of the PDCCH monitoring location. If the request determining component 1184 determines to grant the request, the sending component 1186 sends the indication of the PDCCH monitoring location to the receiving component 1108. The sending component 1186 can then send a DCI communication based on the indication of the PDCCH monitoring location. If the request determining component 1184 determines not to grant the request, the sending component 1186 can optionally send a notification of rejection to the receiving component 1108.

[0175] One or more components of the apparatus 1102 and the apparatus 1180 may perform the above Figure 8-10 Each box in the algorithm of the flowchart. Figure 8-10 Each block in the flowchart of can be performed by a component, and the devices 1102 and 1108 may include one or more of those components. The components may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0176] Fig.12 12 is a diagram 1200 showing an example of a hardware implementation for an apparatus 1102 employing a processing system 1214. The processing system 1214 may be implemented using a bus architecture, generally represented by a bus 1224. The bus 1224 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1214. The bus 1224 links together various circuits including one or more processors and / or hardware components (represented by the processor 1204, components 1104, 1106, and 1108, and computer readable medium / memory 1206). The bus 1224 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described any further.

[0177] The processing system 1214 may be coupled to the transceiver 1210. The transceiver 1210 is coupled to one or more antennas 1220. The transceiver 1210 provides a means for communicating with various other devices over a transmission medium. The transceiver 1210 receives signals from the one or more antennas 1220, extracts information from the received signals, and provides the extracted information to the processing system 1214 (specifically the receiving component 1108). In addition, the transceiver 1210 receives information from the processing system 1214 (specifically the transmitting component 1104), and generates signals to be applied to the one or more antennas 1220 based on the received information. The processing system 1214 includes a processor 1204 coupled to a computer-readable medium / memory 1206. The processor 1204 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1206. The software, when executed by the processor 1204, causes the processing system 1214 to perform the various functions described above for any particular device. The computer-readable medium / memory 1206 may also be used to store data that is manipulated by the processor 1204 when executing software. The processing system 1214 also includes at least one of the components 1104, 1106, and 1108. The component may be a software component that runs in the processor 1204, resides / stored in the computer-readable medium / memory 1206, one or more hardware components coupled to the processor 1204, or some combination thereof. The processing system 1214 may be Figure 2 Components of the UE 120 and may include a TX processor 264, an RX processor 258 and / or at least one of a controller / processor 280 and / or a memory 282.

[0178] In one configuration, an apparatus 1102 for wireless communication (e.g., a UE) includes: a unit for monitoring a set of operating conditions associated with the UE; a unit for sending a request for an indication of a PDCCH monitoring location associated with receiving a next DCI communication based on the monitoring; and a unit for monitoring in the PDCCH monitoring location if an indication is received in response to the request. In some configurations, the apparatus 1102 for wireless communication also includes: a unit for sending a request for one or more uplink resources; and a unit for receiving a grant of one or more uplink resources in response to the request. In some configurations, the apparatus 1102 for wireless communication also includes: a unit for receiving an indication of an identification PDCCH monitoring location in response to the request. In some configurations, the apparatus 1102 for wireless communication also includes: a unit for detecting a next DCI communication based on monitoring in the PDCCH monitoring location. In some configurations, the apparatus 1102 for wireless communication also includes: a unit for receiving a notification of a base station's rejection of the request. The above means may be one or more of the above components of the device 1102 and / or a processing system 1214 of the device 1102 configured to perform the functions recited by the above means. As described above, the processing system 1214 may include the TX processor 264, the RX processor 258, and the controller / processor 280.

[0179] Fig.13 1300 is a diagram illustrating an example of a hardware implementation for an apparatus 1108 employing a processing system 1314. The processing system 1314 may be implemented using a bus architecture, generally represented by bus 1324. The bus 1324 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1314. The bus 1324 links together various circuits including one or more processors and / or hardware components (represented by the processor 1304, components 1182, 1184, and 1186, and computer readable medium / memory 1306). The bus 1324 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described any further.

[0180] The processing system 1314 may be coupled to the transceiver 1310. The transceiver 1310 is coupled to one or more antennas 1320. The transceiver 1310 provides a means for communicating with various other devices over a transmission medium. The transceiver 1310 receives signals from the one or more antennas 1320, extracts information from the received signals, and provides the extracted information to the processing system 1314 (specifically the receiving component 1182). In addition, the transceiver 1310 receives information from the processing system 1314 (specifically the transmitting component 1186), and generates signals to be applied to the one or more antennas 1320 based on the received information. The processing system 1314 includes a processor 1304 coupled to a computer-readable medium / memory 1306. The processor 1304 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1306. The software, when executed by the processor 1304, causes the processing system 1314 to perform the various functions described above for any particular device. The computer-readable medium / memory 1306 may also be used to store data that is manipulated by the processor 1304 when executing software. The processing system 1314 also includes at least one of the components 1182, 1184, and 1186. The component may be a software component that runs in the processor 1304, resides / stored in the computer-readable medium / memory 1306, one or more hardware components coupled to the processor 1304, or some combination thereof. The processing system 1314 may be Figure 2 Components of BS 110 and may include TX processor 220, RX processor 238 and / or at least one of controller / processor 240 and / or memory 242.

[0181] In one configuration, an apparatus 1180 (e.g., a BS) for wireless communication includes: a unit for receiving a request from a UE for an indication of a PDCCH monitoring location associated with sending a next DCI communication; and a unit for determining whether to grant the request. In some configurations, the apparatus 1180 for wireless communication also includes: a unit for sending an indication of a PDCCH monitoring location associated with sending a next DCI communication to the UE. In some configurations, the apparatus 1180 for wireless communication also includes: a unit for sending a notification of a rejection of the request to the UE. The above-mentioned units may be one or more of the above-mentioned components of the apparatus 1180 and / or a processing system 1314 of the apparatus 1180 configured to perform the functions recorded by the above-mentioned units. As described above, the processing system 1314 may include a TX processor 220, an RX processor 238, and a controller / processor 240.

[0182] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or / or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or / or a combination of hardware and software.

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

[0184] It will be apparent that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, or / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting in any respect. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, it being understood that software and hardware can be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0185] Even if a specific combination of features is recorded in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically recorded in the claims and / or specifically disclosed in the specification. Although each dependent claim listed below may only be directly subordinate to one claim, the disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. The phrase "at least one of" the list of items refers to any combination of those 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, and any combination of identical elements in multiples (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc or any other ordering of a, b and c).

[0186] Any element, action or instruction used herein should not be interpreted as critical or necessary, unless clearly described as such. In addition, as used herein, the articles "a" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more projects (e.g., related projects, unrelated projects, combinations of related projects and unrelated projects, etc.), and can be used interchangeably with "one or more". In the case of only expecting one project, the phrase "only one" or similar language is used. In addition, as used herein, the terms "has", "have", "having" and / or similar terms are intended to be open terms. In addition, unless otherwise clearly stated, the phrase "based on" is intended to mean "based at least in part on".

Claims

1. A method of wireless communication performed by a user equipment (UE), include: monitoring a set of operating conditions associated with the UE; transmitting, based on the monitoring, a first request for an indication of a search space identifier or a control resource set (CORESET) identifier, or both, for identifying a physical downlink control channel (PDCCH) monitoring location associated with receiving a next downlink control information (DCI) communication; receiving the indication identifying the PDCCH monitoring position in response to the first request and before the PDCCH monitoring position; and In response to the indication, monitoring is performed in the PDCCH monitoring location.

2. The method according to claim 1, in, At least one operating condition in the set of operating conditions is associated with a channel between the UE and a wireless network component, or At least one operating condition in the operating condition set is associated with the state of the UE, or The operating condition set includes an estimated traffic volume of the UE on one or more uplink resources of the channel, or The operating condition set includes a traffic pattern characteristic of the UE on one or more uplink resources of the channel, or The operating condition set includes an error rate on the channel, or The at least one operating condition in the operating condition set includes a power state of the UE, or Its combination.

3. The method according to claim 2, in, The channels include a physical uplink shared channel (PUSCH) including one or more uplink resources allocated to the UE.

4. The method according to claim 2, in, The set of operating conditions includes whether the channel includes one or more uplink resources allocated to the UE according to a semi-persistent scheduling (SPS) or a configured grant (CG) protocol.

5. The method according to claim 4, in, The sending of the first request is triggered when the one or more uplink resources are not allocated using the SPS or the CG protocol.

6. The method according to claim 2, in, The sending of the first request is triggered when: the estimated traffic volume exceeds a traffic volume threshold.

7. The method according to claim 2, in, The sending of the first request is triggered when the traffic pattern characteristic of the channel is associated with aperiodic traffic, periodic traffic during an interval exceeding an interval threshold, or a combination thereof.

8. The method according to claim 2, in, The sending of the first request is triggered when: the error rate on the channel is lower than an error rate threshold.

9. The method according to claim 2, in, The power state of the UE includes a battery charge level of the UE, a charging state of the UE, or a combination thereof.

10. The method according to claim 9, in, The sending of the first request is triggered when: the battery charge level of the UE is below a charging threshold, the charging status of the UE indicates that the UE is not charging, or a combination thereof.

11. The method according to claim 1, further comprising: include: sending a second request for one or more uplink resources; as well as receiving a grant for the one or more uplink resources in response to the second request, The first request for the indication is sent on the one or more uplink resources.

12. The method according to claim 11, in, The one or more uplink resources are associated with a physical uplink control channel (PUCCH) or a medium access control (MAC) command element (CE).

13. The method according to claim 1, in, The indication is received via a DCI communication or a Medium Access Control (MAC) Command Element (CE).

14. The method according to claim 1, further comprising: include: The next DCI communication is detected based on the monitoring in the PDCCH monitoring location.

15. The method according to claim 1, in, The indication is associated with a change to one or more CORESETs of the UE.

16. The method according to claim 1, further comprising: include: A notification of the rejection is received from the wireless network component.

17. The method according to claim 1, in, The first request includes information from the set of operating conditions that triggers the sending of the first request.

18. A method of wireless communication performed by a wireless network component, include: receiving, from a user equipment (UE), a request for an indication of a search space identifier or a control resource set (CORESET) identifier, or both, for identifying a physical downlink control channel (PDCCH) monitoring location associated with sending a next downlink control information (DCI) communication; determining to grant the request; as well as In response to the determination and prior to the PDCCH monitoring location, the indication identifying the PDCCH monitoring location associated with sending the next DCI communication is sent to the UE.

19. The method according to claim 18, in, The indication is associated with a change to one or more CORESETs of the UE.

20. The method according to claim 18, in, The determination is based in part on one or more network criteria including loading conditions, operator policies, permissions associated with the UE, or a combination thereof.

21. The method according to claim 18, in, The request is received in association with information based on monitoring of a set of operating conditions by the UE, and Wherein the determination is based in part on the received information.

22. The method according to claim 21, in, At least one operating condition in the set of operating conditions is associated with a channel between the UE and the wireless network component, One or more operating conditions in the operating condition set are associated with the state of the UE, or Its combination.

23. A user equipment (UE), include: Memory; as well as at least one processor coupled to the memory and configured to: monitoring a set of operating conditions associated with the UE; transmitting, based on the monitoring, a first request for an indication of a search space identifier or a control resource set (CORESET) identifier, or both, for identifying a physical downlink control channel (PDCCH) monitoring location associated with receiving a next downlink control information (DCI) communication; receiving the indication identifying the PDCCH monitoring position in response to the first request and before the PDCCH monitoring position; and In response to the indication, monitoring is performed in the PDCCH monitoring location.

24. The UE according to claim 23, in, At least one operating condition in the set of operating conditions is associated with a channel between the UE and a wireless network component, or At least one operating condition in the operating condition set is associated with the state of the UE, or The operating condition set includes an estimated traffic volume of the UE on one or more uplink resources of the channel, or The operating condition set includes a traffic pattern characteristic of the UE on one or more uplink resources of the channel, or The operating condition set includes an error rate on the channel, or The at least one operating condition in the operating condition set includes a power state of the UE, or Any combination thereof.

25. A wireless network component, include: Memory; as well as at least one processor coupled to the memory and configured to: receiving, from a user equipment (UE), a request for an indication of a search space identifier or a control resource set (CORESET) identifier, or both, for identifying a physical downlink control channel (PDCCH) monitoring location associated with sending a next downlink control information (DCI) communication; determining to grant the request; as well as In response to the determination and prior to the PDCCH monitoring location, the indication identifying the PDCCH monitoring location associated with sending the next DCI communication is sent to the UE.

Images