Demodulation reference signal parameter selection for grant-free user equipment uplink transmission

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different transmit parameter values. The UE may select a resource from the plurality of resources in the resource pool. The UE may select a DMRS parameter set based on at least one transmit parameter value associated with a physical uplink shared channel (PUSCH) message. The UE may select a DMRS parameter from the selected DMRS parameter set. The UE may transmit a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter. Numerous other aspects are described.

Description

DEMODULATION REFERENCE SIGNAL PARAMETER SELECTION FOR GRANT- FREE USER EQUIPMENT UPLINK TRANSMISSIONCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to U.S. Patent Application No. 18 / 896,048, filed on September 25, 2024, entitled “DEMODULATION REFERENCE SIGNAL PARAMETER SELECTION FOR GRANT-FREE USER EQUIPMENT UPLINK TRANSMISSION,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for demodulation reference signal parameter selection for grant-free user equipment uplink transmission.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and / or other traffic. The services may include unicast, multicast, and / or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and / or device transmit power, among other examples). Examples of such multiple-access RATs include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single -carrier frequency division multiple access (SC- FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR). NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3 GPP). NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (loT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-0097-5700PCT 1device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication), massive multiple -input multiple -output (MIMO), disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high- precision positioning, and / or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution.SUMMARY

[0005] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The one or more processors may be configured to select a resource from the plurality of resources in the resource pool. The one or more processors may be configured to select a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a physical uplink shared channel (PUSCH) message. The one or more processors may be configured to select a DMRS parameter from the selected DMRS parameter set. The one or more processors may be configured to transmit, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

[0006] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to transmit, to a UE, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The one or more processors may be configured to receive, from the UE, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

[0007] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool,0097-5700PCT 2wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The method may include selecting a resource from the plurality of resources in the resource pool. The method may include selecting a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message. The method may include selecting a DMRS parameter from the selected DMRS parameter set. The method may include transmitting, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, to a UE, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The method may include receiving, from the UE, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The set of instructions, when executed by one or more processors of the UE, may cause the UE to select a resource from the plurality of resources in the resource pool. The set of instructions, when executed by one or more processors of the UE, may cause the UE to select a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message. The set of instructions, when executed by one or more processors of the UE, may cause the UE to select a DMRS parameter from the selected DMRS parameter set. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the0097-5700PCT 3plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive, from the UE, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

[0011] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The apparatus may include means for selecting a resource from the plurality of resources in the resource pool. The apparatus may include means for selecting a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message. The apparatus may include means for selecting a DMRS parameter from the selected DMRS parameter set. The apparatus may include means for transmitting, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The apparatus may include means for receiving, from the UE, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

[0013] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and / or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings.

[0014] The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with0097-5700PCT 4associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.

[0016] Fig. 1 is a diagram illustrating an example of a wireless communication network, in accordance with the present disclosure.

[0017] Fig. 2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0018] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0019] Fig. 4 is a diagram illustrating an example of configured grant communication, in accordance with the present disclosure.

[0020] Fig. 5-6 are diagrams illustrating examples associated with demodulation reference signal parameter selection for grant-free UE uplink transmission, in accordance with the present disclosure.

[0021] Figs. 7 is a diagram illustrating an example process performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure.

[0022] Fig. 8 is a diagram illustrating an example process performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.

[0023] Figs. 9-10 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.DETAILED DESCRIPTION

[0024] Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other0097-5700PCT 5aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and / or functionalities in addition to or other than the structures and / or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0025] Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0026] In a wireless network, a network node may use dynamic scheduling to schedule physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) transmissions of a user equipment (UE). For example, the network node may configure scheduling parameters in control signaling information (e.g., radio resource control (RRC) information and / or downlink control information (DCI)) that is provided to the UE, and the UE may receive PDSCH messages and / or transmit PUSCH messages according to the scheduling parameters. Per-UE and / or per-transmission scheduling may require the network node to transmit a large amount of control signaling, particularly when there are a high number of UEs and / or where there is heavy network traffic. However, by using UE grant-free scheduling, the network node can reduce network node signaling overhead.

[0027] For example, in a configured grant (CG) resource allocation, the UE may be configured to perform uplink (UL) transmission on a PUSCH without receiving individual resource allocations from the network node. Rather, in a CG resource allocation, the network node may configure dedicated uplink resources for the UE, or may configure a resource pool including uplink resources shared by multiple UEs. As a result, when the UE has uplink data to transmit, the UE may transmit the uplink data using the dedicated resource configured for the UE or using a resource selected from the resource pool without receiving an uplink grant. When a relatively large quantity of UEs are present on a network (e.g., a large quantity of internet of things (loT) devices), it may be necessary for the network node to transmit a relatively large quantity of control signaling information to provide UL scheduling information for the UEs.0097-5700PCT 6

[0028] Accordingly, a CG resource allocation may enable a UE to schedule the UL transmissions of the UE. For example, a network node may provide the UE with scheduling configurations and a pool of resources as part of a CG provided to the UE. The UE may select a resource from the resource pool and use the resource for scheduling an UL transmission. By enabling grant-free UL transmissions, the signaling and transmission overhead of the network node can be reduced. However, because the network node provides the grant-free scheduling configurations and the pool of resources to the UE, the network node does not enable the UE to be fully flexible in scheduling itself. For example, a network node may enable multiple overlapping CG-PUSCH configurations to support payload and MCS adaptation, and the UE may select one of the CG-PUSCH configurations on which to transmit based on, for example, a probability of whether the UE can access one of the resources in the resource pool. However, the configuration and whether over-provisioning is enabled depend on an implementation of the network node. Additionally, a configuration has limited flexibility (e.g., inability to control the probability of a UE accessing a resource in the resource pool, fixed resource pool size, and / or homogenous resource pools), such that the UE may be unable to schedule transmissions in a manner that is efficient for both the UE transmitting the PUSCH message and the network node decoding the PUSCH message.

[0029] For example, in the case of a grant-free UL transmission, once the UE has received the configuration information and the resource pool from the network node, the UE may select a resource with the proper MCS and payload size and transmit a PUSCH message to the network node using the selected resource. However, the network node performs blind channel estimation and decoding for each of the resources in the resource pool, resulting in increased processing overhead and increased power consumption. For example, where a received PUSCH message could be associated with multiple parameters, the network node may attempt to decode the PUSCH message with each possible parameter (or combination of parameters) until the network node can successfully decode the PUSCH message, resulting in a potentially high- latency and resource-intensive process. For example, in a network environment that includes a large number of UEs transmitting grant-free PUSCH messages, the network node may perform blind channel estimation and decoding for each PUSCH message according to each permutation of possible transmission parameters, resulting in increased network overhead, potentially delayed decoding of the PUSCH message, a potentially delayed response from the network node, and a potential PUSCH message decoding failure necessitating retransmissions of the PUSCH message. Additionally, different UEs operating according to a self-scheduling configuration may transmit on the same resource, resulting in collisions that may cause interference to each other and / or degrade performance. Accordingly, self-scheduled or grant- free UL transmissions based on a resource pool configuration may be suitable only for small0097-5700PCT 7scale applications (e.g., when a low number of UEs are present on the network and / or during low traffic periods on the network).

[0030] Various aspects relate generally to selecting demodulation reference signal (DMRS) parameters for grant-free UL transmissions to enable efficient detection of transmission parameters for a grant-free UL transmission and reduced complexity for decoding of the grant- free UL transmission at a network node. Some aspects more specifically relate to a UE receiving a resource pool configuration from a network node, where the resource pool is associated with multiple DMRS parameter sets that are each associated with a possible value for an uplink transmit parameter or a possible combination of values for multiple uplink transmit parameters. The UE may select an appropriate resource and an associated DMRS parameter (e.g., port / scrambling sequence) from a DMRS parameter set based on at least one transmit parameter (e.g., MCS and / or payload size), and the UE may transmit a PUSCH message in the selected resource using the selected DMRS parameter. In some aspects, the network node may detect the DMRS parameter in the PUSCH message and may decode the PUSCH message based on at least one transmit parameter associated with the detected DMRS parameter. For example, because the UE selected the transmit resource and the associated DMRS parameter based on the at least one transmit parameter, the network node is enabled to unambiguously identify the transmit parameters associated with the grant-free PUSCH message according to the resource pool configuration that was provided to the UE. In some aspects, the network node may provide an update to the resource pool configuration based on updates to network conditions (e.g., network traffic or a number of served UEs), where the updated resource pool configuration may enable the UE to adapt transmissions efficiently according to the updated network conditions. For example, where multiple UEs are in communication with a network node, the network node may provide an updated resource pool configuration to one or more UEs to enable each of the one or more UEs to adapt, for example, a resource selection and / or DMRS parameter selection according to a transmit parameter (e.g., MCS and / or payload size) that is appropriate for current network conditions.

[0031] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by enabling a UE to select a DMRS parameter for inclusion in a grant-free UL transmission to a network node, the described techniques can be used to reduce the complexity and increase the efficiency of decoding PUSCH messages at the network node. By simplifying the decoding process at the network node, the configuration may reduce network latency and conserve power, processing, and / or other resources. For example, by reducing the decoding complexity at the network node, the network node may process and potentially respond to the PUSCH message in less time, resulting in lower latency in the communications between the UE and the network node. Additionally, where a large number of UEs are in communication with a network node,0097-5700PCT 8overall latency may be reduced in communications between the network node and the UEs. Additionally, by simplifying the decoding process at the network node, the configuration may increase the probability that the network node successfully decodes PUSCH transmissions, thus reducing the probability of retransmissions.

[0032] Multiple -access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, loT connectivity and management, and network function virtualization (NFV).

[0033] As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, nonterrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, loT (including passive or ambient loT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, and / or artificial intelligence or machine learning (AI / ML), among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and / or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0034] Fig. 1 is a diagram illustrating an example of a wireless communication network 100, in accordance with the present disclosure. The wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a0097-5700PCT 9network node (NN) 110a, a network node 110b, a network node 110c, and a network node 1 lOd. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e.

[0035] The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and / or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless communication networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular RAT (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G / NR RAT, and / or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another.

[0036] Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHz), FR2 (24.25 GHz through 52.6 GHz), FR3 (7.125 GHz through 24.25 GHz), FR4a or FR4-1 (52.6 GHz through 71 GHz), FR4 (52.6 GHz through 114.25 GHz), and FR5 (114.25 GHz through 300 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz), which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz,” if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and / or that are included in mid -band frequencies. Similarly, the term “millimeter wave,” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-a or FR4- 1, or FR5, and / or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and / or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS), in which multiple RATs (for example, 4G / Long Term Evolution (LTE) and 5G / NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example,0097-5700PCT 10FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges.

[0037] A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP), a transmission reception point (TRP), a mobility element, a core, a network entity, a network element, a network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0038] A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures). For example, a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack), or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture), meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.

[0039] Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 may implement a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance), or in a virtualized radio access network (vRAN), also known as a cloud radio access network (C-RAN), to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.

[0040] The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). A CU may host one or more higher layer control functions, such as RRC functions, packet data convergence protocol (PDCP) functions, and / or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control0097-5700PCT 11(RLC) layer, a medium access control (MAC) layer, and / or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT), an inverse FFT (iFFT), beamforming, physical random access channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120.

[0041] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally, or alternatively, a network node 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and / or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and / or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment.

[0042] Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or an NTN network node).0097-5700PCT 12

[0043] The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and / or disaggregated network nodes, among other examples. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c.Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and / or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts), whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts).

[0044] In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link). The radio access link may include a downlink and an uplink. “Downlink” (or “DL”) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL”) refers to a communication direction from a UE 120 to a network node 110. Downlink channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit DCI (for example, scheduling information, reference signals, and / or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCHs), and downlink data channels may include one or more PDSCHs. Uplink channels may similarly include one or more control channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and / or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more physical uplink control channels (PUCCHs), and uplink data channels may include one or more PUSCHs. The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.

[0045] Downlink and uplink resources may include time domain resources (frames, subframes, slots, and / or symbols), frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial domain resources (particular transmit directions and / or beam parameters). Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs). A BWP may be a continuous block of0097-5700PCT 13frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs). A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and / or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor), leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.

[0046] As described above, in some aspects, the wireless communication network 100 may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or “lAB-donor”). The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally, or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). An IAB network also generally includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply as IAB nodes (or “lAB-nodes”). Each nonanchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and / or spatial resources) may be shared between access links and backhaul links.

[0047] In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110). In this case, the wireless communication network 100 may0097-5700PCT 14include or be referred to as a “multi-hop network.” In the example shown in Fig. 1, the network node 1 lOd (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally, or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.

[0048] The UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and / or smart jewelry, such as a smart ring or a smart bracelet), an entertainment device (for example, a music device, a video device, and / or a satellite radio), an XR device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that may communicate via a wireless medium.

[0049] A UE 120 and / or a network node 110 may include one or more chips, system -on- chips (SoCs), chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry”). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions.0097-5700PCT 15

[0050] The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-access memory (RAM) or read-only memory (ROM), or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry”). One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally, or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, Institute of Electrical and Electronics Engineers (IEEE) compliant) modem or a cellular (for example, 3 GPP 4G LTE, 5G, or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.

[0051] Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC), UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as “MTC UEs”. An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and / or a location tag. Some UEs 120 may be considered loT devices and / or may be implemented as NB-IoT (narrowband loT) devices. An loT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and / or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100).0097-5700PCT 16

[0052] Some UEs 120 may be classified according to different categories in association with different complexities and / or different capabilities. UEs 120 in a first category may facilitate massive loT in the wireless communication network 100, and may offer low complexity and / or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical loT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, fullcapability UEs, and / or premium UEs that are capable of URLLC, eMBB, and / or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and / or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability). A UE 120 of the third category may be referred to as a reduced capacity UE (“RedCap UE”), a mid-tier UE, an NR-Light UE, and / or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and / or eMTC UEs, and mission- critical loT devices and / or premium UEs. RedCap UEs may include, for example, wearable devices, loT devices, industrial sensors, and / or cameras that are associated with a limited bandwidth, power capacity, and / or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and / or smart city deployments, among other examples.

[0053] In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary). As an example, the UE 120a may directly transmit data, control information, or other signaling as a side link communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication. In various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to- device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and / or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and / or other operations for sidelink communications.

[0054] In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full -duplex operation in addition to halfduplex operation. A network node 110 or a UE 120 operating in a half-duplex mode may0097-5700PCT 17perform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods. Half-duplex operation may involve timedivision duplexing (TDD), in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time). In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources). By operating in a full-duplex mode, network nodes 110 and / or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full- duplex operation may involve frequency-division duplexing (FDD), in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120.

[0055] In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. “MIMO” generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO). Some RATs may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time domain or the frequency domain, single -frequency-network (SFN) transmission, or non -coherent joint transmission (NC-JT).

[0056] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive, from a network node 110, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; select a resource from the plurality of resources in the resource pool; select a DMRS parameter set from the plurality of DMRS0097-5700PCT 18parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message; select a DMRS parameter from the selected DMRS parameter set; and transmit, to the network node 110, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit, to a UE 120, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; and receive, from the UE 120, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0058] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

[0059] Fig. 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network, in accordance with the present disclosure.

[0060] As shown in Fig. 2, the network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t > 1), a set of antennas 234 (shown as 234a through 234v, where v > 1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and / or the TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller / processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and / or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and / or other components that facilitate communication with the UE 120 or another network node.

[0061] The terms “processor,” “controller,” or “controller / processor” may refer to one or more controllers and / or one or more processors. For example, reference to “a / the processor,” “a / the controller / processor,” or the like (in the singular) should be understood to refer to any one0097-5700PCT 19or more of the processors described in connection with Fig. 2, such as a single processor or a combination of multiple different processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig. 2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0062] In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig. 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

[0063] For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data (“downlink data”) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue). In some examples, the transmit processor 214 may select one or more MCSs for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS(s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI)) and / or control information (for example, CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and / or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS), a DMRS, or a channel state information (CSI) reference signal (CSI-RS)) and / or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS)).

[0064] The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be0097-5700PCT 20provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.

[0065] A downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and / or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and / or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and / or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.

[0066] For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232), may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and / or may be further processed by the receive processor 238 to obtain decoded data and / or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and / or another type of data sink) and provide the decoded control information to a processor, such as the controller / processor 240.

[0067] The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and / or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and / or frequency domain resources that the UE 120 may use to transmit and / or receive0097-5700PCT 21communications using an RRC configuration (for example, a semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure a CG for the UE 120.

[0068] One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and / or the controller / processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110). In some aspects, the RF chain may be or may be included in a transceiver of the network node 110.

[0069] In some examples, the network node 110 may use the communication unit 244 to communicate with a core network and / or with other network nodes. The communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, optical fiber, common public radio interface (CPRI), and / or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and / or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and / or an interface, such as a network interface.

[0070] The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r > 1), a set of modems 254 (shown as modems 254a through 254u, where u > I), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller / processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and / or another component that facilitates communication with the network node 110 and / or another UE 120.

[0071] For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the0097-5700PCT 22respective demodulator component to condition (for example, fdter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and / or an application executed on the UE 120), and may provide decoded control information and system information to the controller / processor 280.

[0072] For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data (“uplink data”) from a data source 262 (such as a data pipeline, a data queue, and / or an application executed on the UE 120) and control information from the controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receive processor 258 and / or the controller / processor 280 may determine, for a received signal (such as received from the network node 110 or another UE), one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RS SI) parameter, a reference signal received quality (RSRQ) parameter, a CQI parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and / or another parameter. The control information may facilitate parameter selection and / or scheduling for the UE 120 by the network node 110.

[0073] The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS), and / or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM). The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator0097-5700PCT 23component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0074] The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and / or another type of uplink channel. An uplink signal may carry one or more TBs of data. Sidelink data and control transmissions (that is, transmissions directly between two or more UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0075] One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Fig. 2. As used herein, “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. “Antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. “Antenna module” may refer to circuitry including one or more antennas, which may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0076] In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam). For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength,0097-5700PCT 24or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range.

[0077] The amplitudes and / or phases of signals transmitted via antenna elements and / or subelements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and / or amplitude) to generate one or more beams, which is referred to as beamforming. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. “Beam” may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and / or a vertical direction), and / or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and / or a set of directional resources associated with the signal. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and / or phases of the signal(s) to form one or more beams. The shape of a beam (such as the amplitude, width, and / or presence of side lobes) and / or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of the multiple signals relative to each other.

[0078] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements. Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing.

[0079] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.0097-5700PCT 25

[0080] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such one or more network nodes 110). The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or that can communicate indirectly with the core network 320 via one or more disaggregated control units, such as a Non-RT RIC 350 associated with a Service Management and Orchestration (SMO) Framework 360 and / or a Near-RT RIC 370 (for example, via an E2 link). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via Fl interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs 340.

[0081] Each of the components of the disaggregated base station architecture 300, including the CUs 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.

[0082] In some aspects, the CU 310 may be logically split into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 may be controlled by the corresponding DU 330.

[0083] The SMO Framework 360 may support RAN deployment and provisioning of nonvirtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an 01 interface. For virtualized network elements, the SMO Framework 360 may interact with a0097-5700PCT 26cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an 02 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and / or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and / or a 6G RAN, such as an open eNB (O- eNB) 380, via an 01 interface. Additionally, or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective 01 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0084] The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, AI / MU workflows including model training and updates, and / or policy-based guidance of applications and / or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an Al interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, and / or an O-eNB with the Near-RT RIC 370.

[0085] In some aspects, to generate AI / MU models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI / MU models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).

[0086] The network node 110, the controller / processor 240 of the network node 110, the UE 120, the controller / processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other componcnt(s) of Figs. 1, 2, or 3 may implement one or more techniques or perform one or more operations associated with DMRS parameter selection for grant-free UL transmission, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, any other component(s) of Fig.2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 700 of Fig. 7, process 800 of Fig. 8, or other processes as described herein (alone or in conjunction with one or more other processors). The memory 242 may store data and program0097-5700PCT 27codes for the network node 110, the network node 110, the CU 310, the DU 330, or the RU 340. The memory 282 may store data and program codes for the UE 120. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing a set of instructions (for example, code or program code) for wireless communication. The memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). The memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). For example, the set of instructions, when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110, the UE 120, the CU 310, the DU 330, or the RU 340, may cause the one or more processors to perform process 700 of Fig. 7, process 800 of Fig. 8 or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0087] In some aspects, the UE 120 includes means for receiving, from a network node 110, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; means for selecting a resource from the plurality of resources in the resource pool; means for selecting a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message; means for selecting a DMRS parameter from the selected DMRS parameter set; and / or means for transmitting, to the network node 110, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0088] In some aspects, the network node 110 includes means for transmitting, to a UE 120, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; and / or means for receiving, from the UE 120, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter. The means for the network node 110 to perform operations described herein may include, for example, one or more of communication manager0097-5700PCT 28150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0089] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0090] Fig. 4 is a diagram illustrating an example 400 of CG communication, in accordance with the present disclosure. As shown, example 400 includes a network node 110 and a UE 120.

[0091] As shown in Fig. 4, and by reference number 405, the network node 110 may transmit a CG configuration to the UE 120. For example, the network node 110 may transmit configuration information (e.g., in an RRC message, in a DCI message, and / or in another signaling message) that identifies the CG. In some aspects, the configuration information identifying the CG may indicate a resource allocation (e.g., in a time domain, frequency domain, spatial domain, and / or code domain) and / or a periodicity associated with the resource allocation. The CG may identify a resource or set of resources available to the UE 120 for transmission of an uplink communication (e.g., data and / or control information). For example, the CG configuration may identify a resource allocation for a PUSCH. In some aspects, the CG configuration may identify a resource pool or multiple resource pools that may be available to the UE 120 for an uplink transmission.

[0092] In some aspects, the CG configuration may configure contention-free CG communication with resources dedicated for the UE 120 to transmit uplink communications. In this case, the CG configuration may indicate a resource allocation (e.g., in a time domain, frequency domain, spatial domain, and / or code domain) dedicated for the UE 120 to use to transmit uplink communications. In some aspects, the CG configuration may configure the resource allocation for the UE 120 to occur periodically, such that the resource allocation corresponds to periodically occurring transmission time occasions. As shown in Fig. 4, and by reference number 410, when the UE 120 has uplink data to transmit, the UE 120 transmits the uplink data in the CG resources identified by the CG configuration. For example, the UE 120 transmits the uplink data in one of the CG uplink occasions identified in the CG configuration using the configured resource allocation.

[0093] A CG configuration with regular periodic CG uplink occasions with a dedicated resource allocation for the UE 120 may be convenient for a UE 120 with periodic uplink traffic (e.g., with trivial jitter). The CG configuration may configure the periodicity associated with the resource allocation to associate CG uplink occasions with periodic nominal arrival times at which traffic to be transmitted to the network node 110 is expected to arrive at (or be ready to be transmitted by) the UE 120. However, the actual arrival times at which the traffic arrives (or is ready to be transmitted) by the UE 120 may be different than the nominal arrival times, and0097-5700PCT 29this difference in times is known as jitter. In some aspects, traffic jittering may be handled by configuring multiple CGs around the nominal arrival times. In some aspects, multiple opportunities for the UE 120 to transmit the uplink communication may be defined within a CG uplink occasion. The UE 120 may be configured with multiple CG uplinks to allow the UE 120 to repeatedly transmit the CG uplink communications and increase the likelihood that the network node 110 receives the communications. In some cases, CG uplink communication may depend on dynamic grant re-transmission. In some aspects, to suppress a quantity of dynamic grants, the CG can be configured with blind re-transmissions via multiple repetitions per occasion.

[0094] In some cases, CG configurations with dedicated resources allocated per UE 120 may be inefficient. For example, CG configurations with dedicated UE 120 resources for a large number of UEs 120 may result in consumption of an excessive amount of PUSCH resources. In this case, a considerable portion of the PUSCH resources may be inefficiently utilized, which reduces system capacity. For example, when multiple CG configurations for a UE 120 are used for de-jittering, only a subset of CG resources may be effectively utilized. In another example, when multiple transmission opportunities are defined per CG uplink occasion, only one opportunity may be effectively utilized. In yet another example, when a blind repetition scheme is used for re-transmissions, a packet may have been already decoded after the first one or more repetitions (early decoding) such that a remainder of the repetitions are unnecessary. Unlike downlink communication, this type of inefficient consumption of system resources cannot be addressed by scheduling, as the network node 110 does not know exactly when traffic will arrive at the UEs 120.

[0095] In some aspects, statistical multiplexing schemes may be used to allocate CG uplink resource access among multiple UEs 120. Statistical multiplexing of CG uplink communications from multiple UEs 120 may be useful in cases in which there are a high number of UEs 120 associated with somewhat random traffic arrivals at the network node and / or cases in which a traffic arrival density for traffic arriving at the UEs 120 is time varying. For example, statistical multiplexing of CG uplink communications from multiple UEs 120 may be useful for a network deployment, such as an industrial wireless sensor network, with a large capacity of UEs 120. In such cases, the uplink traffic associated with at least a group of UEs 120 may be delay insensitive.

[0096] As shown in Fig. 4, the CG configuration may configure contention-based CG communication with resource pools that are available for multiple UEs 120 to use to transmit uplink communications. The contention-based CG configuration uses statistical multiplexing to share the resource pools among multiple UEs 120. A resource pool includes multiple resources (e.g., in a time domain, frequency domain, spatial domain, and / or code domain) that can be allocated for uplink transmission for one or more UEs 120. For example, an x-axis of an0097-5700PCT 30illustrated resource pool may indicate transmission times and a y-axis of the illustrated resource pool may indicate resources (e.g., frequency domain, spatial domain, and / or code domain) that can be allocated at each transmission time. In some aspects, the same resource pools may be configured for multiple UEs 120.

[0097] As further shown in Fig. 4, and by reference number 415, for the contention -based CG configuration, when the UE 120 has uplink data to be transmitted, the UE 120 performs an admission control procedure and selects one or more resources from the resource pool if the admission control procedure is successful. In some aspects, the admission control procedure may include the UE 120 selecting a random number (e.g., between 0 and 1 or some other range), comparing the random number and a threshold, and determining whether the random number satisfies the threshold. If the random number satisfies the threshold, then the admission is successful and the UE 120 selects a resource from the resource pool to transmit the uplink communication.

[0098] In some aspects, the network node 110 may control the probability of the UE 120 accessing the resource pool by setting and / or adjusting the threshold. For example, the network node 110 may dynamically adjust the threshold to permit more or fewer UEs 120 to access the resource pool in order to prevent resource collisions. Additionally, or alternatively, the network node 110 may assign different thresholds to be used by different UEs 120.

[0099] Based at least in part on the UE 120 determining that the random number satisfies the threshold, the UE 120 may select a resource from the resource pool to transmit the uplink communication. The UE 120 may select the resource from the resource pool using randomized and / or pseudo-randomized resource selection. For example, the UE 120 may use a hashing function based at least in part on a UE 120 identifier, time, and / or resource pool index to select the resource from the resource pool. In some aspects, the network node 110 may adjust the size of the resource pool rather than controlling the probability of the UE 120 accessing the resource pool. In some aspects, the network node 110 may support heterogenous resource pools, which support an extra dimension of flexibility in selecting the resources.

[0100] As further shown in Fig. 4, and by reference number 420, the UE 120 transmits the uplink communication to the network node 110 on the CG resource. For example, the UE 120 may transmit the uplink communication as a PUSCH communication using a resource allocation identified by the CG.

[0101] Accordingly, a CG resource allocation may enable a UE to self-schedule UL transmissions (e.g., grant-free UL transmissions). By enabling grant-free UL transmissions, the signaling and transmission overhead of the network node can be reduced. Furthermore, when the network node provides the grant-free scheduling configurations and the pool of resources to the UE, the network node enables the UE to schedule certain UL transmit parameters. For0097-5700PCT 31example, in the case of a grant-free UL transmission, once the UE has received the configuration information and the resource pool from the network node, the UE may select transmit parameters such as an MCS and payload size, select a resource with the proper MCS and payload size, and transmit a PUSCH message to the network node using the selected resource. However, because the network node is unaware of the transmit parameters selected by the UE, the network node performs blind channel estimation and decoding for each of the resources in the resource pool, resulting in increased processing overhead and increased power consumption. Accordingly, self-scheduling or grant-free UL transmissions based on a resource pool configuration is generally suitable for only small scale applications (e.g., when a low number of UEs are present on the network and / or where low network traffic is present).

[0102] As described more fully in Figs. 5-6, by providing a resource pool configuration to the UE, the UE may be enabled select a transmission resource and associated DMRS parameters for grant-free UL transmissions, the network node may detect transmission parameters for and decode a grant-free UL transmission in a more efficient manner and with reduced complexity. For example, where the UE selects a transmission resource and an associated DMRS parameter based on at least one transmit parameter, the network node, upon receiving a grant-free transmission from the UE, is enabled to unambiguously identify the at least one transmit parameter according to the resource pool configuration that was provided to the UE. In some aspects, the network node may provide an update to the resource pool configuration based on updates to network conditions (e.g., network traffic or a number of served UEs), where the updated resource pool configuration may enable the UE to adapt transmissions efficiently according to the updated network conditions. For example, where multiple UEs are in communication with a network node, the network node may provide an updated resource pool configuration to one or more UEs to enable each of the one or more UEs to adapt, for example, a resource selection and / or DMRS parameter selection according to a transmit parameter (e.g., MCS and / or payload size) that is appropriate for current network conditions.

[0103] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.

[0104] Fig. 5 is a diagram illustrating an example 500 associated with DMRS parameter selection for grant-free UL transmission, in accordance with the present disclosure.

[0105] As described herein, multiple UEs may select a resource from the resource pool (e.g., randomly or based on the resource being suitable for a given set of one or more transmit parameters) and the UEs may each select a DMRS parameter (e.g., a port / scrambling sequence) from a DMRS parameter set associated with the selected resource and based on one or more transmit parameters such as an MCS and / or a payload size. In some aspects, each resource in the resource pool is associated with multiple DMRS parameter sets, and each DMRS parameter set is associated with a given value for a transmit parameter (e.g., set 1 for MCS X 540, set 1 for0097-5700PCT 32MCS Y 545, and so on) or a combination of values for multiple transmit parameters (e.g., set 1 for MCS X and payload size TB1, set 2 for MCS Y and payload size TB1, set 2 for MCS Y and payload size TB2, and so on). Additionally, each UE may transmit a grant-free PUSCH message in the selected resource, where the grant-free PUSCH message includes a selected DMRS parameter 510 and a payload 520. In some aspects, the DMRS parameter selection may be independent of the UE (e.g., the DMRS choice is not a function of a UE identifier), and is instead dependent on the transmit parameter(s) for a grant-free UL transmission.

[0106] Additionally, in some aspects, where the UE is transmitting in multiple resources, the UE may select different DMRS parameters (e.g., port / scrambling sequences) for different resources. For example, as shown in Fig. 5, a resource pool 505 includes resources selected by three UEs, denoted UE1 520, UE2 525, and UE3 530, where UE1 520 and UE2 525 are each transmitting in two resources and UE3 530 is transmitting in one resource. In each selected resource, the UE performs a grant-free UL transmission that includes a DMRS 510 and a payload 520. The DMRS 510 transmitted by the UE is associated with a DMRS parameter 535 (e.g., a port / scrambling sequence) in a DMRS parameter set associated with the resource selected for the grant-free UL transmission. As a result, the network node may be enabled to unambiguously identify the transmit parameters associated with the grant-free UL transmission that is received from a UE, because the selected DMRS parameter indicates the UL transmit parameters to the network node. The network node may then detect the DMRS parameter (e.g., a port / scrambling sequence) associated with the grant-free UL transmission, identify the DMRS set to which the DMRS parameter belongs, and identify the UL transmit parameters associated with the identified DMRS set.

[0107] In some aspects, the network node may configure a resource pool with different DMRS parameter sets (e.g., DMRS ports / scrambling sequence sets) for each resource in the resource pool, and the network node may transmit the resource pool configuration to a UE. In some aspects, for each resource in the resource pool, the network node may indicate different transmit parameter options (e.g., MCS options) for the UE to select and a set of DMRS parameters 535 (e.g., DMRS ports / scrambling sequences) for each transmit parameter. In some aspects, for each resource in the resource pool, the network node may indicate different payload size options for the UE to select and a set of DMRS parameters 535 (e.g., DMRS ports / scrambling sequences) for each payload size option. In some aspects, the network node may indicate different MCS options and different payload size options for the UE to select and a set of DMRS parameters for each MCS option, each payload size option, and / or each combination of an MCS option and a payload size option. In some aspects, each set of DMRS parameters includes one or more DMRS parameters (e.g., DMRS ports and / or DMRS scrambling sequences).0097-5700PCT 33

[0108] In some aspects, a network node may configure a resource pool 505 including various resources 515 that are each associated with multiple DMRS parameter sets, where the DMRS parameters 510 in each DMRS parameter set may be associated with values for one or more transmit parameters. For example, the network node may configure a first DMRS parameter set 540 for MCS X and a second DMRS parameter set 545 for MCS Y. Additionally, the network node may configure a resource pool with a first DMRS parameter set 550 for a payload size TB 1 and a second DMRS parameter set 560 for a payload size TB2. Each DMRS parameter set may include one or more DMRS parameters 510 associated with the DMRS parameter set, which in turn, are associated with a resource 515 in the resource pool 505. By configuring different DMRS parameter sets for different MCS values, payload sizes, or other transmit parameters, the UE may select the DMRS parameter 510 that is associated with a selected resource, where the network node may then detect the different DMRS parameters 510 for a resource based on a certain metric. For example, the network node may map a detected DMRS port / scrambling sequence to an MCS value and / or a payload size and may proceed with decoding the grant-free PUSCH message based on the mapping. In some aspects, the resource pool configuration may include a cyclic redundancy code (CRC) associated with each resource, where the network node may perform a CRC pass on a received grant-free PUSCH message as an additional technique to unambiguously identify a transmission.

[0109] In some aspects, the network node may update one or more sets of DMRS parameters 510 for a given MCS and / or payload size based on a network condition (e.g., incoming traffic to the network node), and the network node may indicate the update to one or more UEs through a group common physical downlink control channel (GC-PDCCH). For example, where multiple UEs are in communication with a network node, the network node may provide an updated resource pool configuration to one or more UEs to enable the UE to adapt, for example, its resource selection and / or DMRS parameter selection according to a transmit parameter (e.g., MCS and / or payload size) that is appropriate for network conditions.

[0110] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

[0111] Fig. 6 is a diagram illustrating an example 600 associated with DMRS parameter selection for grant-free UE UL transmission, in accordance with the present disclosure. As shown in Fig. 6, example 600 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0112] As shown by reference number 605, the network node 110 may transmit, and the UE 120 may receive, a resource pool configuration for a resource pool that includes multiple0097-5700PCT 34resources. Additionally, the resource pool configuration may indicate multiple DMRS parameter sets associated with each of the resources in the resource pool, where the DMRS parameter sets are associated with different candidate values for at least one transmit parameter (e.g., an MCS and a payload size).

[0113] As shown by reference number 610, the UE 120 may select a resource from the resource pool based on at least one transmit parameter (e.g., proper MCS and payload size) for a grant-free PUSCH message and according to the resource pool configuration. The selected resource may be associated with multiple DMRS parameter sets, which are each associated with a value or a combination of values for one or more transmit parameters. Additionally, in some aspects, the UE may select the resource based on the UE having UL data to transmit. As shown by reference number 615, depending on the at least one transmit parameter (e.g., MCS and payload size), the UE 120 may identify a DMRS parameter set (e.g., a DMRS port / scrambling sequence set) associated with the selected resource. As shown by reference number 620, the UE 120 may select a DMRS parameter from the selected DMRS parameter set. In some aspects, the UE 120 may randomly select the DMRS parameter from the selected DMRS parameter set. In some aspects, when a UE 120 is transmitting in multiple resources, the UE 120 may select different DMRS parameters for each resource in which the UE 120 is transmitting. In some aspects, there may be different transmit parameters (e.g., MCS, payload size, or the like) in different resources. For example, the UE may select a DMRS parameter and / or DMRS parameter set mapped to different transmit parameter values for different resources.

[0114] As shown by reference number 625, the UE 120 may transmit, and the network node 110 may receive, the grant-free PUSCH message in the selected resource, including the selected DMRS parameter. As shown by reference number 630, the network node 110 may attempt to detect different DMRS parameters for a resource based on a configured metric (e.g., a transmit parameter, including an MCS and / or payload size).

[0115] In some aspects, when the resource bandwidth is sufficiently broad and / or the resource is distributed, the network node 110 may detect the DMRS parameter according to coherent combining in the time domain. For example, the UE 120 may encode information in one or more codewords that are modulated to form one or more OFDM symbols. The UE 120 may generate a pilot / reference signal associated with the one or more OFDM symbols (e.g., a DMRS and / or other suitable reference signal), and transmit the pilot reference signal and the OFDM symbols over the PUSCH. The network node 110 may receive the pilot / reference signal and the OFDM symbols and may use the pilot / reference signal to obtain CSI associated with the physical channel. For example, the network node 110 may demodulate and decode the pilot / reference signal and the OFDM symbols, may perform a channel estimation of the physical channel based at least in part on the demodulation and / or decoding of the pilot / reference signal, and may adjust or modify demodulation and / or decoding parameters for the network node 1100097-5700PCT 35based at least in part on the channel estimation in order to increase the efficiency and performance of demodulation and / or decoding for the network node 110. By using coherent combining in the time domain, the network node 110 may increase demodulation and / or decoding performance in scenarios having relatively high signal -to-noise ratio (SNR). Accordingly, a coherent combining technique may be used to detect the DMRS port / scrambling sequence for the received grant-free PUSCH message.

[0116] In some aspects, when the resource bandwidth is sufficiently broad and / or the resource is distributed, the network node 110 may detect the DMRS parameter according to non-coherent combining in a frequency domain. For example, the network node 110 may directly demodulate and decode a received OFDM symbol without performing a channel estimation based on a pilot signal or a reference signal. This permits the UE 120 to use differential modulation (e.g., where information is modulated based at least in part on the phase difference between adjacent coded OFDM symbols) and / or sequence-based modulation (e.g., where information is modulated jointly on a sequence of OFDM symbols). However, the longer that channel coherence is used (e.g., the greater the quantity of adjacent coded OFDM symbols that are considered to be coherent), the greater the complexity of encoding at the UE 120 and decoding at the network node 110. As a result, non-coherent combining may be challenging in scenarios having a high SNR. By using non-coherent combining in the frequency domain, the network node 110 may increase demodulation and / or decoding performance in low SNR scenarios. Accordingly, a non-coherent combining technique may be used to detect the DMRS port / scrambling sequence for the received grant-free PUSCH message.

[0117] The network node 110 may then map the detected DMRS parameter to an MCS and a payload size, and the network node 110 may proceed with decoding the PUSCH message based on at least one of a transmit MCS and / or payload size associated with the detected DMRS parameter. By including the selected DMRS parameter in the grant-free PUSCH message, the network node 110 may be aware of the MCS and payload size associated with the grant-free PUSCH message, and as a result, the network node 110 may be able to unambiguously identify the transmit parameters associated with the grant-free PUSCH message. For example, by including the DMRS parameter in the grant-free PUSCH message, the blind channel estimation and decoding process may be simplified, where the network node 110 may begin decoding the grant-free PUSCH message based on the MCS and payload size associated with the DMRS parameter. Accordingly, the DMRS parameter selection-based configuration reduces the complexity of the blind channel estimation and decoding process and reduces the overhead processing by the network node for large scale transmissions and / or network environments with an increased number of UEs or with high traffic volumes. For example, where multiple DMRS parameters are detected by a network node 110 (e.g., where a DMRS parameter is included in each PUSCH transmission from a UE 120), the DMRS parameter selection-based configuration0097-5700PCT 36of grant-free UL transmissions enables the network node 110 to efficiently identify the transmit parameters associated with each grant-free PUSCH transmission according to the DMRS parameters associated with the grant-free PUSCH transmission. Accordingly, by simplifying the decoding process at the network node, the configuration may increase the probability that the network node successfully decodes PUSCH transmissions, thus reducing the probability of retransmissions.

[0118] As described herein, by enabling a UE 120 to select a DMRS parameter for inclusion in a grant-free UE transmission to a network node, decoding grant-free PUSCH messages at the network node 110 may be simplified and the decoding efficiency may be increased. By simplifying the decoding process at the network node 110, the configuration may reduce network latency and conserve power, processing, and / or other resources. For example, by reducing the decoding complexity at the network node 110, the network node 110 may process and potentially respond to the grant-free PUSCH message in less time, resulting in lower latency in the communications between the UE 120 and the network node 110. Additionally, where a large number of UEs 120 are in communication with a network node and / or where network traffic is relatively high, overall latency may be reduced between the network node and the UEs 120.

[0119] As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.

[0120] In some aspects, a UE 120 may receive, from a network node 110, a resource pool configuration 605, wherein the resource pool configuration indicates a resource pool 505 including a plurality of resources 515, and wherein the resource pool configuration further indicates a plurality of DMRS scrambling sequence sets for each resource 515 of the plurality of resources 515. The UE 120 may select a resource 515 from the plurality of resources 515 in the resource pool 505. The UE 120 may further select 615 a DMRS scrambling sequence set from the plurality of DMRS scrambling sequence sets associated with the selected resource 515 based on at least one transmit parameter value. The UE 120 may further select 620 a DMRS scrambling sequence from the selected DMRS scrambling sequence set. The UE 120 may transmit 625, to the network node 110, a PUSCH message in the selected resource 515 based on the DMRS scrambling sequence.

[0121] In some aspects, the selected resource 515 may be selected from the plurality of resources 515 in the resource pool 505 based on at least one transmit parameter value associated with the PUSCH message. In some aspects, the at least one transmit parameter value may include an MCS value or a payload size. In some aspects, the selected resource 515 may be randomly selected from the plurality of resources 515 in the resource pool 505. In some aspects, the selected DMRS scrambling sequence may be randomly selected from the selected DMRS scrambling sequence set.0097-5700PCT 37

[0122] In some aspects, the UE 120 may receive, from the network node 110, an update to the resource pool configuration including a change to at least one association between a DMRS scrambling sequence set and a transmit parameter value. In some aspects, the update to the resource pool configuration may be received via a GC-PDCCH.

[0123] In some aspects, the network node 110 may transmit, to the UE 120, a resource pool configuration 605, wherein the resource pool configuration indicates a resource pool 505 including a plurality of resources 515, and wherein the resource pool configuration further indicates a plurality of DMRS scrambling sequence sets for each resource 515 of the plurality of resources 515. The plurality of DMRS scrambling sequence sets may be associated with at least one transmit parameter value. The network node 110 may receive 625, from the UE 120, a PUSCH message in a selected resource based on a selected DMRS scrambling sequence.

[0124] In some aspects, the network node 110 may detect the DMRS scrambling sequence in the PUSCH message. The network node 110 may decode the PUSCH message based on at least one transmit parameter associated with the detected DMRS scrambling sequence. In some aspects, the DMRS scrambling sequence may be detected according to non-coherent combining in a frequency domain. In some aspects the DMRS scrambling sequence may be detected according to coherent combining in a time domain. In some aspects, the at least one transmit parameter value may include at least one of an MCS or a payload size. In some aspects, the network node 110 may transmit, to the UE 120, an updated resource pool configuration based on at least one change in a network condition. In some aspects, the network condition may include network traffic in a wireless network. In some aspects, the updated resource pool configuration may be transmitted via a GC-PDCCH.

[0125] In some aspects, a UE 120 may receive, from a network node 110, a resource pool configuration 605, wherein the resource pool configuration indicates a resource pool 505 including a plurality of resources 515, and wherein the resource pool configuration further indicates a plurality of DMRS port sets for each resource 515 of the plurality of resources 515. The UE 120 may select a resource 515 from the plurality of resources 515 in the resource pool 505. The UE 120 may further select 615 a DMRS port set from the plurality of DMRS port sets associated with the selected resource 515 based on at least one transmit parameter value. The UE 120 may further select 620 a DMRS port from the selected DMRS port set. The UE 120 may transmit 625, to the network node 110, a PUSCH message in the selected resource 515 based on the DMRS port.

[0126] In some aspects, the selected resource 515 may be selected from the plurality of resources 515 in the resource pool 505 based on at least one transmit parameter value associated with the PUSCH message. In some aspects, the at least one transmit parameter value may include an MCS value or a payload size. In some aspects, the selected resource 515 may be0097-5700PCT 38randomly selected from the plurality of resources 515 in the resource pool 505. In some aspects, the selected DMRS port may be randomly selected from the selected DMRS port set.

[0127] In some aspects, the UE 120 may receive, from the network node 110, an update to the resource pool configuration including a change to at least one association between a DMRS port set and a transmit parameter value. In some aspects, the update to the resource pool configuration may be received via a GC-PDCCH.

[0128] In some aspects, the network node 110 may transmit, to the UE 120, a resource pool configuration 605, wherein the resource pool configuration indicates a resource pool 505 including a plurality of resources 515, and wherein the resource pool configuration further indicates a plurality of DMRS port sets for each resource 515 of the plurality of resources 515. The plurality of DMRS port sets may be associated with at least one transmit parameter value. The network node 110 may receive 625, from the UE 120, a PUSCH message in a selected resource based on a selected DMRS port.

[0129] In some aspects, the network node 110 may detect the DMRS port in the PUSCH message. The network node 110 may decode the PUSCH message based on at least one transmit parameter associated with the detected DMRS port. In some aspects, the DMRS port may be detected according to non-coherent combining in a frequency domain. In some aspects the DMRS port may be detected according to coherent combining in a time domain. In some aspects, the at least one transmit parameter value may include at least one of an MCS or a payload size. In some aspects, the network node 110 may transmit, to the UE 120, an updated resource pool configuration based on at least one change in a network condition. In some aspects, the network condition may include network traffic in a wireless network. In some aspects, the updated resource pool configuration may be transmitted via a GC-PDCCH.

[0130] Fig. 7 is a diagram illustrating an example process 700 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 700 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with DMRS parameter selection for grant-free UE UL transmission.

[0131] As shown in Fig. 7, in some aspects, process 700 may include receiving, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter (block 710). For example, the UE (e.g., using reception component 902 and / or communication manager 906, depicted in Fig. 9) may receive, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the0097-5700PCT 39plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter, as described above.

[0132] As further shown in Fig. 7, in some aspects, process 700 may include selecting a resource from the plurality of resources in the resource pool (block 720). For example, the UE (e.g., using communication manager 906, depicted in Fig. 9) may select a resource from the plurality of resources in the resource pool, as described above.

[0133] As further shown in Fig. 7, in some aspects, process 700 may include selecting a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message (block 730). For example, the UE (e.g., using communication manager 906, depicted in Fig. 9) may select a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message, as described above.

[0134] As further shown in Fig. 7, in some aspects, process 700 may include selecting a DMRS parameter from the selected DMRS parameter set (block 740). For example, the UE (e.g., using communication manager 906, depicted in Fig. 9) may select a DMRS parameter from the selected DMRS parameter set, as described above.

[0135] As further shown in Fig. 7, in some aspects, process 700 may include transmitting, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter (block 750). For example, the UE (e.g., using transmission component 904 and / or communication manager 906, depicted in Fig. 9) may transmit, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter, as described above.

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

[0137] In a first aspect, the resource is selected from the plurality of resources in the resource pool based on the at least one transmit parameter value associated with the PUSCH message.

[0138] In a second aspect, the at least one transmit parameter value includes at least one of a MCS value or a payload size.

[0139] In a third aspect, the resource is randomly selected from the plurality of resources in the resource pool.

[0140] In a fourth aspect, the DMRS parameter is randomly selected from the selected DMRS parameter set.0097-5700PCT 40

[0141] In a fifth aspect, process 700 includes receiving, from the network node, an update to the resource pool configuration, wherein the update includes a change to at least one association between a DMRS parameter set and a transmit parameter value.

[0142] In a sixth aspect, the update to the resource pool configuration is received via a GC- PDCCH.

[0143] In a seventh aspect, the plurality of DMRS parameter sets are each associated with one or more DMRS ports for a given value of the at least one transmit parameter.

[0144] In an eighth aspect, the plurality of DMRS parameter sets are each associated with one or more DMRS scrambling sequences for a given value of the at least one transmit parameter.

[0145] Although Fig. 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0146] Fig. 8 is a diagram illustrating an example process 800 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process 800 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with DMRS parameter selection for grant-free UE UL transmission.

[0147] As shown in Fig. 8, in some aspects, process 800 may include transmitting, to a UE, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter (block 810). For example, the network node (e.g., using transmission component 1004 and / or communication manager 1006, depicted in Fig. 10) may transmit, to a UE, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter, as described above.

[0148] As further shown in Fig. 8, in some aspects, process 800 may include receiving, from the UE, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter (block 820). For example, the network node (e.g., using reception component 1002 and / or communication manager 1006, depicted in Fig. 10) may receive, from the UE, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter, as described above.0097-5700PCT 41

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

[0150] In a first aspect, process 800 includes detecting the DMRS parameter in the PUSCH message, and decoding the PUSCH message based on at least one transmit parameter associated with the detected DMRS parameter.

[0151] In a second aspect, the DMRS parameter is detected according to non-coherent combining in a frequency domain.

[0152] In a third aspect, the DMRS parameter is detected according to coherent combining in a time domain.

[0153] In a fourth aspect, the at least one transmit parameter value includes at least one of a MCS or a payload size.

[0154] In a fifth aspect, process 800 includes transmitting, to the UE, an updated resource pool configuration based on at least one change in a network condition.

[0155] In a sixth aspect, the network condition includes network traffic in a wireless network.

[0156] In a seventh aspect, the updated resource pool configuration is transmitted via a GC- PDCCH.

[0157] Although Fig. 8 shows example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0158] Fig. 9 is a diagram of an example apparatus 900 for wireless communication, in accordance with the present disclosure. The apparatus 900 may be a UE, or a UE may include the apparatus 900. In some aspects, the apparatus 900 includes a reception component 902, a transmission component 904, and / or a communication manager 906, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 906 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 900 may communicate with another apparatus 908, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 902 and the transmission component 904. The communication manager 906 may be included in, or implemented via, a processing system (for example, the processing system 140 described in connection with Fig. 1 of the UE).

[0159] In some aspects, the apparatus 900 may be configured to perform one or more operations described herein in connection with Figs. 5-6. Additionally, or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as process 700 of Fig. 7. In some aspects, the apparatus 900 and / or one or more components0097-5700PCT 42shown in Fig. 9 may include one or more components of the UE described in connection with Fig. 1. Additionally, or alternatively, one or more components shown in Fig. 9 may be implemented within one or more components described in connection with Fig. 1. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer- readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0160] The reception component 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 908. The reception component 902 may provide received communications to one or more other components of the apparatus 900. In some aspects, the reception component 902 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 900. In some aspects, the reception component 902 may include one or more components of the UE 120 described above in connection with Figure 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the UE.

[0161] The transmission component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 908. In some aspects, one or more other components of the apparatus 900 may generate communications and may provide the generated communications to the transmission component 904 for transmission to the apparatus 908. In some aspects, the transmission component 904 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 908. In some aspects, the transmission component 904 may include one or more components of the UE 120 described above in connection with Figure 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the UE 120 of the UE described in connection with Fig. 1. In some aspects, the transmission component 904 may be co-located with the reception component 902.

[0162] The communication manager 906 may support operations of the reception component 902 and / or the transmission component 904. For example, the communication manager 906 may receive information associated with configuring reception of communications by the reception component 902 and / or transmission of communications by the transmission component 904. Additionally, or alternatively, the communication manager 906 may generate and / or provide control information to the reception component 902 and / or the transmission component 904 to control reception and / or transmission of communications.0097-5700PCT 43

[0163] The reception component 902 may receive, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The communication manager 906 may select a resource from the plurality of resources in the resource pool. The communication manager 906 may select a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a PUSCH message. The communication manager 906 may select a DMRS parameter from the selected DMRS parameter set. The transmission component 904 may transmit, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

[0164] The reception component 902 may receive, from the network node, an update to the resource pool configuration, wherein the update includes a change to at least one association between a DMRS parameter set and a transmit parameter value.

[0165] The number and arrangement of components shown in Fig. 9 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 9. Furthermore, two or more components shown in Fig. 9 may be implemented within a single component, or a single component shown in Fig. 9 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 9 may perform one or more functions described as being performed by another set of components shown in Fig. 9.

[0166] Fig. 10 is a diagram of an example apparatus 1000 for wireless communication, in accordance with the present disclosure. The apparatus 1000 may be a network node, or a network node may include the apparatus 1000. In some aspects, the apparatus 1000 includes a reception component 1002, a transmission component 1004, and / or a communication manager 1006, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 1006 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 1000 may communicate with another apparatus 1008, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1002 and the transmission component 1004. The communication manager 1006 may be included in, or implemented via, a processing system (for example, the processing system 150 described in connection with Fig. 1 of the network node).

[0167] In some aspects, the apparatus 1000 may be configured to perform one or more operations described herein in connection with Figs. 5-6. Additionally, or alternatively, the0097-5700PCT 44apparatus 1000 may be configured to perform one or more processes described herein, such as process 800 of Fig. 8. In some aspects, the apparatus 1000 and / or one or more components shown in Fig. 10 may include one or more components of the network node described in connection with Fig. 1. Additionally, or alternatively, one or more components shown in Fig. 10 may be implemented within one or more components described in connection with Fig. 1. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0168] The reception component 1002 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1008. The reception component 1002 may provide received communications to one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may perform signal processing on the received communications, and may provide the processed signals to the one or more other components of the apparatus 1000. In some aspects, the reception component 1002 may include one or more components of the UE 120 described above in connection with Figure 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the network node. In some aspects, the reception component 1002 and / or the transmission component 1004 may include or may be included in a network interface. The network interface may be configured to obtain and / or output signals for the apparatus 1000 via one or more communications links, such as a backhaul link, a midhaul link, and / or a fronthaul link.

[0169] The transmission component 1004 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1008. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmission component 1004 for transmission to the apparatus 1008. In some aspects, the transmission component 1004 may perform signal processing on the generated communications, and may transmit the processed signals to the apparatus 1008. In some aspects, the transmission component 1004 may include one or more components of the UE 120 described above in connection with Figure 1, such as a radio, one or more RF chains, one or more transceivers, or one or more modems, each of which may in turn be coupled with one or more antennas of the UE 120 of the network node described in connection with Fig. 1. In some aspects, the transmission component 1004 may be co-located with the reception component 1002.

[0170] The communication manager 1006 may support operations of the reception component 1002 and / or the transmission component 1004. For example, the communication0097-5700PCT 45manager 1006 may receive information associated with configuring reception of communications by the reception component 1002 and / or transmission of communications by the transmission component 1004. Additionally, or alternatively, the communication manager 1006 may generate and / or provide control information to the reception component 1002 and / or the transmission component 1004 to control reception and / or transmission of communications.

[0171] The transmission component 1004 may transmit, to a UE a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of DMRS parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter. The reception component 1002 may receive, from the UE, a PUSCH message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

[0172] The communication manager 1006 may detect the DMRS parameter in the PUSCH message.

[0173] The communication manager 1006 may decode the PUSCH message based on at least one transmit parameter associated with the detected DMRS parameter.

[0174] The transmission component 1004 may transmit, to the UE, an updated resource pool configuration based on at least one change in a network condition.

[0175] The number and arrangement of components shown in Fig. 10 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 10. Furthermore, two or more components shown in Fig. 10 may be implemented within a single component, or a single component shown in Fig. 10 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 10 may perform one or more functions described as being performed by another set of components shown in Fig. 10.

[0176] The following provides an overview of some Aspects of the present disclosure:

[0177] Aspect 1 : A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; selecting a resource from the plurality of resources in the resource pool; selecting a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a physical uplink shared channel (PUSCH) message; selecting a DMRS parameter from the selected0097-5700PCT 46DMRS parameter set; and transmitting, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

[0178] Aspect 2: The method of Aspect 1, wherein the resource is selected from the plurality of resources in the resource pool based on the at least one transmit parameter value associated with the PUSCH message.

[0179] Aspect 3: The method of Aspect 2, wherein the at least one transmit parameter value includes at least one of a modulation and coding scheme (MCS) value or a payload size.

[0180] Aspect 4: The method of any of Aspects 1-3, wherein the resource is randomly selected from the plurality of resources in the resource pool.

[0181] Aspect 5: The method of any of Aspects 1-4, wherein the DMRS parameter is randomly selected from the selected DMRS parameter set.

[0182] Aspect 6: The method of any of Aspects 1-5, further comprising: receiving, from the network node, an update to the resource pool configuration, wherein the update includes a change to at least one association between a DMRS parameter set and a transmit parameter value.

[0183] Aspect 7: The method of Aspect 6, wherein the update to the resource pool configuration is received via a group common physical downlink control channel (GC- PDCCH).

[0184] Aspect 8: The method of any of Aspects 1-7, wherein the plurality of DMRS parameter sets are each associated with one or more DMRS ports for a given value of the at least one transmit parameter.

[0185] Aspect 9: The method of any of Aspects 1-8, wherein the plurality of DMRS parameter sets are each associated with one or more DMRS scrambling sequences for a given value of the at least one transmit parameter.

[0186] Aspect 10: A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE), a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; and receiving, from the UE, a physical uplink shared channel (PUSCH) message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

[0187] Aspect 11: The method of Aspect 10, further comprising: detecting the DMRS parameter in the PUSCH message; and decoding the PUSCH message based on at least one transmit parameter associated with the detected DMRS parameter.0097-5700PCT 47

[0188] Aspect 12: The method of Aspect 11, wherein the DMRS parameter is detected according to non-coherent combining in a frequency domain.

[0189] Aspect 13: The method of Aspect 11, wherein the DMRS parameter is detected according to coherent combining in a time domain.

[0190] Aspect 14: The method of any of Aspects 10-13, wherein the at least one transmit parameter value includes at least one of a modulation and coding scheme (MCS) or a payload size.

[0191] Aspect 15: The method of any of Aspects 10-14, further comprising: transmitting, to the UE, an updated resource pool configuration based on at least one change in a network condition.

[0192] Aspect 16: The method of Aspect 15, wherein the network condition includes network traffic in a wireless network.

[0193] Aspect 17: The method of Aspect 15, wherein the updated resource pool configuration is transmitted via a group common physical downlink control channel (GC- PDCCH).

[0194] Aspect 18: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-17.

[0195] Aspect 19: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-17.

[0196] Aspect 20: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-17.

[0197] Aspect 21 : A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-17.

[0198] Aspect 22: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-17.

[0199] Aspect 23: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-17.0097-5700PCT 48

[0200] Aspect 24: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-17.

[0201]

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

[0203] As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.

[0204] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

[0205] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0206] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended0097-5700PCT 49to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based on or otherwise in association with” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of’). It should be understood that “one or more” is equivalent to “at least one.”

[0207] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.0097-5700PCT 50

Claims

WHAT IS CLAIMED IS:

1. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the UE to: receive, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; select a resource from the plurality of resources in the resource pool; select a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a physical uplink shared channel (PUSCH) message; select a DMRS parameter from the selected DMRS parameter set; and transmit, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

2. The UE of claim 1, wherein the resource is selected from the plurality of resources in the resource pool based on the at least one transmit parameter value associated with the PUSCH message.

3. The UE of claim 2, wherein the at least one transmit parameter value includes at least one of a modulation and coding scheme (MCS) value or a payload size.

4. The UE of claim 1, wherein the resource is randomly selected from the plurality of resources in the resource pool.

5. The UE of claim 1, wherein the DMRS parameter is randomly selected from the selected DMRS parameter set.

6. The UE of claim 1, wherein the one or more processors are further configured to cause the UE to: receive, from the network node, an update to the resource pool configuration, wherein the update includes a change to at least one association between a DMRS parameter set and a transmit parameter value.0097-5700PCT 517. The UE of claim 6. wherein the update to the resource pool configuration is received via a group common physical downlink control channel (GC-PDCCH).

8. The UE of claim 1, wherein the plurality of DMRS parameter sets are each associated with one or more DMRS ports for a given value of the at least one transmit parameter.

9. The UE of claim 1, wherein the plurality of DMRS parameter sets are each associated with one or more DMRS scrambling sequences for a given value of the at least one transmit parameter.

10. A network node for wireless communication, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the network node to: transmit, to a user equipment (UE), a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; and receive, from the UE, a physical uplink shared channel (PUSCH) message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

11. The network node of claim 10, wherein the one or more processors are further configured to cause the network node to: detect the DMRS parameter in the PUSCH message; and decode the PUSCH message based on at least one transmit parameter associated with the detected DMRS parameter.

12. The network node of claim 11, wherein the DMRS parameter is detected according to non-coherent combining in a frequency domain.

13. The network node of claim 11, wherein the DMRS parameter is detected according to coherent combining in a time domain.

14. The network node of claim 10, wherein the at least one transmit parameter value includes at least one of a modulation and coding scheme (MCS) or a payload size.0097-5700PCT 5215. The network node of claim 10, wherein the one or more processors are further configured to cause the network node to: transmit, to the UE, an updated resource pool configuration based on at least one change in a network condition.

16. The network node of claim 15, wherein the network condition includes network traffic in a wireless network.

17. The network node of claim 15, wherein the updated resource pool configuration is transmitted via a group common physical downlink control channel (GC-PDCCH).

18. A method of wireless communication performed by a user equipment (UE), comprising: receiving, from a network node, a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; selecting a resource from the plurality of resources in the resource pool; selecting a DMRS parameter set from the plurality of DMRS parameter sets associated with the selected resource based on at least one transmit parameter value associated with a physical uplink shared channel (PUSCH) message; selecting a DMRS parameter from the selected DMRS parameter set; and transmitting, to the network node, a PUSCH message in the selected resource, wherein the PUSCH message includes the selected DMRS parameter.

19. The method of claim 18, wherein the resource is selected from the plurality of resources in the resource pool based on the at least one transmit parameter value associated with the PUSCH message.

20. The method of claim 19, wherein the at least one transmit parameter value includes at least one of a modulation and coding scheme (MCS) value or a payload size.

21. The method of claim 18, wherein the resource is randomly selected from the plurality of resources in the resource pool.0097-5700PCT 5322. The method of claim 18, wherein the DMRS parameter is randomly selected from the selected DMRS parameter set.

23. The method of claim 18, wherein the plurality of DMRS parameter sets are each associated with one or more DMRS ports for a given value of the at least one transmit parameter.

24. The method of claim 18, wherein the plurality of DMRS parameter sets are each associated with one or more DMRS scrambling sequences for a given value of the at least one transmit parameter.

25. A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE), a resource pool configuration associated with a plurality of resources in a resource pool and a plurality of demodulation reference signal (DMRS) parameter sets associated with each of the plurality of resources in the resource pool, wherein the plurality of DMRS parameter sets are associated with different values for at least one transmit parameter; and receiving, from the UE, a physical uplink shared channel (PUSCH) message in a resource of the plurality of resources in the resource pool, wherein the PUSCH message includes a DMRS parameter.

26. The method of claim 25, further comprising: detecting the DMRS parameter in the PUSCH message; and decoding the PUSCH message based on at least one transmit parameter associated with the detected DMRS parameter.

27. The method of claim 26, wherein the DMRS parameter is detected according to noncoherent combining in a frequency domain.

28. The method of claim 26, wherein the DMRS parameter is detected according to coherent combining in a time domain.

29. The method of claim 25, wherein the at least one transmit parameter value includes at least one of a modulation and coding scheme (MCS) or a payload size.

30. The method of claim 25, further comprising:0097-5700PCT 54transmiting, to the UE, an updated resource pool configuration based on at least one change in a network condition.0097-5700PCT 55

Images