Messages for discontinuous reception or discontinuous transmission by network entities

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a first network entity can transmit a first message to a neighboring second network entity, where the first message indicates one or more of discontinuous reception (DRX) timing of the first network entity or discontinuous transmission (DTX) timing of the first network entity. The first network entity can initiate at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing. The second network entity can adjust communication scheduling or measurement configuration. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 377,591, filed on September 29, 2022, entitled “MESSAGE FOR NETWORK ENTITY DISCONTINUOUS RECEPTION OR DISCONTINUOUS TRANSMISSION,” and U.S. Non-Provisional Patent Application No. 18 / 343,261, filed on June 28, 2023, entitled “MESSAGE FOR NETWORK ENTITY DISCONTINUOUS RECEPTION OR DISCONTINUOUS TRANSMISSION,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for discontinuous reception or discontinuous transmission messaging by a network entity. Background Art

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

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a first network entity. The method may include sending a first message to a second network entity, wherein the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity. The method may include initiating at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

[0008] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a second network entity. The method may include receiving a first message from a first network entity, the first message indicating one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The method may include adjusting one or more of a communication schedule or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

[0009] Some aspects described herein relate to an apparatus for a first network entity for wireless communication. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to cause the first network entity to send a first message to a second network entity, wherein the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The one or more processors may be configured individually or collectively to cause the first network entity to start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

[0010] Some aspects described herein relate to an apparatus for a second network entity for wireless communication. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to cause the second network entity to receive a first message from a first network entity, the first message indicating one or more of the DRX timing of the first network entity or the DTX timing of the first network entity. The one or more processors may be configured individually or collectively to cause the second network entity to adjust one or more of the communication scheduling or measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a first network entity. The instruction set, when executed by one or more processors of the first network entity, may cause the first network entity to send a first message to a second network entity, wherein the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The instruction set, when executed by one or more processors of the first network entity, may cause the first network entity to start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a second network entity. The instruction set, when executed by one or more processors of the second network entity, may cause the second network entity to receive a first message from a first network entity, the first message indicating one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The instruction set, when executed by one or more processors of the second network entity, may cause the second network entity to adjust one or more of a communication schedule or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a first message to another apparatus, wherein the first message indicates one or more of a DRX timing of the apparatus or a DTX timing of the apparatus. The apparatus may include means for initiating at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a first message from another apparatus, the first message indicating one or more of DRX timing of the other apparatus or DTX timing of the other apparatus. The apparatus may include means for adjusting one or more of communication scheduling or measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

[0015] Aspects collectively include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a network entity (eg, a base station) and a UE in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of a decomposed base station according to the present disclosure.

[0022] Figure 4 2 is a diagram illustrating an example of downlink semi-persistent scheduling communication and an example of uplink configuration grant communication according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of using a transmission inactivity period according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of transmitting an inactivity period according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of a downlink control information format according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example of a network entity that may enter a transmit-inactive state according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example of a message indicating discontinuous reception timing or discontinuous transmission timing according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0030] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0031] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

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

[0033] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technologies (RATs), various aspects of the present disclosure may be applicable to other RATs, such as 3G RATs, 4G RATs, and / or post-5G RATs (e.g., 6G).

[0034] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, an entity B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0035] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0036] In some examples, the cell may not necessarily be fixed, and the geographic area of ​​the cell may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network entities in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0037] In some aspects, the term "base station" (e.g., base station 110) or "network entity" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station" or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network entity" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with base station 110). In some aspects, the term "base station" or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network entity" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network entity" may refer to one of the base station functions but not another. In this way, a single device may include more than one base station.

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

[0039] The wireless network 100 may be a heterogeneous network having network entities including different types of BSs, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0040] The network controller 130 may be coupled to or in communication with a set of network entities and may provide coordination and control for the network entities. The network controller 130 may communicate with the base station 110 via a backhaul communication link. The network entities may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link.

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

[0042] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a network entity, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0045] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0047] With the above examples in mind, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and that the techniques described herein are applicable to those modified frequency ranges.

[0048] In some aspects, a first network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a first message to a second network entity, wherein the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity. The communication manager 150 may initiate at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

[0049] In some aspects, the second network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a first message from a first network entity indicating one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The communication manager 150 may adjust one or more of a communication schedule or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0050] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0051] Figure 2 2 is a diagram illustrating an example 200 of a network entity (e.g., base station 110) communicating with UE 120 in a wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0052] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a set of corresponding antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0053] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0054] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with network entities via the communication unit 294.

[0055] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or antennas coupled to one or more transmit and / or receive components (such as antennas). Figure 2 One or more antenna elements of one or more components).

[0056] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to a network entity. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 4 to 12 )Aspects of any of the methods described herein.

[0057] At a network entity (e.g., base station 110), uplink signals from UE 120 and / or other UEs may be received by antenna 234, processed by modem 232 (e.g., a demodulator component of modem 232 shown as DEMOD), detected by MIMO detector 236 (where applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240. The network entity may include a communication unit 244 and may communicate with network controller 130 via communication unit 244. The network entity may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the network entity may include a modulator and a demodulator. In some examples, the network entity includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to Figures 4 to 12 )Aspects of any of the methods described herein.

[0058] A controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of a network entity and / or UE 120 (e.g., directly executed, or executed after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or the network entity to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0059] In some aspects, the first network entity (e.g., base station 110) includes a component for sending a first message to a second network entity, wherein the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity; and / or a component for starting at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing. In some aspects, the components for the first network entity to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0060] In some aspects, the second network entity (e.g., base station 110) includes a component for receiving a first message from the first network entity, the first message indicating one or more of the DRX timing of the first network entity or the DTX timing of the first network entity; and / or a component for adjusting one or more of the communication scheduling or measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

[0061] In some aspects, a single processor may perform all of the functions described as being performed by the one or more processors. In some aspects, the one or more processors may perform a set of functions together. For example, a first set of (one or more) of the one or more processors may perform a first function described as being performed by the one or more processors, and a second set of (one or more) of the one or more processors may perform a second function described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. References to "one or more processors" should be understood to refer to the combination Figure 2 Any one or more of the processors described. References to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as in conjunction with Figure 2 For example, functions described as being performed by one or more memories may be performed by the same subset of the one or more memories or by a different subset of the one or more memories.

[0062] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0063] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0064] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0065] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a node B, an evolved NB (eNB), an NR BS, a 5GNB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0066] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0067] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0068] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with a core network 320 through one or more decomposed base station units, such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of the following: a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0069] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) configured to receive signals or send signals to one or more of the other units or both via a wireless transmission medium.

[0070] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0071] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as that defined by 3GPP. In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0072] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0073] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0074] The non-RT RIC 315 may be configured to include logic functions that implement non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0075] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0076] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0077] Figure 4 400 and 410 of downlink semi-persistent scheduling (SPS) communications and uplink configuration grant (CG) communications according to the present disclosure. SPS communications may include periodic downlink communications configured for a UE so that a network entity does not need to send a separate downlink control information (DCI) (e.g., directly or via one or more network entities) to schedule each downlink communication, thereby saving signaling overhead. CG communications may include periodic uplink communications configured for a UE so that a network entity does not need to send a separate DCI (e.g., directly or via one or more network entities) to schedule each uplink communication, thereby saving signaling overhead.

[0078] As shown in example 400, a UE may be configured with an SPS configuration for SPS communication. For example, the UE may receive the SPS configuration via an RRC message sent by a network entity (e.g., directly to the UE or via one or more network entities). The SPS configuration may indicate resource allocations associated with SPS downlink communications (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations are repeated, such that scheduled SPS opportunities 405 for the UE occur periodically. The SPS configuration may also configure a hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback resource for the UE to send HARQ-ACK feedback for SPS physical downlink shared channel (PDSCH) communications received in the SPS opportunity 405.

[0079] The network entity may send an SPS activation DCI to the UE (e.g., directly or via one or more network entities) to activate the SPS configuration for the UE. The network entity may indicate communication parameters, such as MCS, resource block (RB) allocations, and / or antenna ports, in the SPS activation DCI for SPS PDSCH communications to be sent in the scheduled SPS opportunity 405. The UE may begin monitoring the SPS opportunity 405 based at least in part on receiving the SPS activation DCI. The UE may avoid monitoring the configured SPS opportunity 405 before receiving the SPS activation DCI. The network entity may send an SPS reactivation DCI to the UE (e.g., directly or via one or more network entities) to change the communication parameters for the SPS PDSCH communications.

[0080] In some cases, such as when there is no downlink traffic to be sent to the UE, the network entity may send an SPS elimination DCI to the UE (e.g., directly or via one or more network entities) to temporarily eliminate or deactivate one or more subsequent SPS opportunities 405 for the UE. The SPS elimination DCI may only deactivate a subsequent SPS opportunity 405 or subsequent N SPS opportunities 405 (where N is an integer). The SPS opportunity 405 after one or more (e.g., N) SPS opportunities 405 after the SPS elimination DCI may remain activated. Based at least in part on receiving the SPS elimination DCI, the UE may avoid monitoring one or more (e.g., N) SPS opportunities 405 after receiving the SPS elimination DCI. The network entity may send an SPS release DCI to the UE (e.g., directly or via one or more network entities) to deactivate the SPS configuration for the UE. The UE may stop monitoring the scheduled SPS opportunity 405 based at least in part on receiving the SPS release DCI.

[0081] As shown in example 410, the UE may be configured with a CG configuration for CG communication. For example, the UE may receive the CG configuration via an RRC message sent by a network entity (e.g., directly to the UE or via one or more network entities). The CG configuration may indicate resource allocations associated with CG uplink communications (e.g., in the time domain, frequency domain, spatial domain, and / or code domain) and the periodicity with which the resource allocations are repeated, such that scheduled CG opportunities 415 for the UE occur periodically. In some examples, the CG configuration may identify a resource pool or multiple resource pools available to the UE for uplink transmissions. The CG configuration may configure contention-free CG communication (e.g., where resources are dedicated to the UE for transmitting uplink communications) or contention-based CG communication (e.g., where the UE contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).

[0082] The network entity may send a CG activation DCI to the UE (e.g., directly or via one or more network entities) to activate the CG configuration for the UE. The network entity may indicate communication parameters such as MCS, RB allocation and / or antenna port in the CG activation DCI for CG physical uplink shared channel (PUSCH) communications to be sent in the scheduled CG opportunity 415. The UE may start transmitting in the CG opportunity 415 based at least in part on receiving the CG activation DCI.

[0083] The network entity may send a CG reactivation DCI to the UE (e.g., directly or via one or more network entities) to change the communication parameters used for CG PUSCH communication. Based at least in part on receiving the CG reactivation DCI, the UE may begin transmitting in the scheduled CG occasions 415 using the communication parameters indicated in the CG reactivation DCI. In some cases, such as when the network entity is expected to override the scheduled CG communication for higher priority communication, the network entity may send a CG cancellation DCI to the UE (e.g., directly or via one or more network entities) to temporarily cancel or deactivate one or more subsequent CG occasions 415 for the UE. The network entity may send a CG release DCI to the UE (e.g., directly or via one or more network entities) to deactivate the CG configuration for the UE. The UE may stop transmitting in the scheduled CG occasions 415 based at least in part on receiving the CG release DCI.

[0084] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0085] Figure 5 is a diagram illustrating an example 500 of using a transmission inactivity period according to the present disclosure. Example 500 shows a network entity 510 (eg, base station 110) and a UE 520 (eg, UE 120) that can communicate with each other via a wireless network (eg, wireless network 100).

[0086] Energy costs account for a large percentage of the operating costs of a network. Therefore, networks are designed to be more energy efficient and environmentally responsible. These designs may include the use of sleep states by the network entity 510, where the network entity 510 sometimes powers down radio components or other components (partially or completely) to reduce energy consumption.

[0087] In some aspects, the network entity 510 may indicate a transmit inactivity period that allows the network entity 510 and / or the UE 520 more opportunities to enter a sleep state and thus consume less energy compared to the current network configuration. The network entity 510 may indicate the transmit inactivity period to the UE. Thus, the network entity 510 and the UE 520 served by the network entity 510 may have more opportunities to sleep and reduce power consumption.

[0088] In some implementations, the transmit inactivity period may be indicated as a pattern (e.g., a pattern of inactive BS TX inactivity state relative to an active state), and the pattern may be a dynamic pattern or a periodic pattern. The network entity 510 may indicate the dynamic pattern via RRC messages and / or layer 1 (L1) signaling (e.g., DCI, MAC control element (MAC CE)). For example, the network entity 510 may use RRC signaling to configure the UE 520 with the option of sending a group common DCI in a cell to indicate a "BS TX inactivity" state. The group common DCI may trigger the start and duration of the "BS TX inactivity" state. The UE may then suspend monitoring of physical downlink control channel (PDCCH) communications and suspend measuring periodic or semi-persistent channel state information reference signals (CSI-RS) (if configured) during the "BS TX inactivity" state (or pattern). The time duration during which the network entity 510 is in the BS TX inactivity state may be referred to as a network "transmit inactivity period". The transmission inactivity period may be a period between active states or a period when the network entity 510 is powered down below a threshold power level. Example 500 shows a transmission inactivity period 522.

[0089] In some aspects, the network entity 510 may define, trigger and / or configure one or more transmission inactivity periods for the BS TX inactivity state without affecting downlink traffic performance. However, before initiating (and indicating) the transmission inactivity period, the network entity 510 may check whether one or more conditions are met. If the conditions are met, the network entity 510 may generate an indication of the transmission inactivity period, as shown by reference numeral 525. For example, the network entity 510 may generate an indication if the following conditions are met: there is no downlink traffic (in the cell or in a neighboring cell) with a latency requirement smaller than the period (time duration) of the transmission inactivity period, and there is no periodic downlink traffic (e.g., SPS traffic) with a period shorter than the period of the transmission inactivity period. In other words, the network entity 510 may check that there is no low-latency downlink traffic to be sent. If such downlink traffic exists, the network entity may not initiate or indicate a transmission inactivity period.

[0090] Although the network entity 510 may check the downlink traffic, the network entity may also check the uplink traffic due to the downlink traffic associated with the scheduled uplink traffic. For example, the network entity 510 may generate an indication (and initiate the BS TX inactive state) if the following conditions are met: there is no uplink traffic with a latency requirement smaller than the period of the transmission inactivity period, no uplink traffic is dynamically scheduled (via DCI), and retransmission is allowed (via DCI) (in the current cell or in a neighboring cell). The network entity 510 may generate an indication if the condition that there is no periodic uplink traffic (e.g., CG) with a period shorter than the period of the transmission inactivity period and retransmission is configured is met. If such uplink traffic exists, the network entity may not initiate or indicate the transmission inactivity period. It should be noted that the network entity 510 may ensure that the synchronization signal block (SSB) is not skipped if certain types of UEs (e.g., UEs using features specified by 3GPP Release 17) are present, and the radio access channel (RACH) opportunity (RO) is not skipped. The network entity 510 may be aware of the above situation by using Release 17 signaling procedures (eg, RRC signaling, DCI, MAC CE).

[0091] If the above conditions for downlink traffic and uplink traffic are met, the network entity 510 may generate an indication of a transmit inactive period. During the transmit inactive period, the network entity 510 may also adjust the transmit power of the network entity 510. This may include, for example, reducing the power used by the network entity 510 for transmission during the transmit inactive period. The reduction in power used for transmission may be part of entering an inactive state or a sleep state. In contrast, an active state or awake state may include a state of processing (e.g., decoding and / or demodulating) downlink signals, uplink signals, and / or channels. The amount of power consumed by the network entity 510 during the awake state may be scaled (increased or decreased) based at least in part on the number of component carriers (CCs), resource utilization, the number of antenna ports, the number of spatial layers, and / or the number of antenna elements.

[0092] Example 500 also illustrates how the network entity 510 can ramp down power from an active state to a sleep state and ramp up power back to an active state. As the time between active states increases, more components can be turned off (power cuts) to save more power, including radio components for transmission and / or reception (radio components). For example, the network entity 510 can turn off the radio frequency (RF) portion and / or the broadband portion of the transmission chain so that the network entity 510 will not send any communications. Switching between a transmission (downlink) active state (transmitting) and a transmission inactive state (not transmitting) can be an operation of a DTX mode, also referred to as a "BS in DTX mode". The transmission active state of the network entity 510 can be referred to as a "BS transmit active" state, and the inactive transmission state of the network entity 510 can be referred to as a "BS TX inactive" state. During the inactive transmission state, there is no downlink transmission and the network entity 510 can enter a sleep state. During the active transmission state, downlink transmission is possible and the network entity 510 cannot enter a sleep state.

[0093] The network entity 510 may reduce the power by a variable amount. For example, the sleep state may include different sleep levels, such as microsleep, shallow sleep, or deep sleep. Compared to the active state, microsleep may cause the network entity 510 to use a reduced amount of power for the radio component. This power reduction may be much less than the power reduction of deep sleep (e.g., the power reduction of deep sleep may be 15 times the power reduction of microsleep). However, microsleep may have very little transition time (e.g., less than 1 millisecond (ms)) and may use very little transition energy. Shallow sleep may be a sleep level between microsleep and deep sleep, with, for example, a power reduction of half the power reduction of deep sleep. Shallow sleep may have a slower transition time than microsleep (e.g., 6ms), but may still be faster than deep sleep. Shallow sleep may cause the network entity 510 to use additional transition energy (relative power vs.ms), which may be about 20 times the transition energy of microsleep. Deep sleep may have the longest sleep period and / or the maximum energy reduction. Deep sleep may also have the longest transition time (eg, 20 ms) and cause the network entity 510 to use the largest amount of energy to transition (eg, approximately 100 times the transition energy of micro sleep).

[0094] As indicated by reference numeral 530, the network entity 510 may send an indication. The indication may specify a periodic BSDTX pattern with "BS Tx active" and "BS Tx inactive" durations, or a dynamic BSDTX pattern where the "BS Tx inactive" period is dynamically triggered by the network entity 510.

[0095] As shown at reference numeral 535, the network entity 510 may adjust the power used for transmission (e.g., reduce the power, set a new power) based at least in part on the indication. This may include adjusting the power to be at a reduced level during the transmission inactivity period. For example, as shown at reference numeral 540, the UE 520 may adjust the power used for reception during the transmission inactivity period. During the transmission inactivity period of the network entity 510, the UE 520 may use the indication of the transmission inactivity period to reduce the power to the receiving radio component (e.g., enter a sleep state), or perform other operations that do not involve the network entity 510. During the transmission inactivity period, the UE 520 may suspend (avoid) actions such as PDCCH monitoring (shown by reference numeral 545) and / or CSI-RS measurement (shown by reference numeral 550). This is because during the transmission inactivity period, the network entity 510 cannot send PDCCH communication, periodic CSI-RS, and semi-persistent CSI-RS. In this way, the network entity 510 can reduce power consumption. The UE 520 may also reduce power consumption and conserve battery power.

[0096] If the UE 520 exits the transmission inactivity period, the UE 520 may remain in an active state (e.g., awake) for the duration of the inactivity timer (e.g., this may extend the activity time). The UE 120 may start the inactivity timer at the time when the PDCCH communication is received (e.g., in the transmission time interval in which the PDCCH communication is received, such as a time slot or a subframe). The UE 520 may remain in an active state until the inactivity timer expires, at which time the UE 520 may enter a sleep state (e.g., for the duration of the inactivity timer). During the duration of the inactivity timer, the UE 520 may continue to monitor the PDCCH communication, may obtain downlink data communication scheduled by the PDCCH communication (e.g., on a downlink data channel such as PDSCH), and / or may prepare and / or send uplink communication scheduled by the PDCCH communication (e.g., on PUSCH). The UE 520 may restart the inactivity timer each time a PDCCH communication of the UE 520 is detected for initial transmission (e.g., but not for retransmission).

[0097] In some aspects, the network entity 510 may utilize inactive reception time or "BS in DRX mode", where DRX is discontinuous reception. The reception inactivity state of the network entity 510 may be referred to as a "BS Rx Inactive" state or a reception inactivity period. During the reception inactivity period, the network entity 510 may put the radio receiver component or other components into a sleep state (e.g., micro-sleep, light sleep, deep sleep).

[0098] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0099] Figure 6 are diagrams illustrating examples 600 and 602 of transmitting an inactivity period according to the present disclosure.

[0100] Example 600 shows a periodic DTX pattern of inactive transmission states (BS TX inactive), each of which has a transmission inactivity period. The network entity 510 may send an indication of the transmission inactivity period using, for example, RRC signaling. This may include via system information (SI) or via dedicated RRC signaling.

[0101] Example 602 illustrates a dynamically triggered transmit inactivity state, where the triggering DCI indicates the timing of one or more transmit inactivity states. This may include a combination of RRC signaling and L1 signaling. As part of the DTX mode, the RRC layer configuration may configure an option with a transmit inactivity period and a list of N transmit inactivity periods with associated parameters (e.g., starting slot offset, duration). RRC signaling may include information about a periodic DTX mode or DTX configuration in an information element (IE) in a system information block (SIB). The DCI may trigger one of the N RRC configured transmit inactivity periods. In the case of signaling via the SIB, paging of the UE is expected and only after a paging cycle, an update of the DTX mode is possible. The minimum value of the paging cycle may be 32 radio frames.

[0102] For both periodic DTX mode and dynamic DTX mode, the start of a transmit inactivity period means that the UE does not monitor PDCCH communications and does not perform (all types of) CSI-RS measurements. In some aspects, the set or list of configured transmit inactivity periods may be reconfigured. In some aspects, the network entity 510 may switch from periodic DTX mode to dynamic DTX mode. DRX may follow a similar pattern.

[0103] As indicated above, Figure 6 Some examples are provided. Other examples can be found in Figure 6 The examples described are different.

[0104] Figure 7 are diagrams illustrating examples 700 and 702 of DCI formats according to the present disclosure.

[0105] Example 700 illustrates DCI format 2_0 for signaling a transmit inactivity period. The DCI format may include a DCI identifier (ID) and a slot format indicator (SFI) (if configured). The DCI may also include a BS TX inactivity trigger. The BS TX inactivity trigger may indicate one of a plurality of preconfigured DTX modes, which may include a starting slot offset (e.g., a starting slot or subslot from a current slot) and / or a duration (e.g., a number of slots or subslots).

[0106] Example 702 shows a DCI format 2_0 that can be scrambled by an SFI radio network temporary identifier (RNTI). This can include up to 128 bits. The DCI may include information for SFI, RB, channel occupancy time (COT), and search space set group (if configured). The DCI may also include a BS TX inactivity trigger. The BS TX inactivity trigger may indicate a starting slot offset and / or duration. By triggering the transmit inactivity state, the network entity 510 may increase the chance of entering a sleep state and reduce power consumption.

[0107] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0108] Figure 88 is a diagram illustrating an example 800 of a network entity that may enter a transmit inactive state according to the present disclosure. A first network entity 810 (e.g., base station 110) and a second network entity 815 (e.g., base station 110) may transmit multiple beams to multiple UEs. Each beam may be associated with a transmit configuration indicator (TCI) state. The network entity 810 may determine to enter a transmit inactive state during two downlink time slots of a configured time slot pattern. The network entity 815 may be scheduled to receive uplink communications during these time slots and other time slots. In anticipation of interference from communications involving the network entity 810, the UE served by the network entity 815 may be scheduled to transmit at a higher transmit power during these time slots. However, the network entity 810 is entering a DTX mode and a DRX mode during these time slots. The network entity 815 is unaware of the upcoming DTX mode and DRX mode of the network entity 810. Therefore, when no other communications with the network entity 810 are scheduled, the UE communicating with the network entity 815 may consume more energy than required when transmitting at a higher transmit power. In addition, communications involving network entity 810 may interfere with communications involving network entity 815 in other time slots. Such interference may degrade communications and waste processing and signaling resources. Network entity 810 may send a deactivation message when deactivating, but the deactivation message is too rare for network entity 815 to effectively save energy. The Xn message payload may also be large, and if a deactivation message is sent for each switch to the transmit inactive state, the frequent switching may consume a large amount of signaling resources.

[0109] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0110] Fig. 9 9 is a diagram illustrating an example 900 of a message indicating DRX timing or DTX timing according to the present disclosure. Example 900 shows a network entity 910 (e.g., base station 110) and a UE 920 (e.g., UE 120) that can communicate with each other via a wireless network (e.g., wireless network 100). Network entity 910 may be a serving cell. Network entity 910 may also communicate with network entity 930 via an Xn Application Protocol (XnAP) interface. Network entity 930 may be a neighboring network entity of network entity 910. For example, some UEs served by network entity 910 may also be served by network entity 930, or interfere with UEs served by network entity 930.

[0111] According to various aspects described herein, network entity 910 may send a first message to network entity 930, as indicated by reference numeral 935. The first message may indicate a DRX timing of a DRX mode or a DTX timing of a DTX mode of network entity 910. The DRX timing may indicate a pattern (e.g., periodicity) for the DRX mode, such as when the network entity 930 is in a receive inactive state during a receive inactive period of the DRX mode, and when the network entity 930 is in a receive active state (on duration) during a receive active period of the DRX mode. The pattern or periodicity may include an interval of an active period between inactive periods, or a length of a cycle. The DTX timing may indicate a pattern (e.g., periodicity) for the DRX mode, such as when the network entity 930 is in a transmit inactive state (on duration) during a transmit inactive period of the DTX mode, and when the network entity 930 is in a transmit active state during a transmit active period of the DTX mode. The first message may be a modification of an existing information element (IE) for the served cell sent by the network entity 910, or a message dedicated to indicating DRX timing or DTX timing. The first message may indicate a semi-persistent mode for DTX, a dynamic mode for DTX, a semi-persistent mode for DRX, and / or a dynamic mode for DRX. Semi-persistent may include semi-static or periodic. The network entity 910 may send the first message via RRC or L1 signaling.

[0112] In some aspects, DRX timing may include parameters such as a starting time slot for a DRX mode and an ending time slot for a DRX mode. DTX timing may include parameters such as a starting time slot for a DTX mode and an ending time slot for a DTX mode. These parameters may include a duration (e.g., number of time slots, milliseconds (ms)) for a DRX mode or a DTX mode. The duration may indicate an ending time slot. That is, given a starting time slot and a duration, an ending time slot may be determined (implicitly indicated). Parameters may also include a starting time slot offset for a cycle.

[0113] The pattern for DRX and / or the pattern for DTX can be periodic or follow a specified frequency or timing. Alternatively, the pattern can be dynamic (indicating a current pattern rather than a periodic pattern). An indication of a dynamic pattern can be sent when a network entity is triggered to send an inactivity state or a network entity receives an inactivity state, and if backhaul is available. If the pattern is dynamic, the starting timeslot (first timeslot) can be the current timeslot or a timeslot that has already occurred (e.g., a negative timeslot value). The starting timeslot can be retroactive, where one or more network entities send inactivity states and / or network entities receive inactivity states are reported (e.g., reportedSignaling support). The pattern can be between network entities (e.g., inter-gNB coordination) or within a split network entity (e.g., intra-gNB coordination, decomposed base station coordination).

[0114] In some aspects, the first message may indicate that the inactivity pattern or parameters (e.g., starting time slot, ending time slot, duration) for DRX are different from the inactivity pattern or parameters for DTX. Alternatively, in some aspects, the first message may indicate that the pattern or parameters for DRX are the same as the pattern or parameters for DTX. For example, if the first message includes a starting time slot, an ending time slot, and an indication that the DRX pattern and the DTX pattern are the same, then both the DTX pattern and the DRX pattern for the network entity 810 start at the starting time slot and end at the ending time slot.

[0115] As shown by reference numeral 940, the network entity 910 may initiate a DRX mode based on DRX timing and / or a DTX mode based on DTX timing. Using the DRX mode or the DTX mode may include reducing power to the radio component, such as in conjunction with Figure 5 The network entity 910 may communicate based at least in part on the DRX timing or the DTX timing. For example, the network entity 910 may send a communication before a start time slot for a DTX mode and refrain from sending until after an end time slot for the DTX mode. The network entity 910 may receive a communication before a start time slot for a DRX mode and refrain from receiving until after an end time slot for the DTX mode.

[0116] In some aspects, as shown by reference numeral 950, the network entity 930 may send a second message. The second message may be a response message in response to the first message. For example, the second message may indicate acceptance of DRX timing or DTX timing. The second message may be a reused message, such as an NG-RAN NODE CONFIGURATION UPDATE message. The second message may be adaptive in size. For example, when DRX or DTX information is to be provided, the second message may only send information related to the inactive state of the network entity (e.g., DRX mode, DTX mode). The network entity 910 may start the DRX mode and / or DTX mode at reference numeral 940 based at least in part on the second message indicating acceptance or confirmation of use of the DRX timing and / or DTX timing.

[0117] In some aspects, the network entity 910 may not start the DRX mode and / or the DTX mode based at least in part on the second message indicating that the DRX mode and the DTX mode are not accepted. If the second message indicates that the DRX mode and the DTX mode are not accepted, the network entity 910 may adjust the DRX timing of the DRX mode and / or the DTX timing of the DTX mode. If the second message indicates that the DRX mode and the DTX mode are not accepted, the network entity 910 may also continue the DRX timing of the DRX mode and / or the DTX timing of the DTX mode.

[0118] As indicated by reference numeral 945, the network entity 930 may adjust communication scheduling or measurement configuration for UEs served by the network entity 930 based at least in part on the DRX timing and / or the DTX timing. For example, during a transmit inactivity period of the DTX mode of the network entity 930 and / or a receive inactivity period of the DRX mode of the network entity 930, the network entity 930 may schedule (or more likely schedule or prioritize scheduling) UEs to transmit and / or receive. For example, when the network entity 910 is in a transmit inactivity state of the DTX mode, the network entity 930 may schedule data transmission and / or CSI-RS to UEs at the edge of the cell or to UEs that experience interference from neighboring network entities. The network entity 930 may schedule aperiodic CSI-RS (A-CSI-RS) to UEs in the cell during the transmit inactivity state and / or the receive inactivity state of the network entity 910. The network entity 930 may know that the A-CSI-RS measurement will be "cleaned" from interference from the network entity 910. The network entity 930 may not schedule (or may be less likely to schedule or de-prioritize scheduling) the UE to transmit and / or receive during the transmission activity period of the DTX mode of the network entity 930 and / or the reception activity period of the DRX mode of the network entity 930. If the first message includes retroactive DTX or DRX information, the network entity 930 may consider the DTX or DRX information when receiving a CSI report from a UE in a coverage cell of the network entity 930.

[0119] In some aspects, the network entity 930 may configure (as part of a measurement configuration) CSI interference measurement (CSI-IM) measurements for UEs served by the network entity 930 based at least in part on the transmit inactivity period of the DTX pattern of the network entity 910. The network entity 930 may be aware that during the transmit inactivity period of the DTX pattern of the network entity 910, the IM measurements are “free” from interference from the network entity 910.

[0120] In some aspects, network entity 930 may enter a DRX mode and / or a DTX mode based at least in part on a DRX mode and / or a DTX mode of network entity 910 so that there is less interference between communications of a UE served by network entity 910 and a UE served by network entity 930.

[0121] In addition to the network entity 910 saving energy when switching to the network entity inactive state, neighboring network entities (such as network entity 930) can save energy and avoid interference during the transmission active period of the DRX mode and / or the reception active period of the DTX mode of the network entity 910. By sharing the DRX timing and / or DTX timing, the network entity can better coordinate the communication and measurement with the neighboring network entity to improve the communication and reduce the collision and interference. Therefore, the network entity can save power and signaling resources.

[0122] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 The examples described are different.

[0123] Fig.10 1 is a diagram illustrating an example process 1000 performed, for example, by a first network entity according to the present disclosure. Example process 1000 is an example in which a first network entity (eg, base station 110, network entity 910) performs operations associated with messaging for network entity DTX or DRX.

[0124] like Fig.10 As shown, in some aspects, process 1000 may include sending a first message to a (neighboring) second network entity, wherein the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity (block 1010). For example, the first network entity (e.g., using Fig.12 The communication manager 1208 and / or the sending component 1204 depicted in the figure can send a first message to the second network entity, wherein the first message indicates one or more of the DRX timing of the first network entity or the DTX timing of the first network entity, as described above.

[0125] like Fig.10 As further shown, in some aspects, process 1000 may include initiating at least one of a DRX mode based on DRX timing or a DTX mode based on DTX timing (block 1020). Fig.12 The communication manager 1208 and / or the active component 1210 depicted in the figure can initiate at least one of a DRX mode according to DRX timing or a DTX mode according to DTX timing, as described above.

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

[0127] In a first aspect, process 1000 includes communicating based at least in part on DRX timing or DTX timing.

[0128] In a second aspect, alone or in combination with the first aspect, the first message indicates that the DRX timing and the DTX timing are the same, and indicates a start time slot and an end time slot for the DRX timing and the DTX timing.

[0129] In a third aspect, alone or in combination with one or more of the first and second aspects, the first message indicates one or more of: a start time slot and an end time slot for DRX timing, or a start time slot and an end time slot for DTX timing.

[0130] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first message is a node configuration update message.

[0131] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the first message is dedicated to a network entity sending or receiving activity.

[0132] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, process 1000 includes receiving a second message from a second network entity, the second message being associated with acceptance or non-acceptance of one or more of the DRX timing or DTX timing indicated in the first message.

[0133] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the second message is a node configuration update confirmation message.

[0134] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the second message is dedicated to providing a response associated with a sending or receiving activity of the network entity.

[0135] In the ninth aspect, alone or in combination with one or more aspects from the first to the eighth aspects, starting at least one of the DRX mode or the DTX mode includes: starting at least one of the DRX mode according to DRX timing or the DTX mode according to DTX timing based at least in part on a second message indicating acceptance of the DRX timing or the DTX timing.

[0136] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the first message indicates one or more of: a semi-persistent mode or a dynamic mode for DTX, or a semi-persistent mode or a dynamic mode for DRX.

[0137] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the first message indicates a first time slot for a dynamic mode of DTX, and the first time slot has occurred.

[0138] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the DRX timing includes the periodicity of the DRX pattern, or the DTX timing includes the periodicity of the DTX pattern.

[0139] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the first message indicates a DTX start offset of a DTX cycle or a DRX start offset of a DRX cycle.

[0140] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0141] Fig.11 1 is a diagram illustrating an example process 1100 performed, for example, by a second network entity according to the present disclosure. Example process 1100 is an example in which a second network entity (eg, base station 110, network entity 930) performs operations associated with messaging for network entity DTX or DRX.

[0142] like Fig.11 As shown, in some aspects, process 1100 may include receiving a first message from a first network entity, the first message indicating one or more of a DRX timing of the first network entity or a DTX timing of the first network entity (block 1110). For example, a second network entity (e.g., using Fig.12The communication manager 1208 and / or receiving component 1202 depicted in the figure may receive a first message from a first network entity, the first message indicating one or more of the DRX timing of the first network entity or the DTX timing of the first network entity, as described above.

[0143] like Fig.11 As further shown, in some aspects, process 1100 may include adjusting one or more of a communication schedule or a measurement configuration based at least in part on one or more of the DRX timing or the DTX timing (block 1120). Fig.12 The communication manager 1208 and / or adjustment component 1212 depicted in FIG. 1 may adjust one or more of the communication scheduling or measurement configurations based at least in part on one or more of the DRX timing or the DTX timing, as described above.

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

[0145] In a first aspect, the first message indicates that the DRX timing and the DTX timing are the same, and indicates a start time slot and an end time slot for the DRX timing and the DTX timing.

[0146] In a second aspect, alone or in combination with the first aspect, the first message indicates one or more of: a start time slot and an end time slot for DRX timing, or a start time slot and an end time slot for DTX timing.

[0147] In a third aspect, alone or in combination with one or more of the first and second aspects, the first message is a node configuration update message.

[0148] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first message is dedicated to a network entity sending or receiving activity.

[0149] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, process 1100 includes sending a second message to a first network entity, the second message being associated with acceptance or non-acceptance of one or more of the DRX timing or the DTX timing indicated in the first message.

[0150] In a sixth aspect, alone or in combination with one or more of aspects one to five, process 1100 includes performing one or more of the following based at least in part on a second message indicating acceptance of DRX timing or DTX timing: adjusting communication scheduling, starting DRX mode, starting DTX mode, or adjusting measurements.

[0151] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the second message is a node configuration update confirmation message.

[0152] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the second message is dedicated to providing a response associated with a sending or receiving activity of the network entity.

[0153] In a ninth aspect, either alone or in combination with one or more of aspects 1 to 8, the first message indicates one or more of: a semi-persistent mode or a dynamic mode for DTX, or a semi-persistent mode or a dynamic mode for DRX.

[0154] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the first message indicates a first time slot for a dynamic mode of DTX, and the first time slot has occurred.

[0155] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, adjusting one or more of the communication scheduling or measurement configurations includes: adjusting one or more of the communication scheduling or measurement configurations based at least in part on one or more of a DRX mode that occurs at least in part based on DRX timing or a DTX mode that occurs at least in part based on DTX timing.

[0156] although Fig.11 An example block diagram of process 1100 is shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0157] Fig.12is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a first network entity (e.g., base station 110, network entity 910) or a second network entity (e.g., a neighboring base station, base station 110, network entity 930). The first network entity and / or the second network entity may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 1208. Communication manager 1208 may control and / or otherwise manage one or more operations of receiving component 1202 and / or sending component 1204. In some aspects, communication manager 1208 may include a communication manager 1208 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network entities. The communications manager 1208 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1208 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1208 can include a receiving component 1202 and / or a sending component 1204. The communication manager 1208 can include an activity component 1210 and / or an adjustment component 1212, among others.

[0158] In some aspects, the apparatus 1200 may be configured to perform Figures 1 to 9 Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein, such as Fig.10 The process of 1000 Fig.11 In some aspects, the apparatus 1200 and / or Fig.12 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0159] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0160] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0161] In some aspects, if the apparatus 1200 is a first network entity, the sending component 1204 can send a first message to a second network entity, wherein the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The active component 1210 can initiate at least one of a DRX mode based on the DRX timing or a DTX mode based on the DTX timing.

[0162] Transmitting component 1204 and / or receiving component 1202 can communicate based at least in part on DRX timing or DTX timing. Receiving component 1202 can receive a second message from a second network entity associated with accepting or not accepting one or more of DRX timing or DTX timing indicated in the first message.

[0163] In some aspects, if the apparatus 1200 is a second network entity or acts as a neighboring network entity, the receiving component 1202 can receive a first message from the first network entity, the first message indicating one or more of the DRX timing of the first network entity or the DTX timing of the first network entity. The adjusting component 1212 can adjust one or more of the communication scheduling or the measurement configuration based at least in part on one or more of the DRX timing or the DTX timing.

[0164] The sending component 1204 can send a second message to the first network entity, the second message associated with accepting or not accepting one or more of the DRX timing or the DTX timing indicated in the first message.

[0165] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The assembly of (one or more) components shown may perform the operations described by Fig.12 Another collection of components shown performs one or more functions.

[0166] The following provides an overview of some aspects of the disclosure:

[0167] Aspect 1: A method of wireless communication performed by a device of a first network entity, the method comprising: sending a first message to a second network entity, wherein the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and starting at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

[0168] Aspect 2: According to the method of aspect 1, the method also includes: communicating at least partially based on the DRX timing or the DTX timing.

[0169] Aspect 3: The method according to aspect 1 or 2, wherein the first message indicates that the DRX timing and the DTX timing are the same, and indicates a start time slot and an end time slot for the DRX timing and the DTX timing.

[0170] Aspect 4: The method according to aspect 1 or 2, wherein the first message indicates one or more of the following: a start time slot and an end time slot for the DRX timing, or a start time slot and an end time slot for the DTX timing.

[0171] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the DRX timing includes the periodicity of the DRX mode, or the DTX timing includes the periodicity of the DTX mode.

[0172] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the first message indicates a DTX start offset of a DTX cycle or a DRX start offset of a DRX cycle.

[0173] Aspect 7: The method according to any one of aspects 1 to 6, wherein the first message is a node configuration update message.

[0174] Aspect 8: The method according to any one of aspects 1 to 6, wherein the first message is dedicated to a network entity sending or receiving activity.

[0175] Aspect 9: According to the method described in any one of Aspects 1 to 8, the method further includes: receiving a second message from the second network entity, the second message being associated with acceptance or non-acceptance of one or more of the DRX timing or the DTX timing indicated in the first message.

[0176] Aspect 10: The method according to aspect 9, wherein the second message is a node configuration update confirmation message.

[0177] Aspect 11: The method according to aspect 9, wherein the second message is dedicated to providing a response associated with a sending or receiving activity of the network entity.

[0178] Aspect 12: A method according to any one of Aspects 9 to 11, wherein starting at least one of the DRX mode or the DTX mode includes: starting the DRX mode according to the DRX timing or at least one of the DTX modes according to the DTX timing based at least in part on accepting the DRX timing or the DTX timing indicated by the second message.

[0179] Aspect 13: A method according to any one of Aspects 1 to 12, wherein the first message indicates one or more of the following: a semi-persistent mode or a dynamic mode for DTX; or a semi-persistent mode or a dynamic mode for DRX.

[0180] Aspect 14: The method according to aspect 13, wherein the first message indicates a first time slot of the dynamic mode for DTX, and wherein the first time slot has occurred.

[0181] Aspect 15: A method of wireless communication performed by a device of a second network entity, the method comprising: receiving a first message from a first network entity, the first message indicating one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and adjusting one or more of a communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

[0182] Aspect 16: The method according to aspect 15, wherein the first message indicates that the DRX timing and the DTX timing are the same, and indicates a start time slot and an end time slot for the DRX timing and the DTX timing.

[0183] Aspect 17: The method according to aspect 15, wherein the first message indicates one or more of the following: a start time slot and an end time slot for the DRX timing, or a start time slot and an end time slot for the DTX timing.

[0184] Aspect 18: The method according to any one of aspects 15 to 17, wherein the first message is a node configuration update message.

[0185] Aspect 19: The method according to any one of aspects 15 to 17, wherein the first message is dedicated to a network entity sending or receiving activity.

[0186] Aspect 20: According to the method according to any one of Aspects 15 to 19, the method also includes: sending a second message to the first network entity, the second message being associated with accepting or not accepting one or more of the DRX timing or the DTX timing indicated in the first message.

[0187] Aspect 21: According to the method of Aspect 20, the method also includes: at least in part based on the second message indicating acceptance of the DRX timing or the DTX timing, perform one or more of the following: adjust communication scheduling, start DRX mode, start DTX mode, or adjust measurement.

[0188] Aspect 22: The method according to aspect 20 or 21, wherein the second message is a node configuration update confirmation message.

[0189] Aspect 23: The method according to aspect 20 or 21, wherein the second message is dedicated to providing a response associated with a sending or receiving activity of the network entity.

[0190] Aspect 24: A method according to any one of Aspects 15 to 23, wherein the first message indicates one or more of: a semi-persistent mode or a dynamic mode for DTX; or a semi-persistent mode or a dynamic mode for DRX.

[0191] Aspect 25: The method according to aspect 24, wherein the first message indicates a first time slot of the dynamic mode for DTX, and wherein the first time slot has occurred.

[0192] Aspect 26: A method according to any one of Aspects 15 to 25, wherein adjusting the communication scheduling or one or more of the measurement configurations includes: adjusting the communication scheduling or one or more of the measurement configurations based at least in part on a DRX mode that occurs at least in part based on the DRX timing or a DTX mode that occurs at least in part based on the DTX timing.

[0193] Aspect 27: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 26.

[0194] Aspect 28: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 26.

[0195] Aspect 29: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 26.

[0196] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 26.

[0197] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 26.

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

[0199] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures and / or functions, etc. As used herein, a "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to a specific software code, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method at least in part based on the description herein.

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

[0201] Although the specific combination of features is stated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically stated in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0202] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "said one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "elements with" A may also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An apparatus of a first network entity for wireless communication, the apparatus comprising: one or more memories; as well as one or more processors, the one or more processors being coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the first network entity to: sending a first message to a second network entity, wherein the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and At least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing is started.

2. The apparatus of claim 1, wherein the one or more processors are individually or collectively configured to cause the first network entity to communicate based at least in part on the DRX timing or the DTX timing. 3 . The apparatus according to claim 1 , wherein the first message indicates that the DRX timing and the DTX timing are the same, and indicates a start time slot and an end time slot for the DRX timing and the DTX timing. 4 . The apparatus according to claim 1 , wherein the DRX timing comprises a periodicity of the DRX mode, or the DTX timing comprises a periodicity of the DTX mode.

5. The apparatus according to claim 1, wherein the first message indicates a DTX start slot offset of a DTX cycle or a DRX start slot offset of a DRX cycle.

6. The apparatus of claim 1, wherein the first message indicates one or more of the following: The start time slot and the end time slot for the DRX timing, or The start time slot and the end time slot used for the DTX timing. The apparatus of claim 1 , wherein the first message is a node configuration update message.

8. The apparatus of claim 1, wherein the first message is dedicated to a network entity sending or receiving activity.

9. The apparatus of claim 1 , wherein the one or more processors are individually or collectively configured to cause the first network entity to receive a second message from the second network entity, the second message being associated with acceptance or non-acceptance of one or more of the DRX timing or the DTX timing indicated in the first message.

10. The apparatus of claim 9, wherein the second message is a node configuration update confirmation message.

11. The apparatus of claim 9, wherein the second message is dedicated to providing a response associated with a network entity sending or receiving activity.

12. The apparatus according to claim 9, wherein in order to start at least one of the DRX mode or the DTX mode, the one or more processors are configured individually or collectively to cause the first network entity to start at least one of the DRX mode according to the DRX timing or the DTX mode according to the DTX timing at least in part based on the second message indicating acceptance of the DRX timing or the DTX timing.

13. The apparatus of claim 1, wherein the first message indicates one or more of: Semi-persistent mode or dynamic mode for DTX; or Semi-persistent mode or dynamic mode for DRX.

14. The apparatus of claim 13, wherein the first message indicates a first time slot for the dynamic mode of DTX, and wherein the first time slot has occurred.

15. An apparatus of a second network entity for wireless communication, the apparatus comprising: one or more memories; as well as one or more processors, the one or more processors being coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the second network entity to: receiving a first message from a first network entity, the first message indicating one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and One or more of a communication schedule or a measurement configuration is adjusted based at least in part on the one or more of the DRX timing or the DTX timing. 16 . The apparatus according to claim 15 , wherein the first message indicates that the DRX timing and the DTX timing are the same, and indicates a start time slot and an end time slot for the DRX timing and the DTX timing.

17. The apparatus of claim 15, wherein the first message indicates one or more of the following: The start time slot and the end time slot for the DRX timing, or The start time slot and the end time slot used for the DTX timing. The apparatus of claim 15 , wherein the first message is a node configuration update message.

19. The apparatus of claim 15, wherein the first message is dedicated to a network entity sending or receiving activity.

20. The apparatus of claim 15, wherein the one or more processors are individually or collectively configured to cause the second network entity to send a second message to the first network entity, the second message being associated with acceptance or non-acceptance of one or more of the DRX timing or the DTX timing indicated in the first message.

21. An apparatus according to claim 20, wherein the one or more processors are configured individually or collectively to cause the second network entity to perform one or more of the following based at least in part on the second message indication to accept the DRX timing or the DTX timing: adjust communication scheduling, start DRX mode, start DTX mode, or adjust measurement.

22. The apparatus of claim 20, wherein the second message is a node configuration update confirmation message.

23. The apparatus of claim 20, wherein the second message is dedicated to providing a response associated with a network entity sending or receiving activity.

24. The apparatus of claim 15, wherein the first message indicates one or more of: Semi-persistent mode or dynamic mode for DTX; or Semi-persistent mode or dynamic mode for DRX.

25. The apparatus of claim 24, wherein the first message indicates a first time slot for the dynamic mode of DTX, and wherein the first time slot has occurred.

26. An apparatus according to claim 15, wherein in order to adjust the communication scheduling or one or more of the measurement configurations, the one or more processors are configured individually or collectively to cause the second network entity to adjust the communication scheduling or one or more of the measurement configurations at least in part based on a DRX mode that occurs at least in part based on the DRX timing or a DTX mode that occurs at least in part based on the DTX timing.

27. A method of wireless communication performed by an apparatus of a first network entity, the method comprising: sending a first message to a second network entity, wherein the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and At least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing is started.

28. The method according to claim 27, wherein the first message indicates that the DRX timing and the DTX timing are the same, and indicates a start time slot and an end time slot for the DRX timing and the DTX timing.

29. The method of claim 27, wherein the first message indicates one or more of the following: The start time slot and the end time slot for the DRX timing, or The start time slot and the end time slot used for the DTX timing.

30. A method of wireless communication performed by an apparatus of a second network entity, the method comprising: receiving a first message from a first network entity, the first message indicating one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and One or more of a communication schedule or a measurement configuration is adjusted based at least in part on the one or more of the DRX timing or the DTX timing.

Images