Random access procedure based on energy harvesting categories

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive configuration information including parameters associated with a plurality of energy harvesting (EH) categories. The UE may select an EH category from the plurality of EH categories based at least in part on the configuration information and an EH state of the UE. The UE may perform a two-step random access channel (RACH) procedure based at least in part on the EH category. Numerous other aspects are described.

Description

Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for performing a random access procedure based on energy harvesting categories. Background Art

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

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

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

[0005] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving configuration information including parameters associated with a plurality of energy harvesting (EH) categories. The method may include selecting an EH category from a plurality of EH categories based at least in part on the configuration information and an EH state of the UE. The method may include performing a 2-step random access channel (RACH) procedure based at least in part on the EH category.

[0006] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include sending configuration information including parameters associated with a plurality of EH categories. The method may include receiving an indication of an EH category selected by a UE. The method may include performing a 2-step RACH procedure with the UE based at least in part on the EH category.

[0007] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive configuration information including parameters associated with multiple EH categories. The one or more processors may be configured to select an EH category from multiple EH categories based at least in part on the configuration information and the EH state of the UE. The one or more processors may be configured to perform a 2-step RACH process based at least in part on the EH category.

[0008] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to send configuration information including parameters associated with multiple EH categories. The one or more processors may be configured to receive an indication of an EH category selected by a UE. The one or more processors may be configured to perform a 2-step RACH procedure with a UE based at least in part on the EH category.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive configuration information including parameters associated with multiple EH categories. The instruction set, when executed by one or more processors of the UE, may cause the UE to select an EH category from multiple EH categories based at least in part on the configuration information and the EH state of the UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to perform a 2-step RACH process based at least in part on the EH category.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send configuration information including parameters associated with a plurality of EH categories. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive an indication of an EH category selected by a UE. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to perform a 2-step RACH procedure with a UE based at least in part on the EH category.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving configuration information including parameters associated with a plurality of EH categories. The apparatus may include means for selecting an EH category from a plurality of EH categories based at least in part on the configuration information and an EH state of the apparatus. The apparatus may include means for performing a 2-step RACH procedure based at least in part on the EH category.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending configuration information including parameters associated with a plurality of EH categories. The apparatus may include means for receiving an indication of an EH category selected by another apparatus. The apparatus may include means for performing a 2-step RACH procedure with another apparatus based at least in part on the EH category.

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

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

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

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

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

[0018] Figure 2 is a diagram illustrating an example of a network entity communicating with a user equipment (UE) in a wireless network according to the present disclosure.

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

[0020] Figure 4 is a diagram illustrating an example of energy harvesting (EH) according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of a 2-step random access channel (RACH) procedure according to the present disclosure.

[0022] Figure 6is a diagram illustrating an example associated with an EH category-based RACH procedure according to the present disclosure.

[0023] Figure 7 is a diagram illustrating an example 700 of timing parameters according to the present disclosure.

[0024] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

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

[0026] Figure 10 to Figure 11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

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

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

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

[0038] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network entity, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included in a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

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

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

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

[0044] In some aspects, a UE (e.g., an IoT device, a zero-power device, UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive configuration information including parameters associated with a plurality of energy harvesting (EH) categories. The communication manager 140 may select an EH category from the plurality of EH categories based at least in part on the configuration information and an EH state of the UE. The communication manager 140 may perform a 2-step random access channel (RACH) procedure based at least in part on the EH category. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0045] In some aspects, a network entity (e.g., base station 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send configuration information including parameters associated with a plurality of EH categories. The communication manager 150 may receive an indication of an EH category selected by a UE and perform a 2-step RACH procedure with the UE based at least in part on the EH category. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0046] As indicated above, Figure 1 Other examples can be found in the Figure 1 Different than described.

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

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

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

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

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

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

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

[0054] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the base station 110 may perform one or more techniques associated with performing a random access procedure based on an EH category. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 900 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of a network entity and / or UE 120, may cause one or more processors, UE 120, and / or a network entity to perform or direct, for example, Figure 8 The process of 800 Fig. 9 The process 900 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0055] In some aspects, a UE (e.g., an IoT device, a zero-power device, a UE 120) includes means for receiving configuration information including parameters associated with a plurality of EH categories; means for selecting an EH category from the plurality of EH categories based at least in part on the configuration information and an EH state of the UE; and / or means for performing a 2-step RACH procedure based at least in part on the EH category. Means for the UE to perform operations described herein may include, for example, one or more of the following: a communications manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0056] In some aspects, a network entity (e.g., a base station 110, a charging device) includes a component for sending configuration information, the configuration information including parameters associated with multiple EH categories; a component for receiving an indication of an EH category selected by a UE; and a component for performing a 2-step RACH procedure with the UE based at least in part on the EH category. In some aspects, the component for the network entity to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

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

[0058] As indicated above, Figure 2 Other examples can be found in the Figure 2 Different than described.

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

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

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

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

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

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

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

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

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

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

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

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

[0071] As indicated above, Figure 3 Other examples can be found in the Figure 3 Different than described.

[0072] Figure 4 is a diagram illustrating an example 400 of energy harvesting according to the present disclosure.

[0073] Energy harvesting includes devices that obtain energy from sources other than batteries on the device. This can include obtaining energy from a source external to the device. Devices using energy harvesting may have small energy storage devices or batteries (e.g., smart watches, RedCap devices, eRedCap devices) or no energy storage devices or batteries (e.g., zero-power devices, IoT devices, wearable devices, or financial devices). Energy harvesting may include converting RF energy transmitted from another device. The harvesting of RF energy may not fully charge the battery, but can be used for some tasks such as data decoding, operating some filters, data reception, data encoding, data reception, and / or data transmission. Energy can accumulate over time. Energy harvesting can also be part of a self-sustaining network, where nodes in the network can interact in the network by sending energy harvested in the network.

[0074] like Figure 4 As shown, an RF receiver (e.g., UE 120) can receive signals (e.g., radio signals carried on radio waves) from an RF transmitter (e.g., base station 110 or UE 120) and convert the electromagnetic energy of these signals into direct current for use by the RF receiver (e.g., using a rectifying antenna including a dipole antenna with an RF diode). The RF receiver can be a low power device or a zero power device. The RF transmitter can be referred to as a "charging device".

[0075] As shown at reference numeral 405, in some aspects, the RF receiver may use a split receiver architecture, where a first set of antennas is configured to harvest energy and a second set of antennas is configured to receive data. In this scenario, each set of antennas may be individually configured to receive signals at certain times, frequencies, and / or via one or more specific beams, such that all signals received by the first set of antennas are harvested to obtain energy, and all signals received by the second set of antennas are processed to receive information.

[0076] As shown by reference numeral 410, in some aspects, an RF receiver may use a time-switched architecture to harvest energy. The time-switched architecture may use one or more antennas to receive signals, and whether the signals are harvested to obtain energy or processed to receive information depends on the time when the signals are received. For example, one or more first time slots may be time slots during which the received signals are transmitted to one or more energy harvesting components to harvest energy, and one or more second time slots may be time slots during which the received signals are processed and decoded to receive information. In some aspects, the time slots may be pre-configured (e.g., by an RF receiver, an RF transmitter, or another device).

[0077] As shown by reference numeral 415, in some aspects, an RF receiver may use a power allocation architecture to harvest energy. The power allocation architecture may use one or more antennas to receive signals, and the signals are processed by one or both of the energy harvesting component and / or the information receiving component according to an energy harvesting rate. For example, the RF receiver may be configured to use a first portion of the received signal for energy harvesting and to use the remaining received signal for information reception. The energy harvesting mode for the device may be semi-statistically configured via RRC messaging. In some aspects, the energy harvesting rate may be pre-configured (e.g., by an RF receiver, an RF transmitter, or another device). Even in energy harvesting mode, communication with a network entity may be required, but with reduced radio capabilities to reduce power consumption.

[0078] The RF receiver may receive a signal for energy harvesting at certain resources (e.g., time, frequency, and / or space resources) and at a certain power level that results in a specific charging rate. The energy harvested by the RF receiver may be used and / or stored for later use. For example, in some aspects, the RF receiver may be powered directly by the harvested energy. In some aspects, the RF receiver may use an energy storage device (such as a battery, a capacitor, and / or a supercapacitor) to gather and store the harvested energy for immediate and / or later use.

[0079] An energy harvesting device may have a low power or wake-up radio that is configured to detect a low power wake-up signal but not perform other communications. An energy harvesting device may have a main radio that is configured to perform communications and consumes more power than the low power radio or the wake-up radio.

[0080] More generally, energy harvesting devices may equally or differently rely on different energy harvesting techniques, such as solar, vibration, thermal, or RF energy harvesting. Since energy is intermittently available, energy harvesting may be predictable or unpredictable.

[0081] Energy harvesting (EH) devices may have limited EH capabilities, energy storage capabilities, and / or RF capabilities, depending on the class of the EH device. Different classes of EH devices may have different capabilities. For example, some IoT devices or sensors may have different capabilities than smart wearable devices (e.g., exercise monitors, medical monitoring devices, gaming device sensors). Some EH classes may have mandatory feature sets and optional feature sets.

[0082] As indicated above, Figure 4 Other examples can be found in the Figure 4 Different from what is described.

[0083] Figure 5 is a diagram illustrating an example 500 of a two-step (2-step) RACH procedure according to the present disclosure. Figure 5 As shown, a network entity (eg, base station 110) and UE 120 may communicate with each other to perform a 2-step RACH procedure.

[0084] As shown by reference numeral 505, the base station 110 may send one or more synchronization signal blocks (SSBs) and random access configuration information, and the UE 120 may receive the one or more synchronization signal blocks and the random access configuration information. In some aspects, the random access configuration information may be sent and / or indicated by system information (e.g., one or more system information blocks (SIBs)) and / or SSBs, such as for contention-based random access. In addition or alternatively, the random access configuration information may be sent in a radio resource control (RRC) message and / or a physical downlink control channel (PDCCH) command message that triggers a RACH procedure, such as for contention-free random access. The random access configuration information may include one or more parameters to be used in a 2-step RACH procedure, such as one or more parameters for sending a random access message (RAM) and / or receiving a random access response (RAR) to a RAM.

[0085] As shown in reference numeral 510, UE 120 may send a RAM preamble, and base station 110 may receive the RAM preamble. As shown in reference numeral 515, UE 120 may send a RAM payload, and base station 110 may receive the RAM payload. As shown, as part of the initial (or first) step of the 2-step RACH process, UE 120 may send a RAM preamble and a RAM payload to base station 110. In some aspects, RAM may be referred to as message A, msgA, a first message, or an initial message in the 2-step RACH process. In addition, in some aspects, the RAM preamble may be referred to as a message A preamble, a msgA preamble, a preamble, or a physical random access channel (PRACH) preamble, and the RAM payload may be referred to as a message A payload, a msgA payload, or a payload. In some aspects, RAM may include some or all of the contents of message 1 (msg1) and message 3 (msg3) of the four-step RACH process described in more detail below. For example, the RAM preamble may include some or all of the contents of message 1 (e.g., a PRACH preamble), and the RAM payload may include some or all of the contents of message 3 (e.g., a UE identifier, uplink control information (UCI), and / or a physical uplink shared channel (PUSCH) transmission).

[0086] As indicated by reference numeral 520, the base station 110 may receive the RAM preamble transmitted by the UE 120. If the base station 110 successfully receives and decodes the RAM preamble, the base station 110 may then receive and decode the RAM payload.

[0087] As shown by reference numeral 525, the base station 110 may send a RAR (sometimes referred to as a RAR message). As shown, the base station 110 may send a RAR message as part of the second step of a 2-step RACH procedure. In some aspects, the RAR message may be referred to as message B, msgB, or a second message in a 2-step RACH procedure. The RAR message may include some or all of the contents of message 2 (msg2) and message 4 (msg4) of a four-step (4-step) RACH procedure. For example, the RAR message may include a detected PRACH preamble identifier, a detected UE identifier, a timing advance value, and / or contention resolution information.

[0088] As part of the second step of the 2-step RACH procedure, the base station 110 may send a physical downlink control channel (PDCCH) communication for the RAR, as shown by reference numeral 530. The PDCCH communication may schedule a physical downlink shared channel (PDSCH) communication including the RAR. For example, the PDCCH communication may indicate a resource allocation for the PDSCH communication (e.g., in downlink control information (DCI)).

[0089] As part of the second step of the 2-step RACH procedure, the base station 110 may send a PDSCH communication for the RAR as scheduled by the PDCCH communication, as shown by reference numeral 535. The RAR may be included in a medium access control (MAC) protocol data unit (PDU) of the PDSCH communication. As shown by reference numeral 540, if the UE 120 successfully receives the RAR, the UE 120 may send a hybrid automatic repeat request (HARQ) acknowledgement (ACK).

[0090] In some scenarios, the base station 110 may fall back from the 2-step RACH procedure to the 4-step RACH procedure after a transmission failure of the 2-step RACH procedure. For example, if the base station 110 successfully detects the PRACH preamble, but fails to decode the PUSCH communication, the base station 110 may switch to the 4-step RACH procedure. This may include sending a fallback indication, as shown by reference numeral 545. The fallback indication may schedule a transmission for the UE 120. As shown by reference numeral 550, the UE 120 may send the scheduled transmission.

[0091] However, UE 120 may not have all the energy to perform the entire RACH process within a single activity duration. In practice, the amount of energy that UE 120 can harvest may be random and unpredictable. Furthermore, UEs may have different EH capabilities and may require different RACH configurations. If UE 120 cannot complete the RACH process, communications may fail and latency may increase.

[0092] As indicated above, Figure 5 Other examples can be found in the Figure 5 Different from what is described.

[0093] Figure 6 6 is a diagram illustrating an example 600 associated with an EH category based RACH procedure according to the present disclosure. Figure 6 As shown, UE 620 (e.g., IoT, zero-power device, UE 120) can harvest energy from network entity 610 (e.g., base station 110). Network entity 610 can operate as a charging device, or another device can operate as a charging device for UE 120.

[0094] According to various aspects described herein, there may be multiple EH categories for a 2-step RACH procedure, where each EH category targets devices with different EH capabilities (e.g., maximum duty cycle supported during a RACH procedure). Each EH category may be configured with different RACH resources and parameters (RACH parameters). The network entity 610 may announce the set of supported EH categories and the parameters associated with each category in system information. The network entity 610 may send configuration information specifying RACH resources and / or parameters.

[0095] UE 620 may select an EH category based at least in part on the EH state and configuration information of UE 620. The EH state may include the current amount of energy stored at UE 620 and / or the ability of UE 620 to collect more energy. UE 620 may perform a 2-step RACH process based at least in part on the EH category. This may include sending an indication of the selected EH category or an indication of a preferred EH category in the MsgA payload of the 2-step RACH process. In some aspects, UE 620 may select between a 2-step RACH process and a 4-step RACH process based at least in part on the EH state of UE 620. UE 620 may also select a RACH process using the RSRP of a downlink reference signal. For example, the network entity 610 may configure an RSRP threshold to give UE 620 more opportunities to use a 2-step RACH process instead of a 4-step RACH process.

[0096] In some aspects, the configuration information may include parameters associated with multiple EH categories. Such parameters may include a maximum duty cycle that can be supported during a RACH process, RACH resources, RACH parameters, a set of PRACH preambles, a number of PRACH opportunities, a periodicity of PRACH opportunities, a PRACH opportunity for each EH category dedicated to a MsgA preamble, and / or a minimum amount of energy required at the start of a 2-step RACH process. The parameters may also include a number of RACH attempts that can be performed without harvesting more energy, the ability of the UE 620 to ensure that the UE 620 will have sufficient energy to complete the 2-step RACH process, a minimum EH rate, and / or parameters for EH categories including the number of RAR windows. The parameters may include timing parameters such as a duration or time gap between sending an MsgA preamble and sending an MsgA payload, a time gap between performing a measurement and sending MsgA, a time gap between sending MsgA and monitoring MsgB, and / or a time gap between two RAR windows.

[0097] By selecting an EH category based at least in part on the EH state and configuration, the UE 620 can ensure that there is sufficient energy to complete the RACH procedure. Thus, the UE 620 can limit connection failures and avoid increases in latency.

[0098] Example 600 shows how UE 620 and / or network entity 610 can ensure that UE 620 has enough energy to complete at least one RACH attempt. Some devices are able to complete RACH attempts without harvesting additional energy during the RACH process. Other devices will need to harvest energy during the RACH process.

[0099] As shown by reference numeral 625, the network entity 610 may announce access criteria for the EH class. This may include sending configuration information including parameters associated with multiple EH classes. For example, one criterion for EH class k is the amount of energy that the UE 620 needs to have at the beginning of the RACH process. This amount may be, for example, greater than or equal to X. k % × Emin. Emin may be the minimum amount of energy required to complete a RACH attempt. Note that the network entity 610 announces X k However, the actual value of Emin need not be announced, which may vary across different device implementations. The network entity 610 may also announce or configure Enominal, which may be the expected number of RACH attempts that the device may perform without acquisition. Thus, if Enominal is configured, the amount of energy that the UE 620 needs to have at the start of the RACH process is greater than or equal to Xk%×Emin×Enominal.

[0100] In some aspects, the criterion may be the EH rate of the device. For example, if X k <100%, then the UE 620 may need to determine (e.g., with 90% certainty) that the UE 620 can harvest energy quickly enough to complete the RACH process without premature termination (due to power outage). The network entity 610 may also advertise the minimum EH rate (EH k) for devices using EH category k. k ). EH k It can be expressed as f k %, so that f k %×Emin is the minimum amount of energy that the device must harvest in a time slot.

[0101] As shown by reference numeral 630, UE 620 may select an EH category based at least in part on the configuration information and the EH state of UE 620. In this example, when UE 620 has a limited amount of energy, UE 620 is able to harvest energy during a 2-step RACH process. For example, UE 620 may select an EH category that provides a time gap 632 (e.g., T1) between the MsgA preamble and the MsgA payload of step 1 of the 2-step RACH process. As shown by reference numeral 635, UE 620 may send an MsgA preamble, but has not yet sent an MsgA payload. UE 620 may enter an EH state, in which UE 620 may harvest energy from an RF signal. As shown by reference numeral 640, network entity 610 may send a signal to UE 620 (charging the UE). Alternatively, another device may charge UE 620. As shown by reference numeral 645, UE 620 may harvest energy from the signal and store the energy in an energy storage device (e.g., a battery). UE 620 may be in a sleep state during energy harvesting. UE 620 may harvest a threshold amount of energy to continue to send MsgA payloads within the configured time slot 632.

[0102] As shown by reference numeral 650, the UE 620 that has harvested sufficient energy may send a MsgA payload. The MsgA payload may include an indication of the selected EH category. When the network entity 610 receives the indication of the selected EH category, the network entity 610 may perform a 2-step RACH procedure based at least in part on the selected EH category. In some aspects, the UE 620 may suggest a preferred EH category, and the network entity 610 may determine whether to use the preferred EH category.

[0103] If the UE 620 does not have sufficient energy to send the MsgA payload, the UE 620 may monitor the fallback RAR. In response to receiving the fallback RAR, the UE 620 may send Msg3 of the 4-step RACH procedure. The UE 620 may send Msg3 in an uplink grant addressed to the cell radio network temporary identifier (C-RNTI) of the UE 620. Msg3 may include an indication of when the UE 620 is able to monitor Msg4 of the 4-2 step RACH procedure. The network entity 610 may send Msg4 based at least in part on the indication, or when the UE 620 is able to monitor Msg4.

[0104] In some aspects, if UE 620 does not have energy to send Msg3 at the PUSCH resources provided by network entity 610 or does not receive MsgB in any RAR window, UE 620 may terminate the current RACH attempt and retransmit Msg A. To retransmit MsgA, UE 620 may be allowed to accumulate sufficient energy and / or change its EH category.

[0105] In some aspects, the UE 620 may complete the 2-step RACH procedure in response to not having sufficient energy and send another Msg A after collecting energy for sending the other Msg A. The UE 620 may select a new EH category before sending the other Msg A, wherein the other Msg A includes an indication of the new EH category.

[0106] The MsgA payload may also include an indication of a time gap for monitoring MsgB. In some aspects, after sending MsgA, the UE 620 may select one or more RAR windows in which to monitor for MsgB based at least in part on the EH state of the UE.

[0107] After sending MsgA, in response to receiving an uplink grant addressed to the UE's RNTI (such as C-RNTI) in the RAR window, UE 620 may terminate the 2-step RACH procedure independent of the EH state of UE 620 .

[0108] In some aspects, the configuration information may specify a monitoring time 652 for the selected EH category. The monitoring time 652 may include, for example, the earliest time slot in which the UE 620 can monitor MsgB. The monitoring time 652 may be a time slot (e.g., T2) after the end of the last uplink transmission. The UE 620 may send an indication of the earliest time slot in a message, such as a MAC control element (MAC CE) with the highest logical channel prioritization (LCP) priority or at least a higher LCP priority than other MAC CEs.

[0109] As indicated by reference numeral 655, the network entity 610 may send MsgB. When the UE 620 is capable of monitoring MsgB, such as during monitoring time 652, the UE 620 may receive MsgB. If the MsgB is successfully received, the UE 620 may terminate the 2-step RACH. This may involve sending an ACK for the MsgB.

[0110] In some aspects, the network entity 610 may configure separate RACH resources for different EH categories. If the network entity 610 does not configure separate RACH resources for different EH categories, the UE 620 may indicate a preferred EH category in a MACCE in the PUSCH payload. This indication may be in addition to the preferred time of MsgB so that if the UE 620 falls back to a 4-step RACH procedure, the indication may be used. If the UE 620 does not have enough energy to send a PUSCH payload, the UE 620 may still continue to monitor the fallback RAR (if there is enough energy for reception).

[0111] As indicated above, Figure 6 Other examples can be found in relation to Figure 6 Different from what is described.

[0112] Figure 7 is a diagram illustrating an example 700 of timing parameters according to the present disclosure.

[0113] In some aspects, the configuration information may include timing parameters such as T1, T2, T3, T4, and N1. T1 may indicate the duration or time gap between the transmission of the MsgA preamble and the transmission of the MsgA payload in step 1 of the 2-step RACH process. The start and end times of T1 or other timing parameters may be the beginning of a transmission or RAR window, the middle of a transmission or RAR window, or the end of a transmission or RAR window. T2 may indicate the time gap between the end of the last uplink transmission (e.g., MsgA payload) and when the UE 620 begins monitoring MsgB. The UE 620 may send an indication of T2 in the MsgA payload. If T2 is longer than the beginning of the first RAR window, the UE 620 may begin monitoring MsgB from T2 if T2 ends within the first RAR window, or begin monitoring at the beginning of the RAR window after T2 ends. If T2 is shorter than the beginning of the first RAR window, the UE 620 may begin monitoring MsgB at the first RAR window. If UE 620 does not send an indication of T2 in the MsgA payload, UE 620 may start monitoring MsgB at the first RAR window.

[0114] T3 may indicate the time gap between the end of the MsgA payload and the start of the next RAR window. T4 may be the time gap between two consecutive RAR windows (e.g., between the start of each RAR window). UE 620 may send the preferred timing parameter in the MAC CE. The MAC CE may also include the preferred EH category. Another timing parameter may be the time gap between the UE 620 performing the measurement and sending the MsgA payload.

[0115] To save power, UE 620 may not monitor MsgB in all RAR windows. N1 may indicate the number of RAR windows used for MsgB reception. UE 620 may send an indication of N1 in the MsgA payload and monitor MsgB in the RAR window according to N1. Therefore, network entity 610 may send MsgB in RAR based at least in part on T4 and / or N1.

[0116] By indicating the timing parameters for monitoring MsgB, the UE 620 can limit how much energy is consumed by monitoring MsgB. The network entity 610 or the UE 620 can also select the timing parameters to enable the UE 620 to collect energy before monitoring MsgB.

[0117] As indicated above, Figure 7 Other examples can be found in the Figure 7 Different from what is described.

[0118] Figure 8 8 is a diagram illustrating an example process 800 performed, for example, by a UE according to the present disclosure. Example process 800 is an example of a UE (eg, UE 120, UE 620) performing operations associated with a RACH procedure based on an EH category.

[0119] like Figure 8 As shown, in some aspects, process 800 may include receiving configuration information including parameters associated with a plurality of EH categories (block 810). For example, a UE (e.g., using Fig.10 The communication manager 1008 and / or receiving component 1002 depicted in FIG. 1004 may receive configuration information including parameters associated with a plurality of EH categories, as described above.

[0120] like Figure 8 As further shown, in some aspects, process 800 may include selecting an EH category from a plurality of EH categories based at least in part on the configuration information and the EH state of the UE (block 820). Fig.10 The communication manager 1008 and / or the selection component 1010 depicted in FIG. 1004 may select an EH category from a plurality of EH categories based at least in part on the configuration information and the EH state of the UE, as described above.

[0121] like Figure 8 As further shown, in some aspects, process 800 may include performing a 2-step RACH process based at least in part on the EH category (block 830). Fig.10 The communication manager 1008 and / or the RACH component 1012 depicted in FIG. 1004 may perform a 2-step RACH process based at least in part on the EH category, as described above.

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

[0123] In a first aspect, performing a 2-step RACH procedure includes sending an indication of an EH category in a MsgA payload.

[0124] In a second aspect, alone or in combination with the first aspect, the parameters associated with the EH category include a maximum duty cycle that can be supported during a RACH procedure.

[0125] In a third aspect, alone or in combination with one or more of the first and second aspects, the parameters associated with the EH category include RACH resources or RACH parameters.

[0126] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the parameters associated with the EH category include one or more of a PRACH preamble set, a number of PRACH opportunities, or a periodicity of PRACH opportunities.

[0127] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the parameters associated with the EH category include a minimum amount of energy required at the start of a 2-step RACH procedure.

[0128] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 800 includes harvesting energy during a 2-step RACH procedure.

[0129] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the parameter associated with the EH category comprises a number of RACH attempts that can be performed without harvesting more energy.

[0130] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the parameters associated with the EH category include the ability of the UE to ensure that the UE will have sufficient energy to complete the 2-step RACH procedure.

[0131] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the parameter associated with the EH category comprises a minimum EH ratio.

[0132] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the parameters associated with the EH category include a time gap between sending the MsgA preamble and sending the MsgA payload.

[0133] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the parameters associated with the EH category include a time gap between performing the measurement and sending the MsgA.

[0134] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the parameters associated with the EH category include a time gap between sending MsgA and monitoring MsgB.

[0135] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 800 includes sending an indication of the time gap in MsgA.

[0136] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 800 includes sending an indication of a preferred EH category for a 2-step RACH procedure.

[0137] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the parameter of the EH category comprises a time gap between two RAR windows.

[0138] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the parameter of the EH category comprises the number of RAR windows.

[0139] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, performing a 2-step RACH process includes: selecting one or more RAR windows in which to monitor MsgB after sending MsgA based at least in part on the EH state of the UE; and terminating the 2-step RACH process independently of the EH state of the UE after sending MsgA in response to receiving an uplink grant addressed to the RNTI of the UE in the RAR window.

[0140] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, process 800 includes sending an indication in Msg3 of when the UE can monitor Msg4 in response to receiving a fallback RAR.

[0141] In a nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, process 800 includes completing a 2-step RACH process in response to not having sufficient energy and sending another MsgA after acquiring energy for sending the other MsgA.

[0142] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, process 800 includes selecting a new EH category before sending the other MsgA, wherein the other MsgA includes an indication of the new EH category.

[0143] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, process 800 includes monitoring a fallback RAR in response to not having sufficient energy to send a MsgA payload.

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

[0145] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a network entity according to the present disclosure. Example process 900 is an example of a network entity (eg, base station 110, network entity 610) performing operations associated with a RACH procedure based on an EH category.

[0146] like Fig. 9 As shown, in some aspects, process 900 may include sending configuration information including parameters associated with a plurality of EH categories (block 910). For example, a network entity (e.g., using Fig.11 The communication manager 1108 and / or the sending component 1104 depicted in FIG. 1104 may send configuration information including parameters associated with multiple EH categories, as described above.

[0147] like Fig. 9 As further shown, in some aspects, process 900 may include receiving an indication of an EH category selected by the UE (block 920). Fig.11 The communication manager 1108 and / or receiving component 1102 depicted in FIG. 1104 may receive an indication of an EH category selected by the UE, as described above.

[0148] like Fig. 9 As further shown, in some aspects, process 900 may include performing a 2-step RACH procedure with the UE based at least in part on the EH category (block 930). Fig.11 The communication manager 1108 and / or RACH component 1110 depicted in FIG. 10A may perform a 2-step RACH procedure with the UE based at least in part on the EH category, as described above.

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

[0150] In a first aspect, parameters associated with the EH category include the maximum duty cycle that the UE can support during a RACH procedure, the minimum amount of energy required by the UE at the start of a 2-step RACH procedure, or the minimum number of RACH attempts that the UE can perform without harvesting more energy.

[0151] In a second aspect, either alone or in combination with the first aspect, the parameters associated with the EH category include a minimum EH rate or the ability of the UE to ensure that the UE will have sufficient energy to complete the 2-step RACH procedure.

[0152] In a third aspect, alone or in combination with one or more of the first and second aspects, parameters associated with the EH category include a first time gap between the UE sending a MsgA preamble and sending a MsgA payload, a second time gap between the UE performing measurements and sending MsgA, or a third time gap between sending MsgA and monitoring MsgB.

[0153] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 900 includes receiving in a MAC CE of a MsgA payload an indication of a first time slot, a second time slot, a third time slot, or a preferred EH category for the UE to use for a 2-step RACH procedure.

[0154] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the parameters of the EH category include a time gap between two RAR windows, or the number of RAR windows, and performing a 2-step RACH procedure includes sending MsgB in the RAR based at least in part on the time gap between the two RAR windows, or the number of RAR windows.

[0155] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 900 includes receiving an indication in Msg3 of when the UE can monitor Msg4, and sending Msg4 based at least in part on the indication.

[0156] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, process 900 includes receiving another MsgA indicating a new EH category selected by the UE before the 2-step RACH process is completed, and performing another 2-step RACH process based at least in part on the new EH category.

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

[0158] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a UE (e.g., UE 120, UE 620), or a UE may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may use receiving component 1002 and transmitting component 1004 to communicate with another apparatus 1006 (such as a UE, a base station, a network entity, a charging device, or another wireless communication device). As further shown, apparatus 1000 may include a communication manager 1008. Communication manager 1008 may control and / or otherwise manage one or more operations of receiving component 1002 and / or transmitting component 1004. In some aspects, communication manager 1008 may include a communication manager 1008 in conjunction with receiving component 1002 and / or transmitting component 1004. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the UE. The communication manager 1008 may be or be similar to Figure 1 and Figure 2 . For example, in some aspects, the communication manager 1008 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1008 can include a receiving component 1002 and / or a sending component 1004. The communication manager 140 can include one or more of a selecting component 1010, a RACH component 1012, and / or an EH component 1014, among other examples.

[0159] In some aspects, the apparatus 1000 may be configured to perform Figures 1 to 7 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown in the figure may include a combination of Figure 2 One or more components of the UE. Additionally or alternatively, Fig.10 One or more of the components shown in the figure may be combined with Figure 2Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

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

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

[0162] The receiving component 1002 can receive configuration information including parameters associated with a plurality of EH categories. The selecting component 1010 can select an EH category from the plurality of EH categories based at least in part on the configuration information and an EH state of the UE. The RACH component 1012 can perform a 2-step RACH procedure based at least in part on the EH category. The EH component 1014 can harvest energy during the 2-step RACH procedure.

[0163] Transmitting component 1004 may transmit an indication of the time gap in MsgA. Transmitting component 1004 may transmit an indication of a preferred EH category for a 2-step RACH procedure. Transmitting component 1004 may transmit an indication of when the UE can monitor Msg4 in Msg3 in response to receiving the fallback RAR.

[0164] Transmitting component 1004 can complete the 2-step RACH process in response to not having sufficient energy and transmit another Msg A after collecting energy for transmitting the another Msg A. Selecting component 1010 can select a new EH category before transmitting the another Msg A, wherein the another Msg A includes an indication of the new EH category.

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

[0166] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication. Apparatus 1100 may be a network entity (e.g., base station 110, network entity 610), or a network entity may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a transmitting component 1104 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may use receiving component 1102 and transmitting component 1104 to communicate with another apparatus 1106 (such as a UE, a base station, a network entity, a charging device, or another wireless communication device). As further shown, apparatus 1100 may include a communication manager 1108. Communication manager 1108 may control and / or otherwise manage one or more operations of receiving component 1102 and / or transmitting component 1104. In some aspects, communication manager 1108 may include a communication manager 1108 in conjunction with receiving component 1102 and / or transmitting component 1104. Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the network entities described. The communication manager 1108 may be or be similar to Figure 1 and Figure 2108. For example, in some aspects, the communications manager 1108 may be configured to perform one or more of the functions described as being performed by the communications manager 150. In some aspects, the communications manager 1108 may include a receiving component 1102 and / or a sending component 1104. The communications manager 1108 may include one or more of a RACH component 1110, among others.

[0167] In some aspects, the apparatus 1100 may be configured to perform Figures 1 to 7 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 One or more components of the network entity. Additionally or alternatively, Fig.11 One or more of the components shown in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code that is stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

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

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

[0170] Transmitting component 1104 can transmit configuration information including parameters associated with a plurality of EH categories. Receiving component 1102 can receive an indication of an EH category selected by a UE. RACH component 1110 can perform a 2-step RACH procedure with the UE based at least in part on the EH category.

[0171] Receiving component 1102 can receive in a MAC CE of a MsgA payload an indication of a first time slot, a second time slot, a third time slot, or a preferred EH category for the UE to use for a 2-step RACH procedure. Receiving component 1102 can receive in Msg3 an indication of when the UE can monitor Msg4.

[0172] Transmitting component 1104 can transmit Msg4 based at least in part on the indication. Receiving component 1102 can receive another MsgA indicating a new EH category selected by the UE before the 2-step RACH procedure is completed. RACH component 1110 can perform another 2-step RACH procedure based at least in part on the new EH category.

[0173] Fig.11 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.11 Two or more components shown in may be implemented in a single component, or Fig.11 The single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The assembly of (one or more) components shown in the executable is described as being composed of Fig.11 Another collection of components shown in the figure performs one or more functions.

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

[0175] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving configuration information including parameters associated with multiple energy harvesting (EH) categories; selecting an EH category from the multiple EH categories based at least in part on the configuration information and the EH state of the UE; and performing a 2-step random access channel (RACH) process based at least in part on the EH category.

[0176] Aspect 2: The method according to aspect 1, wherein performing the 2-step RACH procedure includes sending an indication of the EH category in a MsgA payload.

[0177] Aspect 3: The method according to aspect 1 or 2, wherein the parameter associated with the EH category includes a maximum duty cycle that can be supported during the RACH process.

[0178] Aspect 4: The method according to any one of aspects 1 to 3, wherein the parameter associated with the EH category includes a RACH resource or a RACH parameter.

[0179] Aspect 5: The method according to any one of aspects 1 to 4, wherein the parameters associated with the EH category include one or more of a physical RACH (PRACH) preamble set, a number of PRACH opportunities, or a periodicity of PRACH opportunities.

[0180] Aspect 6: The method according to any one of aspects 1 to 5, wherein the parameters associated with the EH category include a minimum amount of energy required at the start of the 2-step RACH procedure.

[0181] Aspect 7: The method according to any one of aspects 1 to 6 further includes harvesting energy during the 2-step RACH process.

[0182] Aspect 8: The method according to any one of aspects 1 to 7, wherein the parameter associated with the EH category includes a number of RACH attempts that can be performed without harvesting more energy.

[0183] Aspect 9: The method according to any one of aspects 1 to 8, wherein the parameters associated with the EH category include the ability of the UE to ensure that the UE will have sufficient energy to complete the 2-step RACH procedure.

[0184] Aspect 10: The method according to any one of aspects 1 to 9, wherein the parameters associated with the EH category include a minimum EH rate.

[0185] Aspect 11: The method according to any one of aspects 1 to 10, wherein the parameter associated with the EH category includes a time gap between sending the MsgA preamble and sending the MsgA payload.

[0186] Aspect 12: The method according to any one of aspects 1 to 11, wherein the parameter associated with the EH category includes a time gap between performing measurement and sending MsgA.

[0187] Aspect 13: The method according to any one of aspects 1 to 12, wherein the parameter associated with the EH category includes a time gap between sending MsgA and monitoring MsgB.

[0188] Aspect 14: The method according to Aspect 13 further includes sending an indication of the time gap in the MsgA.

[0189] Aspect 15: The method according to any one of aspects 1 to 14, further comprising sending an indication of a preferred EH category for the 2-step RACH procedure.

[0190] Aspect 16: The method according to any one of aspects 1 and 3 to 13, further comprising: monitoring a fallback random access response (RAR) in response to not having sufficient energy to send the MsgA payload.

[0191] Aspect 17: The method according to any one of aspects 1 to 116, wherein the parameter of the EH category includes a time gap between two random access response windows.

[0192] Aspect 18: The method according to any one of aspects 1 to 17, wherein the parameter of the EH category includes the number of random access response windows.

[0193] Aspect 19: A method according to any one of Aspects 1 to 15 and 17 to 18, wherein performing the 2-step RACH process includes: after sending MsgA, selecting one or more random access response (RAR) windows in which to monitor MsgB based at least in part on the EH state of the UE; and in response to receiving an uplink grant addressed to the radio network temporary identifier of the UE in the RAR window, terminating the 2-step RACH process after sending the MsgA independently of the EH state of the UE.

[0194] Aspect 20: The method according to any one of Aspects 1 to 19 further comprises sending, in response to receiving a fallback random access response, an indication in Msg3 of when the UE can monitor Msg4.

[0195] Aspect 21: The method according to any one of aspects 1, 3 to 13 and 15 to 18, further comprising completing the 2-step RACH process in response to not having sufficient energy and sending the other MsgA after acquiring energy for sending the other MsgA.

[0196] Aspect 22: The method according to Aspect 21, further comprising selecting a new EH category before sending the other MsgA, wherein the other MsgA includes an indication of the new EH category.

[0197] Aspect 23: A method of wireless communication performed by a network entity, comprising: sending configuration information including parameters associated with multiple energy harvesting (EH) categories; receiving an indication of an EH category selected by a user equipment (UE); and performing a 2-step random access channel (RACH) procedure with the UE based at least in part on the EH category.

[0198] Aspect 24: A method according to Aspect 23, wherein the parameters associated with the EH category include a maximum duty cycle that the UE can support during the RACH process, a minimum amount of energy required by the UE at the start of the 2-step RACH process, or a minimum number of RACH attempts that the UE can perform without collecting more energy.

[0199] Aspect 25: The method according to aspect 23 or 24, wherein the parameters associated with the EH category include a minimum EH rate or the capability of the UE to ensure that the UE will have sufficient energy to complete the 2-step RACH procedure.

[0200] Aspect 26: A method according to any one of Aspects 23 to 25, wherein the parameters associated with the EH category include a first time gap between the UE sending the MsgA preamble code and sending the MsgA payload, a second time gap between the UE performing measurement and sending MsgA, or a third time gap between sending MsgA and monitoring MsgB.

[0201] Aspect 27: The method according to Aspect 26 also includes receiving an indication of the first time slot, the second time slot, the third time slot, or a preferred EH category for the UE to use for the 2-step RACH process in a medium access control control element (MAC CE) of the MsgA payload.

[0202] Aspect 28: A method according to any one of Aspects 23 to 27, wherein the parameters of the EH category include a time gap between two random access response (RAR) windows, or the number of RAR windows, and wherein performing the 2-step RACH process includes sending MsgB in the RAR based at least in part on the time gap between two RAR windows, or the number of RAR windows.

[0203] Aspect 29: The method according to any one of Aspects 23 to 28 further includes: receiving an indication in Msg3 of when the UE can monitor Msg4; and sending the Msg4 based at least in part on the indication.

[0204] Aspect 30: The method according to any one of Aspects 23 to 29 further includes: receiving another MsgA indicating a new EH category selected by the UE before the 2-step RACH process is completed; and performing another 2-step RACH process based at least in part on the new EH category.

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

[0206] Aspect 32: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 30.

[0207] Aspect 33: An apparatus for wireless communication, comprising at least one means for performing the method according to one or more of aspects 1 to 30.

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

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

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

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

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

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

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

Claims

1. A user equipment (UE) for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: receiving configuration information including parameters associated with a plurality of energy harvesting (EH) categories; selecting an EH category from a plurality of the EH categories based at least in part on the configuration information and an EH state of the UE; and A 2-step random access channel (RACH) procedure is performed based at least in part on the EH category.

2. The UE of claim 1, wherein to perform the 2-step RACH procedure, the one or more processors are configured to send an indication of the EH category in a MsgA payload. 3 . The UE of claim 1 , wherein the parameter associated with the EH category comprises a maximum duty cycle that can be supported during the RACH procedure. 4 . The UE of claim 1 , wherein the parameter associated with the EH category comprises a RACH resource or a RACH parameter.

5. The UE of claim 1, wherein the parameters associated with the EH category include one or more of a physical RACH (PRACH) preamble set, a number of PRACH opportunities, or a periodicity of PRACH opportunities.

6. The UE of claim 1, wherein the parameters associated with the EH category include a minimum amount of energy required at the start of the 2-step RACH procedure.

7. The UE of claim 1, wherein the one or more processors are configured to harvest energy during the 2-step RACH procedure.

8. The UE of claim 1, wherein the parameters associated with the EH category include a number of RACH attempts that can be performed without harvesting more energy.

9. The UE of claim 1, wherein the parameters associated with the EH category include the ability of the UE to ensure that the UE will have sufficient energy to complete the 2-step RACH procedure.

10. The UE of claim 1, wherein the parameters associated with the EH category include a minimum EH rate.

11. The UE of claim 1, wherein the parameter associated with the EH category comprises a time gap between sending a MsgA preamble and sending a MsgA payload.

12. The UE of claim 1, wherein the parameter associated with the EH category includes a time gap between performing measurement and sending MsgA.

13. The UE of claim 1, wherein the parameter associated with the EH category includes a time gap between sending MsgA and monitoring MsgB.

14. The UE of claim 13, wherein the one or more processors are configured to send an indication of the time gap in the MsgA.

15. The UE of claim 1, wherein the one or more processors are configured to send an indication of a preferred EH category for the 2-step RACH procedure.

16. The UE of claim 1, wherein the one or more processors are configured to monitor for a fallback random access response (RAR) in response to not having sufficient energy to send the MsgA payload.

17. The UE according to claim 1, wherein the parameter of the EH category includes a time gap between two random access response windows.

18. The UE according to claim 1, wherein the parameter of the EH category includes the number of random access response windows.

19. The UE of claim 1, wherein to perform the 2-step RACH procedure, the one or more processors are configured to: After sending MsgA, selecting one or more random access response (RAR) windows in which to monitor MsgB based at least in part on the EH state of the UE; and In response to receiving an uplink grant addressed to a radio network temporary identifier of the UE in a RAR window, the 2-step RACH procedure is terminated after sending the MsgA independently of an EH state of the UE.

20. The UE of claim 1, wherein the one or more processors are configured to send, in response to receiving a fallback random access response, an indication in Msg3 of when the UE can monitor Msg4.

21. The UE of claim 1, wherein the one or more processors are configured to complete the 2-step RACH procedure in response to not having sufficient energy and to send another MsgA after collecting energy for sending the another MsgA.

22. The UE of claim 21, wherein the one or more processors are configured to select a new EH category before sending the another MsgA, wherein the another MsgA includes an indication of the new EH category.

23. A network entity for wireless communication, comprising: Memory; and one or more processors coupled to the memory and configured to: sending configuration information including parameters associated with a plurality of energy harvesting (EH) categories; receiving an indication of an EH category selected by a user equipment (UE); and A 2-step random access channel (RACH) procedure is performed with the UE based at least in part on the EH category.

24. The network entity of claim 23, wherein the parameters associated with the EH category include a maximum duty cycle that the UE can support during the RACH procedure, a minimum amount of energy required by the UE at the start of the 2-step RACH procedure, or a minimum number of RACH attempts that the UE can perform without harvesting more energy.

25. The network entity of claim 23, wherein the parameters associated with the EH class include a minimum EH rate or capability of the UE to ensure that the UE will have sufficient energy to complete the 2-step RACH procedure.

26. The network entity of claim 23, wherein the parameters associated with the EH category include a first time gap between the UE sending an MsgA preamble and sending an MsgA payload, a second time gap between the UE performing measurement and sending MsgA, or a third time gap between sending MsgA and monitoring MsgB.

27. The network entity of claim 26, wherein the one or more processors are configured to receive, in a medium access control control element (MAC CE) of the MsgA payload, an indication of the first time slot, the second time slot, the third time slot, or a preferred EH category for the UE to use for the 2-step RACH procedure.

28. The network entity of claim 23, wherein the parameters of the EH category include a time gap between two random access response (RAR) windows, or a number of RAR windows, and wherein to perform the 2-step RACH procedure, the one or more processors are configured to send MsgB in the RAR based at least in part on the time gap between two RAR windows, or the number of RAR windows.

29. The network entity of claim 23, wherein the one or more processors are configured to: receiving in Msg3 an indication of when the UE can monitor Msg4; and The Msg4 is sent based at least in part on the indication.

30. The network entity of claim 23, wherein the one or more processors are configured to: receiving another MsgA indicating a new EH category selected by the UE before the 2-step RACH procedure is completed; and Another 2-step RACH procedure is performed based at least in part on the new EH category.

Images