Power control for non-uniform message transmission
By receiving power control parameters that indicate non-uniform probability, and performing power scaling and normalization of codewords, the power waste problem of non-uniform message transmission in wireless communication systems is solved, and more efficient power utilization is achieved.
Patent Information
- Application Number
- CN202580027496.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-19
- Filing Date
- 2025-03-20
- Publication Date
- 2026-11-17
AI Technical Summary
Existing wireless communication systems fail to effectively utilize the non-uniform probability of bit values in messages when processing non-uniform message transmission, resulting in power waste.
By receiving power control parameters associated with non-uniform probabilities, power scaling of codewords is performed, and normalization is applied where necessary, to optimize power allocation and reduce power consumption for more likely messages.
It achieves more efficient power utilization in wireless communication by optimizing for non-uniform message transmission and reducing the average transmission power requirement.
Smart Images

Figure CN123125973A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. Patent Application No. 18 / 640,863, filed April 19, 2024, entitled “POWER CONTROL FORNON-UNIFORM MESSAGE TRANSMISSIONS”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field
[0003] The following discussion relates to wireless communication, including power control for non-uniform message transmission. Background Technology
[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention
[0005] The described technology relates to improved methods, systems, devices, and apparatuses for power control supporting non-uniform message transmission. For example, the described technology provides for assigning relatively more power to less likely messages and relatively less power to more likely messages to conserve transmission power (e.g., reducing average transmission power). In some examples, a user equipment (UE) may receive control signaling indicating power control parameters. The power control parameters may be associated with a non-uniform probability of a message, and the non-uniform probability may be associated with the probability of bit values present in the message. The UE may perform power scaling of codewords based on the power control parameters, and the codewords include the message. The UE may transmit the codewords based on the power scaling.
[0006] A method for wireless communication by a UE is described. The method may include: receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message; performing a power scaling process for a codeword based on the power control parameter, wherein the codeword includes the message; and transmitting the codeword based on the power scaling process.
[0007] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories (e.g., operative, communicative, functional, electronic, or electrical ground). The one or more processors are capable of operating individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) so that the UE: receives a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message; performs a power scaling process for a codeword, wherein the codeword includes the message, based on the power control parameter; and transmits the codeword based on the power scaling process.
[0008] Another UE for wireless communication is described. The UE may include: means for receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message; means for performing a power scaling process for a codeword based on the power control parameter, wherein the codeword includes the message; and means for transmitting the codeword based on the power scaling process.
[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors (e.g., directly, indirectly, after preprocessing, or without preprocessing) to perform the following actions: receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message; performing a power scaling process for a codeword, wherein the codeword includes the message, based on the power control parameter; and transmitting the codeword based on the power scaling process.
[0010] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting the codeword may include operations, features, components, or instructions for: applying normalization to the codeword after the power scaling process, wherein the normalization may be based on a power value associated with the codebook; and transmitting the codeword based on the normalization.
[0011] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, the normalization may be applied to each symbol associated with the codeword, or to the block length associated with the codeword.
[0012] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, performing the power scaling process for the codeword may include operations, features, components, or instructions for performing the power scaling process for the codeword based on a power threshold, wherein the power associated with the codeword may be limited based on the power threshold.
[0013] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a second control signal indicating the power threshold.
[0014] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for: determining the power threshold based on the one or more bit values included in the message; and sending a signal indicating the power threshold.
[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the message includes a sequence of one or more Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) bits or one or more Hybrid Automatic Repeat Request (HARQ) Negative Acknowledgment (NACK) bits, and the power control parameter may be associated with the non-uniform probability of the message including the one or more HARQ ACK bits or the one or more HARQ Negative Acknowledgment (NACK) bits.
[0016] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting the codeword may include operations, features, components, or instructions for: applying normalization to the codeword after the power scaling process, wherein the normalization may be based on a normalization parameter, wherein the normalization parameter may be associated with the entropy of the distribution of the one or more bit values included in the message, wherein the power control parameter may be associated with the non-uniform probability of the message including independent and identically distributed bit values; and transmitting the codeword based on the normalization.
[0017] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting the codeword may include operations, features, components, or instructions for applying normalization to the codeword after the power scaling process, wherein the normalization may be based on a normalization parameter, wherein the normalization parameter may be associated with the entropy of the distribution of the one or more bit values included in the message, and wherein the power control parameter may be associated with the non-uniform probability of the message including bit values with non-uniform distributions.
[0018] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, the one or more bit values correspond to one or more types of content of the message.
[0019] In some examples of the methods, UEs, and nontransient computer-readable media described herein, this non-uniform probability corresponds to one or more reliability parameters of the message.
[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the bit values associated with the first part of the message may have non-uniform probabilities, and the bit values associated with the second part of the message may have uniform probabilities.
[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the power scaling process may be based on one or more capabilities of the UE.
[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, transmitting the codeword may include operations, features, components, or instructions for: applying normalization to the codeword after the power scaling process, wherein the normalization may be based on a power value associated with the codebook; calculating an average of the amplitude associated with the transmitted signal; and transmitting the codeword based on the normalization and the average.
[0023] In the methods described herein, in some examples of UEs and nontransitory computer-readable media, the mean may be calculated for each symbol associated with the codeword or over the block length associated with the codeword.
[0024] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the power scaling process may be based on the scaling parameter log(1 / p(x)), where p(x) may be the probability of the one or more bit values included in the message. Attached Figure Description
[0025] Figure 1 Examples of wireless communication systems supporting power control for non-uniform message transmission according to one or more aspects of this disclosure are shown.
[0026] Figure 2 Examples of wireless communication systems supporting power control for non-uniform message transmission according to one or more aspects of this disclosure are shown.
[0027] Figure 3 An example of a process flow supporting power control for non-uniform message transmission according to one or more aspects of this disclosure is shown.
[0028] Figure 4 and Figure 5 A block diagram of an apparatus supporting power control for non-uniform message transmission according to one or more aspects of this disclosure is shown.
[0029] Figure 6 A block diagram of a communication manager supporting power control for non-uniform message transmission, according to one or more aspects of this disclosure, is shown.
[0030] Figure 7 A diagram is shown of a system including a device supporting power control for non-uniform message transmission, according to one or more aspects of this disclosure.
[0031] Figure 8 and Figure 9 A flowchart illustrating a method for power control for non-uniform message transmission according to one or more aspects of this disclosure is shown. Detailed Implementation
[0032] User equipment (UE) can receive downlink signaling from network entities, and the UE can send feedback messages for the downlink signaling. For example, the UE can send a feedback codebook (e.g., a bit sequence indicating feedback sent for one or more downlinks), such as a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK) or Negative Acknowledgment (NACK) codebook including feedback bits indicating ACK or NACK information for the received downlink signaling. In some examples, the UE may be more likely to send an ACK (e.g., bit 0) than a NACK (e.g., bit 1). For example, at a 10% block error rate (BLER) in a Physical Downlink Shared Channel (PDSCH), the UE may send 90% ACKs and 10% NACKs. However, the current codebook is designed for uniform probability of messages, where bits 0 and 1 have equal probability, and power is uniformly applied to non-uniform messages.
[0033] Power control techniques for non-uniform message transmission can improve power savings. More power can be allocated to less likely messages, and less power to more likely messages, thus saving average transmission power. In some examples, the UE may receive control signaling indicating power control parameters. These parameters may be associated with the non-uniform probability of a message, and the non-uniform probability may be associated with the probability of a bit value present in the message. The UE may perform power scaling of codewords, where the codeword comprises the message, based on the power control parameters. The UE may transmit the codeword based on the power scaling. In some cases, the message may be a sequence of HARQ ACK and HARQ NACK bit values, and the power control parameters may indicate the non-uniform probability of previous messages including HARQ ACK and HARQ NACK bit values.
[0034] The aspects of this disclosure are first described in the context of a wireless communication system. They are also described in the context of a process flow. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to power control for non-uniform message transmission, and are described with reference to these diagrams.
[0035] Figure 1 An example of a wireless communication system 100 supporting power control for non-uniform message transmission according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0036] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish communication link 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).
[0037] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Examples of UE 115 are illustrated herein. The UE 115 described herein may be able to support communication with various types of devices in the wireless communication system 100, such as other wireless communication devices, including UE 115 or network entity 105. Figure 1 As shown in the figure.
[0038] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. As another example, a node may be network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.
[0039] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links) or one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.
[0040] One or more of the network entities 105 or network equipment described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).
[0041] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entity 105) such as an integrated access and 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, network entity 105 may include one or more of the following: a central unit (CU) such as CU 160, a distributed unit (DU) such as DU 165, a radio unit (RU) such as RU 170, a RAN intelligent controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RTRIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0042] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host upper protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) can connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or a combination thereof, and DU 165, RU 170, or both can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and can each be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by another of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.
[0043] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) can be partially controlled by each other. IAB node 104 can be referred to as a donor entity or IAB donor. DU 165 or RU 170 can be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) can communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) supporting communication links with relay chains or additional entities (e.g., IAB node 104, UE 115) within the access network (e.g., downstream). In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.
[0044] When the techniques described herein are applied in a decomposed RAN architecture environment, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) can be additionally or alternatively performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180).
[0045] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein “device” may also be referred to as a unit, station, terminal, or client, etc. UE 115 may also include or be referred to as personal electronic devices, such as cellular phones, personal digital assistants (PDAs), multimedia / entertainment devices (e.g., radios, MP3 players, or video devices), cameras, gaming devices, navigation / positioning devices (e.g., GNSS (Global Navigation Satellite System) devices based on, for example, GPS (Global Positioning System), BeiDou, GLONASS, or Galileo, or terrestrial devices), tablet computers, laptop computers, netbooks, smartbooks, personal computers, smart devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), drones, robots / robotic devices, vehicles, vehicle equipment, meters (e.g., parking timers, electricity meters, gas meters, water meters), monitors, air pumps, electrical appliances (e.g., kitchen appliances, washing machines, dryers), location tags, medical / healthcare devices, implants, sensors / actuators, displays, or any other suitable device configured to communicate via wireless or wired media. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, which can be implemented in various objects such as appliances, vehicles, or meters.
[0046] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which can sometimes operate as a relay, as well as network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown in the figure.
[0047] UE 115 and network entity 105 can communicate wirelessly with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).
[0048] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.
[0049] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while It can represent the supported Discrete Fourier Transform (DFT) size. Time intervals for communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).
[0050] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.
[0051] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).
[0052] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to transmit control information to UE 115 (e.g., one or more UEs), or it may include a UE-specific search space set for transmitting control information to UE 115 (e.g., a specific UE).
[0053] In some examples, network entity 105 (e.g., base station 140, RU 170) can be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, different network entities (e.g., network entity 105) can support overlapping coverage areas associated with different technologies, such as coverage area 110. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 support communication in coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
[0054] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.
[0055] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) according to peer-to-peer (P2P), D2D, or sidelink protocols. In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in this group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.
[0056] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities can connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.
[0057] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).
[0058] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.
[0059] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.
[0060] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).
[0061] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.
[0062] UE 115 can receive downlink signaling from network entity 105, and UE 115 can send feedback messages for the downlink signaling. For example, UE 115 can send a feedback codebook, such as a HARQ ACK or NACK codebook (e.g., a bit value sequence) including feedback bits indicating ACK or NACK information for the received downlink signaling. In some examples, UE 115 may be more likely to send an ACK (e.g., bit 0) than a NACK (e.g., bit 1). For example, under 10% BLER in PDSCH, UE 115 may send 90% ACK and 10% NACK. However, a regular codebook is designed for uniform probability of messages, where bits 0 and 1 have equal probability, and power is uniformly applied to non-uniform messages.
[0063] Power control techniques for non-uniform message transmission can improve power savings. More power can be applied to less likely messages, and less power to more likely messages, thus saving average transmission power. In some examples, UE 115 may receive control signaling indicating power control parameters. These parameters may be associated with the non-uniform probability of a message, and the non-uniform probability may be associated with the probability of a bit value present in the message. UE 115 may perform power scaling of codewords, where the codeword includes the message, based on the power control parameters. UE 115 may transmit the codeword based on power scaling. In some cases, the message may be a sequence of HARQ ACK and HARQ NACK bit values, and the power control parameters may indicate the non-uniform probability of previous messages including HARQ ACK and HARQ NACK bit values.
[0064] Figure 2An example of a wireless communication system 200 supporting power control for non-uniform message transmission according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 includes a UE 115-a, which may be an example of UE 115 as described herein. The wireless communication system 200 may also include a network entity 105-a, which may be an example of network entity 105 as described herein.
[0065] UE 115-a can communicate with network entity 105-a using communication link 125-a. Communication link 125-a can be an example of an NR or LTE link between UE 115-a and network entity 105-a. Communication link 125-a can include a bidirectional link that enables both uplink and downlink communication. For example, network entity 105-a can use communication link 125-a to send downlink signals (e.g., downlink transmission) to UE 115-a, such as downlink message 205 including downlink control signaling and downlink data signals, and UE 115-a can use communication link 125-a to send uplink message 210 including uplink control signaling and uplink data signals to network entity 105-a (e.g., uplink transmission).
[0066] In some examples, UE 115-a may receive downlink message 205 from network entity 105-a, and UE 115-a may send message 210 providing feedback for the downlink message. For example, UE 115-a may send a feedback codebook, such as a HARQ ACK or NACK codebook including feedback bits indicating ACK and / or NACK information for the received downlink message (e.g., PDSCH transmission). In some examples, UE 115-a may be more likely to send an ACK (e.g., bit 0) than a NACK (e.g., bit 1). For example, network entity 105-a may schedule five messages on the PDSCH, and UE 115-a may send a five-bit message for HARQ ACK / NACK based on the decoding of the PDSCH transmission. Under a 10% BLER in PDSCH, UE115-a can send ACKs 90% of the time and NACKs 10%, or send ACKs (e.g., bit 0) with a 90% probability and NACKs (e.g., bit 1) with a 10% probability. However, the current codebook is designed for uniform message probability, where bits 0 and 1 have equal probability, and power is uniformly applied to non-uniform messages. Power control techniques for non-uniform message transmission can improve power savings. More power can be proportionally assigned to less likely symbols and less power to more likely symbols to save average transmission power and improve error performance.
[0067] In some examples, power control techniques for non-uniform message transmission can provide variable transmission power. For instance, the power per codeword can be scaled relative to the Shannon decoding length of the corresponding message. (See reference) Figure 2 UE 115-a can respond to message 210 (e.g., x k Encode and modulate 215 to obtain codewords. c(x k ) In some cases, the modulation process can be binary phase shift keying (BPSK) with in-phase and quadrature components (I / Q), or one or more other modulation schemes can be used. UE 115-a can perform codeword-based modulation based on power scaling parameters. c(x k ) The power scaling process 220. In some cases, UE 115-a may receive power scaling parameters from network entity 105-a. In some examples, the power scaling parameters may be associated with messages. x k The corresponding non-uniform probability is associated with this. For example, the power scaling process can use scaling parameters. ,in It's a message. xk The non-uniform probability.
[0068] After power scaling, UE 115-a can apply normalization 225. In some cases, UE 115-a can apply normalization parameters. Normalized parameters It can have a unit expected power across the codebook. In some cases, the scaling parameter... Can be used for probability shaping The Maxwell-Boltzmann distribution is relevant. In some examples, UE 115-a may transmit codewords at least in part based on the power scaling process 220 and normalization 225.
[0069] In some examples, power control techniques for ACK / NACK transmissions can scale power based on the probability of the message sequence. For example, if the message sequence... Having probability Then the corresponding codeword is sent. The power available Scaling is applied. After normalization relative to the unit expected power across the entire codebook, the message sequence... Can be mapped to The normalization parameter yes .
[0070] Power control techniques for messages containing independent and identically distributed bit values can scale power based on the probability of the message sequence. If all bits are independent and follow the same Bernoulli distribution (Bern(p)), then the probability can be... ,in This represents the probability of bit 1. m Indicates message The number of 1s in the data, and k Indicates the message length. In some cases, the normalization parameter can be simplified to... ,in It is the entropy of the Bern(p) variable and can be pre-computed for a given value of p. Power scaling can be simplified to... .
[0071] In some examples, power control techniques for messages that include bits with non-uniformly distributed bit values can scale power based on the probability of the message sequence. In some cases, bits may correspond to different types of content. For example, a subset of message bits may correspond to HARQ-ACK, and another subset may correspond to scheduling requests (SR).
[0072] Different reliability requirements may exist for ACK / NACK transmissions. For example, enhanced mobile broadband (eMBB) may have a prior probability of 0.9 for ACK and 0.1 for NACK, while ultra-reliable low-latency communication (URLLC) may have a prior probability of 0.99 for ACK and 0.01 for NACK. If we assume that ACK / NACK are independent and identically distributed within each subset of the message, and that the subsets are independent of each other, the normalization parameter can be simplified. For example, it can follow a Bernoulli distribution. )( A message of length k1 with prior probability distributed according to a Bernoulli distribution, followed by a message of length k1 that follows a Bernoulli distribution. )( For a message of length k2 with a prior probability distributed as k, then ,in m i This is the first message i The number of 1s in the subset (e.g., the number of corresponding bits set to the value "1"), and i =1, 2, and .
[0073] In some cases, a Cyclic Redundancy Check (CRC) can be inserted after the message payload. The CRC can have a uniform prior probability that differs from the prior probability of the payload, and can be computed as a scalar using a general definition to simplify for normalization parameters within a subset of the message. For example, combining a message of length k1 with a prior probability of 0.1 for NACK and 0.9 for ACK, and a CRC of length k2, would result in... Where p is the prior probability of bit 1, m1 is the number of bit 1s in the first subset of the message, and the normalization parameter can be... Alternatively, power scaling can be used for the payload portion of the message that does not include the CRC portion.
[0074] As described herein, network entity 105-a may indicate power control parameters, such as prior probabilities (e.g., bits p or p1, p2 with different prior probabilities). UE 115-a may be configured in an RRC message or indicated to the UE via downlink control information (DCI) or MAC control elements (CE). For example, UE 115-a may receive control signaling (e.g., downlink message 205) indicating power control parameters associated with non-uniform probabilities in the message.
[0075] In some examples, techniques for variable power transmission may include clipping. In some cases, highly improbable message sequences (e.g., all NACKs) can be mapped to very high power. To improve the peak-to-average power ratio (PAPR), the power can be clipped to a power threshold before normalization. T At that point, and based on a power threshold ( T This can be used to limit the power associated with a codeword. For example, power scaling could be... In some examples, network entity 105-a may indicate a power threshold (T) to UE 115-a. For example, this can be configured in an RRC message or indicated to the UE by the DCI or MAC CE. For example, UE 115-a may receive control signaling indicating the power threshold (e.g., downlink message 205). In some examples, UE 115-a may indicate a power threshold or clipping value to network entity 105-a. For example, this can be configured in an RRC message or indicated to the network entity by uplink control information. For example, UE 115-a may send a signal indicating the power threshold (e.g., uplink message 210).
[0076] The power control technique described for non-uniform message transmission can be extended to higher-order modulation. To provide variable transmission power for non-uniform messages, normalization can be applied per symbol, or it can be applied over the entire block length (e.g., for codebook sizes (2^35-2^35)). k (×n) and modulation order , i=1,2, ..., For symbol-normalization, the modulated codeword can be represented as: ,in Furthermore, the normalization parameter can depend on the sending time ( t )for ,in For normalization applied over the entire block length, the modulated codeword can be represented as: ,in And the normalization parameter can be .
[0077] In some examples, power may be wasted if the transmitted symbols have a non-zero mean; therefore, power control techniques for non-uniform message transmission can transmit zero-mean constellations. In some cases, power scaling may not provide zero-mean transmission. In some examples, UE 115-a can iterate between power scaling and mean elimination. For example, UE 115-a can perform a calculation and subtract the mean 230 after normalization 225. In some cases, UE 115-a can calculate the mean (μ) of the amplitude associated with the transmitted signal and subtract that mean from the normalized codeword, i.e. The mean can be calculated by sign. Or calculate the average over the entire block length as .
[0078] Figure 3 An example of a process flow 300 supporting power control for non-uniform message transmission according to one or more aspects of this disclosure is shown. In some examples, process flow 300 may be implemented as described in reference respectively. Figure 1 and Figure 2 The described aspects of the wireless communication systems 100 and 200, or those implemented therein. For example, process flow 300 can be implemented by network entity 105-b, which can be as described in reference... Figure 1 and Figure 2 An example of network entity 105 is described. Process flow 300 can be implemented by UE 115-b, which can be as shown in the reference. Figure 1 and Figure 2 An example of a UE as described.
[0079] In some examples, the operations illustrated in process flow 300 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code (e.g., software executed by a processor), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.
[0080] At 305, UE 115-b may receive a first control signal indicating power control parameters associated with a non-uniform probability of a message. The non-uniform probability may be associated with the probability of one or more bit values included in the message. In some examples, the message may include a sequence of one or more HARQ ACK bits or one or more HARQ NACK bits, and the power control parameters may be associated with the non-uniform probability of a message including one or more HARQ ACK bits or one or more HARQ NACK bits.
[0081] At 310, UE 115-b may receive a second control signal indicating a power threshold. In some examples, UE 115-b may determine the power threshold at least in part based on one or more bit values included in the message, and UE 115-b may send a signal indicating the power threshold to network entity 105-b.
[0082] At 315, UE 115-b may perform a power scaling procedure for a codeword at least in part based on power control parameters. A codeword may include a message. In some examples, UE 115-b may perform the power scaling procedure for a codeword at least in part based on a power threshold, and the power associated with the codeword may be limited at least in part based on the power threshold. In some examples, the power scaling procedure may be at least in part based on one or more capabilities of the UE. In some examples, the power scaling procedure may be at least in part based on a scaling parameter log(1 / p(x)), where p(x) is the probability of one or more bit values included in the message.
[0083] At 320, UE 115-b may apply normalization to the codeword after the power scaling process. Normalization may be based at least in part on power values associated with the codeword. In some examples, normalization may be based at least in part on normalization parameters. In some examples, normalization parameters may be associated with the entropy of the distribution of one or more bit values included in the message, and power control parameters may be associated with the non-uniform probability of a message including independent and identically distributed bit values. In some examples, normalization may be associated with the entropy of the distribution of one or more bit values included in the message, and power control parameters may be associated with the non-uniform probability of a message including non-identically distributed bit values. In some examples, one or more values may correspond to one or more types of content in the message. In some examples, the non-uniform probability corresponds to one or more reliability parameters of the message. In some examples, bit values associated with a first portion of the message may have a non-uniform probability, and bit values associated with a second portion of the message may have a uniform probability. In some examples, normalization may be applied to each symbol associated with the codeword, or to the block length associated with the codeword.
[0084] At 325, UE 115-b can calculate the mean of the amplitude associated with the transmitted signal. In some examples, the mean can be calculated for each symbol associated with the codeword or over the block length associated with the codeword.
[0085] At 330, UE 115-b may transmit codewords at least partially based on the power scaling process. In some examples, UE 115-b may transmit codewords at least partially based on normalization. In some examples, UE 115-b may transmit codewords at least partially based on both normalization and the mean.
[0086] Figure 4 A block diagram 400 is shown of a device 405 supporting power control for non-uniform message transmission according to one or more aspects of this disclosure. Device 405 may be an example of various aspects of UE 115 as described herein. Device 405 may include a receiver 410, a transmitter 415, and a communication manager 420. Device 405 or one or more components of device 405 (e.g., receiver 410, transmitter 415, communication manager 420) may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).
[0087] Receiver 410 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control for non-uniform message transmission). Information may be passed to other components of device 405. Receiver 410 may utilize a single antenna or a collection of antennas.
[0088] Transmitter 415 may provide components for transmitting signals generated by other components of device 405. For example, transmitter 415 may transmit information such as packets associated with various information channels (e.g., control channels, data channels, information channels associated with power control for non-uniform message transmission), user data, control information, or any combination thereof. In some examples, transmitter 415 may be co-located with receiver 410 in a transceiver module. Transmitter 415 may utilize a single antenna or a collection of multiple antennas.
[0089] The communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be examples of components used to perform various aspects of power control for non-uniform message transmission as described herein. For example, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be able to perform one or more of the functions described herein.
[0090] In some examples, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).
[0091] Additionally or alternatively, the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communication management software) (e.g., referred to as processor executable code) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 420, receiver 410, transmitter 415, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).
[0092] In some examples, the communication manager 420 may be configured to use a receiver 410, a transmitter 415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or integrate with the receiver 410, the transmitter 415, or both to acquire information, output information, or perform various other operations as described herein.
[0093] Communication manager 420 may support wireless communication according to examples disclosed herein. For example, communication manager 420 may be capable of, configured to, or operable to support components for receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message. Communication manager 420 may be capable of, configured to, or operable to support components for performing a power scaling process for a codeword based on the power control parameter, wherein the codeword includes a message. Communication manager 420 may be capable of, configured to, or operable to support components for transmitting a codeword based on the power scaling process.
[0094] By including or configuring a communication manager 420 according to an example as described herein, device 405 (e.g., controlling receiver 410, transmitter 415, communication manager 420 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing power consumption and utilizing communication resources more efficiently.
[0095] Figure 5 A block diagram 500 of a device 505 supporting power control for non-uniform message transmission according to one or more aspects of this disclosure is shown. Device 505 may be an example of aspects of device 405 or UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Device 505, or one or more components of device 505 (e.g., receiver 510, transmitter 515, communication manager 520), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).
[0096] Receiver 510 may provide components for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control for non-uniform message transmission). Information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.
[0097] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to power control for non-uniform message transmission). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.
[0098] Device 505 or its various components may be examples of components used to perform various aspects of power control for non-uniform message transmission as described herein. For example, communication manager 520 may include power control parameter manager 525, power scaling manager 530, codeword transmission manager 535, or any combination thereof. Communication manager 520 may be examples of aspects of communication manager 420 as described herein. In some examples, communication manager 520 or its various components may be configured to use receiver 510, transmitter 515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 520 may receive information from receiver 510, transmit information to transmitter 515, or be integrated in combination with receiver 510, transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.
[0099] Communication manager 520 can support wireless communication according to examples disclosed herein. Power control parameter manager 525 is capable of, configured to, or operable to support components for receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message. Power scaling manager 530 is capable of, configured to, or operable to support components for performing a power scaling process for a codeword based on power control parameters, wherein the codeword includes a message. Codeword transmission manager 535 is capable of, configured to, or operable to support components for transmitting codewords based on a power scaling process.
[0100] Figure 6 A block diagram 600 is shown of a communication manager 620 supporting power control for non-uniform message transmission according to one or more aspects of this disclosure. The communication manager 620 may be an example of aspects of the communication manager 420, communication manager 520, or both as described herein. The communication manager 620 or its various components may be examples of components for performing various aspects of power control for non-uniform message transmission as described herein. For example, the communication manager 620 may include a power control parameter manager 625, a power scaling manager 630, a codeword transmission manager 635, a normalization manager 640, an averaging manager 645, a power threshold manager 650, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).
[0101] Communication manager 620 can support wireless communication according to examples disclosed herein. Power control parameter manager 625 is capable of, configured to, or operable to support components for receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message. Power scaling manager 630 is capable of, configured to, or operable to support components for performing a power scaling process for a codeword based on power control parameters, wherein the codeword includes a message. Codeword transmission manager 635 is capable of, configured to, or operable to support components for transmitting codewords based on a power scaling process.
[0102] In some examples, to support codeword transmission, the normalization manager 640 is capable of, configured to, or operable to support components for applying normalization to codewords after a power scaling process, where normalization is based on power values associated with the codebook. In some examples, to support codeword transmission, the codeword transmission manager 635 is capable of, configured to, or operable to support components for transmitting codewords based on normalization.
[0103] In some examples, normalization is applied to each symbol associated with a codeword, or to the block length associated with a codeword.
[0104] In some examples, in order to support the execution of a power scaling process for codewords, the power scaling manager 630 is capable of, configured to, or operable to support components for performing a power scaling process for codewords based on a power threshold, wherein the power associated with the codeword is limited based on the power threshold.
[0105] In some examples, the power threshold manager 650 is capable of, configured to, or able to operate to support components for receiving a second control signal indicating a power threshold.
[0106] In some examples, the power threshold manager 650 is capable of, configured to, or operable to support components for determining a power threshold based on one or more bit values included in a message. In some examples, the power threshold manager 650 is capable of, configured to, or operable to support components for transmitting a signal indicating a power threshold.
[0107] In some examples, the message includes a sequence of one or more Mixed Automatic Repeat Request (HARQ) Acknowledgment (ACK) bits or one or more HARQ Negative Acknowledgment (NACK) bits. In some examples, the power control parameters are associated with a non-uniform probability of messages including one or more HARQ ACK bits or one or more HARQ NACK bits.
[0108] In some examples, to support codeword transmission, the normalization manager 640 is capable of, configured to, or operable to support components for applying normalization to codewords after a power scaling process, wherein the normalization is based on normalization parameters that are associated with the entropy of the distribution of one or more bit values included in the message, and wherein power control parameters are associated with the non-uniform probability of a message including independent and identically distributed bit values. In some examples, to support codeword transmission, the codeword transmission manager 635 is capable of, configured to, or operable to support components for transmitting codewords based on normalization.
[0109] In some examples, to support the transmission of codewords, the normalization manager 640 is capable, configured, or operable to support components for applying normalization to codewords after a power scaling process, wherein the normalization is based on normalization parameters, wherein the normalization parameters are associated with the entropy of the distribution of one or more bit values included in the message, and wherein the power control parameters are associated with the non-uniform probability of a message including bit values with non-uniform distributions.
[0110] In some examples, one or more bit values correspond to one or more types of content in the message.
[0111] In some examples, non-uniform probability corresponds to one or more reliability parameters of the message.
[0112] In some examples, the bit values associated with the first part of the message have non-uniform probabilities, while the bit values associated with the second part of the message have uniform probabilities.
[0113] In some examples, the power scaling process is based on one or more capabilities of the UE.
[0114] In some examples, to support codeword transmission, the normalization manager 640 is capable of, configured to, or operable to support components for applying normalization to the codewords after the power scaling process, where the normalization is based on power values associated with the codebook. In some examples, to support codeword transmission, the mean manager 645 is capable of, configured to, or operable to support components for calculating the mean of the amplitude associated with the transmitted signal. In some examples, to support codeword transmission, the codeword transmission manager 635 is capable of, configured to, or operable to support components for transmitting codewords based on normalization and the mean.
[0115] In some examples, the mean is calculated for each symbol associated with the codeword or over the block length associated with the codeword.
[0116] In some examples, the power scaling process is based on the scaling parameter log(1 / p(x)), where p(x) is the probability of one or more bit values included in the message.
[0117] Figure 7 A diagram of a system 700 including a device 705 supporting power control for non-uniform message transmission, according to one or more aspects of this disclosure, is shown. Device 705 may be an example of device 405, device 505, or UE 115 as described herein, or may include components thereof. Device 705 may communicate with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof) (e.g., wirelessly). Device 705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 720, an input / output (I / O) controller (e.g., I / O controller 710), a transceiver 715, one or more antennas 725, at least one memory 730, code 735, and at least one processor 740. These components may communicate electronically or be coupled in other ways (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 745).
[0118] I / O controller 710 manages the input and output signals of device 705. I / O controller 710 can also manage peripheral devices not integrated into device 705. In some cases, I / O controller 710 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 710 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.
[0119] In some cases, device 705 may include a single antenna. However, in other cases, device 705 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 715 may communicate bidirectionally via one or more antennas 725 using a wired or wireless link as described herein. For example, transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 715 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 725 for transmission; and demodulating packets received from one or more antennas 725. Transceiver 715, or transceiver 715 and one or more antennas 725, may be an example of transmitter 415, transmitter 515, receiver 410, receiver 510, or any combination thereof or components thereof as described herein.
[0120] At least one memory 730 may include random access memory (RAM) and read-only memory (ROM). At least one memory 730 may store computer-readable code, computer-executable code, or processor-executable code, such as code 735. Code 735 may include instructions that, when executed by at least one processor 740, cause device 705 to perform the various functions described herein. Code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 735 may not be directly executable by at least one processor 740, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 730 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.
[0121] At least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic units, one or more discrete hardware components, or any combination thereof). In some cases, at least one processor 740 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 740. At least one processor 740 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 730) to cause device 705 to perform various functions (e.g., functions or tasks supporting power control for non-uniform message transmission). For example, device 705 or components of device 705 may include at least one processor 740 and at least one memory 730 coupled to or coupled to at least one processor 740, the at least one processor 740 and the at least one memory 730 being configured to perform the various functions described herein.
[0122] In some examples, at least one processor 740 may include multiple processors, and at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 740 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 740) and memory circuitry (which may include at least one memory 730)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 740 or a processing system including at least one processor 740 may be configured, capable of being configured, or operable to cause device 705 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 735 (e.g., processor-executable code) stored in at least one memory 730 or otherwise.
[0123] The communication manager 720 can support wireless communication according to examples disclosed herein. For example, the communication manager 720 is capable of, configured to, or operable to support components for receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message. The communication manager 720 is capable of, configured to, or operable to support components for performing a power scaling process for a codeword based on the power control parameter, wherein the codeword includes a message. The communication manager 720 is capable of, configured to, or operable to support components for transmitting a codeword based on the power scaling process.
[0124] By including or configuring a communication manager 720 according to an example as described herein, device 705 can support technologies for improving communication reliability, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, and extending battery life.
[0125] In some examples, the communication manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 715, one or more antennas 725, or any combination thereof, or otherwise cooperating with them. Although the communication manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 720 may be supported or executed by at least one processor 740, at least one memory 730, code 735, or any combination thereof. For example, code 735 may include instructions that can be executed by at least one processor 740 to cause device 705 to perform various aspects of power control for non-uniform message transmission as described herein, or at least one processor 740 and at least one memory 730 may be otherwise configured to perform or support such operations individually or jointly.
[0126] Figure 8 A flowchart illustrating a method 800 for power control of non-uniform message transmission according to one or more aspects of this disclosure is shown. Operation of method 800 may be implemented by a UE or its components as described herein. For example, operation of method 800 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0127] At 805, the method may include receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message. Operation of 805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 805 may be provided by reference to [reference needed]. Figure 6 The power control parameter manager 625 described herein is used to perform this.
[0128] At 810, the method may include performing a power scaling process for a codeword, at least in part, based on power control parameters, wherein the codeword comprises a message. The operation of 810 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 810 may be derived from references... Figure 6 The power scaling manager 630 described is used to perform this.
[0129] At 815, the method may include transmitting codewords at least in part based on a power scaling process. The operation of 815 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 815 may be derived from references... Figure 6 The codeword sending manager 635 described is used to execute this.
[0130] Figure 9 A flowchart illustrating a method 900 for power control of non-uniform message transmission according to one or more aspects of this disclosure is shown. Operation of method 900 may be implemented by a UE or its components as described herein. For example, operation of method 900 may be performed by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.
[0131] At 905, the method may include receiving a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message. Operation of 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 905 may be provided by reference to [reference needed]. Figure 6 The power control parameter manager 625 described herein is used to perform this.
[0132] At 910, the method may include performing a power scaling process for a codeword, at least in part, based on power control parameters, wherein the codeword comprises a message. The operation of 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 910 may be derived from references... Figure 6 The power scaling manager 630 described is used to perform this.
[0133] At 915, the method may include applying normalization to the codeword after the power scaling process, wherein the normalization is based at least in part on the power values associated with the codebook. The operation at 915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 915 may be derived from references... Figure 6 The normalization manager 640 described is used to execute this.
[0134] At 920, the method may include transmitting codewords at least in part based on normalization. The operation at 920 may be performed according to examples disclosed herein. In some examples, aspects of the operation at 920 may be derived from references... Figure 6 The codeword sending manager 635 described is used to execute this.
[0135] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first control signal indicating power control parameters associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with a probability of one or more bit values included in the message; performing a power scaling process for a codeword, wherein the codeword includes the message, based at least in part on the power control parameters; and transmitting the codeword based at least in part on the power scaling process.
[0136] Aspect 2: According to the method of aspect 1, transmitting the codeword further includes: applying normalization to the codeword after the power scaling process, wherein the normalization is based at least in part on a power value associated with the codebook; and transmitting the codeword based at least in part on the normalization.
[0137] Aspect 3: According to the method of aspect 2, wherein the normalization is applied to each symbol associated with the codeword, or to the block length associated with the codeword.
[0138] Aspect 4: The method according to any one of Aspects 1 to 3, wherein performing the power scaling process for the codeword comprises: performing the power scaling process for the codeword at least in part based on a power threshold, wherein the power associated with the codeword is limited at least in part based on the power threshold.
[0139] Aspect 5: According to the method of aspect 4, the method further includes: receiving a second control signal indicating the power threshold.
[0140] Aspect 6: The method according to any one of Aspects 4 to 5, the method further comprising: determining the power threshold based at least in part on the one or more bit values included in the message; and sending a signal indicating the power threshold.
[0141] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the message includes a sequence of one or more mixed Automatic Repeat Request (HARQ) Acknowledgment (ACK) bits or one or more HARQ Negative Acknowledgment (NACK) bits, and the power control parameter is associated with the non-uniform probability of the message including the one or more HARQ ACK bits or the one or more HARQ NACK bits.
[0142] Aspect 8: The method according to any one of Aspects 1 to 7, wherein transmitting the codeword further comprises: applying normalization to the codeword after the power scaling process, wherein the normalization is based at least in part on a normalization parameter, wherein the normalization parameter is associated with the entropy of the distribution of the one or more bit values included in the message, wherein the power control parameter is associated with the non-uniform probability of the message including independent and identically distributed bit values; and transmitting the codeword at least in part based on the normalization.
[0143] Aspect 9: The method according to any one of Aspects 1 to 7, wherein transmitting the codeword further comprises: applying normalization to the codeword after the power scaling process, wherein the normalization is based at least in part on a normalization parameter, wherein the normalization parameter is associated with the entropy of the distribution of the one or more bit values included in the message, wherein the power control parameter is associated with the non-uniform probability of the message including non-uniformly distributed bit values.
[0144] Aspect 10: According to the method of aspect 9, wherein the one or more bit values correspond to one or more types of content of the message.
[0145] Aspect 11: The method according to any one of Aspects 9 to 10, wherein the non-uniform probability corresponds to one or more reliability parameters of the message.
[0146] Aspect 12: The method according to any one of Aspects 9 to 11, wherein the bit values associated with the first portion of the message have non-uniform probabilities, and the bit values associated with the second portion of the message have uniform probabilities.
[0147] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the power scaling process is based at least in part on one or more capabilities of the UE.
[0148] Aspect 14: The method according to any one of Aspects 1 to 13, wherein transmitting the codeword further comprises: applying normalization to the codeword after the power scaling process, wherein the normalization is based at least in part on a power value associated with the codebook; calculating a mean of the amplitude associated with the transmitted signal; and transmitting the codeword based at least in part on the normalization and the mean.
[0149] Aspect 15: The method according to aspect 14, wherein the mean is calculated for each symbol associated with the codeword or over the block length associated with the codeword.
[0150] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the power scaling process is based at least in part on the scaling parameter log(1 / p(x)), where p(x) is the probability of the one or more bit values included in the message.
[0151] Aspect 17: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories (e.g., operatively, communicatively, functionally, electronically, or electrically) and capable of operating individually or jointly to execute the code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the UE to perform a method according to any one of Aspects 1 to 16.
[0152] Aspect 18: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 16.
[0153] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors (e.g., directly, indirectly, after preprocessing, or without preprocessing) to perform the method according to any one of Aspects 1 to 16.
[0154] It should be noted that the methods described herein describe possible specific implementations. Operations and steps can be rearranged or otherwise modified, and other specific implementations are possible. Furthermore, aspects from two or more of these methods can be combined.
[0155] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash OFDM, and other systems and radio technologies not explicitly mentioned herein, including future systems and radio technologies.
[0156] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0157] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, GPU, NPU, FPGA, or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a 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 combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.
[0158] The functionality described herein can be implemented using hardware, software executed by a processor, or any combination thereof. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, firmware, hardwired, or any combination thereof. Features implementing the functionality can also be physically located in various locations, including portions distributed such that the functionality is implemented at different physical locations.
[0159] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase-change memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.
[0160] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., including enumerations of items ending with phrases such as "at least one of..." or "one or more of...") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means, for example, A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be used. For example, if a composition is described as containing components A, B and / or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B and C.
[0161] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of those one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".
[0162] The terms "determine" or "identify" encompass a variety of actions, and therefore, "determine" or "identify" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), ascertainment, etc. Additionally, "determine" or "identify" can include receiving (such as receiving information or signaling, e.g., receiving information or signaling for determination, receiving information or signaling for identification) and accessing (such as accessing data in memory or accessing information). Furthermore, "determine" or "identify" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.
[0163] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numerals and a second reference numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.
[0164] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.
[0165] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Receive a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message; The power scaling process for a codeword, including the message, is performed at least in part based on the power control parameters; and The codeword is transmitted based at least in part on the power scaling process.
2. The UE according to claim 1, wherein, In order to transmit the codeword, the one or more processors can also operate individually or jointly to execute the code to enable the UE to: After the power scaling process, normalization is applied to the codeword, wherein the normalization is based at least in part on power values associated with the codebook; and The codeword is transmitted based at least in part on the normalization.
3. The UE of claim 2, wherein the normalization is applied to each symbol associated with the codeword, or to the block length associated with the codeword.
4. The UE according to claim 1, wherein, In order to perform the power scaling process for the codeword, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The power scaling process for the codeword is performed at least in part based on a power threshold, wherein the power associated with the codeword is limited at least in part based on the power threshold.
5. The UE of claim 4, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive a second control signal indicating the power threshold.
6. The UE of claim 4, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The power threshold is determined at least in part based on the one or more bit values included in the message; and Send a signal indicating the power threshold.
7. The UE according to claim 1, wherein: The message includes a sequence of one or more Mixed Automatic Repeat Request (HARQ) Acknowledgment (ACK) bits or one or more HARQ Negative Acknowledgment (NACK) bits, and The power control parameters are associated with the non-uniform probability of the message, which includes the one or more HARQ ACK bits or the one or more HARQ NACK bits.
8. The UE according to claim 1, wherein, In order to transmit the codeword, the one or more processors can also operate individually or jointly to execute the code to enable the UE to: After the power scaling process, normalization is applied to the codeword, wherein the normalization is based at least in part on a normalization parameter, wherein the normalization parameter is associated with the entropy of the distribution of the one or more bit values included in the message, and wherein the power control parameter is associated with the non-uniform probability of the message comprising independent and identically distributed bit values; and The codeword is transmitted based at least in part on the normalization.
9. The UE according to claim 1, wherein, In order to transmit the codeword, the one or more processors can also operate individually or jointly to execute the code to enable the UE to: After the power scaling process, normalization is applied to the codeword, wherein the normalization is based at least in part on a normalization parameter, wherein the normalization parameter is associated with the entropy of the distribution of the one or more bit values included in the message, wherein the power control parameter is associated with the non-uniform probability of the message including non-uniformly distributed bit values.
10. The UE of claim 9, wherein one or more bit values correspond to one or more types of content of the message.
11. The UE of claim 9, wherein the non-uniform probability corresponds to one or more reliability parameters of the message.
12. The UE of claim 9, wherein the bit values associated with the first portion of the message have non-uniform probabilities, and the bit values associated with the second portion of the message have uniform probabilities.
13. The UE of claim 1, wherein the power scaling process is based at least in part on one or more capabilities of the UE.
14. The UE according to claim 1, wherein, In order to transmit the codeword, the one or more processors can also operate individually or jointly to execute the code to enable the UE to: After the power scaling process, normalization is applied to the codeword, wherein the normalization is based at least in part on the power value associated with the codebook; Calculate the mean of the amplitudes associated with the transmitted signal; as well as The codeword is transmitted based at least in part on the normalization and the mean.
15. The UE of claim 14, wherein the mean is calculated for each symbol associated with the codeword or over a block length associated with the codeword.
16. The UE of claim 1, wherein the power scaling process is at least partially based on the scaling parameter log(1 / p(x)), where p(x) is the probability of the one or more bit values included in the message.
17. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message; The power scaling process for a codeword, including the message, is performed at least in part based on the power control parameters; and The codeword is transmitted based at least in part on the power scaling process.
18. The method of claim 17, wherein sending the codeword further comprises: After the power scaling process, normalization is applied to the codeword, wherein the normalization is based at least in part on the power value associated with the codebook; as well as The codeword is transmitted based at least in part on the normalization.
19. The method of claim 17, wherein performing the power scaling process for the codeword comprises: The power scaling process for the codeword is performed at least in part based on a power threshold, wherein the power associated with the codeword is limited at least in part based on the power threshold.
20. A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to: Receive a first control signal indicating a power control parameter associated with a non-uniform probability of a message, wherein the non-uniform probability is associated with the probability of one or more bit values included in the message; The power scaling process for a codeword, including the message, is performed at least in part based on the power control parameters; and The codeword is transmitted based at least in part on the power scaling process.
