WO2024168571A1

WO2024168571A1 - Historical activity report

Info

Publication number: WO2024168571A1
Application number: PCT/CN2023/076124
Authority: WO
Inventors: Ahmed Elshafie; Wei Yang; Huilin Xu; Gokul SRIDHARAN; Linhai He; Yuchul Kim; Zhikun WU; Wanshi Chen
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-02-15
Filing date: 2023-02-15
Publication date: 2024-08-22
Anticipated expiration: 2025-08-15

Abstract

Apparatus, methods, and computer program products for wireless communication are provided. An example method may include transmitting, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. The example method may further include transmitting, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time.

Description

HISTORICAL ACTIVITY REPORT

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to wireless communication systems with energy harvesting (EH) devices.

INTRODUCTION

Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. 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, and time division synchronous code division multiple access (TD-SCDMA) systems.

These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB) , massive machine type communications (mMTC) , and ultra-reliable low latency communications (URLLC) . Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.

BRIEF SUMMARY

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus (which may be a first network entity, such as a user equipment (UE) ) , are provided. The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to transmit, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. The at least one processor may be configured to transmit, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. The at least one processor may be configured to communicate with the second network entity based on the first network activity history and the second network activity history.

In another aspect of the disclosure, a method, a computer-readable medium, and an apparatus at (which may be a first network entity) . The apparatus may include a memory and at least one processor coupled to the memory. The at least one processor may be configured to receive, at a first time from a second network entity, a first network activity history associated with the second network entity, where the first network activity history includes information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. The at least one processor may be configured to receive, at a second time from the second network entity, a second network activity history associated with the second network entity, where the second network activity history includes information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. The at least one processor may be configured to communicate with the second network entity based on the first network activity history and the second network activity history.

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.

FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.

FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.

FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.

FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.

FIG. 4 is a diagram illustrating example harvesting cycle of an energy harvesting (EH) device.

FIG. 5 is a diagram illustrating example multiplexing of network activity history.

FIG. 6 is a diagram illustrating example communications between a UE and a network entity.

FIG. 7 is a diagram illustrating example report of network activity history.

FIG. 8A is a diagram illustrating an example of report of network activity history being multiplexed with buffer status report (BSR) .

FIG. 8B is a diagram illustrating another example of report of network activity history being multiplexed with BSR.

FIG. 9A is a diagram illustrating another example of report of network activity history being multiplexed with BSR.

FIG. 9B is a diagram illustrating an example of report of network activity history being multiplexed with hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ ACK) .

FIG. 10A is a diagram illustrating an example of BSR.

FIG. 10B is a diagram illustrating an example of BSR with unused bits.

FIG. 11A is a diagram illustrating an example of BSR with unused bits removed.

FIG. 11B is a diagram illustrating an example of network activity history being multiplexed with BSR.

FIG. 12 is a flowchart of a method of wireless communication.

FIG. 13 is a flowchart of a method of wireless communication.

FIG. 14 is a flowchart of a method of wireless communication.

FIG. 15 is a diagram illustrating an example of a hardware implementation for an example apparatus and/or network entity.

FIG. 16 is a diagram illustrating an example of a hardware implementation for an example network entity.

DETAILED DESCRIPTION

If energy arrival is not guaranteed, behavior or power status of an EH device may not be determined by the network, and the network may schedule downlink transmission or uplink transmission for time durations where the device has no power to be in the active state. Aspects provided herein enable the network to receive network activity history associated with the EH device so that the network and the EH device may communicate based on such network activity history, facilitating more efficient communications.

The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) . Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.

Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. 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 (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmit receive point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.

An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs) , one or more distributed units (DUs) , or one or more radio units (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 throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) .

Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance) ) , or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN) ) . Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a Non-Real Time (Non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) Framework 105, or both) . A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.

Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) , configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.

In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 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 implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.

The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 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, demodulation, or the like) depending on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.

Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, 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, or the like) , or both, based on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU (s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.

The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) /machine learning (ML) (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.

In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .

At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102) . The base station 102 provides an access point to the core network 120 for a UE 104. The base stations 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station) . The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base stations 102 /UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .

Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs) ) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 /AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. 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) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz –71 GHz) , FR4 (71 GHz –114.25 GHz) , and FR5 (114.25 GHz –300 GHz) . Each of these higher frequency bands falls within the EHF band.

With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.

The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 /UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 /UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.

The base station 102 may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU.

The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location/positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE) , a serving mobile location center (SMLC) , a mobile positioning center (MPC) , or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the serving base station 102. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS) , global position system (GPS) , non-terrestrial network (NTN) , or other satellite position/location system) , LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS) , sensor-based information (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT) , DL angle-of-departure (DL-AoD) , DL time difference of arrival (DL-TDOA) , UL time difference of arrival (UL-TDOA) , and UL angle-of-arrival (UL-AoA) positioning) , and/or other systems/signals/sensors.

Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.

Referring again to FIG. 1, in some aspects, the UE 104 may include a history component 198. In some aspects, the history component 198 may be configured to transmit, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, the history component 198 may be further configured to transmit, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, the history component 198 may be further configured to communicate with the second network entity based on the first network activity history and the second network activity history.

In certain aspects, the base station 102 may include a history component 199. In some aspects, the history component 199 may be configured to receive, at a first time from a second network entity, a first network activity history associated with the second network entity, where the first network activity history includes information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, the history component 199 may be further configured to receive, at a second time from the second network entity, a second network activity history associated with the second network entity, where the second network activity history includes information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, the history component 199 may be further configured to communicate with the second network entity based on the first network activity history and the second network activity history.

Although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, be, or be included in (e.g., be a component of) a base station (e.g., any base station described herein) , a UE (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, an integrated access and backhauling (IAB) node, a distributed unit (DU) , a central unit (CU) , a remote/radio unit (RU) (which may also be referred to as a remote radio unit (RRU) ) , and/or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or network entity. As another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first, second, and third network nodes may be different relative to these examples. Similarly, reference to a UE, base station, apparatus, device, computing system, or the like may include disclosure of the UE, base station, apparatus, device, computing system, or the like being a network node. For example, disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a specific example is broadened in accordance with this disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node) , the broader example of the narrower example may be interpreted in the reverse, but in a broad open-ended way. In the example above where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more one or more components, a first processing entity, or the like configured to receive the information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, a second processing entity, or the like.

As described herein, communication of information (e.g., any information, signal, or the like) may be described in various aspects using different terminology. Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to transmit information to a second network node. In this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the first network node is configured to provide, send, output, communicate, or transmit information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that the first network node is configured to transmit information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode the information that is provided, sent, output, communicated, or transmitted by the first network node.

FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL/UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically/statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) .

FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and/or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also referred to as single carrier frequency-division multiple access (SC-FDMA) symbols) (for power limited scenarios; limited to a single stream transmission) . The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) and, effectively, the symbol length/duration, which is equal to 1/SCS.

Table 1: Numerology, SCS, and CP

For normal CP (14 symbols/slot) , different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2^μ slots/subframe. The subcarrier spacing may be equal to 2^μ* 15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended) .

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs) . The number of bits carried by each RE depends on the modulation scheme.

As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .

FIG. 2B illustrates an example of various DL channels within a subframe of a frame. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs) , each CCE including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and/or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) /PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.

As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and/or negative ACK (NACK) ) . The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and/or UCI.

FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. In the DL, Internet protocol (IP) packets may be provided to a controller/processor 375. The controller/processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression /decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.

At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.

The controller/processor 359 can be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression /decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.

The controller/processor 375 can be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.

At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with history component 198 of FIG. 1.

At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with history component 199 of FIG. 1.

In addition to higher capability devices, wireless communication may support reduced capability (RedCap) devices. Among others, examples of higher capability devices include premium smartphones, V2X devices, URLLC devices, eMBB devices, etc. Among other examples, reduced capability devices may include wearables (e.g., smart watches, augmented reality glasses, virtual reality glasses, health and medical monitoring devices, etc. ) , industrial wireless sensor networks (IWSN) (e.g., pressure sensors, humidity sensors, motion sensors, thermal sensors, accelerometers, actuators, etc. ) , surveillance cameras, low-end smartphones, etc. For example, NR communication systems may support both higher capability devices and reduced capability devices. A reduced capability device may be referred to as an NR light device, a low-tier device, a lower tier device, etc. Reduced capability UEs may communicate based on various types of wireless communication. For example, smart wearables may transmit or receive communication based on low power wide area (LPWA) /mMTC, relaxed IoT devices may transmit or receive communication based on URLLC, sensors/cameras may transmit or receive communication based on eMBB, etc.

In addition to reduced capability devices, devices with a lower capability than reduced capability devices including lower power consumption and a less complicated structure may be included in wireless communication systems. In some wireless communication systems, passive wireless devices such as zero-power passive IoT wireless devices may be included. Such passive wireless devices may be without active RF components and may perform transmissions based on backscatter communication and may perform reception based on envelope detection or an envelope detector. Backscatter communication may modulate information on an incoming RF signal (which may be a carrier wave that may carry communication between other devices) by an adaptation of antenna load impedance. A passive wireless device may be battery-less or battery assisted. For example, a passive wireless device may operate based on energy harvesting from an incoming radio wave with or without a battery as an additional power source. A passive wireless device may have low power consumption, such as between 1 microwatt to 1000 microwatts. Such passive wireless devices may be devices for inventory management, wireless sensors, or the like. Passive devices may use backscatter communication to communicate with another network entity, such as a base station.

Backscatter communication may enable radio frequency identification (RFID) . For example, a reader may send a continuous waveform signal and interrogate commands. An RF tag (which is a passive wireless device) may harvest energy from the continuous waveform signal and may respond to the interrogation by varying its input impedance (e.g., between conjugate match and strongly mismatched) , therefore modulating the backscattered signals. RFID is a rapidly growing technology impacting many industries due to its potential for inventory/asset management inside and outside warehouse, IoT, sustainable sensor networks in factories and/or agriculture, and smart home. RFID may include small transponders, which may be referred to as tags, emitting an information-bearing signal upon receiving a signal. RFID may be operated without battery at low operational expenditures (OPEX) and may use small amount of resources. RFID may have use lower amount of maintenance and may have a long life-cycle.

As used herein, the term “energy transfer” may be used interchangeably with “energy harvesting” (EH) to refer to a procedure in which a wireless device (which may be referred to as an “energy harvesting wireless device” ) uses a carrier wave transmitted by another wireless device (which may be referred to as a “power provider wireless device” to get energy) . An example of an energy harvesting (EH) device may be a RF tag and an example of a power provider (PP) wireless device may be a RF interrogator (which may also be referred to as “RF reader” ) . Examples of an energy harvesting wireless device may include energy harvesting UEs, RFID tag with battery, RFID tag without battery, or other types of wireless devices with energy harvesting capability (e.g., based on any sources such as laser provided by network or other sources such as solar, thermal, vibration, RF from NW or other sources including various types of wireless communications) . In some aspects, the energy harvesting wireless device may be a UE with a modem and may be capable of performing energy harvesting.

As used herein, the term “network activity history” may refer to information regarding whether a wireless device or a modem at the wireless device is in an active state (such as a discontinuous reception (DRX) ON duration, being turned on for receiving or transmitting data, or other types of activity with other devices) or an inactive state (such as a DRX OFF duration, no energy left, being turned off to not receive or transmit data, unable to transmit or receive data due to performing energy harvesting, or the like) in one or more time units. In some aspects, the term “time unit” may refer to a slot, a mini-slot, a symbol, multiple slots of a defined length, multiple mini-slots of a defined length, or other units of time. A device may be configured with DRX mode to save power. In the DRX mode, the device may be configured with periodic ON durations and OFF durations. The device may monitor PDCCH during ON durations to identify if whether it will have DL or UL data. If the device determines that it may have DL or UL data, the UE may stay awake for another amount of time, which may be specified based on an inactivity timer. If the UE identifies that it does not have DL/UL data, the device may go to sleep and enter the OFF duration. During the OFF duration, the UE may skip monitoring for PDCCH.

As used herein, the term “energy state” (which may also be referred to as “energy mode, ” “energy information, ” or “energy status” ) may refer to one or more of: an energy level profile representing available energy at a device’s energy storage unit or battery over time based on current measurements and prediction over time (e.g., current available energy, predicted future available energy and associated predicted time instances or durations, or the like) , an energy charging profile representing an energy charging rate or other energy charging related parameters related to the device’s energy storage unit or battery (e.g., a current energy charging rate, predicted future energy charging rates and associated predicted time instances or durations, or the like) , an energy discharging profile representing an energy discharging rate (e.g., a current energy discharging rate, predicted future energy discharging rates and associated predicted time instances or durations, or the like) , or other energy discharging related parameters related to the device’s energy storage unit or battery. For example, an energy charging profile may include a current measured charging rate, how long the current charging rate is predicted to last, a predicted charging rate for one or more future time instances or durations, or the like. As one example, the energy charging profile may include P1, P2, P3, P4, …, PN (each of which represent an energy charging rate and T1 (time instance or duration predicted for charging rate P1 to last) , T2 (time instance or duration predicted for charging rate P2 to last) , T3 (time instance or duration predicted for charging rate P3 to last) , T4 (time instance or duration predicted for charging rate P4 to last) , …, TN (time instance or duration predicted for charging rate PN to last) . In some aspects, based on an agreement with two wireless devices (such as a UE and a gNB or between two UEs) , a wireless device may decide based on the profiles (e.g., and the values in each profile including P1, P2, . . ., PN, the parameters, T1, T2, . . ., TN) for each profile of the energy charging profile, the energy discharging profile, or the energy level profile.

An EH device may operate based on reading cycle (e.g., operating and monitoring transmission from other devices) and harvesting cycle (e.g., for harvesting energy) . FIG. 4 is a diagram 400 illustrating example harvesting cycle of an EH device. After receiving a wake up indication (WUI) 402A and transmitting a wake up acknowledgment (WUA) 404A, the energy harvesting device may enter an ON duration 406A of Y time units. After Y units, the energy harvesting device may perform energy harvesting for X units. Upon receiving a WUI 402B and transmitting a WUA 404B, the energy harvesting device may enter another ON duration 406B. Based on an input power to an example EH device (e.g., a RFID tag) and the power consumed by the device during activity, the device active cycle (proportion of X in relation to Y0 may be configured. For example, if the input power is P_x and RF-to-DC conversion efficiency at P_x is η_x, then harvested power is P_x. η_x. If the device would function, the accumulated energy would be higher than the consumed energy. Based on a power used for operating (which may be an integrated chip power of the modem of the device) of P_y, and ON duration (e.g., active state and monitoring transmission from other devices) of Y time units, the condition to operate is P_x. η_x. X≥ P_y . Y. As an example, with a -37 decibel-milliwatts (dBm) input power with a certain RF-to-DC conversion efficiency (e.g., 10%) , then harvested power is -47 dBm. If the device would accumulate the power for X time units (e.g., slots) , the harvested power may be -47 plus 10 times log10 (X) . With an operating power of 10 microwatts (-20 dBm) that operates for Y time units (e.g., slots) , then for the device to be able to be in an ON/active state during the Y time units, -47 plus 10 times log10 (X) would be greater than or equal to -20 plus 10 times log10 (Y) . Accordingly, the ratio of X to Y may be greater than 501. Therefore, as an example, if the device with 10 μW power consumption) has to wakeup (e.g., be active/ON) for Y time units, the device may harvest for X time units, where X/Y=500. As an example of operation with X/Y=500, the device may continuously harvest every 5 seconds to be in the active mode for 10 milliseconds.

Some energy harvesting devices may have unpredictable energy usage. For example, engagement in sidelink or other activities, or battery leakage of the device, may all be unpredictable. Some energy harvesting devices may have a small amount of energy and may engage in switch quickly between an active state and an inactive state (e.g., to frequently perform PDSCH transmission processing or PUSCH transmission) . As an example, an energy harvesting device may perform, within a duration of L time units: 1) X time units for PUSCH transmission, 2) Y time units of PDSCH transmission processing, 3) X time units for PUSCH transmission and Y time units of PDSCH transmission processing, or 4) Z time units of CSI-RS processing. If energy arrival is not guaranteed, behavior or power status of an EH device may not be determined by the network, and the network may schedule downlink transmission or uplink transmission for time durations where the device has no power to be in the active state. Aspects provided herein enable the network to receive network activity history associated with the EH device so that the network and the EH device may communicate based on such network activity history, facilitating more efficient communications. For example, if a DL grant is missing (e.g., not successfully transmitted) , the network may determine what the cause might be such as the EH device being in an inactive state, beam block, or an error in DCI or PDSCH reception. If the network determines the EH device may be in the inactive state in times where the network scheduled DL or UL transmission, the network may reschedule the UL transmission or retransmit the DL transmission. A network activity history may be multiplexed with layer 1 (L1) (PHY layer) signaling such as control information (e.g., UCI) , layer 2 (L2) (RLC layer) signaling such as MAC control element (MAC-CE) , or layer 3 (L3) signaling such as radio resource control (RRC) signaling or non-access stratum (NAS) message. As one example, FIG. 5 is a diagram 500 illustrating example multiplexing of network activity history. As illustrated in FIG. 5, the network activity history may be carried in UCI 504 associated with a PUSCH transmission 502. As one example, the network activity history may be multiplexed with the PUSCH transmission 502 in raw data form, then low-density parity code (LDPC) encoding may be performed based on the same resources for the network activity history and the PUSCH transmission. LDPC encoding may be a linear error correcting code that may be constructed with a bipartite graph. As another example, the network activity history may be multiplexed with the PUSCH transmission 502 after each bit stream of the network activity history and the PUSCH transmission 502 is encoded based on its respective encoder (e.g., polar or sequence based for the network activity history and the UCI 504, LDPC for the PUSCH transmission 502) . Then after puncturing or rate matching the PUSCH, the network activity history may be multiplexed with the PUSCH transmission 502.

Such a network activity history may be different from a powerhead room (PHR) report. A PHR report may indicate the remaining UL transmit power to send data or control signal based on currently scheduled transmissions and may not be an overall energy status report of the device. In PHR, the UE may report how much transmit power is left compared to a maximum transmit power so that the network may accordingly schedule more allocations for UL transmission. However, even with PHR, the network may not know the energy available at the UE, whether the UE can decode data or not, whether the UE can transmit data after finishing the current transmission or not, or the like.

FIG. 6 is a diagram 600 illustrating example communications between a UE 602 (which may be an EH device) and a network entity 604. In some aspects, a network entity may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and may include one or more of a CU, a DU, a RU, a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) , or a Non-Real Time (Non-RT) RIC. In some aspects, communication between the one or more power provider wireless devices or the one or more energy harvesting wireless devices may be downlink communication (e.g., including downlink configured or dynamic grants) , uplink communication (e.g., including uplink configured or dynamic grants) , sidelink communication, backhaul communication, or the like. In some aspects, the network entity 604 may be another UE. In some aspects, the UE 602 and the network entity 604 may communicate based on a particular link associated with a particular interface. The particular interface may be based on a communication system that may use a sinewave (single tone) or multi-tone (OFDM-based) waveform (RF waveforms) transmitted by a first device (e.g., the network entity 604) and reflected/backscattered by a second device, which may be an EH device (e.g., the UE 602) . The first device may be a NW unit, IAB relay, a relay node, a RAN node, a gNB, a TRP associated with the NW, a sidelink UE (remote, primary, PLC, or a controlling unit in sidelink) , a UE-UTRAN (Uu) link UE transmitted waveform or RF signals. The waveform generated by the first device may carry data signal (e.g., PDSCH, PDSCH, PSSCH, among other examples) , reference signal (e.g., CSI-RS, SRS, SSB, among other examples) , or random data or reference signal signals/symbols across different sub-channels/REs. In some examples, the waveform may be sub-channels modulated OFDM signal/waveform or time-domain modulated OFDM-based signal/waveform. The communication signals in the new interface may refer to a modulated waveform/signal generated, based on the capability of the EH device, by the EH device where the waveform can be one of sinewave (single tone) , multi-tone wave (e.g., OFDM-based waveform) . In some examples, the modulation used can be on-off-keying (OOK) , amplitude shift keying (ASK) , frequency shift keying (FSK) , phase shift keying (PSK) , Zadoff Chu, DFT, Walshi/Hadamard, Gold, Reed-Solomon, m-sequence, Chirp, among other examples. In some examples, modulation may occur in time domain or frequency domain or jointly. In some examples, Manchester coding may be used with ASK or OOK. In some example, forward error correction codes and other channel coding may be applied to achieve higher reliability. In some aspects, the UE 602 may use two different interfaces where a first interface is associated with high power mode (or no to low power saving mode) . For example, the first interface may be associated with a Uu or PC5 like interfaces. The UE 602 may use a second interface (which associated with same radio as the first interface with deactivation one or more on RF, hardware (HW) , software (SW) , or firmware (FW) components or with a separate radio (e.g., backscatter-based) radio similar to a tag which may be passive or semi-passive) to be used with low to very low power saving modes (where the UE 602 is maximizing the power saving) . In some aspects, there may be association between the type of the interface and the type of a signal. For example, if the signal is low priority or less important than data and regular UL signals (e.g., HARQ ACK, CSI report, or the like) , the second interface may be used. If the signal is important (e.g., data) , the first interface may be used. In some aspects, the network may assign different signals to different interfaces based on priority, quality of service (QoS) , and power saving at NW and UE or based on reported energy state at the UE 602 (e.g., energy charging rate profile, discharging/power consumption rate profile, energy state/level profile) , or based on UE requests/specifications and traffic (the UE 602 may request for a particular mapping between signals and interfaces using L1 signaling, L2 signaling, or L3 signaling (e.g., in dedicated signal or multiplexed with other signals) and the network can configure using L1 signaling, L2 signaling, or L3 signaling (such as signaling that includes UE assistance information) . As one particular example, an L1 signaling may be a WUS which may be of DCI format 2_6 (which may be a format configured for notifying the power saving information outside DRX Active Time for one or more UE) , a scheduling DCI that schedules a transmission, a non-scheduling DCI that does not schedule a transmission, or multiplexed with a PDSCH transmission. As one particular example, an L3 signaling may be UE assistance information (UAI) . As used herein, the term “UAI” may refer to a type of RRC message in which a UE informs the network of the UE’s internal status so that the network may assign or control resources more efficiently based on the UE’s internal status. In some aspects, an UAI may include a parameter indicative of a configuration requested (which may also be referred to as negotiated) by the UE, and the network may consider whether to configure the configuration requested by the UE.

As illustrated in FIG. 6, the network entity 604 may transmit a configuration 606 indicative of a time difference (e.g., a period) for reporting network activity history. For example, the UE 602 may report network activity history every M time units, where M is a positive integer configured by the configuration 606. The UE 602 may transmit a first network activity history 616A, then after a time difference 650 which may be M units, the UE 602 may transmit a second network activity history 616B. In some aspects, the configuration 606 may be based on L1 signaling, L2 signaling, or L3 signaling. In some aspects, the time period (e.g., quantity of M time units) may be updated, such as in a WUS 607 configured to trigger the UE 602 to enter the active state (e.g., at 608) . In some aspects, the quantity of the M time units may be a function of various parameters related to the energy state of the UE 602, such as a function of worst case scenario based on charging rate profile, discharging rate profile, energy status profile measurements and associated predictions. In some aspects, the quantity of the M time units may be determined by an entity and signaled to the network entity 604 or the UE 602 from the UE 602 or the network entity 604, or another network entity. In some aspects, the WUS 607 may be carried in a DCI format 2_6 652. The DCI format 2_6 may be configured for notifying the power saving information outside DRX Active Time for one or more UEs. The UE 602 may transmit a WUS response to respond to the WUS 607, which may be a network activity history or a separate response 607X (which may correspond to 654) , then enter the active state at 608 (which may correspond to DRX active time 656) . In some aspects, the WUS 607 or another signal may include information indicative of whether a network activity history of the UE 602 may be multiplexed with another signal.

Each of the first network activity history 616A or the second network activity history 616B may include information regarding whether the UE 602 is in an active state or an inactive state for one or more time units, such as each of the one or more time units. Referring to FIG, 7, FIG. 7 is a diagram 700 illustrating example report of network activity history. As illustrated in FIG. 7, the UE may be in the inactive state (OFF) during time unit 702A, in the active state (ON) during time unit 702B, ON during time unit 702C, ON during time unit 702D, OFF during time unit 702F, OFF during time unit 702G, ON during time unit 702H, ON during time unit 702I, and OFF during time unit 702J. The first network activity history 616A or the second network activity history 616B may include entries 704A to 704J, which 704A includes a “0” indicating the UE is in the inactive state (OFF) during time unit 702A, 704B includes a “1” indicating the UE is in the active state (ON) during time unit 702B, 704C includes a “1” indicating the UE is in the active state (ON) during time unit 702C, 704D includes a “1” indicating the UE is in the active state (ON) during time unit 702D, 704E includes a “0” indicating the UE is in the inactive state (OFF) during time unit 702E, 704F includes a “0” indicating the UE is in the inactive state (OFF) during time unit 702F, 704G includes a “1” indicating the UE is in the active state (ON) during time unit 702G, 704H includes a “1” indicating the UE is in the active state (ON) during time unit 702H, 704I includes a “0” indicating the UE is in the inactive state (OFF) during time unit 702I, 704J includes a “0” indicating the UE is in the inactive state (OFF) during time unit 702J. In some aspects, first network activity history 616A or the second network activity history 616B may include entries 706A to 706C, which bundles four time units and report accordingly. The entry 706A includes a “1” indicating the UE is in the active state (ON) for a duration, (e.g., being ON more than a threshold configured based on L1 signaling, L2 signaling, L3 signaling, or a mapping function) , during time units 702A-702D, the entry 706B includes a “0” indicating the UE is in the inactive state (OFF) for a duration, (e.g., being ON less than a threshold configured based on L1 signaling, L2 signaling, L3 signaling, or a mapping function) , during time units 702E-702H, and the entry 706C includes a “1” indicating the UE is in the active state (ON) for a duration, (e.g., being ON more than a threshold configured based on L1 signaling, L2 signaling, L3 signaling, or a mapping function) , during time units 702I-702J.

In some aspects, the first network activity history 616A or the second network activity history 616B may include information regarding the time units where the UE 602 is in the active state, such as information regarding the time units 702B, 702C, 702D, 702H, and 702I.

Referring back to FIG. 6, in some aspects, the first network activity history 616A or the second network activity history 616B may be transmitted in a dedicated transmission or by request (e.g., via request 611, which may be a non-scheduling DCI, or DCI 612A, which may also schedule the first network activity history 616A) . When the UE 602 transmits the first network activity history 616A or the second network activity history 616B based on a request, the UE 602 may transmit the first network activity history 616A or the second network activity history 616B based on time and frequency resources configured by the request. In some aspects, the UE 602 may transmit the first network activity history 616A or the second network activity history 616B by multiplexing the first network activity history 616A or the second network activity history 616B with another L1 signaling, L2 signaling, or L3 signaling, such as a CSI report, a PHR, a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a wakeup signal, a cell WUS, UAI, part of a PUSCH as UCI as illustrated in FIG. 5, or the like.

As an example, the multiplexing may be based on joint entries in a data structure (such as a table) configured without signaling or configured based on L1, L2, or L3 signaling between the UE 602 and the network entity 604. In another example, the multiplexing may be based on using a portion of bits that may be otherwise used for reporting a quantity (e.g., in BSR, SR, or HARQ-ACK) to include the first network activity history 616A or the second network activity history 616B. In another example, the multiplexing may be based on concatenating one or more bits that may be otherwise used for reporting a quantity (e.g., in BSR, SR, or HARQ-ACK) and use time and frequency resources for the concatenated bits to include the first network activity history 616A or the second network activity history 616B. In another example, the multiplexing may be based on multiplexing the first network activity history 616A or the second network activity history 616B after encoding each information in the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to a wakeup signal, the cell WUS, the UAI, the PUSCH, and use the same time and frequency resources or extend the time and frequency resources.

In some aspects, to multiplex the first network activity history 616A or the second network activity history 616B with a PHR or SR, the UE may use reserved (R) bits in PHR or split the 8 bits used for a single entry PHR for PHR and remaining for network activity history. The configuration of how many bits may be used for network activity history may be configured based on L1 signaling, L2 signaling, L3 signaling, or without signaling, and may be based on the time period (e.g., quantity of M) for transmitting the network activity history. In some aspects, configuration of how many bits may be used for network activity history may be further based on an EH class (e.g., type) associated with the UE 602. In some aspects, the PHR may include an additional entry for the network activity history. In some aspects, the PHR may be reduced to make room for carrying the network activity history. In some aspects, one or more logical channel identifier (LCID) or logical channel group identifier (LCGID) may be associated with one or more SRs and the UE 602 may multiplex the network activity history on one or more SRs of a subset of LCIDs/LCGIDs defined to allow multiplexing of the network activity history.

In some aspects, to multiplex the first network activity history 616A or the second network activity history 616B with BSR, SR, HARQ ACK, or a RACH message, one or more codebooks that may be configured for multiplexing may be used. For example, a codebook may be configured for joint BSR and network activity history of one or more time units, a codebook may be configured for joint SR and network activity history of one or more time units, a codebook may be configured for joint HARQ ACK and network activity history of one or more time units, or a codebook may be configured for joint RACH message and network activity history of one or more time units. As one example, a table of codebook is provided below:

Table 2

FIG. 9B is a diagram 950 illustrating an example of report of network activity history being multiplexed with HARQ ACK. As illustrated in FIG. 9B, the network activity history 954 is multiplexed with HARQ ACK 952. In some aspects, to multiplex the first network activity history 616A or the second network activity history 616B on SR or HARQ ACK (which may be 1 bit, 2 bit, or the like) with PUCCH format 0 (e.g., format for HARQ) or other formats, the UE 602 may use: (1) a first cyclic shift (CS) for network activity history and a second CS (which may be different from the first CS) for HARQ ACK/SR or (2) a single CS (e.g., when a single codebook is used) for network activity history and the HARQ ACK/SR, where the single CS may be indicative of the joint codepoint. A cyclic shift may be a delay of a length with respect to a time reference (e.g., at a beginning of a symbol) . As one example of the joint codepoint, to represent a total of Y bits where X bit is for the HARQ ACK or SR and Y-X number of bits are used for the network activity history, where Y and X are a positive integers and Y is larger than X. A total number of 2^Y number of CSs may be configured for the UE 602 to use, and a CS may be selected based on observed activity and the current SR/HARQ ACK.

In some aspects, for HARQ ACK of some formats, such as PUCCH, the time and frequency resources configured for the HARQ ACK may be split, and a first subset of the time and frequency resources may be used for carrying the HARQ ACK and a second subset of the time and frequency resources may be used for carrying the network activity history (e.g., when the used codebook is not a single codebook with a single table) . In some aspects, the first subset of the time and frequency resources and the second subset of the time and frequency resources may be based on quantities of bits for the HARQ ACK or the network activity history, coding rate (e.g., and associated reliability and target metrics) , and priority associated with the HARQ ACK or the network activity history.

In some aspects, the UE 602 may transmit the network activity history after every K (K being a positive integer that may be configured based on L1 signaling, L2 signaling, L3 signaling, or without signaling) occasions/transmissions carrying a type of transmission (e.g., HARQ-ACK, SR, CSI report, or the like) . At the Kth occasion or a first UL resource after the Kth occasion, the UE 602 may multiplex the first network activity history 616A or the second network activity history 616B with a transmission that may take place at the Kth occasion or on the first UL resource after the Kth occasion (which may be done regardless of what’s the type of the transmission) . In some aspects, the network activity history (e.g., the first network activity history 616A or the second network activity history 616B) may be transmitted after K HARQ-ACK PUCCH occasions, after K SR occasions, after K BSR occasions, or after any K UL occasions. In some aspects, the UE 602 may transmit the network activity history (e.g., the first network activity history 616A or the second network activity history 616B) at a beginning of an active state (e.g., an DRX ON interval) as a response to the WUS or at an end of each active state based on configured UL allocations or multiplexed with another signal. For example, the UE 602 may transmit the network activity history (e.g., the first network activity history 616A or the second network activity history 616B) with the HARQ-ACK of PDCCH skipping signal, at an end of burst signal to the network entity 604, in a configured grant at end of each DRX active time, after extension of active time for the DRX ON interval, or the like.

In some aspects, the UE 602 may transmit the network activity history in one or configured periodic UL occasions. In some aspects, based on a request (e.g., based on L1 signaling, L2 signaling, or L3 signaling) from the network entity 604, the UE 602 may determine UL resources to multiplex the network activity history with. For example, the request may include information indicative of a timer period in which the UE 602 may multiplex the network activity history with another signaling.

In some aspects, the network entity 604 may transmit a transmission history 610 indicative of time units where the network entity 604 sent DL data to the UE 602 so that the UE 602 would know whether it successfully received the DL data that’s scheduled for the UE 602. In some aspects, the transmission history 610 may be included in a WUS signal (e.g., the WUS 607, dedicated MAC-CE, transmitted with PDSCH, transmitted with PDSCH scheduling or non-scheduling DCI, or transmitted with other L1 signaling, L2 signaling, or L3 signaling) . In some aspects, if a subset of the time units where the network entity 604 sent DL data to the UE 602 are not monitored by the UE 602 due to the UE 602 being in the inactive state, the UE 602 may report the subset of the time units to the network entity 604 (e.g., in the first network activity history 616A or the second network activity history 616B) .

In some aspects, in the transmission history 610, the network entity 604 may transmit information indicative of time units where the network entity 604 sent transport block (TB) of high priority or quality of service (QoS) to the UE 602 to reschedule a retransmission (e.g., 620) . In some aspects, the packet delay budget may not be met and there may be room to transmit the TB on the same slot.

Based on the first network activity history 616A or the second network activity history 616B, the UE 602 or the network entity 604 may be able to communicate at 618, such as by transmitting or receiving retransmission 620 or groupcast signal 622. The first network activity history 616A or the second network activity history 616B may facilitate in: (1) determining whether the network entity 604 may retransmit a packet or not (e.g., using a self-decodable redundancy version (RV) ) , (2) determining whether the UE 602 may retransmit a packet or not (e.g., using a self-decodable RV) , (3) determining whether to retransmit a groupcast signal 622 to the UE 602 (which may be transmitted when the UE 602 is in the inactive state and not received) , (4) determining whether an error in DL or UL is caused by the UE 602 being in the inactive state and retransmit accordingly, or (5) determining whether the UE 602 may retransmit HARQ ACK for missed DL data (e.g., may not retransmit HARQ ACK for data that the network entity 604 determined to be missed due to the UE 602 being in the inactive state) .

In some aspects, the UE 602 and the network entity 604 may determine a redundancy version to communicate at 618. Without network activity history, as an example, the network may transmit packets in pattern of RV0, RV2, RV3, RV1 where RV0 and RV3 are self-decodable (e.g., include the systematic bits or information bits’ parity bits) . If the Rx side (UE 602 in case of DL transmission and network entity 604 in case of UL transmission) receives two different RVs of same packet/TB, the Rx side may combine the two different RVs in the Leucine-rich repeat domain and perform decoding (e.g., LDPC decoding) . For UL transmissions, if one RV of a packet is lost due to the UE 602 being in an inactive state, without the network activity history, the network entity may be combining data and noise in the RV of the packet that is not lost with pure noise, which may lead to more errors. As another example, if a non-self-decodable (e.g., RV2) is used in a subsequent retransmission of a packet that was transmitted initially with self-decodable (e.g., RV0) , even if the packet arrives with low noise, the Rx side may not be able to determine what is the data unless the Rx side has received the packet in a RV that is self-decodable. Based on the first network activity history 616A or the second network activity history 616B, the UE 602 or the network entity 604 may be able to retransmit data (e.g., in retransmission 620) based on a self-decodable RV for data that was scheduled to be transmitted in the time period where the UE is in the inactive state.

In some aspect, based on indication from the network entity 604, resources associated with one or more LCIDs or LCGIDs may be entirely used for reporting the network activity history or reducing the BSR on the one or more LCIDs or LCGIDs may be shortened.

FIG. 8A is a diagram 800 illustrating an example of report of network activity history being multiplexed with BSR. As illustrated in FIG. 8A, buffer status #1 804A is shortened to allow the network activity history 806 to be transmitted. Buffer status #2 804B and additional buffer status, such as buffer status #N 804N, are unchanged.

FIG. 8B is a diagram 850 illustrating another example of report of network activity history being multiplexed with BSR. As illustrated in FIG. 8B, buffer status #1 854A is shortened to allow the network activity history 856A to be transmitted. Buffer status #2 854B and additional buffer status until the last buffer status #N 854N, are unchanged. The last buffer status #N 854N is shortened to allow the network activity history 856B to be transmitted.

In some aspects, the network activity history may be associated with a priority. To multiplex the network activity history with the SR, the UE may truncate more bits from BSR based on the priority associated with the network activity history, the priority associated with the BSR, or the size of the network activity history or the BSR. Because the UE 602 may be an EH device of sparse data or on-demand sensing/positioning traffic arrival and fixed packet size, the BSR format may be of a size based on the type of EH device the UE 602 is. In some aspects, the size of the BSR may be configured based on L1 signaling, L2 signaling, L3 signaling, or without signaling. In some aspects, based on length or size of time units to indicate network activity history, and based on number of bits for BSR, the network entity 604 may indicate the UE 602 to use more bits for network activity history of one or more particular LCGIDs or LCIDs or dedicate one or more LCIDs/LCGIDs for such report.

FIG. 9A is a diagram 900 illustrating another example of report of network activity history being multiplexed with BSR. The network entity 604 may assign dedicated LCID or LCGIDs which may be used for the network activity history. Therefore, resources associated with the dedicated LCGID or LCGIDs may be used for transmitting the network activity history 906, and the rest of the buffer status, such as buffer status #1 904A and buffer status #2 904B, are unaffected.

In some aspects, the network entity 604 or the UE 602 may interpret some PHY signals, such as signals for SR, BSR, PUSCH, PUCCH, HARQ-ACK, UL RACH with PDCCH order, or the like, as not received/transmitted if there is no energy for last one or more slot during a defined time window before the signal. For example, for HARQ ACK, there may be no power/energy to receive the corresponding PDSCH or PDSCHs within a window or a set of PDSCHs scheduled by a single DCI and such no energy may be interpreted as NACK. In some aspects, absence of a number of a particular type of UL channels may be mapped (e.g., interpreted by a network entity as) to a duration of UE being in an inactive state (e.g., due to lack of energy or performing energy harvesting cycle) where it cannot transmit or receive. In some aspects, the UE 602 may include the network activity history in one or more bits that is not used in a PHR, a BSR MAC-CE, or another type of signaling. For example, the one or more bits may be not used because one or more corresponding LCG buffers associated with one or more LCG IDs associated with the one or more bits in a BSR MAC-CE are empty, and there may be nothing to report for those LCG buffers. In some aspects, when an LCG ID bit flag is zero, which indicates that the UE has no data or BSR for the associated LCG ID, the UE may use the byte associated with the LCG bit flag to send the network activity history . In some aspects, the network may indicate, based on L1 signaling, L2 signaling, or L3 signaling, information indicative of which of the LCG IDs (and associated BSRs) where the UE may use the byte to send the network activity history when there the bit flag is zero. As another example, the one or more bits may be not used because one or more component carriers (CCs) associated with the one or more bits in a PHR may be not used. In some aspects, one or more unused bits associated with a particular CC may be used for reporting network activity associated with the particular CC, or other CCs. In some aspects, the network may indicate which CCs PHR may be used for reporting network activity associated with the particular CC, or other CCs. . The UE may be configured to use the one or more bits that may be unused based on L1 signaling, L2 signaling, L3 signaling, or without signaling. In some aspects, the UE may be configured to use the one or more bits in an order configured by the network entity 604. In some aspects, the NW can enable or disable the feature of multiplexing with the one or more L1 signaling, L2 signaling, or L3 signaling, (e.g., multiplexing with MAC-CEs such as MAC-CE multiplexing with BSR or PHR, among others) ) and also configure which LCGs BSRs or PHRs CCs, among other example, can be used to multiplex with. In the example of MAC-CEs, under the enabled feature of multiplexing, the UE may indicate in the MAC header which LCGs’ BSRs or CCs’ PHR is used for activity report. The UE may also include configuration of the activity report (e.g., size of how many reports are included, which may be indicated by a positive integer M) in the header. In some aspects, the UE may select which unused LCGs BSR bits or CCs’ PHR bits from the set of configured LCGs/CCs’ PHR by the network. In some aspects, the UE may determine which bits it used and which method of multiplexing the network activity history (e.g., using unused MAC-CE, using the reserved bits in the MAC-CE, or use portion of a byte) without signaling from the network. The UE may indicate, in the header, the bits used for multiplexing the network activity history.

FIG. 10A is a diagram 1000 illustrating an example of BSR. As illustrated in FIG. 10A, the BSR MAC-CE may include LCG ID #0, LCG ID #1, LCG ID #2, LCG ID #3, LCG ID #4, LCG ID #5, LCG ID #6, and LCG ID #7. The BSR MAC-CE may include a set of entries, where each entry may be a bit, a byte, one or more bits, or the like. An entry 1004A may be used for BSR of LCG ID #0, an entry 1004B may be used for BSR of LCG ID #1, an entry 1004C may be used for BSR of LCG ID #2, an entry 1004D may be used for BSR of LCG ID #3, an entry 1004E may be used for BSR of LCG ID #4, an entry 1004F may be used for BSR of LCG ID #5, an entry 1004G may be used for BSR of LCG ID #6, and an entry 1004H may be used for BSR of LCG ID #7.

FIG. 10B is a diagram 1050 illustrating an example of BSR with unused bits. As illustrated in FIG. 10B, the BSR MAC-CE may include an entry 1054B which may be used for BSR of LCG ID #1, an entry 1054D which may be used for BSR of LCG ID #3, an entry 1054E which may be used for BSR of LCG ID #4, and an entry 1054F which may be used for BSR of LCG ID #5. The BSR MAC-CE may also include one or more unused entries 1054A, 1054C, 1054G, and 1054H because there may be no BSR of LCG ID #0, BSR of LCG ID #2, BSR of LCG ID #6, or BSR of LCG ID #7. In some aspects, the unused entries may be transmitted as dummy bits.

FIG. 11A is a diagram 1100 illustrating an example of BSR with unused bits removed. As illustrated in FIG. 11A, the BSR MAC-CE may include an entry 1104B which may be used for BSR of LCG ID #1, an entry 1104D which may be used for BSR of LCG ID #3, an entry 1104E which may be used for BSR of LCG ID #4, an entry 1104F which may be used for BSR of LCG ID #5. The BSR MAC-CE may not include unused entries.

FIG. 11B is a diagram 1150 illustrating an example of network activity history being multiplexed with BSR. As illustrated in FIG. 11B, the BSR MAC-CE may include an entry 1154B which may be used for BSR of LCG ID #1, an entry 1154D which may be used for BSR of LCG ID #3, an entry 1154E which may be used for BSR of LCG ID #4, and an entry 1154F which may be used for BSR of LCG ID #5. The BSR MAC-CE may also include one or more entries 1154A, 1154C, 1154G, and 1154H that may be used for reporting network activity history because there may be no BSR of LCG ID #0, BSR of LCG ID #2, BSR of LCG ID #6, or BSR of LCG ID #7. In some aspects, the one or more entries 1154A, 1154C, 1154G, and 1154H may be used for reporting network activity history based on L1 signaling, L2 signaling, L3 signaling, or without signaling from the network. In some aspects, the UE 602 may include, in an header associated with the BSR MAC-CE, which one of the one or more entries 1154A, 1154C, 1154G, and 1154H is used for reporting network activity history.

In some aspects, instead of BSR MAC-CE, PHR MAC-CE may be multiplexed for reporting of network activity history. Each entry in the PHR MAC-CE may be respectively associated with a CC ID. For each CC ID that does not have a PHR to report, the UE 602 may be allowed, based on L1 signaling, L2 signaling, L3 signaling, or without signaling, to use the corresponding entry in the PHR MAC-CE for reporting of network activity history associated with the corresponding CC ID or other CC IDs. In some aspects, the UE 602 may include, in an header associated with the PHR MAC-CE, which one of the one or more entries is used for reporting network activity history.

FIG. 12 is a flowchart 1200 of a method of wireless communication. The method may be performed by first network entity, which may be a UE (e.g., the UE 104, the UE 602; the apparatus 1504) .

At 1210, the first network entity may transmit, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. For example, the UE 602 may transmit, at a first time to a second network entity 604, a first network activity history 616A associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, 1210 may be performed by history component 198.

At 1220, the first network entity may transmit, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. For example, the UE 602 may transmit, at a second time to the second network entity 604, a second network activity history 616B associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, 1220 may be performed by history component 198.

At 1230, the first network entity may communicate with the second network entity based on the first network activity history and the second network activity history. For example, the UE 602 may communicate with the second network entity based on the first network activity history and the second network activity history (e.g., at 618) . In some aspects, 1230 may be performed by history component 198.

FIG. 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by first network entity, which may be a UE (e.g., the UE 104, the UE 602; the apparatus 1504) .

At 1302, the first network entity may receive a configuration indicative of a time difference between the first time and the second time, or a wake-up signal configured to cause the first network entity to enter the active state. For example, the UE 602 may receive a configuration (e.g., 606) indicative of a time difference between the first time and the second time, or a wake-up signal (e.g., 607) configured to cause the first network entity to enter the active state (e.g., at 608) . In some aspects, 1306 may be performed by history component 198.

At 1310, the first network entity may transmit, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. For example, the UE 602 may transmit, at a first time to a second network entity 604, a first network activity history 616A associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, 1310 may be performed by history component 198.

At 1320, the first network entity may transmit, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. For example, the UE 602 may transmit, at a second time to the second network entity, a second network activity history 616B associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, 1320 may be performed by history component 198. In some aspects, a time difference between the first time and the second time is based on an energy state associated with the second network entity. In some aspects, the energy state includes at least one of an energy level profile of the second network entity including at least one of a current energy value or a future energy value associated with a first predicted duration, an energy charging profile of the second network entity including at least one of a current energy charging value or a future energy charging value associated with a second predicted duration, or an energy discharging profile of the second network entity including at least one of a current energy discharging value or a future energy discharging value associated with a third predicted duration.

As part of 1310 or 1320, in some aspects, at 1312, the first network entity may transmit the first network activity history or the second network activity history in a dedicated transmission. For example, the UE 602 may transmit the first network activity history 616A or the second network activity history 616B in a dedicated transmission. In some aspects, 1312 may be performed by history component 198.

As part of 1310 or 1320, in some aspects, at 1314, the first network entity may multiplex the first network activity history or the second network activity history with a CSI report, a PHR, an SR, a HARQ ACK, one or more RACH messages, a BSR, a response to a WUS, a cell WUS, UAI, or a PUSCH transmission. For example, the UE 602 may multiplex the first network activity history or the second network activity history with a CSI report, a PHR, an SR, a HARQ ACK, one or more RACH messages, a BSR, a response to a WUS, a cell WUS, UAI, or a PUSCH transmission (e.g., at 614A or 614B) . In some aspects, 1314 may be performed by history component 198. In some aspects, to multiplex the first network activity history or the second network activity history, the first network entity may multiplex the first network activity history or the second network activity history with the CSI report, the PHR, the SR, the HARQ ACK, the one or more of RACH messages (e.g., a first message for preamble which may be message A in 2-step RACH or preamble or RRC connection request which may be message 1 or message 3 in 4-step RACH, or the like) , the BSR, the response to WUS to wake up the UE, cell WUS, or the PUSCH transmission as a set of joint entries in a data structure configured independent of the second network entity. In some aspects, the term “cell WUS” may refer to a transmission from a UE to wake up a cell of a network. For example, upon receiving a cell WUS, a network entity may wake up to enter a DRX active time and remain active for the DRX active time. In some aspects, to multiplex the first network activity history or the second network activity history, the first network entity may include the first network activity history or the second network activity history in one or more bits associated with the CSI report, the PHR, the SR, the HARQ ACK, the one or more of RACH messages, the BSR, the response to WUS, cell WUS, the UAI, or the PUSCH transmission. In some aspects, to include the first network activity history or the second network activity history in one or more bits associated with the SR or the HARQ ACK, the first network entity may use a first cyclic shift for the first network activity history or the second network activity history, and use a second cyclic shift for the SR or the HARQ ACK, where the first cyclic shift is different from the second cyclic shift. In some aspects, to include the first network activity history or the second network activity history in one or more bits associated with the SR or the HARQ ACK, the first network entity may use a cyclic shift for the first network activity history or the second network activity history and the SR or the HARQ ACK, where the first network activity history or the second network activity history and the SR or the HARQ ACK are associated with one codebook. In some aspects, to include the first network activity history or the second network activity history in one or more bits in the SR or the HARQ ACK, the first network entity may include the first network activity history or the second network activity history in a first symbol and include the SR or the HARQ ACK in a second symbol. In some aspects, the BSR or the PHR is included in a MAC control element (MAC-CE) report, and where to include the first network activity history or the second network activity history in one or more bits in the BSR or the PHR, the first network entity may include the first network activity history or the second network activity history in one or more unused bits in the MAC-CE report. In some aspects, to multiplex the first network activity history or the second network activity history, the first network entity may include the first network activity history or the second network activity history in a set of time and frequency resources for one or more bits configured for indicating one or more quantities associated with the BSR, the SR, or the HARQ ACK. In some aspects, to multiplex the first network activity history or the second network activity history, the first network entity may multiplex the first network activity history or the second network activity history after encoding information in the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission. In some aspects, to multiplex the first network activity history or the second network activity history with the PUSCH transmission, the first network entity may multiplex first data of the first network activity history or the second network activity history and second data of the PUSCH transmission and perform low-density parity-check (LDPC) encoding after multiplexing the first data and the second data. In some aspects, to multiplex the first network activity history or the second network activity history with the PUSCH transmission, the first network entity may encode each bit stream associated with the PUSCH transmission and the first network activity history or the second network activity history based on respective encoder and include the first network activity history or the second network activity history in a set of time and frequency configured for UCI associated with the PUSCH transmission based on rate-matching or puncturing. In some aspects, to multiplex the first network activity history or the second network activity history with the PHR, the first network entity may use one or more reserved bits in the PHR to include the first network activity history or the second network activity history. In some aspects, to multiplex the first network activity history or the second network activity history with the SR, the first network entity may multiplex the first network activity history or the second network activity history with one or more SR occasions based on a logical channel identifier (LCID) or a logical channel group identifier (LCGID) associated with the one or more SR occasions.

As part of 1310 or 1320, in some aspects, at 1316, the first network entity may receive DCI indicative of a set of time and frequency resources configured for the first network activity history or the second network activity history. For example, the UE 602 may receive DCI (e.g., 612A or 612B) indicative of a set of time and frequency resources configured for the first network activity history or the second network activity history. In some aspects, 1316 may be performed by history component 198. In some aspects, to transmit the first network activity history or the second network activity history, the first network entity may transmit the first network activity history or the second network activity history based on the set of time and frequency resources.

In some aspects, a time difference between the first time and the second time corresponds to one or more occasions of a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a WUS, a cell WUS, UAI, or a PUSCH transmission. In some aspects, the first network entity may transmit the first network activity history or the second network activity history as a response to a wake-up signal configured to trigger the DRX ON interval. In some aspects, the first time or the second time corresponds to an end of a discontinuous reception (DRX) ON interval and the first network entity may transmit the first network activity history or the second network activity history in a dedicated transmission or multiplex the first network activity history or the second network activity history with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, a RACH message, a BSR, a response to a wake-up signal (WUS) , one or more RACH messages, a cell WUS, UAI, or a PUSCH transmission. In some aspects, to transmit the first network activity history, the first network entity may receive, from the second network entity, a request for the first network activity history, where the request includes information indicative of one or more resources for transmitting the first network activity history and the first network entity may transmit the first network activity history in the one or more resources. In some aspects, the request further includes information indicative of a time period, and where the first time is within the time period.

In some aspects, the first network entity may receive, from the second network entity, a transmission history including information indicative of one or more slots including transmission from the second network entity to the first network entity, where the transmission history is configured to be included in an L1 signaling, an L2 signaling, an L3 signaling, a wake-up signal configured to trigger the first network entity to enter the active state, or a PDSCH transmission. In some aspects, the first network entity is in the inactive state during a subset of the one or more slots, and where the first set of time units includes the subset of the one or more slots.

In some aspects, the first network entity may receive, from the second network entity, a transmission history including information indicative of one or more slots including a transport block (TB) for retransmission or a packet delay budget including information indicative of a slot available for transmission.

At 1330, the first network entity may communicate with the second network entity based on the first network activity history and the second network activity history. For example, the UE 602 may communicate with the second network entity based on the first network activity history and the second network activity history (e.g., at 618) . In some aspects, 1330 may be performed by history component 198.

As part of 1330, in some aspects, at 1332, the first network entity may receive a retransmission of one or more packets from the second network entity based on the first network activity history and the second network activity history. For example, the UE 602 may receive a retransmission (e.g., 620) of one or more packets from the second network entity based on the first network activity history and the second network activity history (e.g., to retransmit packets transmitted when the UE is off) . In some aspects, 1332 may be performed by history component 198.

As part of 1330, in some aspects, at 1334, the first network entity may determine a redundancy version of a retransmission for a PUCCH transmission or a PUSCH transmission to the second network entity based on the first network activity history and the second network activity history. For example, the UE 602 may determine a redundancy version of a retransmission for a PUCCH transmission or a PUSCH transmission to the second network entity based on the first network activity history and the second network activity history. In some aspects, 1334 may be performed by history component 198.

As part of 1330, in some aspects, at 1336, the first network entity may receive a groupcast signal from the second network entity based on the first network activity history and the second network activity history. For example, the UE 602 may receive a groupcast signal (e.g., 622) from the second network entity based on the first network activity history and the second network activity history. In some aspects, 1336 may be performed by history component 198.

FIG. 14 is a flowchart 1400 of a method of wireless communication. The method may be performed by a network entity (e.g., the base station 102, the network entity 604, the network entity 1502, the network entity 1602) .

At 1410, the network entity may receive, at a first time from a second network entity, a first network activity history associated with the second network entity, where the first network activity history includes information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. For example, the network entity 604 may receive, at a first time from a second network entity (e.g., UE 602) , a first network activity history 616A associated with the second network entity, where the first network activity history includes information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, 1410 may be performed by history component 199.

At 1420, the network entity may receive, at a second time from the second network entity, a second network activity history associated with the second network entity, where the second network activity history includes information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. For example, the network entity 604 may receive, at a second time from the second network entity, a second network activity history 616B associated with the second network entity, where the second network activity history includes information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, 1420 may be performed by history component 199.

In some aspects, the network entity may transmit a configuration (e.g., 606) indicative of a time difference between the first time and the second time, or a wake-up signal configured to cause the second network entity to enter the active state. In some aspects, a time difference between the first time and the second time is based on an energy state associated with the second network entity. In some aspects, the energy state includes at least one of an energy level profile of the second network entity including at least one of a current energy value or a future energy value associated with a first predicted duration, an energy charging profile of the second network entity including at least one of a current energy charging value or a future energy charging value associated with a second predicted duration, or an energy discharging profile of the second network entity including at least one of a current energy discharging value or a future energy discharging value associated with a third predicted duration.

In some aspects, the network entity may transmit DCI indicative of a set of time and frequency resources configured for the first network activity history or the second network activity history, where to receive the first network activity history or the second network activity history, the first network entity may receive the first network activity history or the second network activity history based on the set of time and frequency resources.

In some aspects, the first network activity history or the second network activity history is multiplexed with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more of RACH messages, a BSR, a response to a wake-up signal (WUS) , a cell WUS, UAI, or a PUSCH transmission. In some aspects, the first network activity history or the second network activity history is multiplexed with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to WUS, the cell WUS, the UAI, or the PUSCH transmission as a set of joint entries in a data structure configured independent of the second network entity. In some aspects, the first network activity history or the second network activity history is included in one or more bits associated with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission. In some aspects, the first network activity history or the second network activity history is included in one or more bits associated with the SR or the HARQ ACK, where the first network activity history or the second network activity history is based on a first cyclic shift, where the SR or the HARQ ACK is based on a second cyclic shift, and where the first cyclic shift is different from the second cyclic shift. In some aspects, the first network activity history or the second network activity history and the SR or the HARQ ACK is based on a cyclic shift, where the first network activity history or the second network activity history and the SR or the HARQ ACK are associated with one codebook.

In some aspects, the first network activity history or the second network activity history is included in a first symbol, and the SR or the HARQ ACK is included in a second symbol. In some aspects, the first network activity history or the second network activity history is included in a first symbol, and the SR or the HARQ ACK is included in a second symbol. In some aspects, the BSR or the PHR is included in a MAC-CE report, and the first network activity history or the second network activity history is included in one or more unused bits in the MAC-CE report. In some aspects, the first network activity history or the second network activity history is included in a set of time and frequency resources for one or more bits configured for indicating one or more quantities associated with the BSR, the SR, or the HARQ ACK.

In some aspects, the first network activity history or the second network activity history is multiplexed after encoding information in the CSI report, the PHR, the SR, the HARQ ACK, the one or more of RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission. In some aspects, first data of the first network activity history or the second network activity history is multiplexed with second data of the PUSCH transmission and low-density parity-check (LDPC) encoding is performed on the multiplexed first data and the second data. In some aspects, each bit stream associated with the PUSCH transmission and the first network activity history or the second network activity history is encoded based on respective encoder. In some aspects, the first network activity history or the second network activity history is included in a set of time and frequency configured for UCI associated with the PUSCH transmission based on rate-matching or puncturing. In some aspects, one or more reserved bits in the PHR includes the first network activity history or the second network activity history. In some aspects, the first network activity history or the second network activity history is multiplexed with one or more SR occasions based on a logical channel identifier (LCID) or a logical channel group identifier (LCGID) associated with the one or more SR occasions.

In some aspects, a time difference between the first time and the second time corresponds to one or more occasions of a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a WUS, a cell WUS, UAI, or a PUSCH transmission. In some aspects, the first time or the second time corresponds to a beginning of a discontinuous reception (DRX) ON interval, and where to receive the first network activity history or the second network activity history, the first network entity may receive the first network activity history or the second network activity history as a response to a wake-up signal configured to trigger the DRX ON interval. In some aspects, to receive the first network activity history, the first network entity may transmit, to the second network entity, a request for the first network activity history, where the request includes information indicative of one or more resources for transmitting the first network activity history and receive the first network activity history in the one or more resources. In some aspects, the request further includes information indicative of a time period, and where the first time is within the time period. In some aspects, the first network entity may transmit, to the second network entity, a transmission history including information indicative of one or more slots including transmission from the second network entity to the second network entity, where the transmission history is configured to be included in a layer 1 (L1) signaling, a layer 2 (L2) signaling, a layer 3 (L3) signaling, a wake-up signal configured to trigger the second network entity to enter the active state, or a PDSCH transmission. In some aspects, the second network entity is in the inactive state during a subset of the one or more slots, and where the first set of time units includes the subset of the one or more slots. In some aspects, the first network entity may receive, from the second network entity, a transmission history including information indicative of one or more slots including a transport block (TB) for retransmission or a packet delay budget including information indicative of a slot available for transmission.

At 1430, the network entity may communicate with the second network entity based on the first network activity history and the second network activity history. For example, the network entity 604 may communicate with the second network entity (e.g., UE 602) based on the first network activity history and the second network activity history (e.g., at 618) . In some aspects, 1430 may be performed by history component 199. In some aspects, to communicate with the second network entity based on the first network activity history and the second network activity history, the first network entity may transmit a retransmission of one or more packets to the second network entity based on the first network activity history and the second network activity history. In some aspects, to communicate with the second network entity based on the first network activity history and the second network activity history, the first network entity may determine (e.g., and use) a redundancy version of a retransmission for a PUCCH transmission or a PUSCH transmission to the second network entity based on the first network activity history and the second network activity history. In some aspects, to communicate with the second network entity based on the first network activity history and the second network activity history, the first network entity may transmit a groupcast signal to the second network entity based on the first network activity history and the second network activity history.

FIG. 15 is a diagram 1500 illustrating an example of a hardware implementation for an apparatus 1504. The apparatus 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., cellular RF transceiver) . The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the apparatus 1504 may further include one or more subscriber identity modules (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the apparatus 1504 may further include a Bluetooth module 1512, a WLAN module 1514, a satellite system module 1516 (e.g., GNSS module) , one or more sensor modules 1518 (e.g., barometric pressure sensor /altimeter; motion sensor such as inertial management unit (IMU) , gyroscope, and/or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and/or other technologies used for positioning) , additional memory modules 1526, a power supply 1530, and/or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the satellite system module 1516 may include an on-chip transceiver (TRX) /receiver (RX) . The cellular baseband processor 1524 communicates through the transceiver (s) 1522 via one or more antennas 1580 with the UE 104 and/or with an RU associated with a network entity 1502. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium /memory 1524', 1506', respectively. The additional memory modules 1526 may also be considered a computer-readable medium /memory. Each computer-readable medium /memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the cellular baseband processor 1524 /application processor 1506, causes the cellular baseband processor 1524 /application processor 1506 to perform the various functions described herein. The computer-readable medium /memory may also be used for storing data that is manipulated by the cellular baseband processor 1524 /application processor 1506 when executing software. The cellular baseband processor 1524 /application processor 1506 may be a component of the UE 350 and may include the memory 360 and/or at least one of the TX processor 368, the RX processor 356, and the controller/processor 359. In one configuration, the apparatus 1504 may be a processor chip (modem and/or application) and include just the cellular baseband processor 1524 and/or the application processor 1506, and in another configuration, the apparatus 1504 may be the entire UE (e.g., see 350 of FIG. 3) and include the additional modules of the apparatus 1504.

As discussed herein, the history component 198 may be configured to transmit, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, the history component 198 may be further configured to transmit, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, the history component 198 may be further configured to communicate with the second network entity based on the first network activity history and the second network activity history. The history component 198 may be within the cellular baseband processor 1524, the application processor 1506, or both the cellular baseband processor 1524 and the application processor 1506. The history component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the apparatus 1504 may include a variety of components configured for various functions. In one configuration, the apparatus 1504, and in particular the cellular baseband processor 1524 and/or the application processor 1506, includes means for transmitting, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, the apparatus 1504 may further include means for transmitting, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, the apparatus 1504 may further include means for communicating with the second network entity based on the first network activity history and the second network activity history. In some aspects, the apparatus 1504 may further include means for receiving a configuration indicative of a time difference between the first time and the second time, or a wake-up signal configured to cause the first network entity to enter the active state. In some aspects, the apparatus 1504 may further include means for receiving DCI indicative of a set of time and frequency resources configured for the first network activity history or the second network activity history, where to transmit the first network activity history or the second network activity history, the apparatus 1504 may further included means for transmitting the first network activity history or the second network activity history based on the set of time and frequency resources. In some aspects, the apparatus 1504 may further include means for multiplexing the first network activity history or the second network activity history with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a buffer status report (BSR) , a response to a wake-up signal (WUS) , a cell WUS, UAI, or a PUSCH transmission. In some aspects, the apparatus 1504 may further include means for multiplexing the first network activity history or the second network activity history with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission as a set of joint entries in a data structure configured independent of the second network entity. In some aspects, the apparatus 1504 may further include means for including the first network activity history or the second network activity history in one or more bits associated with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission. In some aspects, the apparatus 1504 may further include means for using a first cyclic shift for the first network activity history or the second network activity history. In some aspects, the apparatus 1504 may further include means for using a second cyclic shift for the SR or the HARQ ACK, where the first cyclic shift is different from the second cyclic shift. In some aspects, the apparatus 1504 may further include means for using a cyclic shift for the first network activity history or the second network activity history and the SR or the HARQ ACK, where the first network activity history or the second network activity history and the SR or the HARQ ACK are associated with one codebook. In some aspects, the apparatus 1504 may further include means for including the first network activity history or the second network activity history in a first symbol. In some aspects, the apparatus 1504 may further include means for including the SR or the HARQ ACK in a second symbol. In some aspects, the apparatus 1504 may further include means for including the first network activity history or the second network activity history in a first symbol. In some aspects, the apparatus 1504 may further include means for including the SR or the HARQ ACK in a second symbol. In some aspects, the apparatus 1504 may further include means for including the first network activity history or the second network activity history in one or more unused bits in the MAC-CE report. In some aspects, the apparatus 1504 may further include means for including the first network activity history or the second network activity history in a set of time and frequency resources for one or more bits configured for indicating one or more quantities associated with the BSR, the SR, or the HARQ ACK. In some aspects, the apparatus 1504 may further include means for multiplexing the first network activity history or the second network activity history after encoding information in the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission. In some aspects, the apparatus 1504 may further include means for multiplexing first data of the first network activity history or the second network activity history and second data of the PUSCH transmission. In some aspects, the apparatus 1504 may further include means for performing low-density parity-check (LDPC) encoding after multiplexing the first data and the second data. In some aspects, the apparatus 1504 may further include means for encoding each bit stream associated with the PUSCH transmission and the first network activity history or the second network activity history based on respective encoder. In some aspects, the apparatus 1504 may further include means for including the first network activity history or the second network activity history in a set of time and frequency configured for UCI associated with the PUSCH transmission based on rate-matching or puncturing. In some aspects, the apparatus 1504 may further include means for using one or more reserved bits in the PHR to include the first network activity history or the second network activity history. In some aspects, the apparatus 1504 may further include means for multiplexing the first network activity history or the second network activity history with one or more SR occasions based on a logical channel identifier (LCID) or a logical channel group identifier (LCGID) associated with the one or more SR occasions. In some aspects, the apparatus 1504 may further include means for transmitting the first network activity history or the second network activity history as a response to a wake-up signal configured to trigger the DRX ON interval. In some aspects, the apparatus 1504 may further include means for transmitting the first network activity history or the second network activity history in a dedicated transmission or multiplex the first network activity history or the second network activity history with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a buffer status report (BSR) , a response to a wake-up signal (WUS) , a cell WUS, UAI, or a PUSCH transmission. In some aspects, the apparatus 1504 may further include means for receiving, from the second network entity, a request for the first network activity history, where the request includes information indicative of one or more resources for transmitting the first network activity history. In some aspects, the apparatus 1504 may further include means for transmitting the first network activity history in the one or more resources. In some aspects, the apparatus 1504 may further include means for receiving, from the second network entity, a transmission history including information indicative of one or more slots including transmission from the second network entity to the first network entity, where the transmission history is configured to be included in a layer 1 (L1) signaling, a layer 2 (L2) signaling, a layer 3 (L3) signaling, a wake-up signal configured to trigger the first network entity to enter the active state, or a PDSCH transmission. In some aspects, the apparatus 1504 may further include means for receiving, from the second network entity, a transmission history including information indicative of one or more slots including a transport block (TB) for retransmission or a packet delay budget including information indicative of a slot available for transmission. In some aspects, the apparatus 1504 may further include means for receiving a retransmission of one or more packets from the second network entity based on the first network activity history and the second network activity history. In some aspects, the apparatus 1504 may further include means for determining a redundancy version of a retransmission for a PUCCH transmission or a PUSCH transmission to the second network entity based on the first network activity history and the second network activity history. In some aspects, the apparatus 1504 may further include means for receiving a groupcast signal from the second network entity based on the first network activity history and the second network activity history. The means may be the history component 198 of the apparatus 1504 configured to perform the functions recited by the means. As described herein, the apparatus 1504 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the means.

FIG. 16 is a diagram 1600 illustrating an example of a hardware implementation for a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or an RU 1640. For example, depending on the layer functionality handled by the component 199, the network entity 1602 may include the CU 1610; both the CU 1610 and the DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both the DU 1630 and the RU 1640; or the RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include on-chip memory 1612'. In some aspects, the CU 1610 may further include additional memory modules 1614 and a communications interface 1618. The CU 1610 communicates with the DU 1630 through a midhaul link, such as an F1 interface. The DU 1630 may include a DU processor 1632. The DU processor 1632 may include on-chip memory 1632'. In some aspects, the DU 1630 may further include additional memory modules 1634 and a communications interface 1638. The DU 1630 communicates with the RU 1640 through a fronthaul link. The RU 1640 may include an RU processor 1642. The RU processor 1642 may include on-chip memory 1642'. In some aspects, the RU 1640 may further include additional memory modules 1644, one or more transceivers 1646, antennas 1680, and a communications interface 1648. The RU 1640 communicates with the UE 104. The on-chip memory 1612', 1632', 1642' and the additional memory modules 1614, 1634, 1644 may each be considered a computer-readable medium /memory. Each computer-readable medium /memory may be non-transitory. Each of the processors 1612, 1632, 1642 is responsible for general processing, including the execution of software stored on the computer-readable medium /memory. The software, when executed by the corresponding processor (s) causes the processor (s) to perform the various functions described herein. The computer-readable medium /memory may also be used for storing data that is manipulated by the processor (s) when executing software.

As discussed herein, the history component 199 may be configured to receive, at a first time from a second network entity, a first network activity history associated with the second network entity, where the first network activity history includes information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, the history component 199 may be further configured to receive, at a second time from the second network entity, a second network activity history associated with the second network entity, where the second network activity history includes information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, the history component 199 may be further configured to communicate with the second network entity based on the first network activity history and the second network activity history. The history component 199 may be within one or more processors of one or more of the CU 1610, DU 1630, and the RU 1640. The history component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1602 may include a variety of components configured for various functions. In one configuration, the network entity 1602 includes means for receiving, at a first time from a second network entity, a first network activity history associated with the second network entity, where the first network activity history includes information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time. In some aspects, the network entity 1602 may further include means for receiving, at a second time from the second network entity, a second network activity history associated with the second network entity, where the second network activity history includes information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time. In some aspects, the network entity 1602 may further include means for communicating with the second network entity based on the first network activity history and the second network activity history. The means may be the history component 199 of the network entity 1602 configured to perform the functions recited by the means. As described herein, the network entity 1602 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means.

It is understood that the specific order or hierarchy of blocks in the processes /flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes /flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.

The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”

As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.

Aspect 1 is a first network entity for wireless communication, including: a memory; and at least one processor coupled to the memory, where the at least one processor is configured to: transmit, at a first time to a second network entity, a first network activity history associated with the first network entity, where the first network activity history includes information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time; transmit, at a second time to the second network entity, a second network activity history associated with the first network entity, where the second network activity history includes information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time; and communicate with the second network entity based on the first network activity history and the second network activity history.

Aspect 2 is the first network entity of aspect 1, where the at least one processor is configured to: receive a configuration indicative of a time difference between the first time and the second time, or a wake-up signal configured to cause the first network entity to enter the active state.

Aspect 3 is the first network entity of any of aspect 1-2, where a time difference between the first time and the second time is based on an energy state associated with the first network entity, and where the energy state includes at least one of: an energy level profile of the first network entity including at least one of a current energy value or a future energy value associated with a first predicted duration, an energy charging profile of the first network entity including at least one of a current energy charging value or a future energy charging value associated with a second predicted duration, or an energy discharging profile of the first network entity including at least one of a current energy discharging value or a future energy discharging value associated with a third predicted duration.

Aspect 4 is the first network entity of any of aspect 1-3, where the at least one processor is configured to: receive DCI indicative of a set of time and frequency resources configured for the first network activity history or the second network activity history, where to transmit the first network activity history or the second network activity history, the at least one processor is configured to transmit the first network activity history or the second network activity history based on the set of time and frequency resources.

Aspect 5 is the first network entity of any of aspect 1-4, where to transmit the first network activity history or the second network activity history, the at least one processor is configured to: multiplex the first network activity history or the second network activity history with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a wake-up signal (WUS) , a cell WUS, UAI, or a PUSCH transmission.

Aspect 6 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history, the at least one processor is configured to: multiplex the first network activity history or the second network activity history with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission as a set of joint entries in a data structure configured independent of the second network entity.

Aspect 7 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history, the at least one processor is configured to: include the first network activity history or the second network activity history in one or more bits associated with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission.

Aspect 8 is the first network entity of aspect 7, where to include the first network activity history or the second network activity history in one or more bits associated with the SR or the HARQ ACK, the at least one processor is configured to: use a first cyclic shift for the first network activity history or the second network activity history; and use a second cyclic shift for the SR or the HARQ ACK, where the first cyclic shift is different from the second cyclic shift.

Aspect 9 is the first network entity of aspect 7, where to include the first network activity history or the second network activity history in one or more bits associated with the SR or the HARQ ACK, the at least one processor is configured to: use a cyclic shift for the first network activity history or the second network activity history and the SR or the HARQ ACK, where the first network activity history or the second network activity history and the SR or the HARQ ACK are associated with one codebook.

Aspect 10 is the first network entity of aspect 7, where to include the first network activity history or the second network activity history in one or more bits in the SR or the HARQ ACK, the at least one processor is configured to: include the first network activity history or the second network activity history in a first symbol; and include the SR or the HARQ ACK in a second symbol.

Aspect 11 is the first network entity of aspect 7, where to include the first network activity history or the second network activity history in one or more bits in the SR or the HARQ ACK, the at least one processor is configured to: include the first network activity history or the second network activity history in a first symbol; and include the SR or the HARQ ACK in a second symbol.

Aspect 12 is the first network entity of aspect 7, where the BSR or the PHR is included in a MAC control element (MAC-CE) report, and where to include the first network activity history or the second network activity history in one or more bits in the BSR or the PHR, the at least one processor is configured to: include the first network activity history or the second network activity history in one or more unused bits in the MAC-CE report.

Aspect 13 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history, the at least one processor is configured to: include the first network activity history or the second network activity history in a set of time and frequency resources for one or more bits configured for indicating one or more quantities associated with the BSR, the SR, or the HARQ ACK.

Aspect 14 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history, the at least one processor is configured to: multiplex the first network activity history or the second network activity history after encoding information in the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission.

Aspect 15 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history with the PUSCH transmission, the at least one processor is configured to: multiplex first data of the first network activity history or the second network activity history and second data of the PUSCH transmission; and perform low-density parity-check (LDPC) encoding after multiplexing the first data and the second data.

Aspect 16 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history with the PUSCH transmission, the at least one processor is configured to: encode each bit stream associated with the PUSCH transmission and the first network activity history or the second network activity history based on respective encoder; and include the first network activity history or the second network activity history in a set of time and frequency configured for UCI associated with the PUSCH transmission based on rate-matching or puncturing.

Aspect 17 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history with the PHR, the at least one processor is configured to: use one or more reserved bits in the PHR to include the first network activity history or the second network activity history.

Aspect 18 is the first network entity of aspect 5, where to multiplex the first network activity history or the second network activity history with the SR, the at least one processor is configured to: multiplex the first network activity history or the second network activity history with one or more SR occasions based on a logical channel identifier (LCID) or a logical channel group identifier (LCGID) associated with the one or more SR occasions.

Aspect 19 is the first network entity of any of aspect 1-18, where a time difference between the first time and the second time corresponds to one or more occasions of a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a WUS, a cell WUS, UAI, or a PUSCH transmission.

Aspect 20 is the first network entity of any of aspect 1-19, where the first time or the second time corresponds to a beginning of a discontinuous reception (DRX) ON interval, and where to transmit the first network activity history or the second network activity history, the at least one processor is configured to: transmit the first network activity history or the second network activity history as a response to a wake-up signal configured to trigger the DRX ON interval.

Aspect 21 is the first network entity of any of aspect 1-20, where the first time or the second time corresponds to an end of a discontinuous reception (DRX) ON interval, and where to transmit the first network activity history or the second network activity history, the at least one processor is configured to: transmit the first network activity history or the second network activity history in a dedicated transmission or multiplex the first network activity history or the second network activity history with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a wake-up signal (WUS) , a cell WUS, UAI, or a PUSCH transmission.

Aspect 22 is the first network entity of any of aspect 1-21, where to transmit the first network activity history, the at least one processor is configured to: receive, from the second network entity, a request for the first network activity history, where the request includes information indicative of one or more resources for transmitting the first network activity history; and transmit the first network activity history in the one or more resources.

Aspect 23 is the first network entity of aspect 22, where the request further includes information indicative of a time period, and where the first time is within the time period.

Aspect 24 is the first network entity of any of aspect 1-23, where the at least one processor is configured to: receive, from the second network entity, a transmission history including information indicative of one or more slots including transmission from the second network entity to the first network entity, where the transmission history is configured to be included in a layer 1 (L1) signaling, a layer 2 (L2) signaling, a layer 3 (L3) signaling, a wake-up signal configured to trigger the first network entity to enter the active state, or a PDSCH transmission.

Aspect 25 is the first network entity of aspect 24, where the first network entity is in the inactive state during a subset of the one or more slots, and where the first set of time units includes the subset of the one or more slots.

Aspect 26 is the first network entity of any of aspect 1-25, where the at least one processor is configured to: receive, from the second network entity, a transmission history including information indicative of one or more slots including a transport block (TB) for retransmission or a packet delay budget including information indicative of a slot available for transmission.

Aspect 27 is the first network entity of any of aspect 1-26, where to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to: receive a retransmission of one or more packets from the second network entity based on the first network activity history and the second network activity history.

Aspect 28 is the first network entity of any of aspect 1-27, where to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to: determine a redundancy version of a retransmission for a PUCCH transmission or a PUSCH transmission to the second network entity based on the first network activity history and the second network activity history.

Aspect 29 is the first network entity of any of aspect 1-28, where to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to: receive a groupcast signal from the second network entity based on the first network activity history and the second network activity history.

Aspect 30 is a first network entity for wireless communication, including: a memory; and at least one processor coupled to the memory, where the at least one processor is configured to: receive, at a first time from a second network entity, a first network activity history associated with the second network entity, where the first network activity history includes information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time; receive, at a second time from the second network entity, a second network activity history associated with the second network entity, where the second network activity history includes information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time; and communicate with the second network entity based on the first network activity history and the second network activity history.

Aspect 31 is the first network entity of aspect 30, where the at least one processor is configured to: transmit a configuration indicative of a time difference between the first time and the second time, or a wake-up signal configured to cause the second network entity to enter the active state.

Aspect 32 is the first network entity of any of aspect 30-31, where a time difference between the first time and the second time is based on an energy state associated with the second network entity, and where the energy state includes at least one of: an energy level profile of the second network entity including at least one of a current energy value or a future energy value associated with a first predicted duration, an energy charging profile of the second network entity including at least one of a current energy charging value or a future energy charging value associated with a second predicted duration, or an energy discharging profile of the second network entity including at least one of a current energy discharging value or a future energy discharging value associated with a third predicted duration.

Aspect 33 is the first network entity of any of aspect 30-32, where the at least one processor is configured to: transmit DCI indicative of a set of time and frequency resources configured for the first network activity history or the second network activity history, where to receive the first network activity history or the second network activity history, the at least one processor is configured to receive the first network activity history or the second network activity history based on the set of time and frequency resources.

Aspect 34 is the first network entity of any of aspect 30-33, where the first network activity history or the second network activity history is multiplexed with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a wake-up signal (WUS) , a cell WUS, UAI, or a PUSCH transmission.

Aspect 35 is the first network entity of aspect 34, where the first network activity history or the second network activity history is multiplexed with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission as a set of joint entries in a data structure configured independent of the second network entity.

Aspect 36 is the first network entity of aspect 34, the first network activity history or the second network activity history is included in one or more bits associated with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission.

Aspect 37 is the first network entity of aspect 36, where the first network activity history or the second network activity history is included in one or more bits associated with the SR or the HARQ ACK, where the first network activity history or the second network activity history is based on a first cyclic shift; and the SR or the HARQ ACK is based on a second cyclic shift, where the first cyclic shift is different from the second cyclic shift.

Aspect 38 is the first network entity of aspect 36, where the first network activity history or the second network activity history and the SR or the HARQ ACK is based on a cyclic shift, where the first network activity history or the second network activity history and the SR or the HARQ ACK are associated with one codebook.

Aspect 39 is the first network entity of aspect 36, where the first network activity history or the second network activity history is included in a first symbol; and the SR or the HARQ ACK is included in a second symbol.

Aspect 40 is the first network entity of aspect 36, where the first network activity history or the second network activity history is included in a first symbol; and the SR or the HARQ ACK is included in a second symbol.

Aspect 41 is the first network entity of aspect 36, where the BSR or the PHR is included in a MAC control element (MAC-CE) report, and the first network activity history or the second network activity history is included in one or more unused bits in the MAC-CE report.

Aspect 42 is the first network entity of aspect 34, where the first network activity history or the second network activity history is included in a set of time and frequency resources for one or more bits configured for indicating one or more quantities associated with the BSR, the SR, or the HARQ ACK.

Aspect 43 is the first network entity of aspect 34, where the first network activity history or the second network activity history is multiplexed after encoding information in the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the cell WUS, the UAI, or the PUSCH transmission.

Aspect 44 is the first network entity of aspect 34, first data of the first network activity history or the second network activity history is multiplexed with second data of the PUSCH transmission; and low-density parity-check (LDPC) encoding is performed on the multiplexed first data and the second data.

Aspect 45 is the first network entity of aspect 34, where each bit stream associated with the PUSCH transmission and the first network activity history or the second network activity history is encoded based on respective encoder; and the first network activity history or the second network activity history is included in a set of time and frequency configured for UCI associated with the PUSCH transmission based on rate-matching or puncturing.

Aspect 46 is the first network entity of aspect 34, where one or more reserved bits in the PHR includes the first network activity history or the second network activity history.

Aspect 47 is the first network entity of aspect 34, where to the first network activity history or the second network activity history is multiplexed with one or more SR occasions based on a logical channel identifier (LCID) or a logical channel group identifier (LCGID) associated with the one or more SR occasions.

Aspect 48 is the first network entity of any of aspect 30-47, where a time difference between the first time and the second time corresponds to one or more occasions of a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a WUS, a cell WUS, UAI, or a PUSCH transmission.

Aspect 49 is the first network entity of any of aspect 30-48, where the first time or the second time corresponds to a beginning of a discontinuous reception (DRX) ON interval, and where to receive the first network activity history or the second network activity history, the at least one processor is configured to: receive the first network activity history or the second network activity history as a response to a wake-up signal configured to trigger the DRX ON interval.

Aspect 50 is the first network entity of any of aspect 30-49, where the first time or the second time corresponds to an end of a discontinuous reception (DRX) ON interval, and where to receive the first network activity history or the second network activity history, the at least one processor is configured to: receive the first network activity history or the second network activity history in a dedicated transmission or the first network activity history or the second network activity history is multiplexed with a CSI report, a powerhead room report (PHR) , a scheduling request (SR) , a HARQ ACK, one or more RACH messages, a BSR, a response to a wake-up signal (WUS) , a cell WUS, UAI, or a PUSCH transmission.

Aspect 51 is the first network entity of any of aspect 30-50, where to receive the first network activity history, the at least one processor is configured to: transmit, to the second network entity, a request for the first network activity history, where the request includes information indicative of one or more resources for transmitting the first network activity history; and receive the first network activity history in the one or more resources.

Aspect 52 is the first network entity of aspect 51, where the request further includes information indicative of a time period, and where the first time is within the time period.

Aspect 53 is the first network entity of any of aspect 30-52, where the at least one processor is configured to: transmit, to the second network entity, a transmission history including information indicative of one or more slots including transmission from the second network entity to the second network entity, where the transmission history is configured to be included in a layer 1 (L1) signaling, a layer 2 (L2) signaling, a layer 3 (L3) signaling, a wake-up signal configured to trigger the second network entity to enter the active state, or a PDSCH transmission.

Aspect 54 is the first network entity of aspect 42, where the second network entity is in the inactive state during a subset of the one or more slots, and where the first set of time units includes the subset of the one or more slots.

Aspect 55 is the first network entity of any of aspect 30-54, where the at least one processor is configured to: receive, from the second network entity, a transmission history including information indicative of one or more slots including a transport block (TB) for retransmission or a packet delay budget including information indicative of a slot available for transmission.

Aspect 56 is the first network entity of any of aspect 30-55, where to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to: transmit a retransmission of one or more packets to the second network entity based on the first network activity history and the second network activity history.

Aspect 57 is the first network entity of any of aspect 30-56, where to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to: determine a redundancy version of a retransmission for a PUCCH transmission or a PUSCH transmission to the second network entity based on the first network activity history and the second network activity history.

Aspect 58 is the first network entity of any of aspect 30-57, where to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to: transmit a groupcast signal to the second network entity based on the first network activity history and the second network activity history.

Aspect 59 is a method of wireless communication for implementing any of aspects 1 to 29.

Aspect 60 is an apparatus for wireless communication including means for implementing any of aspects 1 to 29.

Aspect 61 is a computer-readable medium (e.g., a non-transitory computer-readable medium) having code stored thereon that, when executed by an apparatus, causes the apparatus to implement any of aspects 1 to 29.

Aspect 62 is a method of wireless communication for implementing any of aspects 30 to 58.

Aspect 63 is an apparatus for wireless communication including means for implementing any of aspects 30 to 58.

Aspect 64 is a computer-readable medium (e.g., a non-transitory computer-readable medium) having code stored thereon that, when executed by an apparatus, causes the apparatus to implement any of aspects 30 to 58.

Claims

A first network entity for wireless communication, comprising:

a memory; and

at least one processor coupled to the memory, wherein the at least one processor is configured to:

transmit, at a first time to a second network entity, a first network activity history associated with the first network entity, wherein the first network activity history comprises information indicative of whether the first network entity in an active state or an inactive state for each time unit in a first set of time units before the first time;

transmit, at a second time to the second network entity, a second network activity history associated with the first network entity, wherein the second network activity history comprises information indicative of whether the first network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time; and

communicate with the second network entity based on the first network activity history and the second network activity history.
The first network entity of claim 1, wherein the at least one processor is configured to:

receive a configuration indicative of a time difference between the first time and the second time, or a wake-up signal configured to cause the first network entity to enter the active state.
The first network entity of claim 1, wherein a time difference between the first time and the second time is based on an energy state associated with the first network entity, and wherein the energy state comprises at least one of:

an energy level profile of the first network entity including at least one of a current energy value or a future energy value associated with a first predicted duration,

an energy charging profile of the first network entity including at least one of a current energy charging value or a future energy charging value associated with a second predicted duration, or

an energy discharging profile of the first network entity including at least one of a current energy discharging value or a future energy discharging value associated with a third predicted duration.
The first network entity of claim 1, wherein the at least one processor is configured to:

receive downlink control information (DCI) indicative of a set of time and frequency resources configured for the first network activity history or the second network activity history, wherein to transmit the first network activity history or the second network activity history, the at least one processor is configured to transmit the first network activity history or the second network activity history based on the set of time and frequency resources.
The first network entity of claim 1, wherein to transmit the first network activity history or the second network activity history, the at least one processor is configured to:

multiplex the first network activity history or the second network activity history with a channel state information (CSI) report, a powerhead room report (PHR) , a scheduling request (SR) , a hybrid automatic repeat request (HARQ) acknowledgment (ACK) , one or more random access channel (RACH) messages, a buffer status report (BSR) , a response to a wake-up signal (WUS) , a cell WUS, UE assistance information (UAI) , or a physical uplink shared channel (PUSCH) transmission.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history, the at least one processor is configured to:

multiplex the first network activity history or the second network activity history with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to WUS, the cell WUS, the UAI, or the PUSCH transmission as a set of joint entries in a data structure configured independent of the second network entity.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history, the at least one processor is configured to:

include the first network activity history or the second network activity history in one or more bits associated with the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to WUS, the cell WUS, the UAI, or the PUSCH transmission.
The first network entity of claim 7, wherein to include the first network activity history or the second network activity history in one or more bits associated with the SR or the HARQ ACK, the at least one processor is configured to:

use a first cyclic shift for the first network activity history or the second network activity history; and

use a second cyclic shift for the SR or the HARQ ACK, wherein the first cyclic shift is different from the second cyclic shift.
The first network entity of claim 7, wherein to include the first network activity history or the second network activity history in one or more bits associated with the SR or the HARQ ACK, the at least one processor is configured to:

use a cyclic shift for the first network activity history or the second network activity history and the SR or the HARQ ACK, wherein the first network activity history or the second network activity history and the SR or the HARQ ACK are associated with one codebook.
The first network entity of claim 7, wherein to include the first network activity history or the second network activity history in one or more bits in the SR or the HARQ ACK, the at least one processor is configured to:

include the first network activity history or the second network activity history in a first symbol; and

include the SR or the HARQ ACK in a second symbol.
The first network entity of claim 7, wherein to include the first network activity history or the second network activity history in one or more bits in the SR or the HARQ ACK, the at least one processor is configured to:

include the first network activity history or the second network activity history in a first symbol; and

include the SR or the HARQ ACK in a second symbol.
The first network entity of claim 7, wherein the BSR or the PHR is included in a medium access control (MAC) control element (MAC-CE) report, and wherein to include the first network activity history or the second network activity history in one or more bits in the BSR or the PHR, the at least one processor is configured to:

include the first network activity history or the second network activity history in one or more unused bits in the MAC-CE report.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history, the at least one processor is configured to:

include the first network activity history or the second network activity history in a set of time and frequency resources for one or more bits configured for indicating one or more quantities associated with the BSR, the SR, or the HARQ ACK.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history, the at least one processor is configured to:

multiplex the first network activity history or the second network activity history after encoding first information in the CSI report, the PHR, the SR, the HARQ ACK, the one or more RACH messages, the BSR, the response to the WUS, the UAI, or the PUSCH transmission.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history with the PUSCH transmission, the at least one processor is configured to:

multiplex first data of the first network activity history or the second network activity history and second data of the PUSCH transmission; and

perform low-density parity-check (LDPC) encoding after multiplexing the first data and the second data.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history with the PUSCH transmission, the at least one processor is configured to:

encode each bit stream associated with the PUSCH transmission and the first network activity history or the second network activity history based on respective encoder; and

include the first network activity history or the second network activity history in a set of time and frequency configured for uplink control information (UCI) associated with the PUSCH transmission based on rate-matching or puncturing.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history with the PHR, the at least one processor is configured to:

use one or more reserved bits in the PHR to include the first network activity history or the second network activity history.
The first network entity of claim 5, wherein to multiplex the first network activity history or the second network activity history with the SR, the at least one processor is configured to:

multiplex the first network activity history or the second network activity history with one or more SR occasions based on a logical channel identifier (LCID) or a logical channel group identifier (LCGID) associated with the one or more SR occasions.
The first network entity of claim 1, wherein a time difference between the first time and the second time corresponds to one or more occasions of a channel state information (CSI) report, a powerhead room report (PHR) , a scheduling request (SR) , a hybrid automatic repeat request (HARQ) acknowledgment (ACK) , one or more random access channel (RACH) messages, a buffer status report (BSR) , UE assistance information (UAI) , or a physical uplink shared channel (PUSCH) transmission.
The first network entity of claim 1, wherein the first time or the second time corresponds to a beginning of a discontinuous reception (DRX) ON interval, and wherein to transmit the first network activity history or the second network activity history, the at least one processor is configured to:

transmit the first network activity history or the second network activity history as a response to a wake-up signal configured to trigger the DRX ON interval.
The first network entity of claim 1, wherein the first time or the second time corresponds to an end of a discontinuous reception (DRX) ON interval, and wherein to transmit the first network activity history or the second network activity history, the at least one processor is configured to:

transmit the first network activity history or the second network activity history in a dedicated transmission or multiplex the first network activity history or the second network activity history with a channel state information (CSI) report, a powerhead room report (PHR) , a scheduling request (SR) , a hybrid automatic repeat request (HARQ) acknowledgment (ACK) , one or more random access channel (RACH) messages, a buffer status report (BSR) , a response to a wake-up signal (WUS) , a cell WUS, UE assistance information (UAI) , or a physical uplink shared channel (PUSCH) transmission.
The first network entity of claim 1, wherein to transmit the first network activity history, the at least one processor is configured to:

receive, from the second network entity, a request for the first network activity history, wherein the request comprises information indicative of one or more resources for transmitting the first network activity history; and

transmit the first network activity history in the one or more resources.
The first network entity of claim 22, wherein the request further comprises information indicative of a time period, and wherein the first time is within the time period.
The first network entity of claim 1, wherein the at least one processor is configured to:

receive, from the second network entity, a transmission history comprising information indicative of one or more slots comprising transmission from the second network entity to the first network entity, wherein the transmission history is configured to be included in a layer 1 (L1) signaling, a layer 2 (L2) signaling, a layer 3 (L3) signaling, a wake-up signal configured to trigger the first network entity to enter the active state, or a physical downlink shared channel (PDSCH) transmission.
The first network entity of claim 24, wherein the first network entity is in the inactive state during a subset of the one or more slots, and wherein the first set of time units comprises the subset of the one or more slots.
The first network entity of claim 1, wherein the at least one processor is configured to:

receive, from the second network entity, a transmission history comprising information indicative of one or more slots comprising a transport block (TB) for retransmission or a packet delay budget comprising information indicative of a slot available for transmission.
The first network entity of claim 1, wherein to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to:

receive a retransmission of one or more packets from the second network entity based on the first network activity history and the second network activity history.
The first network entity of claim 1, wherein to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to:

determine a redundancy version (RV) of a retransmission for a physical uplink control channel (PUCCH) transmission or a physical uplink shared channel (PUSCH) transmission to the second network entity based on the first network activity history and the second network activity history.
The first network entity of claim 1, wherein to communicate with the second network entity based on the first network activity history and the second network activity history, the at least one processor is configured to:

receive a groupcast signal from the second network entity based on the first network activity history and the second network activity history.
A first network entity for wireless communication, comprising:

a memory; and

at least one processor coupled to the memory, wherein the at least one processor is configured to:

receive, at a first time from a second network entity, a first network activity history associated with the second network entity, wherein the first network activity history comprises information indicative of whether the second network entity in an active state or an inactive state for each time unit in a first set of time units before the first time;

receive, at a second time from the second network entity, a second network activity history associated with the second network entity, wherein the second network activity history comprises information indicative of whether the second network entity is in the active state or the inactive state for each time unit in a second set of time units after the first time and before the second time; and

communicate with the second network entity based on the first network activity history and the second network activity history.