Power control of intermediate UE for ambient IoT system
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-09-29
- Publication Date
- 2026-08-13
Smart Images
Figure CN2025125372_13082026_PF_FP_ABST
Abstract
Description
POWER CONTROL OF INTERMEDIATE UE FOR AMBIENT IOT SYSTEMTECHNICAL FIELD
[0001] The present disclosure relates to wireless communications, and more specifically to a user equipment (UE) , a network entity, a processor for wireless communication and methods for power control of UE.BACKGROUND
[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. Each network communication devices, such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) . Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)) .
[0003] In recent years, Internet of Things (IoT) has attracted much attention in the wireless communication world. More “things” are expected to be interconnected for improving productivity efficiency and increasing comforts of life. Study on solutions for ambient IoT in NR has been approved by 3GPP. In future release such as 6G, enhancement on ambient IoT is still needed.SUMMARY
[0004] The present disclosure relates to a user equipment (UE) , a network entity, a processor for wireless communication, methods and a computer readable medium for power control of UE for A-IoT system.
[0005] In a first aspect, there is provided a UE. The UE comprises: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol; determine a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message; and perform the R2D transmission with the determined transmit power.
[0006] In a second aspect, there is provided a network entity. The network entity comprises: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: transmit, to a user equipment (UE) , at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol.
[0007] In a third aspect, there is provided a processor for wireless communication. The processor comprises: at least one memory; and a controller coupled with the at least one memory and configured to cause the controller to: receive, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol; determine a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message; and perform the R2D transmission with the determined transmit power.
[0008] In a fourth aspect, there is provided a method performed by a user equipment (UE) , the method comprising: receiving, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol; determining a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message; and performing the R2D transmission with the determined transmit power.
[0009] In an fifth aspect, there is provided a method performed by a network entity, the method comprising: transmitting, to a user equipment (UE) , at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol.
[0010] In a sixth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed by a processor of an apparatus, causing the apparatus to perform the method according to the fourth or the fifth aspect of the disclosure.
[0011] In some implementations of the methods, the UE and the network entity described herein, the R2D message is one of a paging message or an access trigger message, and wherein, to determine the transmit power of R2D transmission carrying the R2D message, the UE determines a first transmit power as the first maximum transmit power or as a function of the first maximum transmit power and an offset corresponding to the M value of the R2D transmission.
[0012] In some implementations of the methods, the UE and the network entity described herein, the R2D message is a random identifier (ID) response message, and wherein, to determine the transmit power of R2D transmission carrying the R2D message, the UE determines a first transmit power as the first maximum transmit power or as a function of the first maximum transmit power and an offset corresponding to the M value of the R2D transmission.
[0013] In some implementations of the methods, the UE and the network entity described herein, the R2D message is a random ID response message, and wherein, to determine the transmit power of R2D transmission carrying the R2D message, the UE determines the first transmit power as a function of the first maximum transmit power and a maximum pathloss between the UE and devices echoed in the random ID response message.
[0014] In some implementations of the methods, the UE and the network entity described herein, the first transmit power is determined as a function of the first maximum transmit power, the maximum pathloss between the UE and the devices echoed in the random ID response message, and an offset corresponding to the M value of the R2D transmission.
[0015] In some implementations of the methods, the UE and the network entity described herein, the at least one parameter further comprises at least one of: one or more parameters related to Uu interface; or a second maximum transmit power or an offset related to the first maximum transmit power.
[0016] In some implementations of the methods, the UE and the network entity described herein, to determine the transmit power of R2D transmission carrying the R2D message, the UE determines a second transmit power as a function of the pathloss between the UE and the base station and the one or more parameters related to Uu interface; and / or determine a third transmit power as the second maximum transmit power, or based on the offset related to the first maximum transmit power and the first maximum transmit power.
[0017] In some implementations of the methods, the UE and the network entity described herein, to determine the transmit power of R2D transmission carrying the R2D message, the UE further determines the transmit power of the R2D transmission as a minimum of the first transmit power and the second transmit power.
[0018] In some implementations of the methods, the UE and the network entity described herein, to determine the transmit power of R2D transmission carrying the R2D message, the UE determines the transmit power of the R2D transmission as a minimum of the first transmit power and the third transmit power.
[0019] In some implementations of the methods, the UE and the network entity described herein, to determine the transmit power of R2D transmission carrying the R2D message, the UE determines the transmit power of the R2D transmission as a minimum of the first transmit power, the second transmit power and the third transmit power.BRIEF DESCRIPTION OF THE DRAWINGS
[0020] FIG. 1 illustrates an example of a wireless communications system in which some embodiments of the present disclosure can be implemented.
[0021] FIG. 2A illustrates Topology 2 where a UE acts an intermediate node between a base station and ambient IoT device (s) .
[0022] FIG. 2B illustrates an example of an ambient IoT system based on Topology 2.
[0023] FIG. 3 illustrates a process flow of a procedure for power control of intermediate UE for an ambient IoT system in accordance with some example embodiments of the present disclosure.
[0024] FIG. 4 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure.
[0025] FIG. 5 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure.
[0026] FIG. 6 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.
[0027] FIG. 7 illustrates a flowchart of a method performed by a network entity in accordance with aspects of the present disclosure.
[0028] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.DETAILED DESCRIPTION
[0029] Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. The disclosure described herein can be implemented in various manners other than the ones described below. In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0030] References in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
[0031] It shall be understood that although the terms “first” and “second” or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, procedures, or apparatuses are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
[0032] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of embodiments. As used herein, the singular forms “a, ” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises, ” “comprising, ” “has, ” “having, ” “includes” and / or “including, ” when used herein, specify the presence of stated features, elements, components and / or the like, but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof. For example, the term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ” The term “based on” is to be read as “based at least in part on. ” The term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ” The term “another embodiment” is to be read as “at least one other embodiment. ” The use of an expression such as “A and / or B” can mean either “only A” or “only B” or “both A and B. ” Other definitions, explicit and implicit, may be included below.
[0033] Aspects of the present disclosure are described in the context of a wireless communications system. FIG. 1 illustrates an example of a wireless communications system 100 in which some embodiments of the present disclosure can be implemented. The wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
[0034] The one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology. A network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface. In a 3GPP non-terrestrial network (NTN) , a network entity 102 in form of a satellite can directly communicate to UE 104 using NR / LTE Uu interface. The satellite may be a transparent satellite or a regenerative satellite. For NTN with a transparent satellite, a base station on earth may communicate with a UE via the satellite. For NTN with a regenerative satellite, the base station may be on board and directly communicate with the UE.
[0035] A network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112. For example, a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies. In some implementations, a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0036] The one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, an ambient IoT device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In some other implementations, a UE 104 may be mobile in the wireless communications system 100.
[0037] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1. Additionally, or alternatively, a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
[0038] A UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface. In some embodiments, a UE 104 may be an ambient IoT device which supports backscattered transmission to the network entities 102 or other UEs 104.
[0039] A network entity 102 may support communications with the core network 106, or with another network entity 102, or both. For example, a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) . The network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) . In some implementations, the network entities 102 may communicate with each other directly (e.g., between the network entities 102) . In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) . In some implementations, one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) . An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
[0040] In some implementations, a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 102 may include one or more of a central unit (CU) , a distributed unit (DU) , a radio unit (RU) , a RAN Intelligent Controller (RIC) (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
[0041] An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) . In some implementations, one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU)) .
[0042] Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU. For example, a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack. In some implementations, the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160.
[0043] Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or multiple different cells (e.g., via one or more RUs) . In some implementations, a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
[0044] A CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u) , and a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface) . In some implementations, a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
[0045] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as registration management, mobility management, connection management, access authentication and authorization etc. for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
[0046] The core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) . The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102. The core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) . The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
[0047] In the wireless communications system 100, the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) . In some implementations, the network entities 102 and the UEs 104 may support different resource structures. For example, the network entities 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the network entities 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) . The network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0048] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0049] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames) . Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0050] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) . In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0051] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) . In some implementations, the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) . In some implementations, FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0052] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) . For example, FR1 may be associated with a first numerology (e.g., μ=0) , which includes 15 kHz subcarrier spacing; a second numerology (e.g., μ=1) , which includes 30 kHz subcarrier spacing; and a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) . For example, FR2 may be associated with a third numerology (e.g., μ=2) , which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., μ=3) , which includes 120 kHz subcarrier spacing.
[0053] Work Item Description (WID) ‘New WID on Solutions for Ambient IoT (Internet of Things) in NR Phase 2 [RP-251885] has been agreed with the support of topology 2, including support for Deployment Scenario 2 with Topology 2 with intermediate UE as Reader. One of the objectives includes necessary power control and collision handling procedures between intermediate UE and base station (BS) .
[0054] According to the WID the power control of intermediate UE needs to be studied. Intermediate UE is in the coverage of serving gNB, and the ambient IoT system supports standalone, in-band and guardband deployment. For the power control of intermediate UE following aspects need to be considered: The transmit power of reader to device (R2D) to ensure the coverage / signal quality of Ambient IoT system. For in-band and guardband deployment the interference to uplink reception shall be controlled, e.g., interference due to IBE of Ambient IoT system. Interference to other intermediate UE when multiple intermediate UEs are under one serving gNB.
[0055] FIG. 2A illustrates Topology 2 where a UE acts an intermediate node between a base station and ambient IoT device (s) . As illustrated, the ambient IoT device communicates bidirectionally with an intermediate node between the device and a base station. In this topology, the intermediate node can be a UE which is capable of ambient IoT. The intermediate node may transfer ambient IoT data and / or signalling between the BS and the ambient IoT device.
[0056] FIG. 2B illustrates an example of an ambient IoT system based on Topology 2. For the inventory of an A-IoT system, the power control of intermediate UE is related to the control of transmit power of reader to device (R2D) transmission, the R2D transmission during an inventory procedure includes R2D transmission carrying paging message, R2D transmission carrying access occasion trigger message and R2D transmission carrying random ID response message (i.e., Msg2 in contention-based random access (CBRA)) .
[0057] For the power control of intermediate UE, the following aspects are considered in this disclosure. Aspect #1, the transmit power of intermediate UE could guarantee reliable communication within the A-IoT system. Aspect #2, the transmit power of intermediate UE in controlled to avoid higher interference to NR Uu UE for in-band and guard-band deployment due to in-band emission (IBE) . Aspect #3 the transmit power of intermediate UE is controlled to avoid the interference to other intermediate UE since multiple intermediate UEs may be in one gNB.
[0058] FIG. 3 illustrates a process flow of a procedure for power control of intermediate UE for an ambient IoT system in accordance with some example embodiments of the present disclosure. The process flow 300 may involve a UE 301, a network entity 302, and one or more ambient IoT devices 303. The process flow 300 may be applied to the wireless communications system 100 with reference to FIG. 1, for example, the UE 301 may be any of UEs 104 acting as an intermediate node in an ambient IoT system. In some cases, the network entity 302 may be any of the network entities 102, for example, the network entity 302 may be a base station (e.g., gNB) . It would be appreciated that the process flow 300 may be applied to other communication scenarios.
[0059] At 310, the network entity 302 transmits, to the UE 301, at least one parameter 315 related power control of R2D transmission. Correspondingly, at 320, the UE 301 receives the at least one parameter 315 from the network entity 302.
[0060] In some embodiments, the at least one parameter 315 may comprise a first maximum transmit power (PCMAX) ; or a list of offsets corresponding to different M values, where each M value represents a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol. These parameters are related to Aspect #1, and can be used by the UE 301 to determine its transmit power to ensure reliable communication within the A-IoT system.
[0061] In some embodiments, the at least one parameter 315 may comprise one or more parameters related to Uu interface. These parameters correspond to Aspect #2, and can be used by the UE 301 to control the transmit power of R2D transmission, thereby avoiding excessive interference to NR Uu UE for in-band and guard-band deployment.
[0062] In some embodiments, the at least one parameter 315 may further comprise a second maximum transmit power (PCMAX2) or an offset related to the first maximum transmit power. These parameters correspond to Aspect #3, and can be used by the UE 301 to control the transmit power of R2D transmission, for the purpose of avoiding interference to other intermediate UEs. A detailed description of how the network-provided parameters are used will be presented in the following sections.
[0063] At 330, the UE 301 determines a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message. For R2D transmission during an inventory procedure, several R2D messages could be carried by R2D transmission, including paging message, ransom identifier (ID) response message (i.e., Msg2 in a random access (RACH) procedure) and access occasion trigger message. Depending on the type of R2D message, the UE may apply different power control schemes.
[0064] At 340, the UE 301 performs the R2D transmission with the determined transmit power, and the R2D message 345 is transmitted to the ambient IoT device (s) 303.
[0065] In some embodiments, the UE may determine respective transmit powers for Aspects #1, #2, and #3, namely P1, P2, and P3, and may apply a final transmit power (P) for the R2D transmission based on any combination of P1, P2, and P3, as indicated by the network or as determined by the UE implementation. Details are provided below.
[0066] With respect to Aspect #1, a first transmit power (P1) of intermediate UE may be determined to guarantee the communication of the A-IoT system. For R2R transmission carrying a paging message or an access occasion trigger message, the R2D transmission is broadcasted. Therefore, the first transmit power could be based on a maximum transmit power configured by the NW, e.g., PCMAX, . P1=PCMAX [dBm]
[0067] According to the study and evaluation of A-IoT, the coverage of R2D transmission is impacted by the M value. The coverage of R2D transmission is decreased when M value is increased, for example, the coverage of R2D with M=24 is much smaller than the coverage of R2D with M=2. In the inventory procedure, the changing of M value will cause the device to perform D2R transmission in incorrect access occasion, for example, if intermediate UE changes the M value of R2D transmission carrying Access occasion trigger message to 24 and the M value of R2D transmission carrying a paging message is smaller than 24, some devices may miss the R2D transmission carrying the access trigger message and cannot identify correct access occasion.
[0068] To ensure same or similar coverage of different M values, the transmit power of R2D transmission could be related to M value. In some embodiments, the UE may determine the first transmit power as a function of the first maximum transmit power and an offset corresponding to the M value of the R2D transmission.
[0069] For example, the configured maximum transmit power of the intermediate UE is only applied for the maximum M value, e.g., M=24, when M value is not the maximum M value, the transmit power of R2D transmission could be reduced with an offset, details could be as following: When M=24, the transmit power of intermediate UE is P1=PCMAX [dBm] . For other M values (e.g., 2 / 6 / 12) , the transmit power is P1=PCMAX-Δoffset_M [dBm] . The Δoffset_M could be a pre-defined or configured list related to each M value, for example, Δoffset_2 when M=2, Δoffset_6 when M=6, Δoffset_12 when M=12. Alternatively, a factor value f (M) could be configured or pre-defined for different M values, for example, P1=PCMAX-10 log10 (f (M)) [dBm]
[0070] For R2D transmission carrying a random ID response message, the transmit power may depend on the types of ambient IoT devices. For example, if the inventory procedure involves passive device (s) , the intermediate UE has no knowledge of the pathloss between intermediate UE and a specified device. In this case, the transmit power for R2D transmission carrying random ID response message could be the same as for the paging message or the access occasion trigger message. That is, the first transmit power (P1) may be the configured maximum transmit power (PCMAX) or as a function of the first maximum transmit power and an offset corresponding to the M value of the R2D transmission.
[0071] If the inventory procedure involves active device (s) , the intermediate UE may know the pathloss between intermediate UE and the device (s) . Therefore, the transmit power could be based on the maximum pathloss between intermediate and multiple devices, the pathloss between intermediate UE and device could be reported by the device together with device to reader (D2R) transmission carrying Msg 1 during RACH.
[0072] Further, depending on whether the impact of M value is considered, the UE may have two options in determining the transmit power for the random ID response message. If the impact of M value is not considered, the transmit power for R2D transmission carrying Random ID response (Msg 2) may be: P1=min (PCMAX, P0+10*log10 (MRB) +α*PLMAX) [dBm] where P0 and α are configured by the NW, MRB is number of resource blocks (RBs) of this R2D transmission.
[0073] If the impact of M value is considered, the power control could be firstly defined for maximum M value, e.g. M=24, P1=min (PCMAX, P0+10*log10 (MRB) +α*PLMAX) [dBm] For other M value (e.g., 2, 6, or 12) , the offset could be introduced as following P1=min (PCMAX, P0+10*log10 (MRB) +α*PLMAX-Δoffset_M) [dBm] where Δoffset_M is a pre-defined or configured list related to each M value, for example, Δoffset_2 when M=2, Δoffset_6 when M=6, Δoffset_12 when M=12. Alternatively, a factor value f (M) could be configured or pre-defined for different M value, for example, P1=min (PCMAX, P0+10*log10 (MRB) +α*PLMAX-10 log10 (f (M) )) [dBm] where PLMAX is the maximum pathloss among multiple devices to be echoed in this R2D transmission.
[0074] With respect to Aspect #2, a second transmit power (P2) of intermediate UE may be determined to avoid the IBE of A-IoT system. The second transmit power may depend on the pathloss between the intermediate UE and the base station.
[0075] In this aspect to avoid the IBE of A-IoT system, the based station (e.g., gNB) could configure parameters related to power control of intermediate UE. For example, parameters related to Uu interface, namely, P0 _Uu and αUu may be configured to the intermediate UE to control the interference to the Uu interface.
[0076] In some embodiments, the intermediate UE may determine the second transmit power as a function of the pathloss between the UE and the base station and the parameter (s) related to the Uu interface. For example, the second transmit power could be determined as follows: P2=P0 _Uu+10 log10 (MRB) +αUu*PLUu [dBm] where PLUu is the pathloss between the base station and the intermediate UE.
[0077] With respect to Aspect #3, the transmit power of the intermediate UE may depend on the location or pathloss among multiple intermediate UEs. Since the intermediate UE is determined by the base station, the base station may have knowledge of the location of each intermediate UE. To mitigate interference between intermediate UEs, the base station may control the transmit power of an intermediate UE by providing one or more additional parameters related to the power control of the R2D transmission to the UE.
[0078] In some embodiments, one additional maximum transmit power could be configured to the intermediate UE, e.g., PCMAX2. The UE may determine a third transmit power (P3) as follows: P3=PCMAX2
[0079] In some embodiments, an offset related to the first maximum transmit power PCMAX could be configured to the intermediate UE. The third transmit power could be: P3=PCMAX-Δoffset
[0080] Whether the interference to other intermediate UE shall be considered or not depends on whether the allocated resources for A-IoT communication overlap. If the resources for two intermediate UEs for A-IoT communication overlap, the interference may need to be considered. The overlapped resource between intermediate UEs could be fully overlapped or partial overlapped. In such cases, the base station may further indicate which resource within the allocated resources shall consider P3, while for the other resource, P3 is not needed to be considered.
[0081] In some embodiments, the final transmit power (P) of the intermediate UE may be determined by considering one or more of the above three aspects. Whether Aspect#2 and Aspect#3 shall be considered or not could be based on the indication of the base station.
[0082] When the UE is not configured with parameters related to the Uu interface and / or is not configured with the second maximum transmit power or an offset to the first maximum transmit power, the UE may not consider Aspect #2 and / or Aspect #3. For example, if P0 _Uu and αUu are not configured to the intermediate UE, it means Aspect#2 is not needed to be considered by the intermediate UE, and if PCMAX2 / Δoffset is not configured to the intermediate UE, it means Aspect#3 is not needed to be considered by intermediate UE.
[0083] Alternatively, the UE may be configured with these parameters and it may determine whether to consider Aspect #2 and / or Aspect #3 based on dynamic activation or deactivation signaling from the base station.
[0084] In some embodiments, if the base station indicates that Aspect#2 and Aspect#3 are not needed to be considered, the final transmit power of intermediate UE could be P=P1
[0085] If the base station indicates that Aspect#2 is needed to be considered and Aspect#3 is not needed to be considered, the final transmit power of the intermediate UE could be P=min {P1, P2}
[0086] If the base station indicates that Aspect#3 is needed to be considered and aspect#2 is not needed to be considered, the final transmit power of the intermediate UE could be P=min {P1, P3}
[0087] If the base station indicates that both Aspect#2 and Aspect#3 are needed to be considered, the final transmit power of the intermediate UE could be P=min {P1, P2, P3}
[0088] FIG. 4 illustrates an example of a device that is suitable for implementing some embodiments of the present disclosure. The device 400 may be an example of a UE 104 or network entity 102 as described herein. The device 400 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 400 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 402, a memory 404, a transceiver 406, and, optionally, an I / O controller 408. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0089] The processor 402, the memory 404, the transceiver 406, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the processor 402, the memory 404, the transceiver 406, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
[0090] In some implementations, the processor 402, the memory 404, the transceiver 406, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 402 and the memory 404 coupled with the processor 402 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 402, instructions stored in the memory 404) .
[0091] For example, the processor 402 may support wireless communication at the device 400 in accordance with examples as disclosed herein. The device 400 may be an example of UE 104, e.g. an ambient IoT device. In this case, the processor 402 may be configured to operable to support means for receiving, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol; means for determining a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message; and means for performing the R2D transmission with the determined transmit power. The processor 402 may be configured to operable to support other means for performing any of the action (s) in the description.
[0092] The device 400 may be an example of a network entity 102 or UE 104. In this case, the processor 402 may be configured to operable to support means for transmitting a command that schedules at least one corresponding uplink (UL) transmission for each of one or more UEs of a plurality of UEs; means for transmitting, to a user equipment (UE) , at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol. The processor 402 may be configured to operable to support other means for performing any of the action (s) in the description.
[0093] The processor 402 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some implementations, the processor 402 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 404) to cause the device 400 to perform various functions of the present disclosure.
[0094] The memory 404 may include random access memory (RAM) and read-only memory (ROM) . The memory 404 may store computer-readable, computer-executable code including instructions that, when executed by the processor 402 cause the device 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executable by the processor 402 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some implementations, the memory 404 may include, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
[0095] The I / O controller 708 may manage input and output signals for the device 400. The I / O controller 408 may also manage peripherals not integrated into the device 400. In some implementations, the I / O controller 408 may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller 408 may utilize an operating system such as or another known operating system. In some implementations, the I / O controller 408 may be implemented as part of a processor, such as the processor 402. In some implementations, a user may interact with the device 400 via the I / O controller 408 or via hardware components controlled by the I / O controller 408.
[0096] In some implementations, the device 400 may include a single antenna 410. However, in some other implementations, the device 400 may have more than one antenna 410 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 406 may communicate bi-directionally, via the one or more antennas 410, wired, or wireless links as described herein. For example, the transceiver 406 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 406 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 410 for transmission, and to demodulate packets received from the one or more antennas 410. The transceiver 406 may include one or more transmit chains, one or more receive chains, or a combination thereof.
[0097] A transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) . The transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) . The transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmit chain may also include one or more antennas 410 for transmitting the amplified signal into the air or wireless medium.
[0098] A receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receive chain may include one or more antennas 410 for receive the signal over the air or wireless medium. The receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0099] FIG. 5 illustrates an example of a processor 500 is suitable for implementing some embodiments of the present disclosure. The processor 500 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 500 may include a controller 502 configured to perform various operations in accordance with examples as described herein. The processor 500 may optionally include at least one memory 504. Additionally, or alternatively, the processor 500 may optionally include one or more arithmetic-logic units (ALUs) 506. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
[0100] The processor 500 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 500) or other memory (e.g., random access memory (RAM) , read-only memory (ROM) , dynamic RAM (DRAM) , synchronous dynamic RAM (SDRAM) , static RAM (SRAM) , ferroelectric RAM (FeRAM) , magnetic RAM (MRAM) , resistive RAM (RRAM) , flash memory, phase change memory (PCM) , and others) .
[0101] The controller 502 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. For example, the controller 502 may operate as a control unit of the processor 500, generating control signals that manage the operation of various components of the processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0102] The controller 502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 504 and determine subsequent instruction (s) to be executed to cause the processor 500 to support various operations in accordance with examples as described herein. The controller 502 may be configured to track memory address of instructions associated with the memory 504. The controller 502 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 502 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 502 may be configured to manage flow of data within the processor 500. The controller 502 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 500.
[0103] The memory 504 may include one or more caches (e.g., memory local to or included in the processor 500 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementation, the memory 504 may reside within or on a processor chipset (e.g., local to the processor 500) . In some other implementations, the memory 504 may reside external to the processor chipset (e.g., remote to the processor 500) .
[0104] The memory 504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 500, cause the processor 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 502 and / or the processor 500 may be configured to execute computer-readable instructions stored in the memory 504 to cause the processor 500 to perform various functions (e.g., functions or tasks supporting transmit power prioritization) . For example, the processor 500 and / or the controller 502 may be coupled with or to the memory 504, the processor 500, the controller 502, and the memory 504 may be configured to perform various functions described herein. In some examples, the processor 500 may include multiple processors and the memory 504 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0105] The one or more ALUs 506 may be configured to support various operations in accordance with examples as described herein. In some implementation, the one or more ALUs 506 may reside within or on a processor chipset (e.g., the processor 500) . In some other implementations, the one or more ALUs 506 may reside external to the processor chipset (e.g., the processor 500) . One or more ALUs 506 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 506 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 506 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 506 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 506 to handle conditional operations, comparisons, and bitwise operations.
[0106] The processor 500 may support wireless communication in accordance with examples as disclosed herein. The processor 500 may be implemented at a UE 104, e.g., an ambient IoT device. In this case, the processor 500 may be configured to operable to support means for receiving a command that schedules at least one corresponding uplink (UL) transmission for each of one or more UEs of a plurality of UEs including the UE; means for determining a resource of a set of resources for at least one UL transmission for the UE based on an identifier of the UE; and means for performing the at least one UL transmission on the determined resource.
[0107] The processor 500 may be implemented at a network entity 102 or UE 104. In this case, the processor 500 may be configured to operable to support means for transmitting a command that schedules at least one corresponding uplink (UL) transmission for each of one or more UEs of a plurality of UEs; means for determining, for each of the one or more UEs, a resource of a set of resources for at least one UL transmission for the UE based on an identifier of the UE; and means for performing at least one UL reception on the determined resource.
[0108] FIG. 6 illustrates a flowchart of a method 600 performed by a UE in accordance with aspects of the present disclosure. The operations of the method 600 may be implemented by a device or its components as described herein. For example, the operations of the method 600 may be performed by a UE 104 as described herein. In some implementations, the UE 104 may execute a set of instructions to control the function elements of the UE 104 to perform the described functions. Additionally, or alternatively, the UE 104 may perform aspects of the described functions using special-purpose hardware.
[0109] At 610, the method may include receiving, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol. The operations of 610 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 610 may be performed by a UE 104 as described with reference to FIG. 1.
[0110] At 620, the method may include determining a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message. The operations of 620 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 620 may be performed by a UE 104 as described with reference to FIG. 1.
[0111] At 630, the method may include performing the R2D transmission with the determined transmit power. The operations of 630 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 630 may be performed by a UE 104 as described with reference to FIG. 1.
[0112] FIG. 7 illustrates a flowchart of a method 700 performed by a network entity in accordance with aspects of the present disclosure. The operations of the method 700 may be implemented by a device or its components as described herein. For example, the operations of the method 700 may be performed by a network entity 102 as described herein. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
[0113] At 710, the method may include transmitting, to a user equipment (UE) , at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol. The operations of 710 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 710 may be performed by a network entity 102 as described with reference to FIG. 1.
[0114] It should be noted that the methods described herein describes possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.
[0115] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
[0116] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
[0117] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
[0118] As used herein, including in the claims, an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” or “one or both of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
[0119] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A user equipment (UE) comprising:a processor; anda transceiver coupled to the processor,wherein the processor is configured to:receive, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol;determine a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message; andperform the R2D transmission with the determined transmit power.2.The UE of claim 1, wherein the R2D message is one of a paging message or an access trigger message, and wherein, to determine the transmit power of R2D transmission carrying the R2D message, the processor is configured to:determine a first transmit power as the first maximum transmit power or as a function of the first maximum transmit power and an offset corresponding to the M value of the R2D transmission.3.The UE of claim 1, wherein the R2D message is a random identifier (ID) response message, and wherein, to determine the transmit power of R2D transmission carrying the R2D message, the processor is configured to:determine a first transmit power as the first maximum transmit power or as a function of the first maximum transmit power and an offset corresponding to the M value of the R2D transmission.4.The UE of claim 1, wherein the R2D message is a random ID response message, and wherein, to determine the transmit power of R2D transmission carrying the R2D message, the processor is configured to:determine the first transmit power as a function of the first maximum transmit power and a maximum pathloss between the UE and devices echoed in the random ID response message.5.The UE of claim 4, wherein the first transmit power is determined as a function of the first maximum transmit power, the maximum pathloss between the UE and the devices echoed in the random ID response message, and an offset corresponding to the M value of the R2D transmission.6.The UE of claim 1, wherein the at least one parameter further comprises at least one of:one or more parameters related to Uu interface; ora second maximum transmit power or an offset related to the first maximum transmit power.7.The UE of claim 6, wherein to determine the transmit power of R2D transmission carrying the R2D message, the processor is configured to at least one of:determine a second transmit power as a function of the pathloss between the UE and the base station and the one or more parameters related to Uu interface; ordetermine a third transmit power as the second maximum transmit power, or based on the offset related to the first maximum transmit power and the first maximum transmit power.8.The UE of claim 7, wherein, to determine the transmit power of R2D transmission carrying the R2D message, the processor is further configured to:determine the transmit power of the R2D transmission as a minimum of the first transmit power and the second transmit power.9.The UE of claim 7, wherein, to determine the transmit power of R2D transmission carrying the R2D message, the processor is further configured to:determine the transmit power of the R2D transmission as a minimum of the first transmit power and the third transmit power.10.The UE of claim 7, wherein, to determine the transmit power of R2D transmission carrying the R2D message, the processor is further configured to:determine the transmit power of the R2D transmission as a minimum of the first transmit power, the second transmit power and the third transmit power.11.A network entity comprising:a processor; anda transceiver coupled to the processor,wherein the processor is configured to:transmit, to a user equipment (UE) , at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol.12.The network entity of claim 11, wherein the at least one parameter further comprises at least one of:one or more parameters related to Uu interface; ora second maximum transmit power or an offset related to the first maximum transmit power.13.A processor for wireless communication, comprising:at least one memory; anda controller coupled with the at least one memory and configured to cause the controller to:receive, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol;determine a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message; andperform the R2D transmission with the determined transmit power.14.A method performed by a UE, comprising:receiving, from a network entity, at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol;determining a transmit power of R2D transmission carrying an R2D message based on the at least one parameter and at least one of: an M value of the R2D transmission, a type of the R2D message; andperforming the R2D transmission with the determined transmit power.15.A method performed by a network entity, comprising:transmitting, to a user equipment (UE) , at least one parameter related to power control of reader to device (R2D) transmission, wherein the at least one parameter comprises at least one of: a first maximum transmit power; or a list of offsets corresponding to different M values, each M value representing a number of chips within an orthogonal frequency division multiplexing (OFDM) symbol.