Power and resource allocation for non-orthogonal multiple access (NOMA)

Abstract

The present disclosure provides systems, methods, and devices for wireless communication that support power allocation or resource allocation for non-orthogonal multiple access (NOMA). In a first aspect, a method of wireless communication includes a user equipment (UE) randomly selecting a parameter value associated with a power level of a plurality of power target levels; and transmitting the uplink communication to the network entity using the power level. In a second aspect, a method of wireless communication includes receiving, by a UE, an indicator indicating a plurality of resource candidates from a network entity, each resource candidate of the plurality of resource candidates overlapping at least one other resource candidate of the plurality of resource candidates; and transmitting an uplink communication to the network entity using a resource candidate of the plurality of resource candidates. Other aspects and features are also claimed and described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application No. 17 / 934,809, filed on September 23, 2022, entitled “POWER AND RESOURCE ALLOCATION FOR NON-ORTHOGONAL MULTIPLE ACCESS (NOMA)”, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to power and resource allocation for non-orthogonal multiple access (NOMA), such as power allocation or resource element allocation for grant-free communication. Some features may enable and provide improved communications, including increased multiplexing gain and uplink cell capacity, reduced control overhead, efficient resource utilization, grant-free uplink communications, or a combination thereof. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as a base station (or Node B) that may support communication of several user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0006] The base station may send data and control information to the UE on the downlink, or receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmissions from neighboring base stations or other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from other UEs communicating with neighboring base stations or from uplink transmissions of other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows with more UEs accessing long-range wireless communication networks and more short-range wireless systems deployed in communities. Research and development continues to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications.

[0008] In an environment with high connectivity, such as a home network or an Internet of Things (IoT) application, the network may need to support large connection density, small packet sizes, bursty communications that may have large inter-arrival times, or a combination thereof. Such a network configured to operate according to uplink grants for uplink communications may suffer from reduced multiplexing gain and uplink cell capacity, increased control overhead, poor resource utilization, or a combination thereof. Summary of the invention

[0009] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all the expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. The sole purpose of this summary is to present some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to more specific embodiments presented later.

[0010] In one aspect of the disclosure, a method of wireless communication by a user equipment (UE) includes randomly selecting a parameter value associated with a power level among a plurality of power target levels. The method also includes sending an uplink communication to a network entity using the power level.

[0011] In some implementations, the method further includes receiving, from the network entity, a configuration including or indicating the plurality of power target levels, and wherein the parameter value is a power level selected from the plurality of power target levels.

[0012] In some other implementations of the method, the parameter value is a physical random access channel (PRACH) preamble. In some such implementations, the method includes determining the power level based on the PRACH preamble and based on mapping data that maps the PRACH preamble to the power target level.

[0013] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to randomly select a parameter value associated with a power level in a plurality of power target levels. The at least one processor is further configured to initiate transmission of an uplink communication to a network entity using the power level.

[0014] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes a component for randomly selecting a parameter value associated with a power level in a plurality of power target levels. The apparatus also includes a component for sending an uplink communication to a network entity using the power level.

[0015] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations including: randomly selecting a parameter value associated with a power level in a plurality of power target levels. The operations also include: sending an uplink communication to a network entity using the power level.

[0016] In an additional aspect of the present disclosure, a method for wireless communication by a UE includes: receiving an indicator indicating a plurality of resource candidates from a network entity. Each resource candidate in the plurality of resource candidates overlaps with at least one other resource candidate in the plurality of resource candidates. The method also includes: sending an uplink communication to the network entity based on the resource candidate in the plurality of resource candidates.

[0017] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive an indicator indicating a plurality of resource candidates from a network entity. Each resource candidate in the plurality of resource candidates overlaps with at least one other resource candidate in the plurality of resource candidates. The at least one processor is also configured to initiate transmission of an uplink communication to the network entity based on a resource candidate in the plurality of resource candidates.

[0018] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes a component for receiving an indicator indicating a plurality of resource candidates from a network entity. Each resource candidate in the plurality of resource candidates overlaps with at least one other resource candidate in the plurality of resource candidates. The apparatus also includes a component for sending an uplink communication to the network entity based on a resource candidate in the plurality of resource candidates.

[0019] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations including: receiving an indicator indicating a plurality of resource candidates from a network entity. Each resource candidate in the plurality of resource candidates overlaps with at least one other resource candidate in the plurality of resource candidates. The operations also include: sending an uplink communication to the network entity based on a resource candidate in the plurality of resource candidates.

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

[0021] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or uses can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementations can be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some practical environments, the equipment in conjunction with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by adding a dash and a second label to distinguish between similar components after the reference label. If only the first reference label is used in the specification, the description applies to any one of the similar components having the same first reference label, regardless of the second reference label.

[0023] Figure 1 is a block diagram illustrating details of an example wireless communication system in accordance with one or more aspects.

[0024] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) according to one or more aspects.

[0025] Figure 3 A diagram illustrating an example decomposed base station architecture in accordance with one or more aspects is shown.

[0026] Figure 4 is a block diagram illustrating an example wireless communication system that supports power allocation and resource allocation for non-orthogonal multiple access (NOMA) according to one or more aspects.

[0027] Figure 5 is a diagram illustrating an example of available power allocation for NOMA according to one or more aspects.

[0028] Figure 6 is a diagram illustrating an example allocation of available resources for NOMA according to one or more aspects.

[0029] Figure 7 is a flowchart illustrating an example process for supporting power allocation or resource allocation for NOMA according to one or more aspects.

[0030] Figure 8 is a flowchart illustrating an example process for supporting power allocation or resource allocation for NOMA according to one or more aspects.

[0031] Fig. 9 is a block diagram of an example UE supporting power allocation or resource allocation for NOMA according to one or more aspects.

[0032] Fig.10 is a flowchart illustrating an example process for supporting power allocation or resource allocation for NOMA according to one or more aspects.

[0033] Fig.11 is a flowchart of an example process for supporting power allocation or resource allocation for NOMA according to one or more aspects.

[0034] Fig.12 is a block diagram of an example base station supporting power allocation or resource allocation for NOMA according to one or more aspects.

[0035] The same reference numbers and designations in different drawings represent the same elements. DETAILED DESCRIPTION

[0036] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to limit the scope of the present disclosure. Instead, the specific embodiments include specific details for providing a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0037] The present disclosure provides systems, devices, methods and computer-readable media that support power allocation or resource allocation for non-orthogonal multiple access (NOMA). For example, in a first aspect, the present disclosure implements power allocation for one or more user equipment (UE). For illustration, the UE may randomly select a parameter value associated with a power level in a plurality of power target levels, and use the power level to send an uplink communication to a network entity. In some specific implementations, the UE may receive a configuration including or indicating a plurality of power target levels, and the parameter value is a power level selected from the plurality of power target levels. In other specific implementations, the UE may receive mapping data that maps a physical random access channel (PRACH) preamble to a plurality of power target levels. In such specific implementations, the parameter value may be a PRACH preamble, and the UE may determine based on the power level based on the PRACH preamble using the mapping data. In a second aspect, the present disclosure implements resource allocation for one or more UEs. For illustration, the UE may receive an indicator indicating a plurality of resource candidates, and send an uplink communication to a network entity based on a resource candidate in the plurality of resource candidates. The plurality of resource candidates may include a plurality of frequency domain resource candidates or a plurality of time domain resource candidates. In some implementations, at least one of the plurality of resource candidates overlaps with at least one other of the plurality of resource candidates. In some other implementations, each of the plurality of resource candidates overlaps with at least one other of the plurality of resource candidates, or overlaps with each other of the plurality of resource candidates. The UE may select a resource candidate from the plurality of resource candidates based on a demodulation reference signal (DMRS) port of the UE or based on a PRACH preamble. In some implementations, the indicator indicating the plurality of resource candidates includes or indicates mapping data that maps a DMRS port to a plurality of resource candidates or maps a PRACH preamble to a plurality of resource candidates. Additionally, the uplink communication may indicate a DMRS port or a PRACH preamble so that a network entity can determine or identify a resource candidate.

[0038] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages or benefits. In some aspects, the present disclosure provides techniques for creating or having a grant-free situation in a multiple access environment where a base station or other network entity receives communications, wherein the communications have an asymmetric signal to interference plus noise ratio (SINR). The asymmetric SINR enables a base station or network entity to perform continuous interference cancellation with respect to multiple received communications. In some other aspects, the present disclosure may implement and provide improved communications, including increased multiplexing gain and uplink cell capacity, reduced control overhead, efficient resource utilization, grant-free uplink communications, or a combination thereof. For example, in NOMA, a UE performing grant-free transmission may transmit as long as it has a packet without going through control signaling. Additionally, grant-free operation and multiple access achieve efficient resource utilization.

[0039] The present disclosure generally relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various specific implementations, various techniques and apparatuses can be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA networks, and the like.

[0040] (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices), sixth generation (6G) networks, and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0041] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0042] For example, a TDMA network may implement a radio technology such as the Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standard for the GSM EDGE (Enhanced Data Rate for GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network of GSM / EDGE together with connecting base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents a component of the GSM network through which telephone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to subscriber phones (also known as user terminals or user equipment (UE)) and from subscriber phones to the PSTN and the Internet. The network of a mobile phone operator may include one or more GERANs, which may be coupled with UTRAN in the case of a UMTS / GSM network. Additionally, the operator network may also include one or more LTE networks, or one or more other networks. Various network types may use different radio access technologies (RATs) and RANs.

[0043] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These radio technologies and standards are known or under development. For example, 3GPP is a collaboration between telecommunications association groups to define a globally applicable third generation (3G) mobile phone specification. 3GPP LTE is a 3GPP plan to improve the UMTS mobile phone standard. 3GPP can define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G, 5G NR or 6G technology; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of the present disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0044] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT), with ultra-high density (e.g., about 1M nodes / km 2 ), ultra-low complexity (e.g., about 10s of bits / second), ultra-low power consumption (e.g., about 10+ years battery life), and deep coverage with the ability to reach challenging locations; (2) including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) providing services with enhanced mobile broadband (including extremely high capacity (e.g., about 10Tbps / km 2 ), extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness coverage with advanced discovery and optimization.

[0045] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes arise for FR2, which is often (interchangeably) referred to as the “millimeter wave” (mmWave) band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “mmWave” band by the International Telecommunication Union (ITU).

[0046] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" and the like can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used in this article, the term "mmWave" and the like can broadly represent frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0047] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform features. These features may include scalable parameter sets and transmission time intervals (TTIs); a common flexible framework that efficiently multiplexes services and features using dynamic, low-latency time division duplex (TDD) designs or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can efficiently address various services operating across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD or TDD implementations, the subcarrier spacing may appear at 15kHz, such as over bandwidths of 1MHz, 5MHz, 10MHz, 20MHz, etc. For various other outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz over 80MHz / 100MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, the subcarrier spacing may occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments transmitting over mmWave components at 28GHz TDD, the subcarrier spacing may occur at 120kHz over a 500MHz bandwidth.

[0048] 5G NR's scalable parameter sets facilitate scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design where uplink or downlink scheduling information, data, and acknowledgments are in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0049] For clarity, certain aspects of the devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0050] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate using any combination of licensed spectrum or unlicensed spectrum depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0051] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementation or use can be implemented via integrated chip specific implementation or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail equipment or purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementation can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems containing one or more described aspects. In some practical environments, the equipment in combination with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be implemented in a wide variety of embodiments of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0052] Figure 1 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in are likely to have related corresponding components in other network arrangements (including, for example, cellular-style network arrangements and non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.)).

[0053] Figure 1The illustrated wireless network 100 includes many base stations 105 and other network entities. A base station may be a station that communicates with a UE, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In a specific implementation of the wireless network 100 herein, the base station 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in a specific implementation of the wireless network 100 herein, the base station 105 may provide wireless communication using one or more frequencies (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof) in the same frequency as an adjacent cell. In some examples, a separate base station 105 or UE 115 may be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0054] A base station may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or a femto cell), or other types of cells. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with a service subscription with a network provider. A small cell (such as a pico cell) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription with a network provider. A small cell (such as a femto cell) will generally also cover a relatively small geographic area (e.g., a home), and in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD) or massive MIMO. Base stations 105a-105c use their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0055] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some cases, the network may be enabled or configured to handle dynamic switching between synchronous or asynchronous operation.

[0056] UE 115 is dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that, although in the standards and specifications promulgated by 3GPP, mobile devices are generally referred to as UEs, such devices may be additionally or otherwise referred to as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, mobile phones, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices or vehicle modules, or some other suitable terminology by those skilled in the art. In this document, a "mobile" device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices (for example) may include one or more specific implementations of UE 115, including mobile phones, cellular phones, smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet computers, and personal digital assistants (PDAs). The mobile device may additionally be an IoT or "Internet of Everything" (IoE) device, such as a car or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-rotor helicopter, a quad-rotor helicopter, a smart energy or security device, a solar panel or solar array, city lighting, tap water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE may be a device that includes a universal integrated circuit card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UE 115a-115d of the specific implementation illustrated in the figure are examples of mobile smart phone type devices accessing the wireless network 100. The UE may also be a machine specially configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). Figure 1 UEs 115e to 115k illustrated in FIG. 1 are examples of various machines configured for communication that access the wireless network 100 .

[0057] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication link (represented as a lightning ball) indicates the wireless transmission between the UE and the serving base station (which is the base station designated to serve the UE on the downlink or uplink) or the expected transmission between the base stations and the backhaul transmission between the base stations. The UE can operate as a base station or other network node in some scenarios. The backhaul communication between the base stations of the wireless network 100 can be carried out using wired or wireless communication links.

[0058] In operation, at the wireless network 100, base stations 105a-105c use 3D beamforming and collaborative spatial techniques (such as coordinated multi-point (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0059] The wireless network 100 of the specific implementation supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e as drones. The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices such as UE 115f (thermometer), UE 115g (smart meter) and UE 115h (wearable device) can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports it to the network through small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD communications or low-latency FDD communications (eg, in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e).

[0060] Figure 2 1 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be Figure 1 For a restricted association scenario (as described above), base station 105 may be any one of the base stations in the UE and one of the UEs. Figure 1 The small cell base station 105f in the example of FIG. 105 and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the list of accessible UEs of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown, the base station 105 may be equipped with antennas 234a through 234t, and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communications.

[0061] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (such as a processor). The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, the transmit processor 220 may process (e.g., encode and symbol map) the data and the control information, respectively, to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, or reference symbols, if applicable, and may provide an output symbol stream to modulators (MODs) 232a to 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include pre-coding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., analog-convert, amplify, filter, and up-convert it) to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0062] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols when necessary, and provide detected symbols. The receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to the data sink 260, and provide decoded control information to the controller 280 (e.g., a processor).

[0063] On the uplink, at the UE 115, the transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller 280 (e.g., for a physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if necessary, further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if necessary, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller 240 .

[0064] The controllers 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as performing or directing Figure 7 , Figure 8 , Fig.10 or Fig.11 Execution of the illustrated processes or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0065] In some cases, the UE 115 and the base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 may traditionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-send (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some specific implementations, the CCA may include an energy detection process to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating the use of the channel. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets (as a manifestation of a collision).

[0066] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 115 via one or more radio frequency (RF) access links. In some implementations, a UE 115 may be served simultaneously by multiple RUs 340.

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

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

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

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

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

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

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

[0074] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a transmit receive point (TRP), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote unit (RU), a core network, an LFM, and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first device, a first computing system, a first one or more components, a first processing entity, etc. configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second one or more components, a second processing entity, etc.

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

[0076] Figure 4 is a block diagram of an example wireless communication system 400 that supports power allocation or resource allocation for NOMA according to one or more aspects. In some examples, the wireless communication system 400 can implement aspects of the wireless network 100. The wireless communication system 400 includes a UE 115, a UE 415, and a base station 105. Although two UEs (115 and 415) and one base station 105 are illustrated, in some other specific implementations, the wireless communication system 400 may generally include a single UE or more than two UEs 115 and may include more than one base station 105.

[0077] The UE 115 may include various components (such as structures, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 402 (hereinafter collectively referred to as "processors 402"), one or more memory devices 404 (hereinafter collectively referred to as "memory 404"), one or more transmitters 416 (hereinafter collectively referred to as "transmitters 416"), and one or more receivers 418 (hereinafter collectively referred to as "receivers 418"). In some specific implementations, the UE 115 may include an interface (e.g., a communication interface) including the transmitter 416, the receiver 418, or a combination thereof. The processor 402 may be configured to execute instructions 405 stored in the memory 404 to perform the operations described herein. In some specific implementations, the processor 402 includes or corresponds to one or more of the receiving processor 258, the transmitting processor 264, and the controller 280, and the memory 404 includes or corresponds to the memory 282.

[0078] The memory 404 includes or is configured to store instructions 405 and grant exemption information 406. The grant exemption information 406 may enable the UE 115 to perform one or more grant exemption operations, such as the transmission of a grant exemption message. In some implementations, the grant exemption message may include an uplink (UL) message, one or more messages of a 2-step random access channel (RACH), or a combination thereof.

[0079] The grant exemption information 406 may include or indicate a plurality of power levels 408, a plurality of resources 410, mapping information 412, or a combination thereof. The plurality of power levels 408 may include a plurality of power target levels, such as a plurality of transmit power target levels. Figure 5 An example of multiple power levels 408 is further described. Multiple resources 410 may include multiple frequency domain resource candidates or multiple time domain resource candidates. Each resource candidate in the multiple resource candidates overlaps with at least one other resource candidate in the multiple resource candidates. Each resource candidate in the multiple resource candidates overlaps with each other resource candidate in the multiple resource candidates. In some specific implementations, at least one resource candidate in the multiple resource candidates overlaps with at least one other resource candidate in the multiple resource candidates. In some other specific implementations, each resource candidate in the multiple resource candidates overlaps with at least one other resource candidate in the multiple resource candidates, or overlaps with each other resource candidate in the multiple resource candidates. This document at least refers to Figure 6 An example of multiple resources 410 is further described. Mapping information 412 may include mapping data. In some implementations, the mapping data may include or correspond to multiple power levels 408 or multiple resources 410. For example, mapping data that maps a PRACH preamble to multiple power target levels. For another example, mapping data that maps a DMRS port to multiple resource candidates. For another example, mapping data that maps a PRACH preamble to multiple resource candidates.

[0080] The transmitter 416 is configured to send reference signals, control information, and data to one or more other devices, and the receiver 418 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 416 may send signaling, control information, and data to the base station 105, and the receiver 418 may receive signaling, control information, and data from the base station. In some implementations, the transmitter 416 and the receiver 418 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 416 or the receiver 418 may include or correspond to a reference signal. Figure 2 One or more components of UE 115 are described.

[0081] In some implementations, the UE 115 may include one or more antenna arrays. The one or more antenna arrays may be coupled to a transmitter 416, a receiver 418, or a communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices (such as with a base station 105). In some implementations, the antenna array may be configured to perform wireless communications using different beams (also referred to as antenna beams). The beams may include Tx beams and Rx beams. For illustration, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements in the antenna array may be configured to communicate using a different corresponding beam, which may have a corresponding direction different from that of the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to generate multiple beams concurrently, for example, using multiple RF chains of UE 115. Each separate set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number of antenna elements greater than two. Although described as an antenna array, in other specific implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different corresponding beam.

[0082] UE 415 may include one or more components as described herein with reference to UE 115. In some implementations, UE 415 is a 5G-capable UE, a 6G-capable UE, or a combination thereof.

[0083] The base station 105 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 452 (hereinafter collectively referred to as "processor 452"), one or more memory devices 454 (hereinafter collectively referred to as "memory 454"), one or more transmitters 456 (hereinafter collectively referred to as "transmitters 456"), and one or more receivers 458 (hereinafter collectively referred to as "receivers 458"). In some specific implementations, the base station 105 may include an interface (e.g., a communication interface) including the transmitter 456, the receiver 458, or a combination thereof. The processor 452 may be configured to execute instructions 460 stored in the memory 454 to perform the operations described herein. In some specific implementations, the processor 452 includes or corresponds to one or more of the receive processor 238, the transmit processor 220, and the controller 240, and the memory 354 includes or corresponds to the memory 242.

[0084] The memory 454 includes or is configured to store instructions 460 and grant-free information 464. The instructions 460 may include decoding logic 462. The decoding logic 462 is configured to enable the processor 452 to perform one or more decoding operations. For example, the decoding logic 462 may be configured to enable the processor 452 to perform continuous interference cancellation. For example, in a multiple access environment, the base station 105 may receive transmissions from two different UEs. The base station 105 may first decode one of the two transmissions, then cancel the correctly decoded transmission and decode the other of the two transmissions. In this way, the base station 105 (or its decoder) may continuously attempt to decode each transmission (e.g., message or packet) in multiple transmissions, and at each step, eliminate the continuously decoded packets from the signal (associated with multiple transmissions). When performing continuous interference cancellation, asymmetric SINRs between different received transmissions (or between different UEs) may be advantageous because the base station 105 may begin to decode the received transmission with the highest SINR. Having equal power is not good, different powers are needed for different time domain and frequency domain resources.

[0085] The grant exemption information 464 may include or correspond to the grant exemption information 406. The grant exemption information 464 may include or indicate a plurality of power levels 466, a plurality of resources 468, mapping information 469, or a combination thereof. In some implementations, the plurality of power levels 466 may include or correspond to the plurality of power levels 408, the plurality of resources 468 may include or correspond to the plurality of resources 410, and the mapping information 469 may include or correspond to the mapping information 412, or a combination thereof.

[0086] The transmitter 456 is configured to send reference signals, synchronization signals, control information, and data to one or more other devices, and the receiver 458 is configured to receive reference signals, control information, and data from one or more other devices. For example, the transmitter 456 may send signaling, control information, and data to the UE 115, and the receiver 458 may receive signaling, control information, and data from the UE. In some implementations, the transmitter 456 and the receiver 458 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 456 or the receiver 458 may include or correspond to a reference signal. Figure 2 One or more components of a base station 105 are described.

[0087] In some implementations, the base station 105 may include one or more antenna arrays. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices (such as with the UE 115). In some implementations, the antenna array may be configured to perform wireless communications using different beams (also referred to as antenna beams). The beams may include Tx beams and Rx beams. For illustration, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different corresponding beam, which may have a corresponding direction different from the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to generate multiple beams concurrently, for example, using multiple RF chains of the base station 105. Each individual set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number of antenna elements greater than two. Although described as an antenna array, in other specific implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different corresponding beam.

[0088] Although described as including a base station 105, the network may alternatively or additionally include one or more network entities. The network entity may include a base station 105, a modem, a router (e.g., a wireless router), or a combination thereof. In some implementations, the network entity may be configured to perform one or more operations described herein with reference to the base station 105. Additionally or alternatively, the network entity may be configured to communicate with the base station 105.

[0089] In some implementations, the wireless communication system 400 implements a 5G NR network. For example, the wireless communication system 400 may include a plurality of 5G-capable UEs 115 and a plurality of 5G-capable base stations 105, such as UEs and base stations configured to operate according to a 5G NR network protocol, such as a 5G NR network protocol defined by 3GPP. In some other implementations, the wireless communication system 400 implements a 6G network.

[0090] During operation of the wireless communication system 400, the base station 105 may generate configuration information 470. For example, the base station 105 may generate configuration information based on grant-free information 464, such as power level 466, resource 468, mapping information 469, or a combination thereof. In some implementations, the configuration information 470 may include or indicate the power level 466, resource 468, mapping information 469, or a combination thereof. Additionally or alternatively, the configuration information 470 may indicate that the UE may perform grant-free access or that the base station 105 is configured for grant-free access.

[0091] The base station 105 may send the configuration information 470. For example, the base station 105 may send the configuration information to one or more UEs, such as UE 115, UE 415, or a combination thereof. In some implementations, the configuration information 470 may be included in a system information block (SIB) or a radio resource control (RRC).

[0092] The UE 115 may receive the configuration information 470 and identify and / or generate the grant exemption information 406 based on the configuration information 470. Although described as the UE 115 receiving an indication of the grant exemption information 406 (e.g., 464) from the base station 105 based on the configuration information 470, in other specific implementations, the UE 115 may have included at least a portion of the grant exemption information 406. For example, the grant exemption information 406 may be defined by a standard.

[0093] UE 115 may determine to send data to base station 105. UE 115 may determine one or more parameters associated with the sending of data. For example, UE 115 may identify a transmit power level, a frequency domain resource, a time domain resource, a DMRS port, a PRACH preamble, or a combination thereof. In some implementations, UE 115 may determine at least one of the one or more parameters based on grant-free message 472. UE 115 may send data based on or according to one or more parameters. For example, UE 115 may send data as grant-free message 472. In some implementations, grant-free message 472 may include or indicate a transmit power level, a frequency domain resource, a time domain resource, a DMRS port, a PRACH preamble, a PRACH preamble index value, or a combination thereof.

[0094] The base station 105 may receive the grant exemption message 472 and may decode the grant exemption message 472. In some implementations, the base station 105 may receive at least a portion of the grant exemption message 472 while the base station 105 receives a portion of the uplink message 474 from the UE 115. The base station 105 may decode the grant exemption message 472 and the uplink message 474 based on the decoding logic 462. For example, the base station 105 may perform successive interference cancellation to decode the grant exemption message 472 and the uplink message 474.

[0095] In some implementations, the base station 105 may assign a set of power targets, such as power level 466 (e.g., 408), to the UE 115. The base station 105 may include an indication of the set of power targets in configuration information 470 (such as an RRC configuration). In some implementations, the RRC configuration may be included in the SIB. The UE 115 may select (e.g., randomly select) a power level and use the selected power level to send the grant exemption message 472. In other implementations, the set of power targets (e.g., power level 408) may be predetermined (such as defined by a standard) and stored at the UE 115. Note that the base station 105 does not need to know the exact power level selected and / or used by the UE 115 to send the grant exemption message 472. Note that when multiple UEs transmit during the same PUSCH opportunity, the PRACH preambles mapped to the same PUSCH opportunity by different UEs should be mapped to different power levels so that transmissions from different UEs have different SINRs.

[0096] In some implementations, the UE 115 may determine the power level based on a random selection of a preamble (such as a preamble for a 2-step RACH). In some such implementations, the UE 115 may include mapping information 412, such as a mapping of a preamble (such as a PRACH preamble) to a power target. Thus, the UE 115 may randomly select a preamble and determine the target power by mapping the preamble (e.g., a PRACH sequence index) to a power level based on the mapping data. In some implementations, the mapping data (or an indication thereof) may be received by the UE 115 from the base station 105. For example, the base station 105 may include an indication of the power level (e.g., 408) in configuration information 470 (such as an RRC configuration). In some implementations, the RRC configuration may be included in an SIB. In some implementations, the set of power targets may be indicated by a parameter such as a msgA-preambleReceivedTargetPower parameter. For illustration, the parameter may include a list of target power values, such as the enumerated list, and the order of the listed target power values ​​indicates the index value of each power value. For another example, the set of power targets may be indicated by a parameter such as the msgA-DeltaPreamble parameter. In other specific implementations, the mapping data (e.g., mapping information 412) may be predetermined (such as defined by a standard) and stored at the UE 115.

[0097] In some implementations, a standard may define the output power for which the UE 115 is configured. For example, a standard may indicate:

[0098]

[0100] Where P CMAX,f,c (i) is the maximum output power configured by the UE for carrier f of serving cell c in PUSCH transmission opportunity i. CMAX，f，c (i) May be defined in [8-1, TS 38.101-1], [8-2, TS 38.101-2] and [8-3, TS 38.101-3].

[0101] P O_PUSCH,b,f,c (j) is composed of the component P O_NOMINAL,PUSCH,b，f，c (j) and the component P O_UE_PUSCH,b,f,c (j), where j is {0, 1, ..., J-1}.

[0102] If the UE has established a dedicated RRC connection using a Type-2 random access procedure as described in clause 8 and no P0-PUSCH-AlphaSet is provided, then for PUSCH transmissions for a Type-2 random access procedure as described in clause 8.1A,

[0103] j=0、P O_UE_PUSCH,b,f,c (0) = 0 and PO_NOMINAL_PUSCH,f,c(0) = P O_PRE +Δ MsgA_PUSCH ,

[0104] Where for the carrier f of the serving cell c, P O_PRE Provided by msgA-preambleReceivedTargetPower, or if msgA-preambleReceivedTargetPower is not provided, then provided by preambleReceivedTargetPower, and provided by msgA-DeltaPramble, or if msgA-DeltaPreamble is not provided, then Delta MsgA_PUSCH =Δ MsgA_PREAMBLE_Msg3 dB.

[0105] In some implementations, the RACH-ConfigGenericTwoStepRA information element (such as that defined in Rel.15, Rel.16 or higher) may include:

[0106]

[0107]

[0108] Note that for the msgA-PreambleReceivedTargetPower parameter, the enumerated values ​​of "first value" and "second value" are exemplary. The enumerated values ​​for the msgA-PreambleReceivedTargetPower parameter may include one or more values, such as a plurality of values ​​including two or more values.

[0109] In some implementations, the MsgA-PUSCH-CDnfig information element (such as an information element defined in Rel.15, Rel.16 or higher) may include:

[0110]

[0111] Note that for the msgA-DeltaPreamble parameter, the enumerated values ​​of "first value" and "second value" are exemplary. The enumerated values ​​for the msgA-DeltaPreamble parameter may include one or more values, such as a plurality of values ​​including two or more values.

[0112] In some implementations, the UE 115 may use resources 410, which may include or indicate FD resources, TD resources, or a combination thereof. For example, the resources 410 may include a pool of candidates that the UE 115 may randomly select. For illustration, the base station 105 may allocate or a standard may define a list of resources. Additionally or alternatively, the selection of one of the resources 410 may be performed based on the mapping information 412.

[0113] In some implementations, the base station 105 may indicate the resources 410 based on mapping data including or indicating a mapping of DMRS ports to resource sets. The mapping data (e.g., mapping information 412, 469) may be sent from the base station 105 to the UE 115, or may be defined by a standard. The UE 115 may know which DMRS port(s) it will use, and may determine one or more of the resources 410 based on the mapping data.

[0114] In some implementations, such as for 2-step RACH, the mapping data (eg, mapping information 412 , 469 ) includes or indicates a mapping of a PRACH preamble to a resource set. For example, the preamble index value may indicate an index value of a resource in the resources 410 .

[0115] In some implementations, the resources 410, 468 or mapping information 412, 469 may be indicated by a parameter such as a frrequencyDomainAllocation parameter. For illustration, the parameter may include a list of resources, such as the enumerated list, and the order of the listed resources indicates the index value of each resource.

[0116] In some implementations, the rrc-ConfiguredUplinkGrant information element (such as that defined in Rel. 15, Rel. 16, or higher) may include:

[0117]

[0118]

[0119] Note that for the frrequencyDomainAllocation parameter, the enumerated values ​​of "first value" and "second value" are exemplary. The enumerated values ​​for the frequencyDomainAllocation parameter may include one or more values, such as a plurality of values ​​including two or more values. Additionally or alternatively, the enumerated values ​​may include bit string values. Note also that additionally or alternatively, the timeDomainOffset parameter or the timeDomainAllocation parameter may include an enumerated list of values.

[0120] In some implementations, the resources 410, 468 or mapping information 412, 469 may be indicated by a parameter such as a frequencyStartMsgA-PUSCH parameter. For illustration, the parameter may include a list of resources, such as the enumerated list, and the order of the listed resources indicates the index value of each resource.

[0121] In some implementations, the MsgA-PUSCH-Resource information element (such as an information element defined in Rel. 15, Rel. 16 or higher) may include:

[0122]

[0123]

[0124] Note that for the frequencyStarrtMsgA-PUSCH parameter, the enumerated values ​​of "first value" and "second value" are exemplary. The enumerated values ​​for the frequencyStarrtMsgA-PUSCH parameter may include one or more values, such as a plurality of values ​​including two or more values. Additionally or alternatively, the enumerated values ​​may include a bit string value. Note also that additionally or alternatively, the msgA-PUSCH-TimeDomainOffset parameter or the msgA-PUSCH-TimeDomainAllocation parameter may include an enumerated list of values.

[0125] As reference Figure 4As described, the present disclosure provides techniques for power allocation and resource allocation for NOMA. For example, in some aspects, the present disclosure provides techniques for creating or having a grant-free situation in a multiple access environment where a base station 105 or another network entity receives communications, wherein the communications have an asymmetric SINR. The asymmetric SINR enables the base station 105 or the network entity to perform continuous interference cancellation with respect to multiple received communications. In some other aspects, the present disclosure may implement and provide improved communications, including increased multiplexing gain and uplink cell capacity, reduced control overhead, efficient resource utilization, grant-free uplink communications, or a combination thereof. For example, in NOMA, a UE 115 or 415 may perform grant-free transmission and transmit as long as it has a packet without going through control signaling.

[0126] Figure 5 4 is a diagram illustrating an example of available power allocation for NOMA according to one or more aspects. For example, the diagram illustrates an example of randomized power control associated with different power levels, such as power levels 408 or 466. Different power levels may be used by different UEs, such as UE 115 and UE 415. For example, different UEs may select or use different power levels.

[0127] As shown, the diagram includes different power levels for each UE for time domain (TD) resources or frequency domain (FD) resources. For example, the diagram includes a first power level PL1, a second power level PL2, and a third power level PL3. Although three power levels are shown, other specific implementations may have different numbers of power levels, such as one power level, two power levels, or more than three power levels.

[0128] Figure 6 4 is a diagram illustrating an example of an allocation of available resources for NOMA according to one or more aspects. For example, the diagram illustrates an example of a partial overlap of FD resources such as resources 410 or 468. Different FD resources may be used by different UEs (e.g., UE 115 and UE 415). For example, different UEs may select or use different FD resources.

[0129] As shown, the figure includes different resource elements (REs) for symbols. For example, the figure includes a first RE RE1, a second RE RE2, a third RE RE3, and a fourth RE RE4. Additionally, as shown, the first RE RE1 spans from the first frequency F1 to the second fifth frequency F5, the second RE RE2 spans from the second frequency F2 to the sixth frequency F6, the third RE RE3 spans from the third frequency F3 to the seventh frequency F7, and the fourth RE RE4 spans from the fourth frequency F4 to the eighth frequency F8. The first RE RE1 at least partially overlaps with at least one other RE, for example, the second RE2, the third RE3, or the fourth RE4. As shown, the first RE RE1 partially overlaps with each of the second RE2, the third RE3, and the fourth RE4. In some specific implementations, each of the first RE1, the second RE2, the third RE3, and the fourth RE4 overlaps with a portion of each of the other REs in the first RE1, the second RE2, the third RE3, and the fourth RE4. Although four REs are shown, other specific implementations may have different numbers of REs, such as one RE, two REs, three REs, or more than four REs.

[0130] Figure 7 700 is a flow chart illustrating an example process 700 for supporting power allocation for NOMA according to one or more aspects. The operations of process 700 may be performed by a UE (such as the one described above with reference to Figures 1 to 4 The UE 115, UE415 or reference Fig. 9 For example, the example operations (also referred to as "boxes") of process 700 may enable UE 115 to support power allocation for NOMA.

[0131] In block 702, the UE randomly selects a parameter value associated with a power level in a plurality of power target levels. The plurality of power target levels may include or correspond to power level 408, power level 466, or Figure 5 Power levels PL1, PL2, PL3.

[0132] In block 704, the UE sends an uplink communication using the power level to a network entity. The network entity may include or correspond to the base station 105. The uplink communication may include or correspond to the grant-free message 472 or the uplink message 474. In some implementations, the uplink communication includes a grant-free uplink communication.

[0133] In some implementations, the UE may receive a configuration including or indicating a plurality of power target levels from a network entity. For example, the configuration may include or correspond to configuration information 470. The UE may receive a SIB or RRC including or indicating the configuration from the network entity. Additionally or alternatively, the configuration may be predetermined (such as based on a standard) and stored at the UE. In some implementations, the parameter value is a power level selected from a plurality of power target levels.

[0134] In some implementations, the uplink communication includes a first message (Msg-A) of a 2-step RACH. The UE may receive mapping data that maps the PRACH preamble to a power target level. For example, the mapping data may include or correspond to mapping information 412 or mapping information 469. In some implementations, the mapping data may be received or indicated by an RRC received by the UE from a network entity. Additionally or alternatively, the mapping data may be predetermined (such as based on a standard) and stored at the UE. In some implementations, the parameter value may include or be associated with the PRACH preamble. For illustration, randomly selecting a parameter value may include randomly selecting a PRACH preamble from a set of multiple PRACH preambles. The UE may determine a power level based on the PRACH preamble and based on the mapping data. For example, the PRACH preamble may correspond to a PRACH sequence index value, and the UE may use the mapping data and determine the power level based on the PRACH sequence index value. In some implementations, the uplink communication includes or indicates a PRACH sequence index value.

[0135] In some implementations, the plurality of power target levels are associated with an enumerated list of the plurality of power target levels included in or indicated by a msgA-preambleReceivedTargetPower parameter. Additionally or alternatively, the plurality of power target levels are associated with an enumerated list of the plurality of power target levels included in or indicated by a msgA-DeltaPreamble parameter.

[0136] Figure 8 800 is a flow chart illustrating an example process 800 for supporting resource allocation for NOMA according to one or more aspects. The operations of process 800 may be performed by a UE (such as the one described above with reference to Figures 1 to 4 The UE 115, UE415 or reference Fig. 9 For example, the example operations (also referred to as "boxes") of process 800 may enable UE 115 to support resource allocation for NOMA.

[0137] In block 802, the UE receives an indicator indicating a plurality of resource candidates from a network entity. The network entity may include or correspond to base station 105. The plurality of resource candidates may include or correspond to resource 410, resource 468, or Figure 6 Each of the plurality of resource candidates overlaps with at least one other resource candidate in the plurality of resource candidates. In some implementations, each of the plurality of resource candidates overlaps with each other resource candidate in the plurality of resource candidates.

[0138] In some implementations, the indicator may be received or indicated by configuration information (such as configuration information 470). For example, the indicator may be received or indicated by an RRC received by the UE from a network entity. Additionally or alternatively, the configuration information may be predetermined (such as based on a standard) and stored at the UE. Additionally or alternatively, the multiple resource candidates include multiple frequency domain resource candidates or multiple time domain resource candidates. In some implementations, the multiple resource candidates include multiple frequency domain resource candidates. In other implementations, the multiple resource candidates include multiple time domain resource candidates.

[0139] In block 804, the UE sends an uplink communication to a network entity based on a resource candidate from among the plurality of resource candidates. The uplink communication may include or correspond to the grant-free message 472 or the uplink message 474. In some implementations, the uplink communication includes a grant-free uplink communication.

[0140] In some implementations, the UE may select a resource candidate from a plurality of resource candidates based on a DMRS port of the UE or based on a PRACH preamble. In some such implementations, the uplink communication may indicate a DMRS port or a PRACH preamble.

[0141] In some implementations, the indicator of the plurality of resource candidates includes or indicates mapping data that maps a DMRS port to a plurality of resource candidates or that maps a PRACH preamble to a plurality of resource candidates. The mapping data may include or correspond to mapping information 412 or mapping information 469. In some implementations, the mapping data may be received or indicated by an RRC received by the UE from a network entity. Additionally or alternatively, the mapping data may be predetermined (such as based on a standard) and stored at the UE.

[0142] In some implementations, the indicator of the plurality of resource candidates may be associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyDomainAllocation parameter or a timeDomainAllocation parameter. Additionally or alternatively, the indicator of the plurality of resource candidates is associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyStartMsgA-PUSCH parameter or a msgA-PUSCH-TimeDomainAllocation parameter.

[0143] Fig. 9 is a block diagram of an example UE 900 that supports power allocation or resource allocation for NOMA according to one or more aspects. The UE 900 may be configured to perform operations, including reference Figures 7 and 8 In some implementations, the UE 900 includes a reference Figures 1 to 4 1 and 115. For example, the UE 900 includes a controller 280 that operates to execute logic or computer instructions stored in a memory 282 and controls components of the UE 900 that provide the features and functionality of the UE 900. The UE 900 transmits and receives signals via radios 901a-901r and antennas 252a-252r under the control of the controller 280. The radios 901a-901r include various components and hardware, such as Figure 2 As illustrated for UE 115, modulators and demodulators 254a-254r, a MIMO detector 256, a receive processor 258, a transmit processor 264, and a TX MIMO processor 266 are included.

[0144] As shown, the memory 282 may include grant exemption information 902 and communication logic 903. The grant exemption information 902 may include or correspond to grant exemption information 406, such as power level 408, resource 410, mapping information 412, or a combination thereof. The communication logic 903 (such as UL communication logic) may be configured to generate one or more grant exemption messages, such as grant exemption message 472. The one or more grant exemption messages may be generated based on the grant exemption information 902. The UE 900 may receive from one or more network entities (such as Figures 1 to 4 Base station 105 or Fig.12 The illustrated base station) receives signals or sends signals to one or more network entities.

[0145] Fig.10 1 is a flow chart illustrating an example process 1000 for supporting power allocation for NOMA according to one or more aspects. The operations of process 1000 may be performed by a network entity (such as the network entity described above with reference to FIG. Figures 1 to 4 The base station 105 or as mentioned above Fig.12 For example, the example operations of process 1000 may enable a network entity to support power allocation for NOMA.

[0146] At block 1002, a network entity receives an uplink communication from a UE that is sent using a power level from a plurality of power target levels. The UE may include or correspond to UE 115 or UE 415. The uplink communication may include or correspond to grant-free message 472 or uplink message 474. In some implementations, the uplink communication includes a grant-free uplink communication. The plurality of power target levels may include or correspond to power level 408, power level 466, or Figure 5 The power levels PL1, PL2, PL3. The power levels may be based on parameter values ​​randomly selected by the UE.

[0147] At block 1004, the network entity decodes the uplink communication. In some implementations, the network entity may use a successive interference cancellation technique to decode the uplink communication. To illustrate, the network entity may receive another uplink communication and may perform successive interference cancellation based on the uplink communication and the another uplink communication to decode the uplink communication and the another uplink communication.

[0148] In some implementations, the network entity sends a configuration including or indicating a plurality of power target levels. For example, the configuration may include or correspond to configuration information 470. The network entity may send a SIB or RRC including or indicating the configuration. Additionally or alternatively, the configuration may be predetermined (such as based on a standard) and stored at the network entity, the UE, or both. In some implementations, the parameter value is a power level selected by the UE from a plurality of power target levels. Additionally or alternatively, the network entity may indicate to the UE that the UE may perform grant-free access.

[0149] In some implementations, the uplink communication includes a first message (Msg-A) of a 2-step RACH. The network entity may send mapping data that maps the PRACH preamble to a power target level. For example, the mapping data may include or correspond to mapping information 412 or mapping information 469. In some implementations, the mapping data may be sent or indicated by an RRC received from the network entity to the UE. Additionally or alternatively, the mapping data may be predetermined (such as based on a standard) and stored at the network entity, the UE, or both. In some implementations, the parameter value may include or be associated with the PRACH preamble. For illustration, the UE may randomly select a parameter value by randomly selecting a PRACH preamble from a set of multiple PRACH preambles. The UE may determine a power level based on the PRACH preamble and based on the mapping data. For example, the PRACH preamble may correspond to a PRACH sequence index value, and the UE may use the mapping data and determine the power level based on the PRACH sequence index value. In some implementations, the uplink communication includes or indicates a PRACH sequence index value. The network entity may determine or identify the PRACH sequence index value and may decode the uplink communication based on the PRACH sequence index value. For example, the network entity may determine a power level based on the PRACH sequence index value using the mapping data and may decode the uplink communication based on the power level.

[0150] In some implementations, the plurality of power target levels are associated with an enumerated list of the plurality of power target levels included in or indicated by a msgA-preambleReceivedTargetPower parameter. Additionally or alternatively, the plurality of power target levels are associated with an enumerated list of the plurality of power target levels included in or indicated by a msgA-DeltaPreamble parameter.

[0151] Fig.11 1 is a flow chart illustrating an example process 1100 for supporting resource allocation for NOMA according to one or more aspects. The operations of process 1100 may be performed by a network entity (such as the one described above with reference to Figures 1 to 4 The base station 105 or as mentioned above Fig.12 For example, the example operations of process 1100 may enable base station 105 to support power allocation for NOMA.

[0152] At block 1102, the network entity sends an indicator of a plurality of resource candidates to a UE. The UE may include or correspond to UE 115 or UE 415. The plurality of resource candidates may include or correspond to resource 410, resource 468, or Figure 6Each of the plurality of resource candidates overlaps with at least one other resource candidate in the plurality of resource candidates. In some implementations, each of the plurality of resource candidates overlaps with each other resource candidate in the plurality of resource candidates.

[0153] In some implementations, the indicator may be received or indicated by configuration information (such as configuration information 470). For example, the indicator may be received or indicated by an RRC sent by a network entity and received by a UE. Additionally or alternatively, the configuration information may be predetermined (such as based on a standard) and stored at the UE. Additionally or alternatively, the multiple resource candidates include multiple frequency domain resource candidates or multiple time domain resource candidates. In some implementations, the multiple resource candidates include multiple frequency domain resource candidates. In other implementations, the multiple resource candidates include multiple time domain resource candidates.

[0154] At block 1104, the network entity receives an uplink communication from the UE based on a resource candidate from a plurality of resource candidates determined by the UE. The uplink communication may include or correspond to a grant-free message 472 or an uplink message 474. In some implementations, the uplink communication includes a grant-free uplink communication. In some implementations, the UE may select a resource candidate from a plurality of resource candidates based on a DMRS port of the UE or based on a PRACH preamble. In some such implementations, the uplink communication may indicate a DMRS port or a PRACH preamble.

[0155] In some implementations, the network entity may use a successive interference cancellation technique to decode the uplink communication. To illustrate, the network entity may receive another uplink communication and may perform successive interference cancellation based on the uplink communication and the another uplink communication to decode the uplink communication and the another uplink communication.

[0156] In some implementations, the indicator of the plurality of resource candidates includes or indicates mapping data that maps a DMRS port to a plurality of resource candidates or that maps a PRACH preamble to a plurality of resource candidates. The mapping data may include or correspond to mapping information 412 or mapping information 469. In some implementations, the mapping data may be received or indicated by an RRC received by the UE from a network entity. Additionally or alternatively, the mapping data may be predetermined (such as based on a standard) and stored at the UE, the network entity, or both.

[0157] In some implementations, the indicator of the plurality of resource candidates may be associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyDomainAllocation parameter or a timeDomainAllocation parameter. Additionally or alternatively, the indicator of the plurality of resource candidates is associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyStartMsgA-PUSCH parameter or a msgA-PUSCH-TimeDomainAllocation parameter.

[0158] Fig.12 is a block diagram of an example base station 1200 supporting power allocation or resource allocation for NOMA according to one or more aspects. Although described as a base station, in other specific implementations, the base station 1200 may include or correspond to a network entity. The base station 1200 may be configured to perform operations, including reference Figure 10 to Figure 11 In some implementations, the base station 1200 includes a reference Figures 1 to 4 The structure, hardware, and components shown and described for base station 105 of the present invention are shown and described in detail. For example, base station 1200 may include a controller 240 that operates to execute logic or computer instructions stored in memory 242 and control components of base station 1200 that provide the features and functionality of base station 1200. Base station 1200 transmits and receives signals via radios 1201a-1201t and antennas 234a-234t under the control of controller 240. Radios 1201a-1201t include various components and hardware, such as those described in Figure 2 , illustrated for base station 105, includes modulators and demodulators 232a-232t, a transmit processor 220, a TX MIMO processor 230, a MIMO detector 236, and a receive processor 238.

[0159] As shown, the memory 242 may include grant exemption information 1202 and decoding logic 1203. The grant exemption information 1202 may include or correspond to the grant exemption information 464, such as power level 466, resource 468, mapping information 46912, or a combination thereof. The decoding logic 1203 may be configured to decode one or more grant exemption messages (such as grant exemption message 472). The one or more grant exemption messages may be decoded based on the grant exemption information 1202. In some specific implementations, the decoding logic 1203 may include or correspond to the decoding logic 462. The base station 1200 may receive from one or more UEs (such as Figures 1 to 4 UE 115, UE 415 or Fig. 9 UE 900) receives a signal or sends a signal to the one or more UEs.

[0160] Please note that reference Figure 7 , Figure 8 , Fig.10 , Fig.11 One or more blocks (or operations) described may be combined with one or more blocks (or operations) described with reference to another figure. Figure 7 One or more boxes (or operations) of Figure 8 One or more boxes (or operations) of . Fig.10 One or more boxes associated with Fig.11 One or more boxes associated with Figure 7 , Figure 8 , Fig.10 or Fig.11 One or more boxes associated with Figures 1 to 4 One or more associated boxes (or operations) are combined. Additionally or alternatively, the above reference Figures 1 to 4 One or more of the operations described may be combined with reference to Fig. 9 or Fig.12 A combination of one or more of the operations described.

[0161] In one or more aspects, techniques for supporting power allocation and resource allocation for non-orthogonal multiple access NOMA may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes or devices described elsewhere herein. In a first aspect, techniques for supporting power allocation or resource allocation for non-orthogonal multiple access (NOMA) may include: randomly selecting a parameter value associated with a power level in a plurality of power target levels. These techniques may also include: sending uplink communications to a network entity using the power level. In some examples, the techniques in the first aspect may be implemented in a method or process. In some other examples, the techniques of the first aspect may be implemented in a wireless communication device (such as a UE, which may include a UE or a component of a UE). In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, a modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, which, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally or alternatively, the wireless communication device may include an interface (eg, a wireless communication interface) including a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.

[0162] In a second aspect, in combination with the first aspect, the uplink communication comprises grant-free uplink communication.

[0163] In a third aspect, in combination with the first aspect or the second aspect, the parameter value is a power level selected from a plurality of power target levels.

[0164] In a fourth aspect, in combination with one or more of the first to third aspects, the techniques further include: receiving a configuration including or indicating a plurality of power target levels from a network entity.

[0165] In a fifth aspect, in combination with the fourth aspect, these techniques further include: receiving a SIB or RRC including the configuration from a network entity.

[0166] In a sixth aspect, in combination with the first aspect, the uplink communication includes a first message (Msg-A) of a 2-step RACH.

[0167] In a seventh aspect, in combination with the first aspect, the techniques further include receiving mapping data mapping a PRACH preamble to a plurality of power target levels.

[0168] In an eighth aspect, in combination with the seventh aspect, the parameter value is a PRACH preamble code.

[0169] In a ninth aspect, in combination with the eighth aspect, a technique for randomly selecting a parameter value includes randomly selecting a PRACH preamble code from a group of multiple PRACH preamble codes.

[0170] In a tenth aspect, in combination with the ninth aspect, the techniques further include determining a power level based on the PRACH preamble and based on the mapping data.

[0171] In an eleventh aspect, in combination with the tenth aspect, the PRACH preamble code corresponds to a PRACH sequence index value.

[0172] In a twelfth aspect, in combination with the eleventh aspect, the uplink communication includes or indicates a PRACH sequence index value.

[0173] In a thirteenth aspect, in combination with the first aspect, the plurality of power target levels are associated with an enumerated list of the plurality of power target levels included in or indicated by a msgA-preambleReceivedTargetPower parameter or a msgA-DeltaPreamble parameter.

[0174] In one or more aspects, techniques for supporting power allocation and resource allocation for non-orthogonal multiple access NOMA may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes or devices described elsewhere herein. In a fourteenth aspect, techniques for supporting power allocation or resource allocation for non-orthogonal multiple access NOMA may include: receiving an indicator indicating multiple resource candidates from a network entity, each of the multiple resource candidates overlapping with at least one other resource candidate of the multiple resource candidates. These techniques may also include: sending an uplink communication to a network entity based on one of the multiple resource candidates. In some examples, the techniques in the fourteenth aspect may be implemented in a method or process. In some other examples, the techniques of the first aspect may be implemented in a wireless communication device (such as a UE, which may include a UE or a component of a UE). In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, a modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, which, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally or alternatively, the wireless communication device may include an interface (e.g., a wireless communication interface) comprising a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.

[0175] In a fifteenth aspect, in combination with the fourteenth aspect, the uplink communication includes grant-free uplink communication.

[0176] In the sixteenth aspect, in combination with the fourteenth aspect or the fifteenth aspect, the multiple resource candidates include multiple frequency domain resource candidates or multiple time domain resource candidates.

[0177] In a seventeenth aspect, in combination with one or more of the fourteenth to sixteenth aspects, each resource candidate of the plurality of resource candidates overlaps with each other resource candidate of the plurality of resource candidates.

[0178] In an eighteenth aspect, in combination with one or more of the fourteenth to seventeenth aspects, these technologies also include: selecting a resource candidate from a plurality of resource candidates based on a DMRS port of the UE or based on a PRACH preamble code.

[0179] In a nineteenth aspect, in combination with the eighteenth aspect, the uplink communication indicates a DMRS port or a PRACH preamble code.

[0180] In a twentieth aspect, in combination with the fourteenth aspect, the indicator indicating the plurality of resource candidates includes or indicates mapping data mapping the DMRS ports to the plurality of resource candidates.

[0181] In a twenty-first aspect, in combination with the twentieth aspect, the indicator indicating the plurality of resource candidates includes or indicates mapping data mapping the PRACH preamble code to the plurality of resource candidates.

[0182] In a twenty-second aspect, in combination with the twenty-first aspect, an indicator indicating a plurality of resource candidates is associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyDomainAllocation parameter or a timeDomainAllocation parameter.

[0183] In a twenty-third aspect, in combination with the twenty-second aspect, an indicator indicating a plurality of resource candidates is associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyStartMsgA-PUSCH parameter or a msgA-PUSCH-TimeDomainAllocation parameter.

[0184] It should be understood by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0185] In this article Figures 1 to 12 The components, functional blocks and modules described include processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software codes, firmware codes, etc. or any combination thereof. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language or other terms. In addition, the features discussed herein may be implemented via dedicated processor circuits, via executable instructions, or a combination thereof.

[0186] The technician will further understand that the various exemplary logic boxes, modules, circuits and algorithm steps described in conjunction with the disclosure of this article can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. The technician can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing departure from the scope of the present disclosure. The technician will also easily recognize that the order or combination of components, methods or interactions described herein are only examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner other than the manner illustrated and described herein.

[0187] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and exemplified in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0188] The hardware and data processing apparatus for implementing the various exemplary logics, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. In some specific implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some specific implementations, specific processes and methods may be performed by circuits specific to a given function.

[0189] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a computer storage medium for execution by a data processing device or for controlling the operation of a data processing device.

[0190] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any medium that can be implemented to transfer a computer program from one place to another. The storage medium may be any available medium that a computer can access. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0191] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to some other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0192] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions on a properly oriented page corresponding to the orientation of the drawing, and may not reflect the proper orientation of any device as implemented.

[0193] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, either individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to subcombinations or variations of subcombinations.

[0194] Similarly, although the operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all the illustrated operations to achieve the desired result. In addition, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations that are not depicted can be combined in the schematically illustrated example process. For example, one or more additional operations can be performed before, after, simultaneously or between any illustrated operations. In some environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the specific implementation described above should not be understood as requiring such separation in all specific implementations, and it should be understood that the program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other specific implementations also fall within the scope of the appended claims. In some cases, the actions narrated in the claims can be performed in different orders and still achieve the desired result.

[0195] As used herein, including in the claims, the term "or" used in a list of two or more items means that any one of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as containing components A, B, or C, the composition may contain A alone; B alone; C alone; A and B combined; A and C combined; B and C combined; or A, B, and C combined. In addition, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these. The term "substantially" is defined as to be largely, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed implementation, the term "substantially" may be replaced with "within [percent] of" a specified content, where the percentage includes 0.1%, 1%, 5%, or 10%.

[0196] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the 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 spirit or scope of the disclosure.

[0197] Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of wireless communication performed by a user equipment (UE), the method comprising: randomly selecting a parameter value associated with a power level from among a plurality of power target levels; as well as An uplink communication is sent to a network entity using the power level.

2. The method of claim 1, wherein the uplink communication comprises a grant-free uplink communication. The method of claim 1 , wherein the parameter value is the power level selected from the plurality of power target levels.

4. The method according to claim 1, further comprising: A configuration including or indicating the plurality of power target levels is received from the network entity.

5. The method according to claim 4, further comprising: A system information block (SIB) or a radio resource control (RRC) including the configuration is received from the network entity.

6. The method of claim 1, wherein the uplink communication comprises a first message (Msg-A) of a 2-step random access channel (RACH).

7. The method according to claim 1, further comprising: receiving mapping data mapping a physical random access channel (PRACH) preamble to the plurality of power target levels; and wherein the parameter value is the PRACH preamble, and The randomly selecting the parameter value comprises randomly selecting the PRACH preamble code from a group of multiple PRACH preamble codes.

8. The method according to claim 7, further comprising: determining the power level based on the PRACH preamble and based on the mapping data; and Wherein the PRACH preamble corresponds to a PRACH sequence index value, and wherein the uplink communication includes or indicates the PRACH sequence index value.

9. The method of claim 1, wherein the plurality of power target levels are associated with an enumerated list of the plurality of power target levels included in or indicated by a msgA-preambleReceivedTargetPower parameter or a msgA-DeltaPreamble parameter.

10. A user equipment (UE), the user equipment (UE) comprising: a memory storing processor readable code; and at least one processor coupled to the memory, the at least one processor being configured to execute the processor readable code so that the at least one processor: randomly selecting a parameter value associated with a power level in a plurality of power target levels; and Transmission of an uplink communication is initiated to a network entity using the power level.

11. The UE according to claim 10, wherein: The uplink communications include grant-free uplink communications; and The parameter value is the power level selected from the plurality of power target levels.

12. The UE of claim 10, wherein the at least one processor is further configured to execute the processor readable code to cause the at least one processor to receive a configuration including or indicating the plurality of power target levels from the network entity.

13. The UE of claim 10, wherein the uplink communication comprises a first message (Msg-A) of a 2-step random access channel (RACH).

14. The UE of claim 10, wherein the at least one processor is further configured to execute the processor readable code to cause the at least one processor to: receiving mapping data that maps a physical random access channel (PRACH) preamble to the plurality of power target levels; and The parameter value is a PRACH preamble code.

15. The UE of claim 14, wherein the at least one processor is further configured to execute the processor readable code to cause the at least one processor to: determining the power level based on the PRACH preamble and based on the mapping data; and Wherein the PRACH preamble corresponds to a PRACH sequence index value, and wherein the uplink communication includes or indicates the PRACH sequence index value.

16. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving, from a network entity, an indicator indicating a plurality of resource candidates, each resource candidate of the plurality of resource candidates overlapping with at least one other resource candidate of the plurality of resource candidates; as well as An uplink communication is sent to the network entity based on a resource candidate from the plurality of resource candidates.

17. The method of claim 16, wherein the uplink communication comprises a grant-free uplink communication.

18. The method according to claim 16, wherein the plurality of resource candidates comprises a plurality of frequency domain resource candidates or a plurality of time domain resource candidates.

19. The method of claim 16, wherein each resource candidate of the plurality of resource candidates overlaps with each other resource candidate of the plurality of resource candidates.

20. The method according to claim 16, further comprising: selecting the resource candidate from the plurality of resource candidates based on a demodulation reference signal (DMRS) port of the UE or based on a physical random access channel (PRACH) preamble; and The uplink communication indicates the DMRS port or the PRACH preamble code.

21. The method of claim 16, wherein the indicator indicating the plurality of resource candidates includes or indicates mapping data mapping a demodulation reference signal (DMRS) port to the plurality of resource candidates.

22. The method of claim 16, wherein the indicator indicating the plurality of resource candidates includes or indicates mapping data mapping a physical random access channel (PRACH) preamble to the plurality of resource candidates.

23. The method of claim 16, wherein the indicator indicating the plurality of resource candidates is associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyDomainAllocation parameter or a timeDomainAllocation parameter.

24. The method of claim 16, wherein the indicator indicating the plurality of resource candidates is associated with an enumerated list of the plurality of resource candidates included in or indicated by a frequencyStartMsgA-P USCH parameter or a msgA-P USCH-TimeDomainAllocation parameter.

25. A user equipment (UE), the user equipment (UE) comprising: a memory storing processor readable code; and at least one processor coupled to the memory, the at least one processor being configured to execute the processor readable code so that the at least one processor: receiving, from a network entity, an indicator indicating a plurality of resource candidates, each resource candidate of the plurality of resource candidates overlapping with at least one other resource candidate of the plurality of resource candidates; as well as An uplink communication is sent to the network entity based on a resource candidate from the plurality of resource candidates.

26. The UE of claim 25, wherein the uplink communication comprises a grant-free uplink communication.

27. The UE according to claim 25, wherein: The multiple resource candidates include multiple frequency domain resource candidates or multiple time domain resource candidates; each resource candidate in the multiple resource candidates overlaps with each other resource candidate in the multiple resource candidates; or A combination of them.

28. The UE of claim 25, wherein the at least one processor is further configured to execute the processor readable code to cause the at least one processor to: selecting the resource candidate from the plurality of resource candidates based on a demodulation reference signal (DMRS) port of the UE or based on a physical random access channel (PRACH) preamble; and The uplink communication indicates the DMRS port or the PRACH preamble code.

29. The UE of claim 25, wherein the indicator indicating the plurality of resource candidates includes or indicates mapping data mapping a demodulation reference signal (DMRS) port to the plurality of resource candidates.

30. The UE of claim 25, wherein the indicator indicating the plurality of resource candidates includes or indicates mapping data mapping a physical random access channel (PRACH) preamble to the plurality of resource candidates.

Images