System information acquisition by energy harvesting device

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) can receive, from a network node, a first system information block (SIB) indicating an energy harvesting capability category supported by the network node. The UE can receive, from the network node and based at least in part on receiving the first SIB and the UE being associated with the energy harvesting capability category, a second SIB having one or more SIB characteristics based at least in part on the energy harvesting capability 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 system information acquisition by energy harvesting devices. 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 network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. The UE may communicate with the network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a sidelink (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[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 using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) 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, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. 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 performing wireless communications by a user equipment (UE). The method may include receiving, from a network node, a first system information block (SIB) indicating an energy harvesting (EH) capability category supported by the network node. The method may include receiving, from the network node and based at least in part on receiving the first SIB and the UE being associated with the EH capability category, a second SIB having one or more SIB characteristics based at least in part on the EH capability category.

[0006] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending a first SIB indicating an EH capability class supported by the network node. The method may include sending a second SIB having one or more SIB characteristics based at least in part on the EH capability class.

[0007] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: receive a first SIB from a network node indicating an EH capability category supported by the network node. The one or more processors may be configured to: receive a second SIB having one or more SIB characteristics based at least in part on the EH capability category from the network node and at least in part on receiving the first SIB and the UE being associated with the EH capability category.

[0008] Some aspects described herein relate to a network node for wireless communication. The network node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to: send a first SIB indicating an EH capability category supported by the network node. The one or more processors may be configured to: send a second SIB having one or more SIB characteristics based at least in part on the EH capability 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, can cause the UE to receive a first SIB indicating an EH capability category supported by the network node from a network node. The instruction set, when executed by one or more processors of the UE, can cause the UE to receive a second SIB having one or more SIB characteristics based at least in part on the EH capability category from the network node and at least in part on receiving the first SIB and the UE being associated with the EH capability category.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, can cause the network node to send a first SIB indicating an EH capability class supported by the network node. The instruction set, when executed by one or more processors of the network node, can cause the network node to send a second SIB having one or more SIB characteristics based at least in part on the EH capability class.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network node, a first SIB indicating an EH capability category supported by the network node. The apparatus may include means for receiving, from the network node and based at least in part on receiving the first SIB and the UE being associated with the EH capability category, a second SIB having one or more SIB characteristics based at least in part on the EH capability category.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a first SIB indicating an EH capability class supported by a network node. The apparatus may include means for sending a second SIB having one or more SIB characteristics based at least in part on the EH capability class.

[0013] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, 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 examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood in the following description when considered in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[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 communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

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

[0020] Figure 4 is a diagram illustrating an example of transmitting and acquiring system information according to the present disclosure.

[0021] Figure 5 is a diagram illustrating an example of radio frequency (RF) energy harvesting according to the present disclosure.

[0022] Figure 6is a diagram of an example associated with system information acquisition by an energy harvesting device according to the present disclosure.

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

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

[0025] Fig. 9 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0026] Fig.10 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 interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[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 can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[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 RATs beyond 5G (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, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). For another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0031] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network node 110 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, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0032] In some examples, the network node 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 ​​the network node 110 and / or a network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 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 network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0033] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a 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 node" may refer to a device configured to perform one or more functions, such as those described herein in conjunction with the network node 110. In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations 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 node" may refer to one of the base station functions, but not another base station function. 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 node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0035] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 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 network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node 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 nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0037] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. 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, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0038] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be 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, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[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 network node 110 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 network node 110.

[0041] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency range designations FRI (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FRI is greater than 6 GHz, FR1 is often (interchangeably) referred to as a "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 a "millimeter wave" band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "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] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as 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, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive from a network node a first system information block (SIB) indicating an EH capability category (also referred to as an EH category) supported by the network node; and receive from the network node and based at least in part on receiving the first SIB and the UE being associated with the EH category a second SIB having one or more SIB characteristics 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, the network node may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may send a first SIB indicating an EH category supported by the network node; and send a second SIB having one or more SIB characteristics 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 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0047] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0048] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The network node 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-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

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

[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 the network node 110 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 may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components).

[0052] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the 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 the network node 110. 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 10 ) or any aspects of any of the methods described herein.

[0053] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 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 the operations described herein (e.g., with reference to Figures 4 to 10 ) or any aspects of any of the methods described herein.

[0054] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the network node 110 may perform one or more techniques associated with system information acquisition by the EH device, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 7 The process of 700 Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 and / or UE 120 (e.g., directly executed, or executed after compilation, conversion and / or interpretation), may cause one or more processors, UE 120 and / or network node 110 to perform or direct, for example, Figure 7 The process of 700 Figure 8 The process 800 of 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, the UE includes a component for receiving a first SIB from a network node indicating an EH category supported by the network node; and / or a component for receiving a second SIB having one or more SIB characteristics based at least in part on the EH category from the network node and at least in part on receiving the first SIB and the UE being associated with the EH category. The components for the UE to perform the operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0056] In some aspects, the network node includes means for transmitting a first SIB indicating an EH category supported by the network node; and / or means for transmitting a second SIB having one or more SIB characteristics based at least in part on the EH category. In some aspects, means for the network node to perform 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 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0059] 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 RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (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.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs or a combination thereof).

[0060] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is 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 examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0061] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed 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)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0062] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links (such as via an F1 interface). Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0063] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0064] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the 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, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0065] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional split such as defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as by one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0066] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering based on functional splitting (e.g., functional splitting defined by 3GPP) (such as lower layer functional splitting). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0067] 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) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 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 implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0068] 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.

[0069] 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 at the SMO framework 305 or the non-RT RIC 315 from a non-network data source or from a network function. 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 the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

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

[0071] Figure 4 4 is a diagram illustrating an example 400 of sending and acquiring system information according to the present disclosure. Figure 4 As shown in , the network node 110 and the UE 120 may communicate with each other. For example, the network node 110 may send system information to the UE 120 to enable communication between the UE 120 and a network accessed via the network node 110.

[0072] As indicated by reference numeral 405, the network node may transmit and the UE may receive a master information block (MIB). The network node transmits the MIB in broadcast form via a physical broadcast channel (PBCH). The network node 110 may periodically transmit the MIB so that the MIB may be periodically received by the UE and used, for example, for cell selection. The MIB may include information about a control resource set (CORESET) and a physical downlink control channel (PDCCH) search space for receiving and decoding SIBs (such as SIB 1).

[0073] As shown by reference numeral 410, the network node may send and the UE may receive SIB1. Collectively, the MIB and SIB1 may be referred to as minimum system information (MSI), and the separate SIB1 may be referred to as remaining minimum system information (RMSI). The network node may send SIB1 via PDCCH communication. As noted herein, the MIB includes parameters for the UE to decode SIB1, which includes cell-specific information specifying parameters for the UE to access the corresponding cell. SIB 1 also includes information indicating the availability and scheduling of other SIBs (e.g., SIB 2 to SIB 9), such as periodicity and system information window size. SIB 1 may also indicate whether other SIBs are provided periodically and / or on demand. If other SIBs can be used on demand, SIB1 may also include information that enables the UE to perform a system information request for an on-demand SIB.

[0074] As indicated by reference numeral 415, the network node 110 may periodically send and the UE 120 may periodically receive other SIBs, such as SIB 1 to SIB 9 (e.g., based on information provided in SIB 1). The other SIBs include system information other than the MSI, which may be used by the network node 110 and the UE 120 for communication. For example, SIB2, SIB3, SIB4, and SIB5 may include information for various types of cell reselection procedures, SIB6, SIB7, and SIB8 may include information associated with various warning and / or alarm notifications, and SIB9 may include timing information. The network node may send the other SIBs via a physical downlink shared channel (PDSCH) communication. As noted herein, the network node may periodically send none, some, or all of the other SIBs.

[0075] As indicated by reference numeral 420, UE 120 may send and network node 110 may receive a system information request. For example, where SIB1 indicates that network node 110 can send one or more of the other SIBs on demand, the UE may request one or more of the other SIBs using information included in SIB1.

[0076] As indicated by reference numeral 425, the network node 110 may send and the UE 120 may receive one or more of the other SIBs based on the system information request. On-demand SIBs may include the same information as corresponding periodic SIBs, but these on-demand SIBs may be requested and sent on demand.

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

[0078] Figure 5 is a diagram illustrating an example 500 of radio frequency (RF) energy harvesting according to the present disclosure. Figure 5 As shown in , an RF receiver (e.g., UE 120) can receive signals (e.g., radio signals carried on radio waves) from an RF transmitter (e.g., network node 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 rectenna including a dipole antenna with an RF diode).

[0079] As shown by reference numeral 505, in some aspects, the RF receiver can use a split receiver architecture in which a first set of antennas is configured to harvest energy and a second set of antennas is configured to receive data. In this case, each set of antennas can 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.

[0080] As shown in reference numeral 510, in some aspects, the RF receiver can use a time switching architecture to collect energy. The time switching architecture can use one or more antennas to receive signals, and whether these signals are collected 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 can be time slots during which the received signals are transmitted to one or more EH components to collect energy, and one or more second time slots can be time slots during which the received signals are processed and decoded to receive information. In some aspects, the time slots can be preconfigured (e.g., by an RF receiver, an RF transmitter, or another device).

[0081] As shown by reference numeral 515, in some aspects, the RF receiver can use a power distribution architecture to harvest energy. The power distribution architecture can use one or more antennas to receive signals, and these signals are processed by one or both of the EH component and / or the information receiving component according to the EH rate. For example, the RF receiver can be configured to use a first portion of the received signal for EH and use the remaining received signal for information reception. In some aspects, the EH rate can be preconfigured (e.g., by the RF receiver, the RF transmitter, or another device).

[0082] The energy harvested by the RF receiver can be used and / or stored for later use. For example, in some aspects, the RF receiver can be powered directly by the harvested energy. In some aspects, the RF receiver can use an energy storage device (such as a battery, capacitor, and / or supercapacitor) to gather and store the harvested energy for immediate and / or later use.

[0083] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different. In some aspects, a UE (e.g., UE 120) can harvest energy in other ways, alone or in combination with RF energy harvesting. For example, a UE can use solar energy harvesting (e.g., using solar panels to convert sunlight into energy), thermal energy harvesting (e.g., using thermoelectric generators to convert heat into energy), and / or mechanical energy harvesting (e.g., using electromagnetic induction to convert vibrations or other physical movements into energy), etc. to harvest energy for storage and / or for actively powering the UE.

[0084] Some EH UEs are able to communicate (e.g., with other UEs and / or network nodes), but require power to send and / or receive communications. There are a variety of different types of EH UEs with a range of capabilities, which may depend on, for example, how much energy the UE can store, how quickly the UE can recharge energy, and how much energy the UE uses to perform various actions. Due to the nature of EH, some EH UEs may not have power available to communicate in the same manner as other UEs that do not rely on EH, which may cause communications with EH UEs to be intermittent. For example, larger communications (e.g., larger transport blocks) may require more energy to receive and process than smaller communications (e.g., smaller transport blocks), and communications that take more time may require more energy to receive and process than relatively shorter communications. This may cause communications with EH UEs to drop, or even cause some UEs to be unable to handle certain types of communications that exceed the capabilities of the EH UE.

[0085] The limited capabilities of some EH UEs may also be problematic when operating in idle mode, since the idle UE and the network have not yet established any connection to coordinate operation. In this case, a predefined procedure (e.g., duty cycle transmission) may enable the exchange of system information to facilitate establishing communications between the network and the UE, but this may consume significant network resources and result in lower performance for some EH UEs that may be more capable than other EH UEs. Issues associated with delivering system information to the UE, including latency, may negatively impact how quickly and efficiently the UE can establish communications with the network, and may prevent some UEs from being able to receive system information in its entirety.

[0086] Some techniques and apparatus described herein enable an EH UE to obtain system information in a manner that accounts for different capabilities of the EH UE. For example, a network node may send a first SIB (e.g., SIB-EH) specific to an EH device. SIB-EH may indicate which EH category(s) the network node supports, so that the EH UE may receive additional system information in a SIB having one or more characteristics based on the UE's EH category. This may enable the network node to send different SIBs for UEs associated with different EH categories, and enable the UE to receive and process SIBs customized for the UE's EH category. Thus, the UE may obtain system information in a manner that accounts for the impact that the EH has on the UE's capabilities. In this way, the network node and the EH UE may communicate system information more efficiently (e.g., relative to relying on legacy SIBs and / or duty cycle transmissions), better support EH UEs with lower capabilities to obtain system information, and have fewer dropped communications between the network node and the EH UE, etc.

[0087] Figure 6 6 is a diagram of an example 600 associated with system information acquisition by an EH device according to the present disclosure. Figure 6 As shown in , a network node (e.g., network node 110) can communicate with one or more UEs (e.g., a first UE, a second UE, and a third UE 120). In some aspects, the UE and the network node can be part of a wireless network (e.g., wireless network 100). The UE can operate in an idle mode (e.g., not connected and / or not yet communicating with a network node). Example UEs include a first UE not associated with an EH (e.g., UE (no EH)), a second UE associated with a first EH category (e.g., UE (EH1)), and a third UE associated with a second EH category (e.g., UE (EH2)).

[0088] As shown by reference numeral 605, the network node may send and one or more of the UEs may receive the MIB. For example, as described herein, the network node may broadcast the MIB via the PBCH, and the MIB may be received by one or more of the UEs. The MIB may include information associated with one or more parameters that may be used by the UE to receive SIB 1 and / or SIB-EH. Although this example depicts that one MIB is received by each example UE and thus includes parameters for receiving both SIB1 (e.g., for the first UE) and SIB-EH (e.g., for the second UE and the third UE), in some aspects, the SIB-EH may be associated with a separate MIB. In this case, the MIB received by the first UE will be different from the MIB received by the second UE and the third UE. In some aspects, when multiple MIBs are used, the UE may be configured to monitor a specific MIB corresponding to the type of UE. For example, the first UE may be configured to monitor only the first MIB carrying information for receiving the SIB, while the second UE and the third UE may be configured to monitor only the second MIB carrying information for receiving the SIB-EH. Any number of separate MIBs may be configured (eg, for different EH classes), and a UE may be configured to monitor any number of MIBs (eg, not just the MIB associated with the UE's EH class).

[0089] As shown by reference numeral 610, the network node may send and one or more of the UEs may receive the SIB-EH. In this example, a first UE that is not associated with an EH category does not receive the SIB-EH because the first UE may instead receive SIB 1 (e.g., as described herein with reference to 620). Both the second UE and the third UE receive the SIB-EH based at least in part on receiving the corresponding MIB. For example, the second UE and the third UE may decode the MIB to obtain one or more parameters for decoding the SIB-EH, and then use these parameters to decode the SIB-EH. In some aspects, the SIB-EH is received via the PDCCH, and the resources carrying the SIB-EH are indicated by the corresponding MIB. Although this example depicts different UEs of different EH categories receiving the same SIB-EH, in some aspects, different SIB-EHs may be sent for different EH categories.

[0090] In some aspects, the SIB-EH indicates one or more EH categories supported by the network node. For example, the network node may be configured to communicate with UEs associated with multiple different EH categories. In this case, the SIB-EH may indicate each EH category in the supported EH categories (e.g., at least EH1 and EH2 in example 600).

[0091] In some aspects, the EH category may be pre-configured and / or defined by a specification. In some aspects, the EH category may be based on capabilities or characteristics of the EH UE. For example, the EH category may be defined based on a maximum number of communications (e.g., transmissions and / or receptions) that the UE can perform with a full charge, a charging rate of the UE, and / or a duration (e.g., average duration) to obtain a full charge.

[0092] In some aspects, different EH categories may be associated with different SIB characteristics, which may enable UEs of different EH categories to obtain system information in different ways. For example, for an EH-specific SIB, the SIB characteristic may indicate whether the EH-specific SIB is to be transmitted via one or multiple transport blocks (TBs). Although multiple TBs may take more time to transmit, some large TBs may be too large for some EH UEs to receive reliably, and dividing the TB into multiple smaller TBs may provide the UE with time to collect energy between transmissions. Another example SIB characteristic may include parameters based at least in part on the EH category. For example, some EH-specific SIBs may include certain parameters related only to the corresponding EH category, such as parameters for indicating how many PDSCH opportunities the EH UE can monitor before recharging. As another example, for parameters, the SIB characteristic may include specific parameter values ​​based at least in part on the EH category. For example, a parameter indicating a random access channel (RACH) interval, a parameter indicating a maximum TB size, and / or a parameter indicating the maximum number of PDSCH opportunities that can be monitored when fully charged, etc., may be different for different EH categories.

[0093] In some aspects, SIB-EH may indicate one or more resources via which EH-specific SIB 1 (e.g., SIB1-EH1 and / or SIB1-EH2) is to be transmitted and / or one or more parameters associated with receiving EH-specific SIB 1. For example, SIB-EH may indicate PDSCH resources for receiving SIB 1-EH 1 and / or SIB1-EH2.

[0094] In some aspects, for an EH class, the SIB-EH may indicate which SIBs may be capable of being used on demand. For example, in addition to or as an alternative to periodically sending each EH-specific SIB, a network node may be capable of sending an EH-specific SIB on demand. In this case, the SIB-EH may include information that enables the UE to request one or more of the SIBs that can be used on demand, such as how to send a request for any given EH-specific SIB. In some aspects, any or all of the EH-specific SIBs may be capable of being used on demand. In some aspects, whether an EH-specific SIB can be used on demand may also depend on the EH class (e.g., an on-demand SIB may be supported by some EH classes but not by other EH classes).

[0095] In some aspects, the EH categories supported by the network node may be based at least in part on radio conditions (e.g., cell load) associated with the network node. For example, if the cellular load on the network node is relatively high, the network node may support fewer EH categories than when the cellular load is relatively low. As conditions change, the network node may dynamically change which EH categories are supported, and any changes may be reflected in the SIB-EH.

[0096] As indicated by reference numeral 615, at least one of the UEs may send, and the network node may receive, a system information request. For example, based at least in part on the SIB-EH indicating that another SIB (e.g., SIB 1-EH1) can be used on demand, the second UE may send a system information request (e.g., using information included in the SIB-EH). In some aspects, the system information request may indicate that the second UE is requesting SIB 1-EH 1. In some aspects, the system information request may include a request for any number of SIBs, EH-specific SIBs, and / or other SIBs. In some aspects, multiple system information requests may be sent (e.g., one request for each on-demand SIB in any number of on-demand SIBs, EH-specific on-demand SIBs, and / or other on-demand SIBs).

[0097] In some aspects, the system information request may be included in a PRACH message (e.g., a random access message or Msg 1). For example, the request may be included in a preamble associated with the corresponding EH category. In some aspects, the system information request may be included in a physical uplink shared channel (PUSCH) message (e.g., Msg3) associated with a RACH procedure. For example, the system information request may be indicated by a medium access control (MAC) control element included in the PUSCH message. In this case, the MAC control element may indicate the requested SIB (e.g., SIB1-EH1) and the EH category (e.g., EH1) of the first UE. In this way, the network node can handle EH-specific system information requests while also performing a RACH procedure.

[0098] As shown by reference numeral 620, the network node may send and at least one UE (e.g., a first UE) may receive SIB1. For example, in this example, SIB1 may be periodically sent because the first UE did not request SIB1. In this example, SIB1 is not EH specific because the network node can support different types of SIBs (EH specific SIBs and / or other SIBs). As described herein, SIB1 includes RMSI that includes cell-specific information that enables the first UE to communicate with the network node and access the corresponding cell. SIB1 may also include information indicating the availability and scheduling of other SIBs and which other SIBs can be used on demand.

[0099] As shown by reference numeral 625, the network node may send and at least one UE (e.g., a second UE) may receive an EH-specific SIB1 (e.g., SIB1-EH1) having one or more characteristics based at least in part on the EH category of the second UE. For example, SIB1-EH1 may be transmitted in multiple TBs and / or may have one or more parameters specific to the corresponding EH category (e.g., EH1), as described herein. In this example, SIB1-EH1 may be sent on demand to the second UE (e.g., based at least in part on the network node receiving a system information request, as described herein). The second UE may monitor SIB1-EH1 based at least in part on the information including SIB-EH and the second UE being included in the EH category corresponding to SIB1-EH1. Like SIB1, SIB1-EH1 may include RMSI, information indicating the availability and scheduling of other SIBs (EH-specific SIBs or other SIBs), and information indicating which other SIBs can be used on demand, etc.

[0100] As shown by reference numeral 630, the network node may transmit and at least one UE (e.g., a third UE) may receive another EH-specific SIB1 (e.g., SIB1-EH2) having one or more characteristics based at least in part on the EH category of the third UE. In this example, SIB1-EH2 may be periodically transmitted (e.g., the schedule is identified by SIB-EH and is not transmitted in response to a system information request). The third UE may monitor SIB1-EH2 based at least in part on the information including SIB-EH and the third UE being included in the EH category corresponding to SIB1-EH2. Like SIB1 and SIB1-EH1, SIB1-EH2 may include RMSI, information indicating the availability and scheduling of other SIBs (EH-specific SIBs or other SIBs), and information indicating which other SIBs can be used on demand, etc.

[0101] As shown by reference numeral 635, the network node may send and at least one UE (e.g., a first UE and a second UE) may receive another SIB that is not EH specific. In this example, SIB2 is not EH specific, but is received by both the first UE and the second UE. In this case, the second UE may be included in an EH category that is capable of receiving SIB2 without changing one or more SIB characteristics of SIB2. Therefore, the network node may abandon the transmission of SIB2 that is specific to an EH category (e.g., EH1), which may save resources while enabling the second UE to efficiently receive system information included in SIB2. For example, SIB2 may be transmitted in a single TB. In this example, although a system information request for SIB2 is not shown, SIB2 may be transmitted periodically or on demand, like other SIBs.

[0102] As shown by reference numeral 640, the network node may send and at least one UE (e.g., a third UE) may receive another EH-specific SIB (e.g., SIB2-EH2). In this example, SIB2-EH2 is EH-specific and may be sent and / or received in a manner similar to SIB 1-EH2 described herein. In this case, SIB2-EH2 may have one or more characteristics different from SIB2 to enable the third UE to obtain system information obtained within the SIB2-EH2.

[0103] In some aspects, a network node may be configured with information identifying multiple EH-specific SIB sets for transmission to an EH UE, such as an EH-specific SIB set for each EH class. In this case, some EH-specific SIBs may be included in more than one EH-specific SIB set (e.g., if multiple EH classes are capable of receiving the same EH-specific SIB), and some EH-specific SIB sets may include one or more SIBs that are not EH-specific. For example, an EH UE with relatively high capabilities (e.g., for charging, energy storage, and / or communication processing) may be able to receive some SIBs that are not EH-specific, while an EH UE with relatively low capabilities may require most or even all SIBs to be EH-specific.

[0104] By sending different SIBs for UEs associated with different EH capabilities, the UEs can obtain system information in a manner that accounts for the impact that EH has on the capabilities of the UE. In this way, network nodes and EH UEs can communicate system information more efficiently (e.g., relative to relying on legacy SIBs and / or duty cycle transmissions), better support lower-capability EH UEs to be able to obtain system information, and have fewer dropped communications between network nodes and EH UEs, etc.

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

[0106] Figure 7 7 is a diagram illustrating an example process 700 performed, for example, by a UE according to the present disclosure. Example process 700 is an example in which a UE (eg, UE 120) performs operations associated with system information acquisition.

[0107] like Figure 7 As shown in FIG. 7 , in some aspects, process 700 may include receiving, from a network node, a first SIB indicating an EH category supported by the network node (block 710). Fig. 9 The communication manager 140 and / or receiving component 902 depicted in FIG. 1 may receive a first SIB from a network node indicating EH categories supported by the network node, as described above.

[0108] like Figure 7 As further shown in FIG. 7 , in some aspects, process 700 may include receiving, from a network node and based at least in part on receiving the first SIB and the UE being associated with the EH category, a second SIB having one or more SIB characteristics based at least in part on the EH category (block 720). For example, a UE (e.g., using Fig. 9 The communication manager 140 and / or receiving component 902 depicted in the figure can receive a second SIB having one or more SIB characteristics based at least in part on the EH category from the network node and at least in part on receiving the first SIB and the UE is associated with the EH category, as described above.

[0109] Process 700 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.

[0110] In a first aspect, the one or more SIB characteristics include at least one of: the second SIB is transmitted via multiple transport blocks; the second SIB includes a parameter based at least in part on the EH category; or for a parameter, the second SIB includes a parameter value based at least in part on the EH category.

[0111] In a second aspect, alone or in combination with the first aspect, a first SIB indicates one or more resources via which a second SIB is to be transmitted.

[0112] In a third aspect, alone or in combination with one or more of the first and second aspects, the EH category is associated with at least one of: a maximum number of communications at full charge, a charging rate, or a duration for obtaining a full charge.

[0113] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first SIB includes information identifying a plurality of different EH categories supported by the network node.

[0114] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, receiving a first SIB includes: receiving a PBCH communication including a MIB and a first SIB; decoding the MIB to obtain one or more parameters for decoding the first SIB; and decoding the first SIB.

[0115] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, receiving the second SIB includes receiving the second SIB via a plurality of transport blocks.

[0116] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 700 includes receiving at least one other SIB in a single transport block.

[0117] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the first SIB further indicates one or more resources in which one or more other SIBs are to be sent.

[0118] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the first SIB further indicates that at least one of the second SIB or at least one of the one or more other SIBs is to be sent via multiple transport blocks.

[0119] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, for the EH category, the first SIB further indicates which SIBs among the plurality of other SIBs can be used as needed.

[0120] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 700 includes sending a request for a second SIB to a network node based at least in part on the first SIB indicating that the second SIB can be used as needed.

[0121] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the request is included in a physical random access channel message.

[0122] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the request includes a preamble associated with an EH category.

[0123] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the request is included in a PUSCH message associated with a random access procedure.

[0124] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the request is indicated by a MAC control element included in a PUSCH message.

[0125] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the MAC control element indicates a second SIB and an EH category.

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

[0127] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a network node in accordance with the present disclosure. The example process 800 is an example in which a network node (eg, network node 110) performs operations associated with system information acquisition.

[0128] like Figure 8 As shown in FIG. 8 , in some aspects, process 800 may include sending a first SIB indicating an EH category supported by a network node (block 810). For example, a network node (e.g., using Fig.10 The communication manager 150 and / or the sending component 1004 depicted in FIG. 1004 may send a first SIB indicating EH categories supported by the network node, as described above.

[0129] like Figure 8 As further shown in FIG. 8 , in some aspects, process 800 may include sending a second SIB having one or more SIB characteristics based at least in part on the EH category (block 820). For example, a network node (e.g., using Fig.10 The communication manager 150 and / or the sending component 1004 depicted in FIG. 1004 may send a second SIB having one or more SIB characteristics based at least in part on the EH category, as described above.

[0130] 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.

[0131] In a first aspect, the one or more SIB characteristics include at least one of: the second SIB is transmitted via multiple transport blocks; the second SIB includes a parameter based at least in part on the EH category; or for a parameter, the second SIB includes a parameter value based at least in part on the EH category.

[0132] In a second aspect, alone or in combination with the first aspect, a first SIB indicates one or more resources via which a second SIB is to be transmitted.

[0133] In a third aspect, alone or in combination with one or more of the first and second aspects, the EH category is associated with at least one of: a maximum number of communications at full charge, a charging rate, or a duration for obtaining a full charge.

[0134] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the first SIB includes information identifying a plurality of different EH categories supported by the network node.

[0135] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, sending the first SIB includes sending a PBCH communication including the MIB and the first SIB.

[0136] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, sending the second SIB includes sending the second SIB via a plurality of transport blocks.

[0137] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the first SIB further indicates one or more resources in which one or more other SIBs are to be sent.

[0138] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the first SIB further indicates that at least one of the second SIB or at least one of the one or more other SIBs is to be sent via multiple transport blocks.

[0139] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, for the EH category, the first SIB further indicates which SIBs among the plurality of other SIBs can be used as needed.

[0140] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 800 includes receiving a request for a first SIB from a UE, and wherein sending the first SIB includes sending the first SIB based at least in part on receiving the request.

[0141] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 800 includes receiving a request for a second SIB from a UE, and wherein sending the second SIB includes sending the second SIB based at least in part on receiving the request.

[0142] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the request is included in a physical random access channel message.

[0143] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the request includes a preamble associated with an EH category.

[0144] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the request is included in a PUSCH message associated with a random access procedure.

[0145] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the request is indicated by a MAC control element included in a PUSCH message.

[0146] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the MAC control element indicates a second SIB and an EH category.

[0147] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 800 includes sending a third SIB associated with another EH category different from the EH category, the third SIB including one or more parameters matching the second SIB.

[0148] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the second SIB is included in a first SIB set of a plurality of SIB sets, each SIB set of the plurality of SIB sets corresponding to a respective EH category.

[0149] 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.

[0150] Fig. 9is a diagram of an example apparatus 900 for wireless communication according to the present disclosure. Apparatus 900 may be a UE, or a UE may include apparatus 900. In some aspects, apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using receiving component 902 and transmitting component 904. As further shown, apparatus 900 may include a communication manager 140. Communication manager 140 may include one or more other components.

[0151] In some aspects, the apparatus 900 may be configured to perform the Figures 4 to 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 and / or Fig. 9 One or more of the components shown in the figure may include a combination of Figure 2 Additionally or alternatively, Fig. 9 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 instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

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

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

[0154] Receiving component 902 can receive from the network node a first SIB indicating an EH category supported by the network node. Receiving component 902 can receive from the network node and based at least in part on receiving the first SIB and the UE being associated with the EH category, a second SIB having one or more SIB characteristics based at least in part on the EH category.

[0155] Receiving component 902 can receive at least one other SIB in a single transport block.

[0156] Transmitting component 904 can transmit a request for a second SIB to a network node based at least in part on the first SIB indicating that the second SIB can be used as needed.

[0157] Fig. 9 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 9 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 9 Two or more components shown in the figure may be implemented in a single component, or Fig. 9 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig. 9 Another set of components shown in the figure performs one or more functions.

[0158] Fig.101 is a diagram of an example apparatus 1000 for wireless communication according to the present disclosure. Apparatus 1000 may be a network node, or a network node 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 communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 150. Communication manager 150 may include one or more other components.

[0159] In some aspects, the apparatus 1000 may be configured to perform the Figures 4 to 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein, such as Figure 8 The process 800. In some aspects, Fig.10 The device 1000 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 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 instructions or code stored in a non-transitory computer-readable medium and may 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 apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 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) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

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

[0162] Transmitting component 1004 may transmit a first SIB indicating an EH class supported by the network node.Transmitting component 1004 may transmit a second SIB having one or more SIB characteristics based at least in part on the EH class.

[0163] Receiving component 1002 can receive a request for a first SIB from a UE.

[0164] Receiving component 1002 can receive a request for a second SIB from a UE.

[0165] Transmitting component 1004 can transmit a third SIB associated with another EH class different from the EH class, the third SIB including one or more parameters matching the second SIB.

[0166] Fig.10 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.10 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.10 Two or more components shown in the figure may be implemented in a single component, or Fig.10 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.10 The assembly of (one or more) components shown in the figure may perform the operations described as being performed by Fig.10 Another set of components shown in the figure performs one or more functions.

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

[0168] Aspect 1: A method of wireless communication performed by a UE, comprising: receiving a first SIB indicating an energy harvesting capability category supported by the network node from a network node; and receiving a second SIB having one or more SIB characteristics at least partially based on the energy harvesting capability category from the network node and at least partially based on receiving the first SIB and the UE being associated with the energy harvesting capability category.

[0169] Aspect 2: A method according to Aspect 1, wherein the one or more SIB characteristics include at least one of the following: the second SIB is sent via multiple transmission blocks; the second SIB includes parameters based at least in part on the energy harvesting capability category; or for parameters, the second SIB includes parameter values ​​based at least in part on the energy harvesting capability category.

[0170] Aspect 3: The method according to any one of aspects 1 to 2, wherein the first SIB indicates one or more resources, and the second SIB is to be sent via the one or more resources.

[0171] Aspect 4: The method according to any one of aspects 1 to 3, wherein the energy harvesting capability category is associated with at least one of: a maximum number of communications at full charge, a charging rate, or a duration for acquiring the full charge.

[0172] Aspect 5: The method according to any one of aspects 1 to 4, wherein the first SIB comprises information identifying a plurality of different energy harvesting capability categories supported by the network node.

[0173] Aspect 6: A method according to any one of Aspects 1 to 5, wherein receiving the first SIB comprises: receiving a PBCH communication including a MIB and the first SIB; decoding the MIB to obtain one or more parameters for decoding the first SIB; and decoding the first SIB.

[0174] Aspect 7: The method according to any one of aspects 1 to 6, wherein receiving the second SIB includes: receiving the second SIB via multiple transport blocks.

[0175] Aspect 8: The method according to aspect 7 further comprises: receiving at least one other SIB in a single transport block.

[0176] Aspect 9: The method according to any one of aspects 1 to 8, wherein the first SIB further indicates one or more resources, and one or more other SIBs are to be sent in the one or more resources.

[0177] Aspect 10: The method according to aspect 9, wherein the first SIB further indicates that at least one of the second SIB or at least one of the one or more other SIBs is to be transmitted via multiple transport blocks.

[0178] Aspect 11: The method according to any one of aspects 1 to 10, wherein for the energy harvesting capability category, the first SIB further indicates which SIBs among a plurality of other SIBs can be used as needed.

[0179] Aspect 12: The method according to aspect 11 further comprises: sending a request for the second SIB to the network node based at least in part on the first SIB indicating that the second SIB can be used as needed.

[0180] Aspect 13: The method according to aspect 12, wherein the request is included in a physical random access channel message.

[0181] Aspect 14: The method of aspect 13, wherein the request includes a preamble associated with the energy harvesting capability category.

[0182] Aspect 15: The method according to aspect 12, wherein the request is included in a PUSCH message associated with a random access procedure.

[0183] Aspect 16: The method according to aspect 15, wherein the request is indicated by a MAC control element included in the PUSCH message.

[0184] Aspect 17: The method according to Aspect 16, wherein the MAC control element indicates the second SIB and the energy harvesting capability category.

[0185] Aspect 18: A method of wireless communication performed by a network node, comprising: transmitting a first SIB indicating an energy harvesting capability class supported by the network node; and transmitting a second SIB having one or more SIB characteristics based at least in part on the energy harvesting capability class.

[0186] Aspect 19: A method according to Aspect 18, wherein the one or more SIB characteristics include at least one of the following: the second SIB is sent via multiple transmission blocks; the second SIB includes parameters based at least in part on the energy harvesting capability category; or for parameters, the second SIB includes parameter values ​​based at least in part on the energy harvesting capability category.

[0187] Aspect 20: The method according to any one of aspects 18 to 19, wherein the first SIB indicates one or more resources, and the second SIB is to be sent via the one or more resources.

[0188] Aspect 21: The method according to any one of aspects 18 to 20, wherein the energy harvesting capability category is associated with at least one of the following: a maximum number of communications at a full charge, a charging rate, or a duration for obtaining the full charge.

[0189] Aspect 22: The method according to any one of aspects 18 to 21, wherein the first SIB comprises information identifying a plurality of different energy harvesting capability categories supported by the network node.

[0190] Aspect 23: The method according to any one of aspects 18 to 22, wherein sending the first SIB includes: sending a PBCH communication including the MIB and the first SIB.

[0191] Aspect 24: The method according to any one of aspects 18 to 23, wherein sending the second SIB comprises: sending the second SIB via multiple transport blocks.

[0192] Aspect 25: The method according to any one of aspects 18 to 24, wherein the first SIB further indicates one or more resources in which one or more other SIBs are to be sent.

[0193] Aspect 26: The method according to aspect 25, wherein the first SIB further indicates that at least one of the second SIB or at least one of the one or more other SIBs is to be transmitted via multiple transport blocks.

[0194] Aspect 27: The method according to any one of aspects 18 to 26, wherein for the energy harvesting capability category, the first SIB further indicates which SIBs among a plurality of other SIBs can be used as needed.

[0195] Aspect 28: The method according to any one of aspects 18 to 27, further comprising: receiving a request for the first SIB from a UE; and wherein sending the first SIB comprises: sending the first SIB based at least in part on receiving the request. Wherein sending the first SIB comprises: sending the first SIB based at least in part on receiving the request.

[0196] Aspect 29: The method according to any one of aspects 18 to 28, further comprising: receiving a request for the second SIB from a UE; and wherein sending the second SIB comprises: sending the second SIB based at least in part on receiving the request. Wherein sending the second SIB comprises: sending the second SIB based at least in part on receiving the request.

[0197] Aspect 30: The method according to aspect 29, wherein the request is included in a physical random access channel message.

[0198] Aspect 31: The method according to aspect 30, wherein the request includes a preamble associated with the energy harvesting capability category.

[0199] Aspect 32: The method according to aspect 29, wherein the request is included in a PUSCH message associated with a random access procedure.

[0200] Aspect 33: The method according to aspect 32, wherein the request is indicated by a MAC control element included in the PUSCH message.

[0201] Aspect 34: The method according to Aspect 33, wherein the MAC control element indicates the second SIB and the energy harvesting capability category.

[0202] Aspect 35: The method according to any one of Aspects 18 to 34 further includes: sending a third SIB associated with another energy harvesting capability category different from the energy harvesting capability category, the third SIB including one or more parameters matching the second SIB.

[0203] Aspect 36: The method according to any one of aspects 18 to 35, wherein the second SIB is included in a first SIB set of a plurality of SIB sets, each SIB set of the plurality of SIB sets corresponding to a corresponding energy harvesting capability category.

[0204] Aspect 37: 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 17.

[0205] Aspect 38: 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 18 to 36.

[0206] Aspect 39: A device for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 17.

[0207] Aspect 40: An apparatus for wireless communication, comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 18 to 36.

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

[0209] Aspect 42: An apparatus for wireless communication, comprising: at least one component for performing the method according to one or more of aspects 18 to 36.

[0210] Aspect 43: 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 17.

[0211] Aspect 44: 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 18 to 36.

[0212] Aspect 45: 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 17.

[0213] Aspect 46: 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 18 to 36.

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

[0215] 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, execution threads, processes and / or functions, etc. As used herein, "processor" is implemented by hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the systems and / or methods are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the systems and / or methods based at least in part on the description herein.

[0216] 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.

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

[0218] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "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 you only want to refer to an item, the phrase "only one" or similar terms will be 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 mean "based at least in part on", unless otherwise explicitly stated. 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 expressly 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, the one or more processors coupled to the memory, the one or more processors configured to: receiving, from a network node, a first system information block (SIB) indicating a class of energy harvesting capabilities supported by the network node; as well as A second SIB having one or more SIB characteristics based at least in part on the energy harvesting capability class is received from the network node and based at least in part on receiving the first SIB and the UE being associated with the energy harvesting capability class.

2. The UE according to claim 1, wherein the one or more SIB characteristics include at least one of the following: The second SIB is sent via a plurality of transport blocks, The second SIB includes parameters based at least in part on the energy harvesting capability category, or For parameters, the second SIB includes parameter values ​​based at least in part on the energy harvesting capability category. 3 . The UE according to claim 1 , wherein the first SIB indicates one or more resources, and the second SIB is to be sent via the one or more resources.

4. The UE of claim 1 , wherein the energy harvesting capability category is associated with at least one of: Maximum number of communications under full charge, Charge rate, or Used to obtain the duration of the full charge. 5 . The UE of claim 1 , wherein the first SIB comprises information identifying a plurality of different energy harvesting capability categories supported by the network node.

6. The UE of claim 1 , wherein to receive the first SIB, the one or more processors are configured to: receiving a physical broadcast channel (PBCH) communication including a master information block (MIB) and the first SIB; decoding the MIB to obtain one or more parameters for decoding the first SIB; and The first SIB is decoded.

7. The UE of claim 1 , wherein to receive the second SIB, the one or more processors are configured to: The second SIB is received via a plurality of transport blocks.

8. The UE of claim 7, wherein the one or more processors are further configured to: At least one other SIB is received in a single transport block.

9. The UE of claim 1, wherein the first SIB further indicates one or more resources in which one or more other SIBs are to be transmitted. 10 . The UE of claim 9 , wherein the first SIB further indicates that at least one of the second SIB or at least one of the one or more other SIBs is to be transmitted via a plurality of transport blocks. 11 . The UE according to claim 1 , wherein for the energy harvesting capability category, the first SIB further indicates which SIBs among a plurality of other SIBs can be used as needed.

12. The UE of claim 11, wherein the one or more processors are further configured to: A request for the second SIB is sent to the network node based at least in part on the first SIB indicating that the second SIB can be used as needed.

13. The UE of claim 12, wherein the request is included in a physical random access channel message.

14. The UE of claim 13, wherein the request comprises a preamble associated with the energy harvesting capability class.

15. The UE of claim 12, wherein the request is included in a Physical Uplink Shared Channel (PUSCH) message associated with a random access procedure.

16. The UE of claim 15, wherein the request is indicated by a medium access control (MAC) control element included in the PUSCH message. 17 . The UE according to claim 16 , wherein the MAC control element indicates the second SIB and the energy harvesting capability category.

18. A network node for wireless communication, comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: sending a first system information block (SIB) indicating a class of energy harvesting capabilities supported by the network node; as well as A second SIB is transmitted having one or more SIB characteristics based at least in part on the energy harvesting capability class.

19. The network node of claim 18, wherein the one or more SIB characteristics include at least one of: The second SIB is sent via a plurality of transport blocks, The second SIB includes parameters based at least in part on the energy harvesting capability category, or For parameters, the second SIB includes parameter values ​​based at least in part on the energy harvesting capability category.

20. The network node of claim 18, wherein the first SIB indicates one or more resources via which the second SIB is to be sent.

21. The network node of claim 18, wherein the energy harvesting capability category is associated with at least one of: Maximum number of communications under full charge, Charging rate, or Used to obtain the duration of the full charge.

22. The network node of claim 18, wherein the first SIB includes information identifying a plurality of different energy harvesting capability categories supported by the network node.

23. The network node of claim 18, wherein to send the first SIB, the one or more processors are configured to: A physical broadcast channel (PBCH) communication including a master information block (MIB) and the first SIB is transmitted.

24. The network node of claim 18, wherein to send the second SIB, the one or more processors are configured to: The second SIB is transmitted via a plurality of transport blocks.

25. The network node of claim 18, wherein the first SIB further indicates one or more resources in which one or more other SIBs are to be sent.

26. The network node of claim 25, wherein the first SIB further indicates that at least one of the second SIB or at least one of the one or more other SIBs is to be sent via multiple transport blocks.

27. The network node of claim 18, wherein for the energy harvesting capability category, the first SIB further indicates which SIBs among a plurality of other SIBs can be used as needed.

28. The network node of claim 18, wherein the one or more processors are further configured to: receiving a request for the first SIB from a user equipment (UE); and Wherein, in order to send the first SIB, the one or more processors are configured to: The first SIB is sent based at least in part on receiving the request.

29. A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a network node, a first system information block (SIB) indicating a class of energy harvesting capabilities supported by the network node; as well as A second SIB having one or more SIB characteristics based at least in part on the energy harvesting capability class is received from the network node and based at least in part on receiving the first SIB and the UE being associated with the energy harvesting capability class.

30. A method of wireless communication performed by a network node, comprising: sending a first system information block (SIB) indicating a class of energy harvesting capabilities supported by the network node; as well as A second SIB is transmitted having one or more SIB characteristics based at least in part on the energy harvesting capability class.

Images