Physical uplink shared channel power control

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can calculate at least one of a nominal power value, an alpha value, or an initial transmit power value for a physical uplink shared channel (PUSCH) transmission occasion in a full duplex slot, where the PUSCH transmission occasion is associated with a radio resource control (RRC) connection resulting from a random access procedure for which the UE did not receive a PUSCH alpha set during or is associated with a random access response uplink grant for transmission or retransmission. The UE can transmit in the PUSCH transmission occasion using at least one of the nominal power value, the alpha value, or the initial transmit power value. Numerous other aspects are described.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 516,206, filed November 21, 2023, entitled “PHYSICAL UPLINK SHAREDCHANNEL POWER CONTROL,” which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for physical uplink shared channel power control. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). 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.

[0005] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0006] In some aspects, a method of wireless communication performed by a user equipment (UE) includes: calculating at least one of a nominal power value, an α value, or an initial transmit power value for a physical uplink shared channel (PUSCH) transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with a radio resource control (RRC) connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with a random access response uplink grant for transmission or retransmission; and transmitting during the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmit power value.

[0007] In some aspects, a method of wireless communication performed by a network node includes: transmitting configuration information associated with a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure that does not include a PUSCH α set or with a random access response uplink grant for transmission or retransmission; and receiving communication via the PUSCH transmission timing based on at least one of a nominal power value, an α value, or an initial transmission power value.

[0008] In some aspects, an apparatus for wireless communication at a UE includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the UE to: calculate at least one of a nominal power value, an α value, or an initial transmit power value for a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with an uplink grant for a random access response for transmission or retransmission; and transmit using at least one of the nominal power value, the α value, or the initial transmit power value during the PUSCH transmission timing.

[0009] In some aspects, an apparatus for wireless communication at a network node includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the network node to: transmit configuration information associated with a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure excluding a PUSCH α set or with a random access response uplink grant for transmission or retransmission; and receive communication via the PUSCH transmission timing based on at least one of a nominal power value, an α value, or an initial transmission power value.

[0010] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: calculate at least one of a nominal power value, an α value, or an initial transmit power value for a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with an uplink grant for a random access response for transmission or retransmission; and transmit during the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmit power value.

[0011] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a network node, cause the network node to: transmit configuration information associated with a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure excluding a PUSCH α set or with a random access response uplink grant for transmission or retransmission; and receive communication via the PUSCH transmission timing based on at least one of a nominal power value, an α value, or an initial transmission power value.

[0012] In some aspects, an apparatus for wireless communication includes: components for calculating at least one of a nominal power value, an α value, or an initial transmit power value for a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with an uplink grant for a random access response for transmission or retransmission; and components for transmitting during the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmit power value.

[0013] In some aspects, an apparatus for wireless communication includes: means for transmitting configuration information associated with a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure that does not include a PUSCH α set or with a random access response uplink grant for transmission or retransmission; and means for receiving communication via the PUSCH transmission timing based on at least one of a nominal power value, an α value, or an initial transmission power value.

[0014] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0015] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0016] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0017] Figure 1 This is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0018] Figure 2 This is a diagram illustrating communication between an example network node and an example user equipment (UE) in a wireless network according to the present disclosure.

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

[0020] Figure 4 This is a diagram illustrating examples of physical channels and reference signals in a wireless network according to this disclosure.

[0021] Figure 5 This is a diagram illustrating an example of full-duplex communication in a wireless network according to the present disclosure.

[0022] Figure 6 This is a diagram illustrating an example of physical uplink shared channel power control according to this disclosure.

[0023] Figure 7 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0024] Figure 8 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0025] Figure 9 This is a diagram of an example device for wireless communication according to the present disclosure.

[0026] Figure 10 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0027] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a method of practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functions other than those available for practicing the various aspects of this disclosure set forth herein, or methods of practice using those other structures and / or functions. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0029] User equipment (UE) can transmit data to network nodes via the Physical Uplink Shared Channel (PUSCH). A PUSCH is a channel that can be shared by the UE and one or more other devices for transmitting data to network nodes. In some cases, the UE can use full-duplex or half-duplex communication to transmit data to network nodes. Full-duplex communication refers to simultaneous bidirectional communication between devices in a wireless network. For example, a UE operating in full-duplex mode can simultaneously (e.g., in the same time slot or the same symbol) transmit uplink communication and receive downlink communication. In contrast, half-duplex communication refers to unidirectional communication between devices at a given time (e.g., downlink communication only or uplink communication only). The UE can perform PUSCH transmission on the active uplink bandwidth portion of the carrier of the serving cell according to one or more parameters. In some examples, the UE can perform PUSCH transmission according to the P0-PUSCH-AlphaSet parameter. Additionally or alternatively, the UE can perform PUSCH transmission (or retransmission) for Msg3 or MsgA according to the initial access procedure. In these examples, it may be necessary to adjust the P0 and nominal power values ​​used for PUSCH power control. For instance, unadjusted P0 and nominal power values ​​may fail to differentiate between half-duplex and full-duplex time slots. In full-duplex time slots, power control may change based on one or more conditions. For example, it may be necessary to increase uplink power to overcome self-interference at network nodes, or it may be necessary to decrease the uplink power to reduce cross-link interference between UEs. Therefore, performing PUSCH transmissions in full-duplex resources using power control with unadjusted P0 or nominal power values ​​may lead to increased interference and may additionally result in reduced network capacity, shorter UE battery life, lower signal-to-noise ratio, and reduced quality of service, among other things.

[0030] Various aspects are involved in wireless communication as a whole. Some aspects are more specifically involved in physical uplink shared channel power control. In some aspects, network nodes may transmit configuration information associated with the timing of PUSCH transmission in a full-duplex time slot, and the UE may receive this configuration information. The timing of PUSCH transmission may be associated with a Radio Resource Control (RRC) connection resulting from a random access procedure during which the UE does not receive an α set, or it may be associated with an uplink grant for a random access response used by the UE for transmission or retransmission. The UE may calculate one or more parameters for performing PUSCH transmission. In one example, the UE may calculate a nominal power value for a Type-1 random access procedure. In another example, the UE may calculate a nominal power value for a Type-2 random access procedure. In another example, the UE may calculate an α value for a Type-1 random access procedure. In yet another example, the UE may calculate an initial transmission power value for either a Type-1 or Type-2 random access procedure. The UE may use at least one of the nominal power value, the α value, or the initial transmission power value to transmit during the PUSCH transmission timing.

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by calculating one or more parameters for the timing of PUSCH transmission in a full-duplex time slot, the described techniques can be used to reduce the likelihood of interference in PUSCH transmission. For example, by calculating one or more parameters for the timing of PUSCH transmission associated with an RRC connection resulting from a random access procedure during which the UE did not receive an α set, or associated with an uplink grant for a random access response made or retransmitted by the UE, the described techniques can be used to reduce the likelihood of interference in PUSCH transmission. Additionally, by calculating one or more parameters for the timing of PUSCH transmission, the described techniques can be used to increase network capacity, extend UE battery life, increase the signal-to-noise ratio, and / or improve the quality of service for PUSCH transmission. In some examples, by calculating at least one of a nominal power value, an α value, or an initial transmission power value for the timing of PUSCH transmission in a full-duplex time slot, the described techniques can be used to reduce the likelihood of interference in PUSCH transmission associated with a Type-1 or Type-2 random access procedure. These example advantages, etc., will be described in more detail below.

[0032] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of 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, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0033] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0034] Figure 1This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

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

[0036] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 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 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

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

[0038] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

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

[0040] Network nodes 110 of 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). CUs 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, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[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, 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, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0042] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., with a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0043] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0044] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating 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. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more PUSCH. The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0045] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may 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 one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

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

[0047] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0048] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle 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 can communicate via a wireless medium, or may be coupled to them.

[0049] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more 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 (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0050] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, 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 are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with 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 collectively referred to as "MTC UEs". An MTC UE may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles or drones, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0052] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, eMBB, and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0053] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use 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 to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0054] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0055] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0056] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may calculate at least one of a nominal power value, an α value, or an initial transmission power value for a PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with an uplink grant for a random access response for transmission or retransmission; and may transmit during the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmission power value. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0057] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may send configuration information associated with the timing of PUSCH transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure that does not include a PUSCH α set, or with an uplink grant for a random access response used for transmission or retransmission; and receive communication via the PUSCH transmission timing based on at least one of a nominal power value, an α value, or an initial transmission power value. Additionally or alternatively, communication manager 150 may perform one or more other operations described herein.

[0058] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0059] Figure 2 This is a diagram illustrating an example network node 110 communicating with an example UE 120 in a wireless network according to the present disclosure.

[0060] like Figure 2As shown, 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 to 232t, where t≥1), a set of antennas 234 (shown as 234a to 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, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0061] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of 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 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 can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0063] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0064] The TX MIMO processor 216 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of modems 232. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for Orthogonal Frequency Division Multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 can further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) together via a set of corresponding antennas 234.

[0065] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

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

[0067] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmission and / or reception of communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or configuration grant (CG) configuration for UE 120.

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

[0069] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0070] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), 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, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

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

[0072] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from 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 receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0073] Transmitter 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmitter 264 can be pre-decoded by TX MIMO processor 266, where applicable, and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can (where applicable) perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, and can provide an assembly of output symbol streams (e.g., U output symbol streams) to the assembly of modems 254. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0074] Modems 254a to 254u can transmit a set of uplink signals (e.g., R uplink signals or U uplink symbols) via a set of corresponding antennas 252. Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals can be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals can carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) typically uses techniques similar to those described for uplink data and control transmission and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0075] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a device that integrates one or more antenna elements (such as one or more components of an antenna). As used herein, "antenna" can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can refer to an array or panel in which antenna groups (such as antenna elements) are arranged to facilitate beamforming by manipulating the parameters of the antenna groups. "Antenna module" can refer to a circuit that includes one or more antennas, and 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 antenna element of antenna 234 or 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, which can be used to independently transmit cross-polarized signals. 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. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0077] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0078] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0079] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0080] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.

[0081] Each component in the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0082] In some respects, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, 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 may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0083] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and 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 implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for 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 communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0085] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0086] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0087] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with physical uplink shared channel power control, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies or perform one or more operations associated with physical uplink shared channel power control, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may execute or instruct, for example Figure 7 Process 700 Figure 8The operation of process 800 or other processes as described herein (alone or in combination with one or more other processors). Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be made to be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 7 Process 700 Figure 8 The process 800 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0088] In some aspects, UE 120 includes components for calculating at least one of a nominal power value, an α value, or an initial transmit power value for PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with an uplink grant for a random access response for transmission or retransmission; and / or components for transmitting during the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmit power value. Components for UE 120 to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0089] In some aspects, network node 110 includes components for transmitting configuration information associated with the timing of PUSCH transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure that does not include a PUSCH α set, or with an uplink grant for a random access response for transmission or retransmission; and / or components for receiving communication via the PUSCH transmission timing based on at least one of a nominal power value, an α value, or an initial transmission power value. Components enabling network node 110 to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0090] Figure 4 This is a diagram illustrating example 400 of a physical channel and reference signal in a wireless network according to this disclosure. For example... Figure 4 As shown, the downlink channel and downlink reference signal can carry information from network node 110 to UE 120, and the uplink channel and uplink reference signal can carry information from UE 120 to network node 110.

[0091] As shown in the figure, downlink channels may include a PDCCH carrying DCI, a PDSCH carrying downlink data, or a Physical Broadcast Channel (PBCH) carrying system information, etc. In some aspects, PDSCH communication may be scheduled by PDCCH communication. As further shown, uplink channels may include a PUCCH carrying UCI, a PUSCH carrying uplink data, or a PRACH for initial network access, etc. In some aspects, UE 120 may send acknowledgment (ACK) or negative acknowledgment (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in the UCI on the PUCCH and / or PUSCH.

[0092] As shown in another figure, downlink reference signals may include synchronization signal blocks (SSBs), CSI-RS, DMRS, positioning reference signals (PRS), or phase tracking reference signals (PTRS), etc. Also as shown, uplink reference signals may include SRS, DMRS, or PTRS, etc.

[0093] The SSB can carry information for initial network acquisition and synchronization, such as PSS, SSS, PBCH, and PBCH DMRS. The SSB is sometimes referred to as the synchronization signal / PBCH (SS / PBCH) block. In some respects, network node 110 can transmit multiple SSBs on multiple corresponding beams, and the SSB can be used for beam selection.

[0094] The CSI-RS can carry information for downlink channel estimation (e.g., downlink CSI acquisition), which can be used for scheduling, link adaptation, or beam management. Network node 110 can configure a CSI-RS set for UE 120, and UE 120 can measure the configured CSI-RS set. Based at least in part on the measurement, UE 120 can perform channel estimation and can report channel estimation parameters to network node 110 (e.g., in a CSI report), such as CQI, pre-decoding matrix indicator (PMI), CSI-RS resource indicator (CRI), layer indicator (LI), rank indicator (RI), or RSRP. Network node 110 can use the CSI report to select transmission parameters for downlink communication to UE 120, such as the number of transmission layers (e.g., rank), pre-decoding matrix (e.g., pre-decoder), modulation and decoding scheme (MCS), or refinement of the downlink beam (e.g., using a beam refinement process or beam management process), etc.

[0095] The DMRS can carry information used to estimate the radio channel for demodulating the associated physical channel (e.g., PDCCH, PDSCH, PBCH, PUCCH, or PUSCH). The design and mapping of the DMRS can be specific to the physical channel it is used to estimate. The DMRS is UE-specific, can be beamformed, can be confined to scheduled resources (e.g., not transmitted over broadband), and can be transmitted only when necessary. As shown, the DMRS is used for both downlink and uplink communication.

[0096] PTRS can carry information for compensating oscillator phase noise. Typically, phase noise increases with the oscillator carrier frequency. Therefore, PTRS can be used at high carrier frequencies (such as millimeter-wave frequencies) to mitigate phase noise. PTRS can be used to track the phase of the local oscillator and to achieve suppression of phase noise and common phase error (CPE). As shown, PTRS is used for both downlink communication (e.g., on PDSCH) and uplink communication (e.g., on PUSCH).

[0097] The PRS may carry information for improving the Observed Time Difference of Arrival (OTDOA) positioning performance of the UE 120 by performing timing or ranging measurements based on signals transmitted by network node 110. For example, the PRS may be a pseudo-random quadrature phase shift keying (QPSK) sequence mapped diagonally with frequency and time offsets to avoid conflicts with cell-specific reference signals and control channels (e.g., PDCCH). Generally, the PRS may be designed to improve the detectability of the UE 120, which may need to detect downlink signals from multiple neighboring network nodes to perform OTDOA-based positioning. Therefore, the UE 120 may receive PRS from multiple cells (e.g., a reference cell and one or more neighboring cells) and may report the Reference Signal Time Difference (RSTD) based on the OTDA measurements associated with the PRS received from the multiple cells. In some aspects, network node 110 may then calculate the positioning of the UE 120 based on the RSTD measurements reported by the UE 120.

[0098] The SRS can carry information for uplink channel estimation, which can be used for scheduling, link adaptation, pre-decoder selection, or beam management, etc. Network node 110 can configure one or more SRS resource sets for UE 120, and UE 120 can transmit SRS on the configured SRS resource sets. The SRS resource sets can have configurable uses, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, etc. Network node 110 can measure the SRS, perform channel estimation at least in part based on these measurements, and use the SRS measurements to configure communication with UE 120.

[0099] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0100] Figure 5 These are illustrations of examples 500, 505, and 510 of full-duplex communication in a wireless network according to this disclosure. "Full-duplex communication" in a wireless network refers to simultaneous bidirectional communication between devices in the wireless network. For example, a UE operating in full-duplex mode can simultaneously (e.g., in the same time slot or the same symbol) transmit uplink communication and receive downlink communication. "Half-duplex communication" in a wireless network refers to unidirectional communication (e.g., downlink communication only or uplink communication only) between devices at a given time (e.g., in a given time slot or a given symbol).

[0101] like Figure 5As shown, Examples 500 and 505 illustrate examples of in-band full-duplex (IBFD) communication. In IBDF, the UE can send uplink communication to and receive downlink communication from the base station on the same time and frequency resources. As shown in Example 500, in the first example of IBDF, the time and frequency resources used for uplink communication can completely overlap with those used for downlink communication. As shown in Example 505, in the second example of IBDF, the time and frequency resources used for uplink communication can partially overlap with those used for downlink communication.

[0102] like Figure 5 As further illustrated, Example 510 shows an example of Sub-Band Full-Duplex (SBFD) communication. In SBFD, a UE can send uplink communication to and receive downlink communication from a base station at the same time but on different frequency resources. For example, different frequency resources can be sub-bands of a frequency band such as a time-division duplex band. In this case, the frequency resources used for downlink communication can be separated from the frequency resources used for uplink communication in the frequency domain by guard bands.

[0103] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0104] UE can serve cell carrier On the uplink of the BWP activity Use with index Parameter set configuration and index The PUSCH is sent in a PUSCH power control adjustment state. In this example, the UE can use the following formula (measured in decibels-milliwatts (dBm)) to determine the timing for PUSCH transmission. PUSCH transmit power :

[0105]

[0106] in:

[0107] It refers to the timing of PUSCH transmission. Service communities carrier The maximum output power configured for the UE.

[0108] It is composed of components With weight The nominal power parameter is composed of the sum of these parameters, where ,

[0109] It is a location parameter that is at least partially based on the location of the UE.

[0110] It is a path loss parameter.

[0111] It is a scaling parameter (e.g., scaling factor) used to adjust the path loss parameter.

[0112] It is a data parameter associated with the number of bits to be sent via PUSCH, and

[0113] These are closed-loop power control parameters.

[0114] In one example The value of is zero (0), and the path loss parameter is negligible. In another example, The value is 1 (1), and the entire path loss parameter can be used.

[0115] If the UE establishes a dedicated RRC connection using a Type-1 random access procedure and is not provided with a P0-PUSCH-AlphaSet, or if a PUSCH corresponding to the uplink grant of the Random Access Response (RAR) is transmitted or retransmitted,

[0116] ,

[0117] ,and

[0118] in:

[0119] Provided by preambleReceivedTargetPower, and Provided by msg3-DeltaPreamble, or if msg3-DeltaPreamble is not provided, then Decibels (dB) above refers to the service area. carrier In other words.

[0120] If the UE establishes a dedicated RRC connection using a Type-2 random access procedure and does not provide a P0-PUSCH-AlphaSet, or for PUSCH transmissions for a Type-2 random access procedure,

[0121] ,

[0122] ,and

[0123] in:

[0124] Provided by msgA-preambleReceivedTargetPower, or by preambleReceivedTargetPower if msgA-preambleReceivedTargetPower is not provided, and Provided by msgA-DeltaPreamble, or if msgA-DeltaPreamble is not provided, then dB, the above refers to the serving cell carrier In other words.

[0125] When the UE is not indicated by P0-PUSCH-AlphaSet and / or when the UE is transmitting or retransmitting PUSCH for Msg3 or MsgA, the P0 and nominal power values ​​used for PUSCH power control may need to be adjusted. For example, unadjusted P0 and nominal power values ​​may not be able to distinguish between half-duplex and full-duplex time slots. In full-duplex time slots, power control may change based on one or more conditions. In some cases, it may be necessary to increase uplink power, for example, to overcome self-interference at network nodes, or it may be necessary to decrease uplink power, for example, to reduce cross-link interference (CLI) between UEs. Therefore, performing PUSCH transmission in full-duplex time slots with power control using unadjusted P0 or nominal power values ​​may result in increased interference and may additionally lead to reduced network capacity, shortened UE battery life, reduced signal-to-noise ratio, and reduced quality of service, etc.

[0126] Figure 6 This is a diagram illustrating Example 600 of physical uplink shared channel power control according to this disclosure.

[0127] As shown by reference numeral 605 in the accompanying drawings, network node 110 may send configuration information associated with the timing of PUSCH transmission in a full-duplex time slot, and UE 120 may receive this configuration information. The configuration information may include information enabling UE 120 to transmit to network node 110 within the PUSCH transmission timing occurring in a full-duplex time slot. In some aspects, the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a PUSCH α set (P0-PUSCH-AlphaSet). In other aspects, the PUSCH transmission timing is associated with uplink grants for random access responses to transmissions or retransmissions made by the UE.

[0128] As shown in the attached figure 610, the UE 120 can calculate at least one of the nominal power value, α value, or initial transmission power value for the timing of PUSCH transmission.

[0129] In the first example, if UE 120 establishes a dedicated RRC connection using a Type-1 random access procedure and is not provided with a P0-PUSCH-AlphaSet, or if the UE is performing a PUSCH transmission (or retransmission) corresponding to an uplink grant in a random access response, and the PUSCH transmission occurs within a full-duplex time slot, then UE 120 may calculate a nominal power value (P_0_nominal) for the PUSCH transmission. In some aspects, calculating the nominal power value may include adding a power offset value to the nominal power value. The power offset value may be received by UE 120 via RRC configuration information or via system information. In some aspects, calculating the nominal power value may include adding the nominal preamble value (P_0_PRE) to the incremental preamble value (delta_preamble_msg3_FD) for message 3 full-duplex, wherein the incremental preamble value for message 3 full-duplex is derived from the message 3 incremental preamble (msg3_DeltaPreamble_FD) for the full-duplex indicator received by UE 120 via RRC configuration information or a System Information Block (SIB). In some aspects, if the incremental preamble value for message 3 full-duplex is not provided, UE 120 may calculate the nominal power value by adding the power offset value to the nominal power value. In some aspects, calculating the nominal power value may include adding the nominal preamble value (P_0_PRE_FD) for full-duplex to the incremental preamble value (delta_preamble_msg3_FD) for message 3 full-duplex, wherein the nominal preamble value for full-duplex is derived from the preamble received target power (preambleReceivedTargetPower_FD) for the full-duplex indicator received by the UE via RRC configuration information or SIB.

[0130] In the second example, if UE 120 establishes a dedicated RRC connection using a Type-2 random access procedure and is not provided with a P0-PUSCH-AlphaSet, or if the UE is performing a PUSCH transmission (or retransmission) corresponding to an uplink grant in a random access response, and the PUSCH transmission occurs within a full-duplex time slot, then UE 120 may calculate a nominal power value (P_0_nominal) for the PUSCH transmission. In some aspects, calculating the nominal power value may include adding a power offset value to the nominal power value. The power offset value may be received by UE 120 via RRC configuration information or via system information. The power offset value may be the same power offset value associated with a Type-1 random access procedure, or it may be a different power offset value. In some aspects, calculating the nominal power value may include adding the nominal preamble value (P_0_PRE) to the incremental preamble value (delta_preamble_msgA_FD) for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the incremental preamble value (msgA_DeltaPreamble_FD) for the full-duplex indicator received by UE 120 via RRC configuration information or SIB. In some aspects, if the incremental preamble value for full-duplex message A is not provided, UE 120 may calculate the nominal power value by adding the power offset value to the nominal power value. In some aspects, calculating the nominal power value may include adding the nominal preamble value (P_0_PRE_FD) for full-duplex use to the incremental preamble value (delta_preamble_msgA_FD) for full-duplex use of message A, wherein the nominal preamble value for full-duplex use is derived from the message A preamble received target power (msgA-preambleReceivedTargetPower_FD) for the full-duplex indicator received by the UE via RRC configuration information or SIB.

[0131] In the third example, if UE 120 establishes a dedicated RRC connection using a Type-1 random access procedure and is not provided with a P0-PUSCH-AlphaSet, or if the UE is performing a PUSCH transmission (or retransmission) corresponding to an uplink grant in a random access response, and the PUSCH transmission occurs within a full-duplex time slot, then UE 120 can calculate the α value for the PUSCH transmission (e.g., In some aspects, calculating the α value may include adding the fixed power offset value to the α value. In some aspects, calculating the α value may include calculating the α value based on the α value of message A (msgA_Alpha_FD) for full-duplex or the α value of message 3 (msg3_Alpha_FD) for full-duplex.

[0132] In the fourth example, if UE 120 establishes a dedicated RRC connection using a Type-1 or Type-2 random access procedure and is not provided with a P0-PUSCH-AlphaSet, or if the UE is performing a PUSCH transmission (or retransmission) corresponding to an uplink grant in a random access response, and the PUSCH transmission occurs in a full-duplex time slot, then UE 120 may calculate an initial transmit power value (P0_UE_PUSCH(0)) for the PUSCH transmission. In some aspects, calculating the initial transmit power value may include obtaining a configuration value for the initial transmit power value. In some aspects, calculating the initial transmit power value may include calculating the initial transmit power value based on parameters received by the UE via an RRC message or a system information message. If the parameters are not provided to UE 120, UE 120 may use a zero value for the parameters.

[0133] As shown by reference numeral 615 in the attached figure, UE 102 may use at least one of the nominal power value, α value, or initial transmit power value to transmit during the PUSCH transmission timing. For example, UE 120 may transmit the PUSCH transmission timing based on the nominal power value, α value, and / or initial transmit power value, and network node 110 may receive the PUSCH transmission timing. This can reduce interference caused by PUSCH transmission in full-duplex time slots and may additionally lead to increased network capacity, extended UE battery life, increased signal-to-noise ratio, and improved quality of service, etc.

[0134] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0135] Figure 7 This is a diagram illustrating an example process 700 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 700 is an example in which a device or UE (e.g., UE 120) performs operations associated with physical uplink shared channel power control.

[0136] like Figure 7 As shown, in some aspects, process 700 may include: calculating at least one of a nominal power value, an α value, or an initial transmission power value for the PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with an uplink grant for a random access response for transmission or retransmission (box 710). For example, (e.g., using...) Figure 9The UE of the Communication Manager 906 described herein may calculate at least one of a nominal power value, an α value, or an initial transmission power value for the timing of PUSCH transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α sets or with an uplink grant for a random access response for transmission or retransmission, as described above.

[0137] like Figure 7 As further shown, in some aspects, process 700 may include: transmitting at the PUSCH transmission timing using at least one of a nominal power value, an α value, or an initial transmission power value (box 720). For example, (e.g., using...) Figure 9 The UE of the transmitting component 904 and / or communication manager 906 described herein may transmit at the PUSCH transmission timing using at least one of the nominal power value, α value or initial transmit power value, as described above.

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

[0139] In the first aspect, calculating the nominal power value, α value, or initial transmit power value includes: calculating the nominal power value, and wherein the random access procedure is a type-1 random access procedure.

[0140] In the second aspect, either alone or in combination with the first aspect, calculating the nominal power value includes adding a fixed nominal power value to a power offset value, wherein the power offset value is received by the UE via an RRC message or a system information message.

[0141] In the third aspect, either alone or in combination with one or more of the first and second aspects, the calculation of the nominal power value includes: adding the nominal preamble value to the incremental preamble value for message 3 full-duplex, wherein the incremental preamble value for message 3 full-duplex is derived from the message 3 incremental preamble for the full-duplex indicator received by the UE via an RRC message or a system information message.

[0142] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the calculation of the nominal power value includes: adding the nominal preamble value for full-duplex to the incremental preamble value for message 3 full-duplex, wherein the nominal preamble value for full-duplex is derived from the preamble received target power for the full-duplex indicator received by the UE via an RRC message or a system information message.

[0143] In the fifth aspect, calculating the nominal power value, α value, or initial transmit power value, either alone or in combination with one or more of the first to fourth aspects, includes: calculating the nominal power value, and wherein the random access procedure is a type-2 random access procedure.

[0144] In the sixth aspect, calculating the nominal power value, either alone or in combination with one or more of the first to fifth aspects, includes adding a fixed nominal power value to a power offset value, wherein the power offset value is received by the UE via an RRC message or a system information message.

[0145] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, calculating the nominal power value includes: adding the nominal preamble value to the incremental preamble value for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the incremental preamble for message A used as a full-duplex indicator received by the UE via an RRC message or a system information message.

[0146] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the calculation of the nominal power value includes: adding the nominal preamble value for full-duplex to the incremental preamble value for message A full-duplex, wherein the nominal preamble value for full-duplex is derived from the message A preamble received by the UE via an RRC message or a system information message as a target power for the full-duplex indicator.

[0147] In the ninth aspect, calculating the nominal power value, α value, or initial transmit power value, alone or in combination with one or more of the first to eighth aspects, includes: calculating the α value, and wherein the random access procedure is a type-1 random access procedure.

[0148] In the tenth aspect, calculating the α value, either alone or in combination with one or more of the first to ninth aspects, includes adding a fixed α value to a fixed offset value.

[0149] In the eleventh aspect, calculating the α value, either alone or in combination with one or more of the first to tenth aspects, includes: calculating the α value based on the α value of message A for full-duplex or the α value of message 3 for full-duplex.

[0150] In the twelfth aspect, calculating the nominal power value, α value, or initial transmission power value, alone or in combination with one or more of the first to eleventh aspects, includes: calculating the initial transmission power value, and wherein the random access procedure is a type-1 random access procedure or a type-2 random access procedure.

[0151] In the thirteenth aspect, calculating the initial transmission power value, either alone or in combination with one or more of the first to twelfth aspects, includes: calculating the initial transmission power value based on a fixed power value.

[0152] In the fourteenth aspect, the calculation of the initial transmit power value, either alone or in combination with one or more of the first to thirteenth aspects, includes: calculating the initial transmit power value based on parameters received by the UE via an RRC message or a system information message.

[0153] although Figure 7 An example box for process 700 is shown, but in some respects, it differs from... Figure 7 Compared to the boxes depicted, process 700 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in process 700 may be executed in parallel.

[0154] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a network node or a device of a network node, according to the present disclosure. Example process 800 is an example in which a device or network node (e.g., network node 110) performs operations associated with physical uplink shared channel power control.

[0155] like Figure 8 As shown, in some aspects, process 800 may include: transmitting configuration information associated with the timing of PUSCH transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure that does not include the transmission of a PUSCH α set, or with an uplink grant for a random access response used for transmission or retransmission (box 810). For example, (e.g., using...) Figure 10 The network node of the transmitting component 1004 and / or communication manager 1006 described herein can transmit configuration information associated with the timing of PUSCH transmission in a full-duplex time slot, wherein the timing of PUSCH transmission is associated with an RRC connection resulting from a random access procedure that does not include the transmission of the PUSCH α set or with an uplink grant for a random access response used for transmission or retransmission, as described above.

[0156] like Figure 8 As further shown, in some aspects, process 800 may include: receiving communication based on at least one of a nominal power value, an α value, or an initial transmission power value via a PUSCH transmission timing (box 820). For example, (e.g., using...) Figure 10 The network node of the receiving component 1002 and / or communication manager 1006 described herein can receive communication based on at least one of the nominal power value, α value, or initial transmission power value via PUSCH transmission timing, as described above.

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

[0158] In the first aspect, communication is based on nominal power values, and the random access procedure is a Type-1 random access procedure.

[0159] In the second aspect, either alone or in combination with the first aspect, the nominal power value is derived from the sum of a fixed nominal power value and a power offset value, wherein the power offset value is sent by the network node via an RRC message or a system information message.

[0160] In the third aspect, either alone or in combination with one or more of the first and second aspects, the nominal power value is derived from the sum of the nominal preamble value and the incremental preamble value for message 3 full-duplex, wherein the incremental preamble value for message 3 full-duplex is derived from the message 3 incremental preamble for the full-duplex indicator sent by the network node via an RRC message or a system information message.

[0161] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the nominal power value is derived from the sum of the nominal preamble value for full-duplex and the incremental preamble value for message 3 full-duplex, wherein the incremental preamble value for message 3 full-duplex is derived from the target power received by the preamble for the full-duplex indicator sent by the network node via an RRC message or a system information message.

[0162] In the fifth aspect, communication is conducted based on a nominal power value, either alone or in combination with one or more of the first to fourth aspects, and the random access procedure is a type-2 random access procedure.

[0163] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the nominal power value is derived from the sum of a fixed nominal power value and a power offset value, wherein the power offset value is sent by the network node via an RRC message or a system information message.

[0164] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the nominal power value is derived from the sum of the nominal preamble value and the incremental preamble value for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the incremental preamble of message A for the full-duplex indicator sent by the network node via an RRC message or a system information message.

[0165] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, the nominal power value is derived from the sum of the nominal preamble value for full-duplex and the incremental preamble value for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the target power received by the message A preamble for the full-duplex indicator sent by the network node via an RRC message or a system information message.

[0166] In the ninth aspect, communication is conducted based on an α value, either alone or in combination with one or more of the first to eighth aspects, and wherein the random access procedure is a type-1 random access procedure.

[0167] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the α value is derived from the sum of a fixed α value and a fixed offset value.

[0168] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, the α value is derived from the α value of message A for full-duplex or the α value of message 3 for full-duplex.

[0169] In the twelfth aspect, communication is conducted based on an initial transmit power value, either alone or in combination with one or more of the first to eleventh aspects, and wherein the random access procedure is a type-1 random access procedure or a type-2 random access procedure.

[0170] In the thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, the initial transmission power value is derived from a fixed power value.

[0171] In the fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the initial transmit power value is derived from parameters transmitted by network nodes via RRC messages or system information messages.

[0172] although Figure 8 An example box for process 800 is shown, but in some respects, it differs from... Figure 8 Compared to the boxes depicted, process 800 may include additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 800 may be executed in parallel.

[0173] Figure 9This is a diagram illustrating an example device 900 for wireless communication according to the present disclosure. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 906 is combined with... Figure 1 The described communication manager 140. As shown, device 900 can communicate with another device 908 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 902 and transmitting component 904.

[0174] In some respects, device 900 can be configured to perform the functions described herein. Figure 6 One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein (such as...). Figure 7 The process 700) or a combination thereof. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) 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 function or operation of the component.

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

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

[0177] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communications by the receiving component 902 and / or the transmission of communications by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communications.

[0178] The communication manager 906 can calculate at least one of a nominal power value, an α value, or an initial transmit power value for the PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with an uplink grant for a random access response used for transmission or retransmission. The transmission component 904 can transmit during the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmit power value.

[0179] Figure 9 The number and arrangement of components shown are provided as an example. In reality, with... Figure 9 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of (one or more) components shown is executable and described as being composed of Figure 9 Another set of components shown performs one or more functions.

[0180] Figure 10 This is a diagram of an example device 1000 for wireless communication according to the present disclosure. Device 1000 may be a network node, or a network node may include device 1000. In some aspects, device 1000 includes a receiving component 1002, a transmitting component 1004, and / or a communication manager 1006 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1006 is combined with... Figure 1 The described communication manager 150. As shown, device 1000 can communicate with another device 1008 (such as a UE or a network node (such as a CU, DU, RU or base station)) using receiving component 1002 and transmitting component 1004.

[0181] In some respects, device 1000 can be configured to perform the functions described herein. Figure 6 One or more operations as described herein. Additionally or alternatively, the apparatus 1000 may be configured to perform one or more processes described herein (such as...). Figure 8 The process 800) or a combination thereof. In some respects, Figure 10 The illustrated device 1000 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 10 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more of the components in this set may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) 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 function or operation of the component.

[0182] Receiver 1002 may receive communications from device 1008, such as reference signals, control information, data communications, or combinations thereof. Receiver 1002 may provide the received communications to one or more other components of device 1000. In some aspects, receiver 1002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1000. In some aspects, receiver 1002 may include combinations of... Figure 2The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, receiver component 1002 and / or transmitter component 1004 may include or be included in a network interface. The network interface may be configured to acquire and / or output signals for device 1000 via one or more communication links, such as backhaul links, midhaul links, and / or fronthaul links.

[0183] Transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1008. In some aspects, one or more other components of device 1000 may generate communications and provide the generated communications to transmitting component 1004 for transmission to device 1008. In some aspects, transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1008. In some aspects, transmitting component 1004 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1004 may co-located with the receive component 1002 in one or more transceivers.

[0184] The communication manager 1006 may support the operation of the receiving component 1002 and / or the transmitting component 1004. For example, the communication manager 1006 may receive information associated with configuring the reception of communications by the receiving component 1002 and / or the transmission of communications by the transmitting component 1004. Additionally or alternatively, the communication manager 1006 may generate control information and / or provide control information to the receiving component 1002 and / or the transmitting component 1004 to control the reception and / or transmission of communications.

[0185] Transmitting component 1004 can transmit configuration information associated with the PUSCH transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with an RRC connection resulting from a random access procedure that does not include the PUSCH α set, or with an uplink grant for a random access response used for transmission or retransmission. Receiving component 1002 can receive communication based on at least one of a nominal power value, an α value, or an initial transmission power value via the PUSCH transmission timing.

[0186] Figure 10The number and arrangement of components shown are provided as an example. In reality, with... Figure 10 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 10 The two or more components shown can be implemented within a single component, or Figure 10 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 10 The collection of (one or more) components shown is executable and described as being composed of Figure 10 Another set of components shown performs one or more functions.

[0187] The following provides an overview of some aspects of this disclosure:

[0188] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: calculating at least one of a nominal power value, an α value, or an initial transmit power value for a physical uplink shared channel (PUSCH) transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with a radio resource control (RRC) connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with a random access response uplink grant for transmission or retransmission; and transmitting at the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmit power value.

[0189] Aspect 2: According to the method of aspect 1, calculating the nominal power value, the α value or the initial transmission power value includes: calculating the nominal power value, and wherein the random access procedure is a type-1 random access procedure.

[0190] Aspect 3: According to the method of aspect 2, the calculation of the nominal power value includes: adding a fixed nominal power value to a power offset value, wherein the power offset value is received by the UE via an RRC message or a system information message.

[0191] Aspect 4: According to the method of aspect 2, the calculation of the nominal power value includes: adding the nominal preamble value to the incremental preamble value for full-duplex message 3, wherein the incremental preamble value for full-duplex message 3 is derived from the incremental preamble of message 3 for full-duplex indicator received by the UE via an RRC message or a system information message.

[0192] Aspect 5: According to the method of aspect 2, the calculation of the nominal power value includes: adding the nominal preamble value for full-duplex to the incremental preamble value for message 3 full-duplex, wherein the nominal preamble value for full-duplex is derived from the preamble received target power for the full-duplex indicator received by the UE via an RRC message or a system information message.

[0193] Aspect 6: The method according to any one of Aspects 1 to 5, wherein calculating the nominal power value, the α value, or the initial transmit power value comprises: calculating the nominal power value, and wherein the random access procedure is a Type-2 random access procedure.

[0194] Aspect 7: According to the method of aspect 6, calculating the nominal power value includes: adding a fixed nominal power value to a power offset value, wherein the power offset value is received by the UE via an RRC message or a system information message.

[0195] Aspect 8: According to the method of aspect 6, the calculation of the nominal power value includes: adding the nominal preamble value to the incremental preamble value for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the incremental preamble of message A for full-duplex indicator received by the UE via an RRC message or a system information message.

[0196] Aspect 9: According to the method of aspect 6, the calculation of the nominal power value includes: adding the nominal preamble value for full-duplex to the incremental preamble value for message A full-duplex, wherein the nominal preamble value for full-duplex is derived from the message A preamble received by the UE via an RRC message or a system information message as a target power for full-duplex indicator.

[0197] Aspect 10: The method according to any one of Aspects 1 to 9, wherein calculating the nominal power value, the α value, or the initial transmit power value comprises: calculating the α value, and wherein the random access procedure is a Type-1 random access procedure.

[0198] Aspect 11: According to the method of aspect 10, calculating the α value includes: adding a fixed α value to a fixed offset value.

[0199] Aspect 12: According to the method of aspect 10, calculating the α value includes: calculating the α value based on the α value of message A for full duplex or the α value of message 3 for full duplex.

[0200] Aspect 13: The method according to any one of Aspects 1 to 12, wherein calculating the nominal power value, the α value, or the initial transmit power value comprises: calculating the initial transmit power value, and wherein the random access procedure is a Type-1 random access procedure or a Type-2 random access procedure.

[0201] Aspect 14: According to the method of aspect 13, calculating the initial transmission power value includes: calculating the initial transmission power value based on a fixed power value.

[0202] Aspect 15: According to the method of aspect 13, calculating the initial transmit power value includes: calculating the initial transmit power value based on parameters received by the UE via an RRC message or a system information message.

[0203] Aspect 16: A method of wireless communication performed by a network node, the method comprising: transmitting configuration information associated with a Physical Uplink Shared Channel (PUSCH) transmission timing in a full-duplex time slot, wherein the PUSCH transmission timing is associated with a Radio Resource Control (RRC) connection resulting from a random access procedure excluding a PUSCH α set or with a random access response uplink grant for transmission or retransmission; and receiving communication via the PUSCH transmission timing based on at least one of a nominal power value, an α value, or an initial transmission power value.

[0204] Aspect 17: The method according to aspect 16, wherein the communication is performed based on the nominal power value, and wherein the random access procedure is a type-1 random access procedure.

[0205] Aspect 18: According to the method of aspect 17, the nominal power value is derived from the sum of a fixed nominal power value and a power offset value, wherein the power offset value is sent by the network node via an RRC message or a system information message.

[0206] Aspect 19: According to the method of aspect 17, the nominal power value is derived from the sum of the nominal preamble value and the incremental preamble value for full-duplex message 3, wherein the incremental preamble value for full-duplex message 3 is derived from the incremental preamble of message 3 for full-duplex indicator sent by the network node via an RRC message or a system information message.

[0207] Aspect 20: According to the method of aspect 17, wherein the nominal power value is derived from the sum of the nominal preamble value for full-duplex and the incremental preamble value for message 3 full-duplex, wherein the incremental preamble value for message 3 full-duplex is derived from the target power received by the preamble for the full-duplex indicator sent by the network node via an RRC message or a system information message.

[0208] Aspect 21: The method according to any one of Aspects 16 to 20, wherein the communication is performed based on the nominal power value, and wherein the random access procedure is a Type-2 random access procedure.

[0209] Aspect 22: According to the method of aspect 21, the nominal power value is derived from the sum of a fixed nominal power value and a power offset value, wherein the power offset value is sent by the network node via an RRC message or a system information message.

[0210] Aspect 23: According to the method of aspect 21, the nominal power value is derived from the sum of the nominal preamble value and the incremental preamble value for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the incremental preamble of message A for a full-duplex indicator sent by the network node via an RRC message or a system information message.

[0211] Aspect 24: According to the method of aspect 21, the nominal power value is derived from the sum of the nominal preamble value for full-duplex and the incremental preamble value for message A full-duplex, wherein the incremental preamble value for message A full-duplex is derived from the target power received by the message A preamble for the full-duplex indicator sent by the network node via an RRC message or a system information message.

[0212] Aspect 25: The method according to any one of Aspects 16 to 24, wherein the communication is performed according to the α value, and wherein the random access procedure is a Type-1 random access procedure.

[0213] Aspect 26: According to the method of aspect 25, wherein the α value is derived from the sum of a fixed α value and a fixed offset value.

[0214] Aspect 27: According to the method of aspect 25, wherein the α value is derived from the α value of message A for full-duplex or the α value of message 3 for full-duplex.

[0215] Aspect 28: The method according to any one of Aspects 16 to 27, wherein the communication is performed based on the initial transmit power value, and wherein the random access procedure is a Type-1 random access procedure or a Type-2 random access procedure.

[0216] Aspect 29: According to the method of aspect 28, the initial transmission power value is derived from a fixed power value.

[0217] Aspect 30: According to the method of aspect 28, the initial transmit power value is derived from parameters transmitted by the network node via an RRC message or a system information message.

[0218] Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to 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 according to one or more of aspects 1 to 30.

[0219] Aspect 32: 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 being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

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

[0221] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 30.

[0222] Aspect 35: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 30.

[0223] Aspect 36: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0224] Aspect 37: 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 being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 30.

[0225] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit all aspects to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various practices.

[0226] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.

[0227] As used in this article, depending on the context, "meeting the threshold" can mean a value 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, not equal to the threshold, etc.

[0228] As used in this article, the phrase “at least one of the items” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple identical elements (e.g., 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).

[0229] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0230] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors individually or collectively configured to cause the UE to: Calculate at least one of a nominal power value, an α value, or an initial transmission power value for the timing of Physical Uplink Shared Channel (PUSCH) transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with a Radio Resource Control (RRC) connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with a random access response uplink grant for transmission or retransmission. as well as Transmission is performed at the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmission power value.

2. The apparatus of claim 1, wherein, in order for the UE to calculate the nominal power value, the α value, or the initial transmit power value, the one or more processors are configured to cause the UE to calculate the nominal power value, and wherein the random access procedure is a type-1 random access procedure.

3. The apparatus of claim 2, wherein, in order for the UE to calculate the nominal power value, the one or more processors are configured to cause the UE to add a fixed nominal power value to a power offset value, wherein the power offset value is received by the UE via an RRC message or a system information message.

4. The apparatus of claim 2, wherein, in order for the UE to calculate the nominal power value, the one or more processors are configured to cause the UE to add the nominal preamble value to an incremental preamble value for message 3 full-duplex, wherein the incremental preamble value for message 3 full-duplex is derived from the message 3 incremental preamble for a full-duplex indicator received by the UE via an RRC message or a system information message.

5. The apparatus of claim 2, wherein, in order for the UE to calculate the nominal power value, the one or more processors are configured to cause the UE to add a nominal preamble value for full-duplex to an incremental preamble value for message 3 full-duplex, wherein the nominal preamble value for full-duplex is derived from a preamble received target power for a full-duplex indicator received by the UE via an RRC message or a system information message.

6. The apparatus of claim 1, wherein, in order for the UE to calculate the nominal power value, the α value, or the initial transmit power value, the one or more processors are configured to cause the UE to calculate the nominal power value, and wherein the random access procedure is a type-2 random access procedure.

7. The apparatus of claim 6, wherein, in order for the UE to calculate the nominal power value, the one or more processors are configured to cause the UE to add a fixed nominal power value to a power offset value, wherein the power offset value is received by the UE via an RRC message or a system information message.

8. The apparatus of claim 6, wherein, in order for the UE to calculate the nominal power value, the one or more processors are configured to cause the UE to add the nominal preamble value to an incremental preamble value for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the incremental preamble for a full-duplex indicator received by the UE via an RRC message or a system information message.

9. The apparatus of claim 6, wherein, in order for the UE to calculate the nominal power value, the one or more processors are configured to cause the UE to add a nominal preamble value for full-duplex to an incremental preamble value for message A full-duplex, wherein the nominal preamble value for full-duplex is derived from the message A preamble received by the UE via an RRC message or a system information message as a target power for a full-duplex indicator.

10. The apparatus of claim 1, wherein, in order for the UE to calculate the nominal power value, the α value, or the initial transmit power value, the one or more processors are configured to cause the UE to calculate the α value, and wherein the random access procedure is a type-1 random access procedure.

11. The apparatus of claim 10, wherein, in order for the UE to calculate the α value, the one or more processors are configured to cause the UE to add a fixed α value to a fixed offset value.

12. The apparatus of claim 10, wherein, in order for the UE to calculate the α value, the one or more processors are configured to cause the UE to calculate the α value based on message A α value for full-duplex or message 3 α value for full-duplex.

13. The apparatus of claim 1, wherein, in order for the UE to calculate the nominal power value, the α value, or the initial transmit power value, the one or more processors are configured to cause the UE to calculate the initial transmit power value, and wherein the random access procedure is a Type-1 random access procedure or a Type-2 random access procedure.

14. The apparatus of claim 13, wherein, in order for the UE to calculate the initial transmit power value, the one or more processors are configured to cause the UE to calculate the initial transmit power value based on a fixed power value or based on parameters received by the UE via an RRC message or a system information message.

15. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the network node to: Configuration information associated with the timing of Physical Uplink Shared Channel (PUSCH) transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with a Radio Resource Control (RRC) connection resulting from a random access procedure that does not include the transmission of the PUSCH α set, or with a random access response uplink grant for transmission or retransmission. as well as Communication is received via the PUSCH transmission timing based on at least one of the nominal power value, α value, or initial transmission power value.

16. The apparatus of claim 15, wherein the communication is performed based on the nominal power value, and wherein the random access procedure is a Type-1 random access procedure.

17. The apparatus of claim 16, wherein the nominal power value is derived from the sum of a fixed nominal power value and a power offset value, wherein the power offset value is sent by the network node via an RRC message or a system information message.

18. The apparatus of claim 16, wherein the nominal power value is derived from the sum of a nominal preamble value and an incremental preamble value for full-duplex message 3, wherein the incremental preamble value for full-duplex message 3 is derived from the incremental preamble of message 3 for a full-duplex indicator sent by the network node via an RRC message or a system information message.

19. The apparatus of claim 16, wherein the nominal power value is derived from the sum of a nominal preamble value for full-duplex and an incremental preamble value for message 3 full-duplex, wherein the incremental preamble value for message 3 full-duplex is derived from the target power received by the preamble for the full-duplex indicator sent by the network node via an RRC message or a system information message.

20. The apparatus of claim 15, wherein the communication is performed based on the nominal power value, and wherein the random access procedure is a type-2 random access procedure.

21. The apparatus of claim 20, wherein the nominal power value is derived from the sum of a fixed nominal power value and a power offset value, wherein the power offset value is sent by the network node via an RRC message or a system information message.

22. The apparatus of claim 20, wherein the nominal power value is derived from the sum of a nominal preamble value and an incremental preamble value for full-duplex message A, wherein the incremental preamble value for full-duplex message A is derived from the incremental preamble of message A for a full-duplex indicator sent by the network node via an RRC message or a system information message.

23. The apparatus of claim 20, wherein the nominal power value is derived from the sum of a nominal preamble value for full-duplex and an incremental preamble value for message A full-duplex, wherein the incremental preamble value for message A full-duplex is derived from the message A preamble received target power for a full-duplex indicator sent by the network node via an RRC message or a system information message.

24. The apparatus of claim 15, wherein the communication is performed according to the α value, and wherein the random access procedure is a Type-1 random access procedure.

25. The apparatus of claim 24, wherein the α value is derived from the sum of a fixed α value and a fixed offset value.

26. The apparatus of claim 24, wherein the α value is derived from the α value of message A for full-duplex or the α value of message 3 for full-duplex.

27. The apparatus of claim 15, wherein the communication is performed based on the initial transmit power value, and wherein the random access procedure is a Type-1 random access procedure or a Type-2 random access procedure.

28. The apparatus of claim 27, wherein the initial transmit power value is derived from a fixed power value or from parameters transmitted by the network node via an RRC message or a system information message.

29. A method for wireless communication performed by a user equipment (UE), the method comprising: Calculate at least one of a nominal power value, an α value, or an initial transmission power value for the timing of Physical Uplink Shared Channel (PUSCH) transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with a Radio Resource Control (RRC) connection resulting from a random access procedure during which the UE does not receive a set of PUSCH α, or with a random access response uplink grant for transmission or retransmission. as well as Transmission is performed at the PUSCH transmission timing using at least one of the nominal power value, the α value, or the initial transmission power value.

30. A method for wireless communication performed by a network node, the method comprising: Configuration information associated with the timing of Physical Uplink Shared Channel (PUSCH) transmission in a full-duplex time slot, wherein the PUSCH transmission timing is associated with a Radio Resource Control (RRC) connection resulting from a random access procedure that does not include the transmission of the PUSCH α set, or with a random access response uplink grant for transmission or retransmission. as well as Communication is received via the PUSCH transmission timing based on at least one of the nominal power value, α value, or initial transmission power value.

Images