Window configuration for cellular discontinuous communication

Abstract

Methods, systems, and devices are described for wireless communication that allow for alignment of a start time of a cell-based discontinuous transmission (DTX) and / or discontinuous reception (DRX) mode between a network entity and one or more user equipments (UEs) within a serving cell associated with the network entity. The alignment may be done via coordination signaling. For example, a network may configure a periodic interval for transmitting information related to a discontinuous mode of operation in a group common downlink control information (GC DCI) message. In some additional examples, the periodic interval may allow for beam sweeping of the GC DCI message as well as efficient cell-based activation or deactivation of the discontinuous mode of operation.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 644,743, filed April 24, 2024, entitled "WINDOW CONFIGURATION FOR CELLULAR DISCONTINUOUS COMMUNICATIONS", and U.S. Provisional Patent Application No. 63 / 518,616, filed August 10, 2023, entitled "WINDOW CONFIGURATION FOR CELLULAR DISCONTINUOUS COMMUNICATIONS", which are assigned to the assignee of this application. Technical Field

[0003] The following text relates to wireless communications, including window configuration for cellular discontinuous communications. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0005] Network entities in the serving cell may employ discontinuous transmission (DTX) mode, discontinuous reception (DRX) mode, or both for power saving. DTX and DRX modes may include a time duration during which the network entity, respectively, restricts transmissions to or from one or more UEs in the serving cell. In some cases, the network entity does not transmit during DTX mode and does not receive during DRX mode. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting window configuration for cellular (e.g., cellular, serving cell-based) discontinuous communication. For example, the described technology allows alignment of the start time of cell-based discontinuous transmission (DTX) and / or discontinuous reception (DRX) modes between a network entity and one or more user equipment (UEs) within a serving cell associated with that network entity. This alignment can be accomplished via coordination signaling. For example, the network can configure periodic intervals for transmitting information related to cell-based discontinuous communication in Group Common Downlink Control Information (GC DCI) messages. In some additional or alternative examples, periodic intervals may allow beamsweeping of GC DCI messages and efficient cell-based activation or deactivation of cell-based discontinuous operation modes.

[0007] A method for wireless communication by a UE is described. The method may include: receiving control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is used to receive one or more instances of a GC DCI message; within the monitoring window, receiving at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicating with a network entity according to the configuration for the cell-based discontinuous operation mode.

[0008] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may operate individually or collectively to execute the code so that the UE: receives control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is for receiving one or more instances of a GC DCI message; within the monitoring window, receives at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicates with a network entity according to the configuration for the cell-based discontinuous operation mode.

[0009] Another UE for wireless communication is described. The UE may include: components for receiving control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is for receiving one or more instances of GC DCI messages; components for receiving at least one instance of the GC DCI message within the monitoring window according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and components for communicating with the network entity according to the configuration for the cell-based discontinuous operation mode.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: receive control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is for receiving one or more instances of GC DCI messages; within the monitoring window, receive at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicate with a network entity according to the configuration for the cell-based discontinuous operation mode.

[0011] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the control information indicates the duration of the periodic interval, the initial offset of the periodic interval relative to the radio frame boundary, or both.

[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the control information indicates the duration of the monitoring window, the timing of one or more control channel monitoring for the at least one instance of receiving the GC DCI message within the monitoring window, the starting offset of the monitoring window relative to the first symbol of the periodic interval, or any combination thereof.

[0013] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the at least one instance receiving the GC DCI message may include operations, features, components, or instructions for: receiving the GC DCI message during a first monitoring time in one or more monitoring times within the monitoring window; and avoiding monitoring at least one other monitoring time that occurs after the first monitoring time in the monitoring window based on the reception of the GC DCI message by the at least one instance during the first monitoring time.

[0014] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the control information indicates the delay duration between the last symbol of the downlink control channel received within the monitoring window and the first time slot of a second periodic interval following the periodic interval, and instances of the GC DCI message may be received via the downlink control channel.

[0015] In some examples of the methods described herein, UEs, and non-transitory computer-readable media, the delay duration may be greater than or equal to the threshold number of symbols.

[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the threshold number of symbols may be a set number of symbols corresponding to a set of subcarrier intervals in a collection of subcarrier intervals for the symbols of the downlink control channel within the monitoring window.

[0017] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for sending a UE capability report to the network entity indicating the minimum latency duration supported by the UE, wherein the threshold number of symbols may be based on the UE capability report.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the number of threshold symbols may be based on whether the configuration for the cell-based discontinuous operation mode indicates an active or deactivated state, whether the configuration for the cell-based discontinuous operation mode configures one or more of DRX mode or DTX mode, or both.

[0019] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, at least one instance of the GC DCI message includes a one-bit indication of activation or deactivation of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode includes jointly configurable DRX and DTX modes.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, at least one instance of the GC DCI message includes a two-bit indication of activation or deactivation of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode includes separately configurable DRX and DTX modes, wherein the first bit of the two-bit indication corresponds to the DRX mode, and the second bit of the two-bit indication corresponds to the DTX mode.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, at least one instance of the GC DCI message includes an indication of an activation or deactivation state for the cell-based discontinuous operation mode of the serving cell set configured by the network entity, and the activation or deactivation state can be applied to the cell-based discontinuous operation mode for each serving cell in the serving cell set.

[0022] The methods, UEs, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for monitoring at least one instance of the GC DCI message in a primary serving cell associated with the UE or in a special serving cell associated with the UE, or both, wherein the at least one instance of receiving the GC DCI message may be based on the monitoring.

[0023] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, each of the one or more instances of the GC DCI message within the monitoring window includes the same DCI message.

[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the cell-based discontinuous operation mode may be cell DRX mode, cell DTX mode, or both.

[0025] A method for wireless communication by a network entity is described. The method may include: transmitting control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is used to transmit one or more instances of a GC DCI message to one or more UEs; within the monitoring window, transmitting at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicating with at least one of the one or more UEs according to the configuration for the cell-based discontinuous operation mode.

[0026] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may operate individually or collectively to execute the code to cause the network entity to: transmit control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is used to transmit one or more instances of a GC DCI message to one or more UEs; within the monitoring window, transmit at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicate with at least one of the one or more UEs according to the configuration for the cell-based discontinuous operation mode.

[0027] Another network entity for wireless communication is described. This network entity may include: components for transmitting control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is used to transmit one or more instances of a GC DCI message to one or more UEs; components for transmitting at least one instance of the GC DCI message within the monitoring window according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and components for communicating with at least one of the one or more UEs according to the configuration for the cell-based discontinuous operation mode.

[0028] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: transmit control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is used to transmit one or more instances of a GC DCI message to one or more UEs; within the monitoring window, transmit at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicate with at least one of the one or more UEs according to the configuration for the cell-based discontinuous operation mode.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates the duration of the periodic interval, the initial offset of the periodic interval relative to the radio frame boundary, or both.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates the duration of the monitoring window, the timing of one or more control channel monitoring for the at least one instance of receiving the GC DCI message within the monitoring window, the starting offset of the monitoring window relative to the first symbol of the periodic interval, or any combination thereof.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the control information indicates the delay duration between the last symbol of the downlink control channel transmitted within the monitoring window and the first time slot of a second periodic interval following the periodic interval, and instances of the GC DCI message may be transmitted via the downlink control channel.

[0032] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the delay duration may be greater than or equal to a threshold number of symbols, which corresponds to a set of subcarrier intervals in a set of multiple subcarrier intervals for the symbols of the downlink control channel within the monitoring window.

[0033] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving from the at least one UE a report indicating a corresponding minimum delay duration supported by each of the at least one UE, wherein the delay duration may be greater than or equal to the number of symbols associated with the maximum delay duration among the corresponding minimum delay durations.

[0034] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the delay duration may be greater than or equal to a threshold number of symbols, which may be based on whether the configuration for the cell-based discontinuous operation mode indicates an active or deactivated state, whether the configuration for the cell-based discontinuous operation mode configures one or more of DRX mode or DTX mode, or both.

[0035] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one instance of the GCDCI message includes a one-bit indication of the cell-based active or deactivated state when the cell-based discontinuous operation mode includes jointly configurable DRX and DTX modes, or a two-bit indication of the active or deactivated state of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode includes individually configurable DRX and DTX modes.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, at least one instance of the GCDCI message includes an indication of an activation or deactivation state for the cell-based discontinuous operation mode for a set of serving cells configured by the network entity, and the activation or deactivation state can be applied to the cell-based discontinuous operation mode for each serving cell in the set of serving cells.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the at least one instance of transmitting the GC DCI message may include operations, features, components, or instructions for: a first instance of transmitting the GC DCI message via a first transmission beam during beam sweep; and a second instance of transmitting the GC DCI message via a second transmission beam that may be different from the first transmission beam during the beam sweep. Attached Figure Description

[0038] Figure 1 An example of a wireless communication system supporting window configuration for cellular discontinuous communication, according to one or more aspects of this disclosure, is shown.

[0039] Figure 2 An example of a wireless communication system supporting window configuration for cellular discontinuous communication, according to one or more aspects of this disclosure, is shown.

[0040] Figure 3 An example of a signaling diagram supporting window configuration for cellular discontinuous communication is shown, according to one or more aspects of this disclosure.

[0041] Figure 4 An example of a signaling diagram supporting window configuration for cellular discontinuous communication is shown, according to one or more aspects of this disclosure.

[0042] Figure 5 An example of a process flow supporting window configuration for cellular discontinuous communication is shown, according to one or more aspects of this disclosure.

[0043] Figure 6 and Figure 7 A block diagram of a device supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown.

[0044] Figure 8 A block diagram of a communication manager that supports window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown.

[0045] Figure 9A diagram is shown of a system including a device supporting window configuration for cellular discontinuous communication, according to one or more aspects of this disclosure.

[0046] Figure 10 and Figure 11 A block diagram of a device supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown.

[0047] Figure 12 A block diagram of a communication manager that supports window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown.

[0048] Figure 13 A diagram is shown of a system including a device supporting window configuration for cellular discontinuous communication, according to one or more aspects of this disclosure.

[0049] Figure 14 and Figure 15 A flowchart illustrating a method for supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. Detailed Implementation

[0050] Network entities can employ cell-based discontinuous operation, including cell-based discontinuous transmission (DTX) mode and cell-based discontinuous reception (DRX) mode, or both, to increase power savings and improve overall device coordination and efficiency in wireless communication systems. For example, cell-based DTX and DRX communication can reduce network power consumption and overall resource utilization by allowing network entities (and corresponding user equipment (UEs)) to periodically enter a sleep state during a set of configured "off" durations (e.g., inactive periods) in a DTX or DRX cycle. For example, a DTX off duration can be the duration during which network entities do not transmit signaling in a DTX cycle, and a DRX off duration can be the duration during which network devices do not receive signaling in a DRX cycle. Conversely, a DTX "on" duration (e.g., active period) can be the duration during which network entities transmit signaling in a DTX cycle, and a DRX on duration can be the duration during which network entities receive signaling in a DRX cycle.

[0051] To notify one or more UEs in the serving cell associated with a network entity of an upcoming cell-based DTX or DRX communication pattern, the network entity may send control signaling (e.g., control information, control message transmission) to the one or more UEs via a Group Common Downlink Control Information (GC DCI) message format that utilizes common scheduling for DTX or DRX communication for the one or more UEs. However, in some cases, one or more UEs may not know when the network entity sends the GC DCI, and one or more UEs may not know when the cell-based DTX or DRX activation duration begins. In such cases, one or more UEs may potentially misdetect the GC DCI and may wake up during the shutdown duration, resulting in power loss because one or more UEs monitor the GC DCI (e.g., other DTX communications) during the configured shutdown duration.

[0052] The techniques described herein allow for the alignment of the start time of cell-based discontinuous operation modes (including DTX and DRX modes) between a network entity and one or more UEs within the serving cell associated with that network entity. This alignment can be accomplished via coordinated signaling. For example, the network entity can configure periodic intervals to convey information related to discontinuous operation modes. A periodic interval may include a monitoring window for at least one instance of GC DCI messages that one or more UEs may expect to receive, the duration for performing discontinuous operation mode communication, and one or more offset or delay durations. More specifically, the network entity can configure an initial delay associated with the periodic interval, and a starting offset of the periodic interval (e.g., a time-ordered or time-first periodic interval) relative to a system frame number boundary. The network entity can also configure a monitoring window during which one or more UEs can monitor one or more instances of GC DCI messages. The network entity can also configure application latency that one or more UEs can use to switch between UE DTX and UE DRX modes or return to sleep to save power. The network entity can also configure the monitoring window to repeat according to periodicity. In some additional examples, the monitoring window may allow beams of GC DCI messages and efficient cell-based activation or deactivation of discontinuous operation modes.

[0053] Various aspects of this disclosure are first described in the context of wireless communication systems and signaling diagrams. These aspects are further illustrated and described by way of apparatus diagrams, system diagrams, and flowcharts relating to window configurations for cellular discontinuous communication.

[0054] Figure 1An example of a wireless communication system 100 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0055] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0056] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0057] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0058] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0059] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0060] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0061] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0062] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0063] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support window configurations for cellular discontinuous communication as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0064] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0065] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0066] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0067] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0068] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0069] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0070] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0071] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0072] Depending on the technology, carriers can be used to multiplex physical channels for communication. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) may be configured for a group of UEs 115. For example, one or more UEs in UE 115 may monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates may refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0073] Network entity 105 may provide communication coverage via one or more cells (e.g., serving cells) (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish neighboring cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, or may include buildings, subsets of buildings, or external space between or overlapping coverage areas.

[0074] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0075] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0076] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0077] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0078] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0079] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0080] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0081] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0082] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0083] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0084] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0085] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0086] Network entity 105 or UE 115 may use beamsweeping technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) for beamforming operations to facilitate directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals based on different beamforming weight sets associated with different transmission directions. Beam directions may be identified (e.g., by a transmitting device (such as network entity 105) or a receiving device (such as UE 115)) by transmission along different beam directions for later transmission or reception by network entity 105.

[0087] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0088] In some examples, transmissions performed by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more subbands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0089] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0090] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval. In some cases, UE 115 or network entity 105 may not support HARQ feedback corresponding to GC DCI. Therefore, techniques for configuring and aligning the start times of cell-based DTX and DRX modes can be used to improve the signaling reliability of UE 115 and network entity 105.

[0091] The techniques described herein allow for the alignment of the start time of cell-based discontinuous communication (including cell-based DTX and DRX modes) between a network entity and one or more UEs 115 within the serving cell associated with network entity 105. The alignment of start times can be accomplished via coordination signaling. For example, network entity 105 can configure periodic intervals to convey information related to discontinuous operation modes. A periodic interval may (at least) include a monitoring window for at least one instance of a GC DCI message that one or more UEs 115 may expect to receive, the duration for performing discontinuous communication, and one or more offset or delay durations. More specifically, network entity 105 can configure an initial delay associated with the periodic interval and a starting offset of the periodic interval relative to a system frame number boundary. Network entity 105 can also configure a monitoring window during which one or more UEs 115 can monitor one or more instances of GC DCI messages. Network entity 105 can also configure one or more UEs 115 to use to switch between UE DTX and UE DRX modes or return to sleep or other low-power modes to save power application latency. Network entity 105 can also configure the monitoring window to repeat periodically. In some additional or alternative examples, the monitoring window may allow beams of GC DCI messages and efficient cell-based activation or deactivation of discontinuous operation modes.

[0092] Figure 2An example of a wireless communication system 200 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entities 105-a and UE 115 (e.g., UE 115-a and UE 115-b), each of which may be as described in reference... Figure 1 Examples of network entity 105 and UE 115 described herein. Although a certain number of UEs 115 and network entities 105 are depicted in the wireless communication system 200, the techniques described herein can support a different number of UEs 115 and network entities 105 within the wireless communication system 200.

[0093] In the wireless communication system 200, network entity 105-a may transmit information (e.g., signaling, messages, transmissions) to UE 115. For example, network entity 105-a may transmit control information (e.g., control information 210-a and control information 210-b), GC DCI message reception (e.g., GC DCI message reception 215-a and GC DCI message reception 215-b), and discontinuous communication (e.g., discontinuous communication 220-a and discontinuous communication 220-b) to UE 115. In some cases, network entity 105-a may transmit information to UE 115 via a broadcast method (e.g., a multicast method). Additionally or alternatively, network entity 105-a may transmit information to UE 115-a and UE 115-b via downlink channel 205-a and downlink channel 205-b, respectively.

[0094] In some examples, UE 115 may send information to network entity 105-a. For example, UE 115 may send capability message transmission and reception and discontinuous communication (e.g., discontinuous communication 220-c and discontinuous communication 220-d) to network entity 105-a. UE 115-a and UE 115-b may send information to the network entity via uplink channel 225-a and uplink channel 225-b, respectively.

[0095] In some wireless communication systems (such as wireless communication system 200), GC DCI signaling may suffer from reduced communication reliability, especially when cell-based discontinuous operation information is indicated via GC DCI signaling. For example, UE 115, network entity 105-a, or both may not support the delivery of HARQ feedback associated with GC DCI signaling. Additionally or alternatively, in some cases, UE 115 may erroneously detect (e.g., incorrectly decode, fail to fully detect) GC DCI messages from network entity 105-a containing information related to cell-based discontinuous operation.

[0096] In such cases, the reduced reliability and error detection of GC DCI can negatively impact the wireless communication system 200. In one example, one or more UEs in UE 115 may perform operations (e.g., loop operation, CSI, beam management (BM), radio link monitoring (RLM), radio resource management (RRM)) while disabling downlink signaling during the cell-based DTX shutdown duration. In another example, UE 115 may waste power monitoring the PDCCH when network entity 105-a does not transmit via the physical downlink control channel (PDCCH) during the cell-based DTX shutdown duration. In some other examples, UE 115 may transmit a sounding reference signal (SRS) or a physical random access channel (PRACH) during the cell-based DRX shutdown duration. Each of these examples can potentially waste wireless communication resources and increase power consumption at UE 115 and network entity 105-a.

[0097] Various aspects of this disclosure relate to aligning the start time of the discontinuous communication window between UE 115 and network entity 105-a, enabling UE 115 to receive GC DCI message transmission and reception from network entity 105-a and perform discontinuous communication with network entity 105-a. This alignment of start times eliminates the association between GC DCI monitoring messages and cell-based discontinuous communication with arbitrary time slots, which increases intra-network coordination because aligning multiple start times for cell-based discontinuous communication between different UEs would require a relatively larger amount of resources and energy.

[0098] Based on the aspects presented herein, and in order to reduce the negative impact on the wireless communication system 200, the start time of cell-based discontinuous communication can be aligned between UE 115 and network entity 105-a. The start time of cell-based discontinuous communication can be associated with the reception time of a GC DCI message carrying information associated with cell-based discontinuous communication at UE 115. Additionally or alternatively, the start time can be associated with application time (e.g., duration for application changes) based on the information associated with cell-based discontinuous communication. For example, the start time can allow UE 115 sufficient time to adjust receive operations, transmit operations, or both (or switch between receive and transmit operations) based on the information associated with cell-based discontinuous communication.

[0099] Accordingly, network entity 105-a may send information associated with cell-based discontinuous communication to UE 115. For example, control information 210-a and control information 210-b may indicate a periodic interval and a monitoring window within that periodic interval. The monitoring window can be used to monitor or receive GC DCI message reception 215-a and GC DCI message reception 215-b. In some cases, GC DCI message reception may contain information associated with cell-based discontinuous communication.

[0100] Network entity 105-a and UE 115 can send discontinuous communications to each other based on information associated with cell-based discontinuous communications. For example, network entity 105-a and UE 115 can send or receive discontinuous communications during the DTX-on or DRX-on periods, respectively. In some cases, this can improve reliability and overall resource utilization in GC DCI signaling.

[0101] Figure 3 An example of a signaling diagram 300 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. Signaling diagram 300 can implement... Figure 1 and Figure 2 These aspects, or are achieved through these aspects. For example, signaling diagram 300 can depict references Figure 2 The periodic intervals 305 described (e.g., periodic intervals 305-a and 305-b) are available for reference. Figure 1 and Figure 2 The described device implements or is implemented by the device. Although an exemplary number of durations, periods, or messages are depicted in signaling diagram 300, it should be noted that this disclosure can be generalized to include any number of such durations, periods, and messages.

[0102] Signaling diagram 300 can depict the signaling diagram from the following: Figure 2 The network entity 105 indicates a periodic interval 305. The periodic interval 305 may include an initial delay 310, an application delay 315 (e.g., application delay 315-a), and a monitoring window 320 (e.g., monitoring window 320-a and monitoring window 320-b). The monitoring window 320 is available for the network entity to send and for the UE to receive at least one instance of GC DCI messages 325 (e.g., GC DCI messages 325-a and GC DCI messages 325-b). The initial delay 310 and application delay 315 allow the UE 115 and network entity 105 to implement any changes to their internal configurations (e.g., receiver configuration, transmitter configuration).

[0103] A network entity may send a configuration indication for cell-based discontinuous communication to one or more UEs. For example, the configuration may include parameters, some or all of which may correspond to or configure some or all aspects of signaling diagram 300. For example, parameters may include an initiating interval configuration that indicates the time period (e.g., duration, cycle duration) of periodic interval 305. The initiating interval configuration may indicate the time period of periodic interval 305 as a number of time slots, symbols, TTIs, or other units of time or resources. Additionally or alternatively, the initiating interval configuration may indicate a starting offset 340 of one or more periodic intervals (e.g., an initial or chronologically ordered first periodic interval, periodic interval 305-a) relative to a radio frame boundary (e.g., an SFN frame boundary).

[0104] Parameters for configuring cell-based discontinuous communication may include monitoring window configuration (e.g., GC DCI monitoring window configuration). The monitoring window configuration may indicate the duration of monitoring window 320. In some cases, the monitoring window configuration may indicate the duration of monitoring window 320 as the number of time slots, symbols, TTIs, or other time or resource units. The monitoring window configuration may also indicate one or more monitoring opportunities (e.g., PDCCH monitoring opportunities, time resources, frequency resources) within monitoring window 320, wherein the one or more monitoring opportunities are available for network entities to transmit and for one or more UEs to receive one or more instances of GC DCI messages 325. The monitoring window configuration may also indicate an initial delay 310 preceding monitoring window 320 within a periodic interval 305. For example, the monitoring window configuration may indicate the duration of initial delay 310 as the number of time slots, symbols, TTIs, or other time or resource units.

[0105] The configuration parameters for cell-based discontinuous communication may include an application delay configuration corresponding to application delay 315. Application delay 315 may be the duration between the last symbol of the monitoring timing of the instance carrying the GC DCI message and the start time slot of the next periodic interval. For example, application delay 315-a may be the duration between the last symbol of the PDCCH carrying the GC DCI message 325-b and the start time slot of the periodic interval 305-b.

[0106] Network entities can utilize application indication delay configuration to ensure that the application delay 315 is greater than or equal to the threshold number of symbols (e.g., OFDM symbols). In some cases, the threshold number of symbols can be specified for each subcarrier interval of the associated PDCCH symbols (e.g., pre-configured at the network entity, pre-configured at the UE). Additionally or alternatively, the threshold number of symbols can be a value from the set of values ​​reported in the UE capability report (e.g., the maximum value). For example, each of these UEs can report a value corresponding to the minimum number of symbols in which the UE can apply the change in discontinuous operation mode indicated by the GC DCI message 325. In such examples, the network entity can select the maximum value from the values ​​reported by the UE as the threshold number of symbols for the application delay 315, allowing the UE sufficient time to adjust its operation in response to the indication of the GC DCI message. Additionally or alternatively, the threshold number of symbols can depend on whether the GC DCI message indicates a cell-based DTX mode or a cell-based DRX mode, and can depend on whether the GC DCI message activates or deactivates cell-based discontinuous communication.

[0107] A network entity may send one or more GC DCI messages within each monitoring window of monitoring window 320. For example, network entity 105 may send GC DCI message 325-a and GC DCI message 325-b within monitoring window 320-a. GC DCI message 325-a and GC DCI message 325-b may be instances of a first GC DCI message. In other words, GC DCI messages 325 in a monitoring window (such as monitoring window 320-a) may all carry the same content (e.g., the content of a DCI message). Monitoring window 320-b may contain the same or a different number of GC DCI messages 325 as monitoring window 320-a. Additionally, GC DCI messages 325 in monitoring window 320-b may be instances of a second GC DCI message, wherein the first GC DCI message and the second GC DCI message may carry the same or different content. Although a certain number of GC DCI messages 325 are depicted herein, it should be noted that this disclosure is extendable to including any number of GC DCI messages 325 within each monitoring window 320.

[0108] GC DCI message 325 may indicate information associated with cell-based discontinuous communication. For example, GC DCI message 325 of monitoring window 320-a may include an indication of activation or deactivation (e.g., activation status or deactivation status) of cell-based discontinuous communication. The indication of activation or deactivation of cell-based discontinuous communication may be associated with (e.g., effective at) the starting candidate position of the next periodic interval (e.g., starting candidate position 330-a, starting candidate position 330-b, and starting candidate position 330-c). For example, an indication of activation of cell-based discontinuous communication received in monitoring window 320-a may indicate that cell-based discontinuous communication will be activated at starting candidate position 330-b.

[0109] In some examples, the UE may monitor all or part of the monitoring window 320. For example, the UE may monitor the monitoring window 320-a until time 335, at which time the UE may receive (e.g., decode, detect) GC DCI message 325-a. In some examples, the UE may suppress monitoring of the remaining GC DCI messages 325 within the monitoring window 320-a after time 335 (e.g., other PDCCH monitoring opportunities) based on the fact that GC DCI messages 325 have been received. In some other examples, the UE may continue monitoring the remaining GC DCI messages 325 within the monitoring window 320-a after time 335.

[0110] According to some aspects of this disclosure, a network entity may send more than one GC DCI message in monitoring window 320 to reduce the probability of UE erroneously detecting GC DCI message 325, as discussed herein. In some cases, the network entity may determine or configure the timing of PDCCH monitoring and the corresponding number of GC DCI messages 325 configured and sent within each monitoring window 320.

[0111] In some cases, the UE may monitor all serving cells communicating with the UE in response to GC DCI message 325 during monitoring window 320. In other cases, the UE may monitor a specific serving cell in response to GC DCI message 325 during monitoring window 320. For example, the UE may monitor a primary serving cell, a special serving cell (e.g., a primary serving cell and a combination of a primary serving cell and a secondary serving cell) or both in response to GC DCI message 325 during monitoring window 320.

[0112] Additionally or alternatively, GC DCI message 325 may carry other information associated with window configuration for cellular discontinuous communication. For example, GC DCI message 325 may indicate a common flag indicating the activation or deactivation of discontinuous operation modes for a certain number of serving cells. For example, a subset of serving cells may correspond to a common flag in a set of serving cells. The subset of serving cells may be configured by a network entity (e.g., the dominant network entity, the network entity sending GC DCI message 325), and this configuration may be executed or indicated via RRC signaling.

[0113] In some examples, a network entity may send a GC DCI message 325 including a public flag that indicates the activation or deactivation of discontinuous communication for a subset of serving cells. At the starting candidate location, each serving cell in the subset of serving cells may activate or deactivate discontinuous communication within the corresponding serving cell based on the activation or deactivation indicated by the public flag.

[0114] Discontinuous communication may include cell-based discontinuous operation modes, including DTX mode, DRX mode, or both, which may be configured jointly or individually. If DTX mode and DRX mode are configured individually, the indication for activating or deactivating the discontinuous operation mode may include two bits, such that one bit indicates activation or deactivation for DTX mode and the other bit indicates activation or deactivation for DRX mode. In some other examples, if DTX mode and DRX mode are configured jointly, the indication for activating or deactivating the discontinuous operation mode may include a common bit, wherein this common bit indicates activation or deactivation for both DTX mode and DRX mode. In some cases, a common bit may allow for lower DCI overhead compared to other options.

[0115] Figure 4 An example of a signaling diagram 400 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. Signaling diagram 400 can implement... Figures 1 to 3 It can be implemented through various aspects, or by these aspects. For example, signaling diagram 400 may include network entity 105-b, which can be respectively Figure 1 and Figure 2Examples of network entities 105 and 105-a are shown in the diagram. The signaling diagram may also include periodic intervals 405, which include an initial delay 410, an application delay 415, a monitoring window (e.g., monitoring window 420), GC DCI messages 425 (e.g., GC DCI message 425-a, GC DCI message 425-b, GC DCI message 425-c, GC DCI message 425-d, GC DCI message 425-e, and GC DCI message 425-f), and a starting candidate position 430, which may correspond to... Figure 3 The corresponding aspects. Although an exemplary number of durations, periods, or message receptions are depicted in signaling diagram 400, this disclosure can be generalized or extended to include any number of such durations, periods, and message receptions.

[0116] Signaling diagram 400 illustrates network entity 105-b transmitting multiple GC DCI messages 425 via multiple transmit beams 435. The multiple transmit beams 435 may be associated with a beam sweeping process. In some systems, beam sweeping for GC DCI message transmission and reception can improve the delivery reliability of the GC DCI messages 425.

[0117] In some cases, each transmit beam 435 may correspond to (e.g., be used for transmission) one or more GC DCI messages 425 transmitted within the monitoring window 420. For example, transmit beam 435-a may correspond to GC DCI messages 425-a and 425-d, transmit beam 435-b may correspond to GC DCI messages 425-b and 425-e, transmit beam 435-c may correspond to GC DCI messages 425-c and 425-f, and transmit beam 435-d may correspond to one or more additional GC DCI messages. In some systems, network entity 105-b may determine or configure parameters of the transmit beams 435, which transmit beams 435 to be included in the beam sweep process, and the number of GC DCI messages 425 to be transmitted via each transmit beam 435 during the monitoring window 420. In some cases, transmit beams 435 may be associated with one or more different directions, frequencies, bandwidths, or other beamforming parameters.

[0118] Figure 5 An example of a process flow 500 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. Process flow 500 can implement... Figures 1 to 4 It can be implemented through various aspects, or by these aspects. For example, process flow 500 may include network entity 105-c and UE 115-c, which can be Figure 1 , Figure 2 and Figure 4Examples of network entity 105 and UE 115. Additionally, some aspects of process flow 500 may be related to... Figure 3 and Figure 4 The discontinuous communication, periodic interval 305 and periodic interval 405 are associated with or based on these discontinuous communication and periodic intervals.

[0119] In the following description of process flow 500, operations may be performed in a different order than those shown, or other operations may be added to or removed from process flow 500. For example, some operations may be omitted from process flow 500, some operations may be performed in a different order or at different times, or other operations may be added to process flow 500. Although UE 115-c and network entity 105-c are shown as performing operations of process flow 500, some aspects of some operations may also be performed by one or more other wireless devices or network devices.

[0120] At point 505, UE 115-c may send a capability report associated with GC DCI message reception and transmission to network entity 105-c. In some cases, the capability report may include one or more values, where at least one of these values ​​corresponds to at least a minimum number of symbols in which UE 115-c is able to apply changes to the discontinuous operation mode indicated by the GC DCI message. The capability report may include additional indications of parameters of UE 115-c associated with GC DCI message reception and transmission and discontinuous operation.

[0121] At point 510, network entity 105-c can determine the number of threshold symbols for the duration of one or more application delays configured for the discontinuous operation mode window. The number of threshold symbols can be based on capability reports received at network entity 105-c from UE 115-c and one or more other UEs. For example, network entity 105-c can select the maximum value among the values ​​received in the capability reports as the number of threshold symbols. In this way, network entity 105-c can select a sufficiently large number of threshold symbols to allow all UEs that have sent capability reports to network entity 105-c to apply changes for discontinuous operation mode within the application delay.

[0122] At point 515, network entity 105-c may send control information to UE 115-c. Network entity 105-c may send the control information to UE 115-c via a downlink control channel or via broadcast or multicast. The control information may indicate a periodic interval, and within that periodic interval, a monitoring window, an initial delay, and an application delay. The control information may also indicate one or more monitoring opportunities within a monitoring window (e.g., PDCCH monitoring opportunities), wherein the monitoring window is for network entity 105-c to send GC DCI messages and for UE 115-c to receive GC DCI messages within the monitoring opportunity.

[0123] Additionally or alternatively, the control information may indicate other aspects of the periodic interval. For example, the control information may indicate the duration of the periodic interval, the initial offset of the periodic interval (e.g., the first periodic interval in chronological order) relative to the radio frame boundary, or both. The control information may also indicate the duration of the monitoring window, the initial delay of the monitoring window relative to the first symbol of the periodic interval, or both. Additionally or alternatively, the control information may indicate the application delay of the periodic interval, wherein the application delay may be the delay duration between the last symbol of the downlink control channel within the monitoring window and the first timeslot of the next periodic interval.

[0124] At 520-a, network entity 105-c may send one or more GC DCI messages during a monitoring window. Network entity 105-c may send one or more GC DCI messages during the monitoring period of the monitoring window. Network entity 105-c may determine the number of instances of GC DCI messages to be transmitted during the monitoring window, wherein each instance of the GC DCI message in the monitoring window carries the same information (e.g., DCI information).

[0125] The GC DCI message may contain information related to cell-based discontinuous operation modes for one or more serving cells associated with network entity 105-c. For example, the GC DCI message may contain an indication to activate or deactivate cell-based discontinuous communication. The indication to activate or deactivate may be a common flag associated with one or more serving cells. For example, the network entity may configure a subset of serving cells from a set of serving cells, wherein this subset of serving cells may be associated with a common flag. The subset of serving cells may be aligned such that each serving cell in the subset activates or deactivates the discontinuous operation mode according to the indication in the common flag.

[0126] Cell-based discontinuous communication can be associated with DTX mode, DRX mode, or both, which can be configured jointly or individually. Indications for activation or deactivation can also be associated with DTX mode, DRX mode, or both. In one example, if DTX and DRX modes are configured jointly, the activation or deactivation indication may contain one bit. One bit indicates the activation or deactivation of both DTX and DRX modes. In another example, if DTX and DRX modes are configured individually, the activation or deactivation indication may contain two bits. Of these two bits, one bit indicates the activation or deactivation of DTX mode, and the other bit indicates the activation or deactivation of DRX mode.

[0127] Network entity 105-c may send GC DCI messages as part of a beam sweeping process (e.g., operation). For example, one or more GC DCI messages in the GC DCI message may correspond to a first transmission beam, and another one or more GC DCI messages in the GC DCI message may correspond to a second transmission beam. Network entity 105-c may determine the number of transmission beams in the beam sweeping process, the parameters of each transmission beam, and the number of DCI messages to be transmitted via each transmission beam. The beam sweeping process can improve the reliability of GC DCI message transmission and reception between network entity 105-c and UE 115-c.

[0128] At 520-b, UE 115-c can monitor GC DCI messages during monitoring times within a monitoring window. As discussed herein, GC DCI messages may contain information associated with cell-based discontinuous communication, such as indications of activation or deactivation of discontinuous operation modes in one or more serving cells.

[0129] UE 115-c can monitor all or part of the monitoring window for discontinuous operation modes. For example, UE 115-c can monitor the monitoring window until it receives a GC DCI message. In some cases, UE 115-c can suppress monitoring of the remaining (e.g., the remaining number) GC DCI messages within the monitoring window after a GC DCI message has been received. In other cases, UE 115-c can continue monitoring the remaining GC DCI messages within the monitoring window after receiving a GC DCI message.

[0130] At point 525, network entity 105-c and UE 115-c can communicate messages based on cell-based discontinuous communication. For example, network entity 105-c can suppress message transmission (e.g., downlink message reception) or message reception (e.g., uplink message reception) during a cell-based DTX shutdown duration or a cell-based DRX shutdown duration, respectively. Similarly, UE 115-c can avoid transmitting messages (e.g., uplink message reception) or monitoring messages (e.g., downlink message reception) during a cell-based DRX shutdown duration or a cell-based DTX shutdown duration.

[0131] Figure 6 A block diagram 600 illustrates a device 605 supporting window configurations for cellular discontinuous communication according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of a UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with window configurations for cellular discontinuous communication). The information may be transmitted to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0133] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to window configurations for cellular discontinuous communication, including packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0134] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of window configuration for cellular discontinuous communication as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0135] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0136] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0137] In some examples, the communication manager 620 may be configured to use a receiver 610, a transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0138] According to the examples disclosed herein, the communication manager 620 may support wireless communication. For example, the communication manager 620 is capable of, configured to, or operable to support components for receiving control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to receive one or more instances of GC DCI messages. The communication manager 620 is capable of, configured to, or operable to support components for receiving at least one instance of GC DCI messages within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The communication manager 620 is capable of, configured to, or operable to support components for communicating with network entities according to a configuration for a cell-based discontinuous operation mode.

[0139] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., at least one processor that controls or is otherwise coupled to receiver 610, transmitter 615, communication manager 620, or a combination thereof) can support techniques for improving network energy efficiency. For example, the UE can more reliably communicate GC DCI message reception and discontinuous operation mode message reception. Increased reliability can result in power savings at the UE due to suppression of monitoring or message transmission during cell-based DTX or DRX shutdown durations, respectively.

[0140] Figure 7 A block diagram 700 illustrates a device 705 supporting a window configuration for cellular discontinuous communication according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0141] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with window configurations for cellular discontinuous communication). The information may be transmitted to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0142] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to window configurations for cellular discontinuous communication, including packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0143] Device 705 or its various components may be examples of various aspects of a window configuration for performing cellular discontinuous communication as described herein. For example, communication manager 720 may include control information manager 725, discontinuous communication manager 730, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0144] According to the examples disclosed herein, the communication manager 720 may support wireless communication. The control information manager 725 is capable of, configured to, or operable to support components for receiving control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to receive one or more instances of GC DCI messages. The control information manager 725 is capable of, configured to, or operable to support components for receiving at least one instance of a GC DCI message within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The discontinuous communication manager 730 is capable of, configured to, or operable to support components for communicating with network entities according to a configuration for a cell-based discontinuous operation mode.

[0145] Figure 8A block diagram 800 illustrates a communication manager 820 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure. The communication manager 820 may be an example of a communication manager 620, a communication manager 720, or aspects thereof as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of window configuration for cellular discontinuous communication as described herein. For example, the communication manager 820 may include a control information manager 825, a discontinuous communication manager 830, a capability report manager 835, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0146] According to the examples disclosed herein, the communication manager 820 may support wireless communication. The control information manager 825 is capable of, configured to, or operable to support components for receiving control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to receive one or more instances of GC DCI messages. In some examples, the control information manager 825 is capable of, configured to, or operable to support components for receiving at least one instance of a GC DCI message within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The discontinuous communication manager 830 is capable of, configured to, or operable to support components for communicating with network entities according to a configuration for a cell-based discontinuous operation mode.

[0147] In some examples, the control information indicates the duration of a periodic interval, the initial offset of the periodic interval relative to the radio frame boundary, or both.

[0148] In some examples, the control information indicates the duration of the monitoring window, the timing of one or more control channel monitoring for at least one instance of receiving GC DCI messages within the monitoring window, the starting offset of the monitoring window relative to the first symbol of the periodic interval, or any combination thereof.

[0149] In some examples, to support at least one instance receiving GC DCI messages, the control information manager 825 is capable of, configured to, or operable to support components for receiving GC DCI messages during a first monitoring time in one or more monitoring times within a monitoring window. In some examples, to support at least one instance receiving GC DCI messages, the control information manager 825 is capable of, configured to, or operable to support components for avoiding monitoring at least one additional monitoring time occurring after the first monitoring time in one or more monitoring times within a monitoring window based on the reception of GC DCI messages by at least one instance during the first monitoring time.

[0150] In some examples, the control information indicates the delay duration between the last symbol of the downlink control channel received within the monitoring window and the first time slot of the second periodic interval following the periodic interval. In some examples, instances of GC DCI messages are received via the downlink control channel.

[0151] In some examples, the delay duration is greater than or equal to the threshold number of symbols. In some examples, the threshold number of symbols is a set number of symbols corresponding to the subcarrier spacing in a set of multiple subcarrier spacings for symbols of the downlink control channel within the monitoring window.

[0152] In some examples, the capability report manager 835 is capable of, configured to, or able to operate to support components for sending UE capability reports to network entities that indicate the minimum latency duration supported by the UE, wherein the number of threshold symbols is based on the UE capability report.

[0153] In some examples, the number of threshold symbols is based on whether the configuration for cell-based discontinuous operation mode indicates an active or deactivated state, and whether the configuration for cell-based discontinuous operation mode is configured with one or more of DRX mode or DTX mode, or both.

[0154] In some examples, when the cell-based discontinuous operation mode includes a jointly configured DRX mode and DTX mode, at least one instance of the GC DCI message includes a one-bit indication of activation or deactivation of the cell-based discontinuous operation mode.

[0155] In some examples, when the cell-based discontinuous operation mode includes separately configured DRX and DTX modes, at least one instance of the GC DCI message includes a two-bit indication of activation or deactivation of the cell-based discontinuous operation mode. In some examples, the first bit of the two-bit indication corresponds to the DRX mode, and the second bit of the two-bit indication corresponds to the DTX mode.

[0156] In some examples, at least one instance of the GC DCI message includes an indication of an active or deactivated state for a cell-based discontinuous operation mode configured by a network entity for a set of serving cells. In some examples, the active or deactivated state applies to the cell-based discontinuous operation mode for each serving cell in the set of serving cells.

[0157] In some examples, the control information manager 825 is capable of, configured to, or able to operate to support components for monitoring at least one instance of GC DCI messages in a primary serving cell associated with the UE or in a special serving cell associated with the UE, or both, wherein at least one instance of receiving GC DCI messages is based on monitoring.

[0158] In some examples, each instance of one or more instances of GC DCI messages within the monitoring window includes the same DCI message. In some examples, the cell-based discontinuous operation mode is cell DRX mode, cell DTX mode, or both.

[0159] Figure 9 A diagram of a system 900 including a device 905 supporting window configuration for cellular discontinuous communication, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0160] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX® Alternatively, it may be another known operating system. Additionally or alternatively, the I / O controller 910 may represent, or interact with, a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0161] In some cases, device 905 may include a single antenna 925. However, in other cases, device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired or wireless link as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0162] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0163] At least one processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting window configuration for cellular discontinuous communication). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process such input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 930 or otherwise.

[0164] According to the examples disclosed herein, the communication manager 920 may support wireless communication. For example, the communication manager 920 is capable of, configured to, or operable to support components for receiving control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to receive one or more instances of GC DCI messages. The communication manager 920 is capable of, configured to, or operable to support components for receiving at least one instance of a GC DCI message within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The communication manager 920 is capable of, configured to, or operable to support components for communicating with network entities according to a configuration for a cell-based discontinuous operation mode.

[0165] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support techniques for improving communication reliability at the UE (particularly during GC DCI communication and discontinuous operation mode communication). For example, the UE can receive GC DCI message transmissions more reliably because the monitoring window is aligned between the UE and the network entity. Since GC DCI message transmissions contain information associated with cell-based discontinuous operation mode communication, the UE can communicate more reliably during discontinuous operation mode, resulting in reduced latency due to error detection transmissions.

[0166] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of the window configuration for cellular discontinuous communication as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0167] Figure 10A block diagram 1000 of a device 1005 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of network entity 105 as described herein. Device 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0168] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0169] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0170] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of window configuration for cellular discontinuous communication as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0171] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0172] Additionally or alternatively, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0173] In some examples, the communication manager 1020 may be configured to use the receiver 1010, the transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or integrate with the receiver 1010, the transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0174] According to the examples disclosed herein, the communication manager 1020 may support wireless communication. For example, the communication manager 1020 is capable of, configured to, or operable to support components for transmitting control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to transmit one or more instances of GC DCI messages to one or more UEs. The communication manager 1020 is capable of, configured to, or operable to support components for transmitting at least one instance of GC DCI messages within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The communication manager 1020 is capable of, configured to, or operable to support components for communicating with at least one of one or more UEs according to a configuration for a cell-based discontinuous operation mode.

[0175] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 (e.g., at least one processor that controls or is otherwise coupled to receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof) can support techniques for improving network energy efficiency. For example, network entities may spend less time monitoring messages during cell-based DRX shutdown durations and less time transmitting messages during cell-based DTX shutdown durations. These can result in less power usage and thus save network energy.

[0176] Figure 11 A block diagram 1100 of a device 1105 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include receiver 1110, transmitter 1115, and communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0177] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0178] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0179] Device 1105 or its various components may be examples of various aspects of a window configuration for performing cellular discontinuous communication as described herein. For example, communication manager 1120 may include control information manager 1125, discontinuous communication manager 1130, or any combination thereof. Communication manager 1120 may be an example of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use receiver 1110, transmitter 1115, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0180] According to the examples disclosed herein, the communication manager 1120 may support wireless communication. The control information manager 1125 is capable of, configured to, or operable to support components for transmitting control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to transmit one or more instances of GC DCI messages to one or more UEs. The control information manager 1125 is capable of, configured to, or operable to support components for transmitting at least one instance of GC DCI messages within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The discontinuous communication manager 1130 is capable of, configured to, or operable to support components for communicating with at least one of one or more UEs according to a configuration for a cell-based discontinuous operation mode.

[0181] Figure 12 A block diagram 1200 is shown of a communication manager 1220 supporting window configuration for cellular discontinuous communication according to one or more aspects of this disclosure. The communication manager 1220 may be an example of a communication manager 1020, a communication manager 1120, or aspects thereof as described herein. The communication manager 1220 or its various components may be examples of components for performing various aspects of window configuration for cellular discontinuous communication as described herein. For example, the communication manager 1220 may include a control information manager 1225, a discontinuous communication manager 1230, a capability reporting manager 1235, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0182] According to the examples disclosed herein, the communication manager 1220 may support wireless communication. The control information manager 1225 is capable of, configured to, or operable to support components for transmitting control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to transmit one or more instances of GC DCI messages to one or more UEs. In some examples, the control information manager 1225 is capable of, configured to, or operable to support components for transmitting at least one instance of a GC DCI message within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The discontinuous communication manager 1230 is capable of, configured to, or operable to support components for communicating with at least one of one or more UEs according to a configuration for a cell-based discontinuous operation mode.

[0183] In some examples, the control information indicates the duration of a periodic interval, the initial offset of the periodic interval relative to a radio frame boundary, or both. In some examples, the control information indicates the duration of a monitoring window, the timing of one or more control channel monitoring for receiving at least one instance of a GC DCI message within the monitoring window, the initial offset of the monitoring window relative to the first symbol of the periodic interval, or any combination thereof.

[0184] In some examples, the control information indicates the delay duration between the last symbol of the downlink control channel transmitted within the monitoring window and the first time slot of the second periodic interval following the periodic interval. In some examples, instances of GC DCI messages are transmitted via the downlink control channel.

[0185] In some examples, the delay duration is greater than or equal to a threshold number of symbols, which corresponds to a set of subcarrier intervals in a set of multiple subcarrier intervals for symbols of the downlink control channel within the monitoring window.

[0186] In some examples, the capability report manager 1235 is capable of, configured to, or able to operate to support components for receiving one or more UE capability reports from at least one UE indicating a corresponding minimum delay duration supported by each of the at least one UE, wherein the delay duration is greater than or equal to the number of symbols associated with the maximum delay duration among the corresponding minimum delay durations.

[0187] In some examples, the delay duration is greater than or equal to a threshold number of symbols, which is based on whether the configuration for cell-based discontinuous operation mode indicates an active or deactivated state, and whether the configuration for cell-based discontinuous operation mode is configured with one or more of DRX mode or DTX mode, or both.

[0188] In some examples, at least one instance of a GC DCI message includes a one-bit indication of the cell-based active or deactivated state when the cell-based discontinuous operation mode includes a jointly configured DRX mode and DTX mode, or a two-bit indication of the cell-based discontinuous operation mode's active or deactivated state when the cell-based discontinuous operation mode includes separately configured DRX mode and DTX mode.

[0189] In some examples, at least one instance of the GC DCI message includes an indication of an active or deactivated state for a cell-based discontinuous operation mode configured by a network entity for a set of serving cells. In some examples, the active or deactivated state applies to the cell-based discontinuous operation mode for each serving cell in the set of serving cells.

[0190] In some examples, to support at least one instance of transmitting GC DCI messages, the control information manager 1225 is capable of, configured to, or operable to support components for transmitting a first instance of GC DCI messages via a first transmit beam during beam sweep. In some examples, to support at least one instance of transmitting GC DCI messages, the control information manager 1225 is capable of, configured to, or operable to support components for transmitting a second instance of GC DCI messages via a second transmit beam different from the first transmit beam during beam sweep.

[0191] Figure 13 A diagram of a system 1300 including a device 1305 supporting window configuration for cellular discontinuous communication, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or may include components thereof. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components supporting output and obtaining communication, such as a communication manager 1320, a transceiver 1310, an antenna 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0192] Transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1310 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that are capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1315, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315, and one or more processors or one or more memory components (e.g., at least one processor 1335, at least one memory 1325, or both), may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0193] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by one or more processors of at least one processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by a processor of at least one processor 1335, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1325 may also include a BIOS, among other things, that controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0194] At least one processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1325) to cause device 1305 to perform various functions (e.g., functions or tasks supporting window configuration for cellular discontinuous communication). For example, device 1305 or components of device 1305 may include at least one processor 1335 and at least one memory 1325 coupled to one or more processors in at least one processor 1335, wherein at least one processor 1335 and at least one memory 1325 are configured to perform the various functions described herein. At least one processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1330) host functions for performing the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories in at least one memory 1325). In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1335 may be a component of a processing system, which can refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1335) and memory circuitry (which may include at least one memory 1325) that receives or receives input and processes that input to produce, generate, or obtain output. The processing system may be configured to perform one or more of the functions described herein. Therefore, at least one processor 1335 or a processing system including at least one processor 1335 may be configured, configured to, or operated to cause the device 1305 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1325 or otherwise.

[0195] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1305, or communication performed between different components of device 1305 that are co-addressable or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, at least one memory 1325, code 1330 and at least one processor 1335 may be located in one component of different components or partitioned between different components).

[0196] In some examples, the communication manager 1320 may manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1320 may manage the delivery of data communications by client devices such as one or more UEs 115. In some examples, the communication manager 1320 may manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1320 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0197] According to the examples disclosed herein, the communication manager 1320 may support wireless communication. For example, the communication manager 1320 is capable of, configured to, or operable to support components for transmitting control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to transmit one or more instances of GC DCI messages to one or more UEs. The communication manager 1320 is capable of, configured to, or operable to support components for transmitting at least one instance of GC DCI messages within the monitoring window based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. The communication manager 1320 is capable of, configured to, or operable to support components for communicating with at least one of one or more UEs according to a configuration for a cell-based discontinuous operation mode.

[0198] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support techniques for enhancing the reliability of GC DCI message transmission and reception and discontinuous operation mode communication at network entities. For example, by configuring a cell-based discontinuous operation mode window, network entities can send GC DCI message transmission and reception more reliably, which allows network entities to communicate more reliably based on cell-based discontinuous communication.

[0199] In some examples, the communication manager 1320 may be configured to use or cooperate with transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof, to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors in at least one processor 1335 to cause device 1305 to perform various aspects of the window configuration for cellular discontinuous communication as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0200] Figure 14 A flowchart illustrating a method 1400 for supporting window configuration for cellular discontinuous communication according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be implemented by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0201] At 1405, the method may include receiving control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to receive one or more instances of GC DCI messages. The operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be provided by reference to [reference needed]. Figure 8 The control information manager 825 described is used to execute this.

[0202] At 1410, the method may include, within a monitoring window, receiving at least one instance of a GC DCI message based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. Operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be provided by reference to [reference needed]. Figure 8 The control information manager 825 described is used to execute this.

[0203] At 1415, the method may include communicating with a network entity according to a configuration for a cell-based discontinuous operation mode. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be provided by reference to [reference needed]. Figure 8 The described discontinuous communication manager 830 is used to execute this.

[0204] Figure 15 A flowchart illustrating a method 1500 for supporting window configuration for cellular discontinuous communication according to various aspects of this disclosure is shown. Operation of method 1500 may be implemented by a network entity or its components as described herein. For example, operation of method 1500 may be implemented by, as referenced... Figures 1 to 5 as well as Figures 10 to 13 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0205] At 1505, the method may include sending control information indicating a periodic interval and a monitoring window within that periodic interval, wherein the monitoring window is used to send one or more instances of GC DCI messages to one or more UEs. The operation of block 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 12 The control information manager 1225 described herein is used to execute this.

[0206] At 1510, the method may include, within a monitoring window, sending at least one instance of a GC DCI message based on control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be provided by reference to [reference needed]. Figure 12 The control information manager 1225 described herein is used to execute this.

[0207] At 1515, the method may include communicating with at least one of one or more UEs according to a configuration for a cell-based discontinuous operation mode. Operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1515 may be provided by reference to [reference needed]. Figure 12 The described discontinuous communication manager 1230 is used to execute this.

[0208] The following provides an overview of the various aspects of this disclosure:

[0209] Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is configured to receive one or more instances of a GC DCI message; within the monitoring window, receiving at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicating with a network entity according to the configuration for the cell-based discontinuous operation mode.

[0210] Aspect 2: According to the method of aspect 1, wherein the control information indicates the duration of the periodic interval, the start offset of the periodic interval relative to the radio frame boundary, or both.

[0211] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the control information indicates the duration of the monitoring window, one or more control channel monitoring times for receiving the at least one instance of the GC DCI message within the monitoring window, the starting offset of the monitoring window relative to the first symbol of the periodic interval, or any combination thereof.

[0212] Aspect 4: According to the method of aspect 3, wherein the at least one instance of receiving the GC DCI message further includes: receiving the GC DCI message during a first monitoring time of one or more monitoring times within the monitoring window; and avoiding monitoring at least one other monitoring time occurring after the first monitoring time within the monitoring window based at least in part on the reception of the GC DCI message by the at least one instance during the first monitoring time.

[0213] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the control information indicates the delay duration between the last symbol of the downlink control channel received within the monitoring window and the first time slot of the second periodic interval following the periodic interval, and the instance of the GC DCI message is received via the downlink control channel.

[0214] Aspect 6: According to the method of aspect 5, the delay duration is greater than or equal to the threshold number of symbols.

[0215] Aspect 7: According to the method of aspect 6, the threshold symbol number is a set number of symbols corresponding to a subcarrier interval among a plurality of subcarrier intervals for symbols of the downlink control channel within the monitoring window.

[0216] Aspect 8: The method according to any one of Aspects 6 to 7, the method further comprising: sending to the network entity a UE capability report indicating a minimum latency duration supported by the UE, wherein the number of threshold symbols is at least partially based on the UE capability report.

[0217] Aspect 9: The method according to any one of Aspects 6 to 8, wherein the number of threshold symbols is at least in part based on whether the configuration for the cell-based discontinuous operation mode indicates an active or deactivated state, whether the configuration for the cell-based discontinuous operation mode configures one or more of DRX mode or DTX mode, or both.

[0218] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the at least one instance of the GC DCI message includes a one-bit indication of activation or deactivation of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode includes a jointly configured DRX mode and DTX mode.

[0219] Aspect 11: The method according to any one of Aspects 1 to 9, wherein the at least one instance of the GC DCI message includes a two-bit indication of activation or deactivation of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode includes separately configured DRX mode and DTX mode, wherein the first bit of the two-bit indication corresponds to the DRX mode and the second bit of the two-bit indication corresponds to the DTX mode.

[0220] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the at least one instance of the GC DCI message includes an indication of an activation or deactivation state for the cell-based discontinuous operation mode for a set of serving cells configured by the network entity, and the activation or deactivation state is applied to the cell-based discontinuous operation mode for each serving cell in the set of serving cells.

[0221] Aspect 13: The method according to aspect 12, the method further comprising: monitoring at least one instance of the GC DCI message in a primary serving cell associated with the UE or in a special serving cell associated with the UE or both, wherein the at least one instance of receiving the GC DCI message is based at least in part on the monitoring.

[0222] Aspect 14: The method according to any one of aspects 1 to 13, wherein each instance of the one or more instances of the GC DCI message within the monitoring window includes the same DCI message.

[0223] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the cell-based discontinuous operation mode is a cell DRX mode, a cell DTX mode, or both.

[0224] Aspect 16: A method for wireless communication at a network entity, the method comprising: transmitting control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is configured to transmit one or more instances of a GC DCI message to one or more UEs; within the monitoring window, transmitting at least one instance of the GC DCI message according to the control information, the at least one instance of the GC DCI message including a configuration for a cell-based discontinuous operation mode; and communicating with at least one of the one or more UEs according to the configuration for the cell-based discontinuous operation mode.

[0225] Aspect 17: The method according to aspect 16, wherein the control information indicates the duration of the periodic interval, the start offset of the periodic interval relative to the radio frame boundary, or both.

[0226] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the control information indicates the duration of the monitoring window, one or more control channel monitoring timings within the monitoring window for receiving the at least one instance of the GC DCI message, the starting offset of the monitoring window relative to a first symbol of the periodic interval, or any combination thereof.

[0227] Aspect 19: The method according to any one of Aspects 16 to 18, wherein the control information indicates the delay duration between the last symbol of the downlink control channel transmitted within the monitoring window and the first time slot of the second periodic interval following the periodic interval, and the instance of the GC DCI message is transmitted via the downlink control channel.

[0228] Aspect 20: According to the method of aspect 19, wherein the delay duration is greater than or equal to a threshold number of symbols, the threshold number of symbols corresponding to a subcarrier interval among a plurality of subcarrier intervals for symbols of the downlink control channel within the monitoring window.

[0229] Aspect 21: The method according to any one of Aspects 19 to 20, the method further comprising: receiving from the at least one UE a report indicating one or more UE capability reports supported by each of the at least one UEs for a corresponding minimum delay duration, wherein the delay duration is greater than or equal to the number of symbols associated with the maximum delay duration among the corresponding minimum delay durations.

[0230] Aspect 22: The method according to any one of Aspects 19 to 21, wherein the delay duration is greater than or equal to a threshold number of symbols, the threshold number of symbols being at least in part based on whether the configuration for the cell-based discontinuous operation mode indicates an active or deactivated state, whether the configuration for the cell-based discontinuous operation mode configures one or more, or both, of DRX mode or DTX mode.

[0231] Aspect 23: The method according to any one of Aspects 16 to 22, wherein the at least one instance of the GC DCI message includes a one-bit indication of the active or deactivated state of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode includes a jointly configured DRX mode and DTX mode, or a two-bit indication of the active or deactivated state of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode includes the individually configured DRX mode and DTX mode.

[0232] Aspect 24: The method according to any one of Aspects 16 to 23, wherein the at least one instance of the GC DCI message includes an indication of an activation or deactivation state for the cell-based discontinuous operation mode for a set of serving cells configured by the network entity, and the activation or deactivation state is applied to the cell-based discontinuous operation mode for each serving cell in the set of serving cells.

[0233] Aspect 25: The method according to any one of Aspects 16 to 24, wherein the at least one instance of transmitting the GC DCI message comprises: a first instance of transmitting the GC DCI message via a first transmit beam during beam sweep; and a second instance of transmitting the GC DCI message via a second transmit beam different from the first transmit beam during the beam sweep.

[0234] Aspect 26: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the UE performs a method according to any one of aspects 1 to 15.

[0235] Aspect 27: A UE for wireless communication, the UE comprising: at least one component for performing a method according to any one of aspects 1 to 15.

[0236] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 15.

[0237] Aspect 29: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code, so that the network entity performs a method according to any one of aspects 16 to 25.

[0238] Aspect 30: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 16 to 25.

[0239] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform a method according to any one of aspects 16 to 25.

[0240] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0241] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0242] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0243] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0244] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0245] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0246] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0247] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0248] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, obtaining, selecting, choosing, building, and other similar actions.

[0249] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0250] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0251] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and capable of operating, alone or in combination, to execute the code to cause the UE to: receive control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is for receiving one or more instances of a group common downlink control information message; within the monitoring window, receive at least one instance of the group common downlink control information message in accordance with the control information, the at least one instance of the group common downlink control information message including a configuration for a cell-based discontinuous operation mode; and communicate with a network entity in accordance with the configuration for the cell-based discontinuous operation mode.

2. The UE of claim 1, wherein the control information indicates a duration of the periodic interval, a starting offset of the periodic interval relative to a radio frame boundary, or both.

3. The UE of claim 1, wherein the control information indicates a duration of the monitoring window, one or more control channel monitoring occasions within the monitoring window for receiving the at least one instance of the group common downlink control information message, a starting offset of the monitoring window relative to a first symbol of the periodic interval, or any combination thereof. To receive the at least one instance of the group common downlink control information message, the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the UE to:

4. The UE of claim 3, wherein, receive the at least one instance of the group common downlink control information message during a first monitoring occasion of the one or more monitoring occasions within the monitoring window; and avoid monitoring at least one other monitoring occasion of the one or more monitoring occasions that occurs after the first monitoring occasion within the monitoring window based at least in part on the reception of the at least one instance of the group common downlink control information message during the first monitoring occasion.

5. The UE of claim 1, wherein: the control information indicates a delay duration between a last symbol of a downlink control channel received within the monitoring window and a first slot of a second periodic interval after the periodic interval, and an instance of the group common downlink control information message is received via the downlink control channel.

6. The UE of claim 5, wherein the delay duration is greater than or equal to a threshold number of symbols.

7. The UE of claim 6, wherein the threshold number of symbols is a set number of symbols corresponding to a subcarrier spacing of a plurality of subcarrier spacings for symbols of the downlink control channel within the monitoring window.

8. The UE of claim 6, wherein the one or more processors are further capable of operating, alone or in combination, to execute the code to cause the UE to: ​ ​ transmitting, to the network entity, a UE capability report indicating a minimum latency duration supported by the UE, wherein the threshold number of symbols is based at least in part on the UE capability report.

9. The UE of claim 6, wherein the threshold number of symbols is based at least in part on one or more of the configuration for the cell-based discontinuous operation mode indicating an active state or a deactivated state, the configuration for the cell-based discontinuous operation mode configuring a discontinuous reception mode or a discontinuous transmission mode, or both.

10. The UE of claim 1, wherein the at least one instance of the group common downlink control information message comprises a one-bit indication of activation or deactivation of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode comprises a jointly configured discontinuous reception mode and a discontinuous transmission mode.

11. The UE of claim 1, wherein the at least one instance of the group common downlink control information message comprises a two-bit indication of activation or deactivation of the cell-based discontinuous operation mode when the cell-based discontinuous operation mode comprises separately configured discontinuous reception mode and discontinuous transmission mode, and a first bit of the two-bit indication corresponds to the discontinuous reception mode and a second bit of the two-bit indication corresponds to the discontinuous transmission mode.

12. The UE of claim 1, wherein the at least one instance of the group common downlink control information message comprises an indication of an active state or a deactivated state of the cell-based discontinuous operation mode for a set of serving cells configured by the network entity, and the active state or the deactivated state applies to the cell-based discontinuous operation mode for each serving cell in the set of serving cells.

13. The UE of claim 12, wherein the one or more processors are further capable of individually or collectively operating to execute the code to cause the UE to: monitor for the at least one instance of the group common downlink control information message in a primary serving cell associated with the UE or in a special serving cell associated with the UE or both, wherein receiving the at least one instance of the group common downlink control information message is based at least in part on the monitoring.

14. The UE of claim 1, wherein each instance of the one or more instances of the group common downlink control information message within the monitoring window comprises a same downlink control information message.

15. The UE of claim 1, wherein the cell-based discontinuous operation mode is a cell discontinuous reception mode, a cell discontinuous transmission mode, or both.

16. A method for wireless communication at a user equipment (UE), the method comprising: receiving control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is for receiving one or more instances of a group common downlink control information message; within the monitoring window, at least one instance of the group common downlink control information message includes a configuration for a cell-based discontinuous operation mode; and communicating with a network entity in accordance with the configuration for the cell-based discontinuous operation mode.

17. The method of claim 16, wherein the control information indicates a duration of the periodic interval, a starting offset of the periodic interval relative to a radio frame boundary, or both.

18. The method of claim 16, wherein the control information indicates a duration of the monitoring window, one or more control channel monitoring occasions within the monitoring window for receiving the at least one instance of the group common downlink control information message, a starting offset of the monitoring window relative to a first symbol of the periodic interval, or any combination thereof.

19. The method of claim 16, wherein receiving the at least one instance of the group common downlink control information message comprises: receiving the at least one instance of the group common downlink control information message during a first monitoring occasion of one or more monitoring occasions within the monitoring window; and avoiding monitoring at least one other monitoring occasion of the one or more monitoring occasions that occurs after the first monitoring occasion within the monitoring window based at least in part on the reception of the at least one instance of the group common downlink control information message during the first monitoring occasion.

20. A user equipment (UE), the user equipment (UE) comprising: means for receiving control information indicating a periodic interval and a monitoring window within the periodic interval, wherein the monitoring window is for receiving one or more instances of a group common downlink control information message; means for receiving, within the monitoring window, at least one instance of the group common downlink control information message in accordance with the control information, the at least one instance of the group common downlink control information message including a configuration for a cell-based discontinuous operation mode; and means for communicating with a network entity in accordance with the configuration for the cell-based discontinuous operation mode.

Images