Apparatus and method for uplink power control for sub-band full-duplex operation
Separate uplink power control parameters for sub-band full-duplex and non-sub-band full-duplex operations address interference and link failures, enhancing communication reliability and responsiveness.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-27
- Publication Date
- 2026-04-02
AI Technical Summary
Existing wireless communication technologies face challenges in managing uplink power control for user equipment in sub-band full-duplex operation, leading to increased crosslink interference and link failures due to simultaneous uplink and downlink communications.
Implementing separate uplink power control parameters for sub-band full-duplex and non-sub-band full-duplex operations, allowing for differentiated power levels in transmissions to reduce interference and enhance communication reliability.
This approach reduces crosslink interference and link failures, enabling more responsive and reliable communication by optimizing power control settings for both modes of operation.
Smart Images

Figure CN2024121869_02042026_PF_FP_ABST
Abstract
Description
APPARATUS AND METHOD FOR UPLINK POWER CONTROL FOR SUB-BAND FULL-DUPLEX OPERATIONFIELD
[0001] This disclosure relates to uplink (UL) power control for a user equipment (UE) for wireless communication with a base station in sub-band full-duplex (SBFD) operation.BACKGROUND
[0002] Legacy 3rd Generation Partnership Project (3GPP) wireless communication technologies employ time-division-duplex (TDD) operation over one or more frequency bands to facilitate timely two-way communication between a base station and at least one user equipment (UE) . During TDD operation, a base station may engage in either uplink (UL) or downlink (DL) communication with the at least one UE during any particular time period. More recently, the use of full-duplex (FD) operation at a base station has been considered as an alternative to non-FD (e.g., TDD) operation. During FD operation, UL and DL communication between the base station and the at least one UE may occur simultaneously over one or more time periods. Use of FD operation may provide one or more benefits, such as more responsive (e.g., lower latency) communication relative to non-FD communication.BRIEF DESCRIPTION OF THE DRAWINGS
[0003] The present disclosure will be readily understood and enabled by the detailed description and accompanying figures of the drawings. Like reference numerals may designate like features and structural elements. Figures and corresponding descriptions are provided as non-limiting examples of aspects, implementations, etc., of the present disclosure, and references to "an" or “one” aspect, implementation, etc., may not necessarily refer to the same aspect, implementation, etc., and may mean at least one, one or more, etc.
[0004] FIG. 1 is a block diagram of an example wireless network, according to various aspects of the present disclosure.
[0005] FIG. 2 is a block diagram illustrating sub-band full-duplex (SBFD) and non-SBFD operation at a base station, according to various aspects of the present disclosure.
[0006] FIG. 3A is a textual block diagram illustrating Transmission Configuration Indication (TCI) state information elements (IEs) associated with different values of a unified TCI state type that reference uplink power control parameters, according to various aspects of the present disclosure.
[0007] FIGS. 3B and 3C are textual block diagrams illustrating uplink power control and serving cell configuration IEs providing power control parameters for SBFD and non-SBFD operation, according to various aspects of the present disclosure.
[0008] FIGS. 3D and 3E are textual block diagrams illustrating uplink power control IEs providing power control parameters for SBFD and non-SBFD operation, according to various aspects of the present disclosure.
[0009] FIG. 4A is a textual block diagram illustrating a TCI state IE for a joint unified TCI state type referencing power control parameters for SBFD and non-SBFD operation, according to various aspects of the present disclosure.
[0010] FIG. 4B is a textual block diagram illustrating a bandwidth part (BWP) uplink dedicated IE referencing power control parameters for SBFD and non-SBFD operation, according to various aspects of the present disclosure.
[0011] FIG. 4C is a textual block diagram illustrating a serving cell configuration IE referencing power control parameters for SBFD operation, according to various aspects of the present disclosure.
[0012] FIG. 4D is a textual block diagram illustrating a bandwidth part (BWP) uplink dedicated IE referencing power control parameters for SBFD operation, according to various aspects of the present disclosure.
[0013] FIG. 5 is a textual block diagram illustrating a TCI state IE for a separate unified TCI state type referencing power control parameters for SBFD and non-SBFD operation, according to various aspects of the present disclosure.
[0014] FIG. 6 is a flow diagram illustrating a method for a base station to employ uplink power control for SBFD and non-SBFD operation, according to various aspects of the present disclosure.
[0015] FIG. 7 is a flow diagram illustrating a method for a user equipment to employ uplink power control for SBFD and non-SBFD operation, according to various aspects of the present disclosure.
[0016] FIG. 8 is a diagram of an example of components of a device according to various aspects of the present disclosure.DETAILED DESCRIPTION
[0017] The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings may identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description, as other implementations may be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.
[0018] FIG. 1 is an example network 100 according to one or more implementations described herein. Example network 100 may include one or more user equipment (UEs) 110-1 and / or 110-2 (collectively, UEs 110) , a radio access network (RAN) 120 including one or more RAN nodes or base stations (BSs) 122-1 and / or 122-2 (collectively, BS 122) , a core network (CN) 130, application servers 140, and external networks 150.
[0019] The systems and devices of example network 100 may operate in accordance with one or more communication standards, such as Second-Generation (2G) , Third-Generation (3G) , Fourth-Generation (4G) (e.g., Long-Term Evolution (LTE) ) , and / or Fifth-Generation (5G) (e.g., New Radio (NR) ) communication standards of the Third-Generation Partnership Project (3GPP) . Additionally, or alternatively, one or more of the systems and devices of example network 100 may operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., Sixth-Generation (6G) standards, Seventh-Generation (7G) standards, etc. ) , Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., Wireless Metropolitan Area Network (WMAN) , Worldwide Interoperability for Microwave Access (WiMAX) , etc. ) , and more.
[0020] UEs 110 may include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks) . Additionally, or alternatively, UEs 110 may include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs) , pagers, laptop computers, desktop computers, wireless handsets, smartwatches, etc.
[0021] UEs 110 may communicate and establish a connection (e.g., be communicatively coupled) with RAN 120, which may involve one or more wireless channels 114-1 and / or 114-2 (collectively, wireless channels 114) , each of which may include a physical communications interface / layer.
[0022] As shown, UE 110 may also, or alternatively, connect to access point (AP) 116 via connection interface 118, which may include an air interface enabling UE 110 to communicatively couple with AP 116. AP 116 may comprise a wireless local area network (WLAN) , WLAN node, WLAN termination point, etc. The connection 118 may comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and AP 116 may comprise a wireless fidelity router or other AP. While not explicitly depicted in FIG. 1, AP 116 may be connected to another network (e.g., the Internet) without connecting to RAN 120 or CN 130.
[0023] RAN 120 may include one or more RAN nodes 122-1 and 122-2 (referred to collectively as RAN nodes 122, and individually as RAN node 122) that enable channels 114 to be established between UEs 110 and RAN 120. RAN nodes 122 may include network access points configured to provide radio baseband functions for data and / or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi, etc. ) . As examples, therefore, a RAN node may be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc. ) , a next-generation base station (e.g., a 5G base station, NR base station, next-generation eNBs (gNB) , etc. ) . RAN nodes 122 may include a roadside unit (RSU) , a transmission reception point (TRxP or TRP) , and one or more other types of ground stations (e.g., terrestrial access points) . In some scenarios, RAN node 122 may be a dedicated physical device, such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells, or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. Additionally, or alternatively, one or more of RAN nodes 122 can be next-generation eNBs (i.e., gNBs) that can provide E-UTRA user plane and control plane protocol terminations 126, 128 toward UEs 110, and that can be connected to a 5G core network (5GC) 130 via a Next Generation (NG) interface 124.
[0024] Any of the RAN nodes 122 can terminate an air interface protocol and can be the first point of contact for UEs 110. In some implementations, any of the RAN nodes 122 can fulfill various logical functions for the RAN 120, including, but not limited to, radio network controller (RNC) functions, such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEs 110 can be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 122 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency-division multiple-access (OFDMA) communication technique (e.g., for downlink communications) or a single-carrier frequency-division multiple-access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications) , although the scope of such implementations is not necessarily limited in this regard. The OFDM signals can include a plurality of orthogonal subcarriers.
[0025] In some implementations, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 122 to UEs 110, and uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element (RE) . Each resource grid includes resource blocks (RBs) , which describe the mapping of certain physical channels to resource elements. Each RB may include a collection of REs; in the frequency domain, this may represent the smallest quantity of resources that currently may be allocated. There are several different physical downlink channels that are conveyed using such RBs.
[0026] The RAN nodes 122 may be configured to communicate with one another via interface 123. In implementations where the system is an LTE system, interface 123 may be an X2 interface. In NR systems, interface 123 may be an Xn interface. The X2 interface may be defined between two or more RAN nodes 122 (e.g., two or more eNBs / gNBs or a combination thereof) that connect to Evolved Packet Core (EPC) or CN 130, or between two eNBs connecting to an EPC.
[0027] CN 130 may include a plurality of network elements 132, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UEs 110) who are connected to the CN 130 via the RAN 120. In some implementations, CN 130 may include an EPC, a 5G CN, and / or one or more additional or alternative types of CNs. The components of the CN 130 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
[0028] As shown, CN 130, application servers 140, and external networks 150 may be connected to one another via interfaces 134, 136, and 138, which may include IP network interfaces.
[0029] Previously, in Release 18 (Rel-18) of the 3GPP standards, full-duplex (FD) operation was considered as an alternative to time-division-duplex (TDD) operation (e.g., to render more responsive, lower-latency communication) . A possible form of FD operation is sub-band full-duplex (SBFD) operation, in which one or more sub-bands within one or more slots of a frame may be employed for uplink communication, while one or more other sub-bands within the same slots may be used for downlink communication.
[0030] FIG. 2 is a block diagram illustrating both SBFD operation and non-SBFD (e.g., TDD) operation at a base station 122, according to various aspects of the present disclosure. As shown, at base station 122, a TDD slot 220 may include a downlink (DL) bandwidth part (BWP) 202 and an uplink (UL) BWP 204, during which communication between base station 122 and one or more UEs 110 may occur. In some aspects, DL BWP 202 and UL BWP 204 may be separated in time by a guard (G) BWP 206, during which neither UL or DL communication between base station 122 and UEs 110 may occur. Accordingly, at any particular point in time within TDD slot 220, communication between base station 122 and UE 110 is unidirectional (e.g., either in the UL or DL direction) .
[0031] Also shown in FIG. 2 is an SBFD slot 222 during which one or more DL sub-bands (SBs) 212 and one or more UL SBs 214 may be configured. Further, in some aspects, as depicted in FIG. 2, one or more guard (G) SBs 216 may be configured in SBFD slot 222 to separate DL SBs 212 and UL SBs 214, although G SBs 216 may not be present in other aspects. Consequently, UL and DL communication may take place between base station 122 and UEs 110 during SBFD slot 222, thus possibly providing more responsive communication in either or both UL and DL communication, as no time periods exist within SBFD slot 222 during which UL or DL communication is prohibited.
[0032] In some aspects, one or more UEs 110 may only operate in a half-duplex mode. However, when multiple such UEs 110 are communicating concurrently with base station 122, full-duplex communication in SBFD slot 222 may remain beneficial.
[0033] Further, in some aspects, for a UE 110 that is capable of transmission using both symbol types (e.g., SBFD and non-SBFD, sometimes referred to as Configuration-2) , even if only capable of operating in half-duplex mode, different power control settings for transmission by UE 110 for SBFD and non-SBFD operation may be useful. For example, in TDD slot 220, base station 122 may simultaneously employ all antenna elements of base station 122 for DL BWP 202 or UL BWP 204. Conversely, in SBFD slot 222, some antenna elements of base station 122 may be employed for DL SBs 212 while other antenna elements of base station 122 may be simultaneously employed for UL SBs 214. Consequently, use of different power levels in UL transmissions by UEs 110 to base station 122 during SBFD and non-SBFD operation may reduce link failure incidence in some aspects.
[0034] Further, in some aspects, crosslink interference (CLI) between UEs 110 (e.g., a first UE 110 receiving DL communication in downlink SBs 212 from base station 122) may experience interference caused by a second UE 110 transmitting UL communication to base station 122. Under such conditions, use of different (e.g., lower) power levels for transmission in UL SB 214 by the first UE 110 that may negatively impact the second UE 110 may be worthwhile. Accordingly, use of different power levels in UL transmissions by UEs 110 to base station 122 during SBFD and non-SBFD operation may reduce CLI in such cases.
[0035] As is discussed in greater detail below, some aspects of the present disclosure facilitate the provision and use of separate uplink power control parameters for SBFD and non-SBFD operation. In some aspects, a UE may receive at least one message including one or more sets of first UL transmission power control parameters for SBFD operation, and one or more sets of second UL transmission power control parameters for non-SBFD operation. The UE may configure a transceiver for data transmission in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameter, and configure the transceiver for data transmission in one or more non-SBFD slots using a second set of the one or more sets of second UL transmission power control parameters.
[0036] FIG. 3A is a textual block diagram illustrating Transmission Configuration Indication (TCI) state information elements (IEs) in 3GPP communications associated with different values of a unified TCI state type (e.g., UnifiedTCI-StateType) that reference uplink power control parameters, according to various aspects of the present disclosure. In some aspects, the TCI state IEs may be transmitted in a Radio Resource Control (RRC) message (e.g., an RRC Reconfiguration message) by base station 122 to a particular UE 110.
[0037] In some aspects, when a unified TCI state type possesses a “joint” value, an associated TCI state information element may include both UL and DL channel configuration parameters for that TCI state. Conversely, when a unified TCI state type possesses a “separate” value, different TCI states and associated configuration parameters may be employed for the UL and DL channels. Further, in some aspects, the UL channels to which the UL configuration parameters may apply may include a Sounding Reference Signal (SRS) , a Physical UL Control Channel (PUCCH) , and a Physical UL Shared Channel (PUSCH) .
[0038] Accordingly, in some aspects, as shown in FIG. 3A, a joint value for the unified TCI state type indicates that base station 122 may provide a TCI state information element 302 (e.g., TCI-State) for a TCI state (e.g., indicated by a tci-StateId field) that includes various UL and DL parameters. Similarly, in some aspects, a separate value for the unified TCI state type indicates that base station 122 may provide a TCI state information element for a TCI state that includes configuration parameters for either the DL or UL configuration parameters. More specifically, a TCI state information element 304 (e.g., TCI-UL-State-r17) associated with a TCI state (e.g., indicated by a tci-UL-StateId-r17 field) may carry configuration parameters for the UL channels.
[0039] In both cases for the unified TCI state type shown in FIG. 3A, the related TCI state information element may include information that provides or references UL power control configuration parameters for the corresponding TCI state. For example, TCI state information elements 302 and 304 each include an RS index (e.g., pathlossReferenceRS-Id-r17) for obtaining a downlink pathloss estimate for PUSCH, PUCCH, and SRS transmissions for the associated TCI state. Also included may be a UL power control parameter identifier 306 (e.g., ul-powerControl-r17) that references UL power control parameters for the corresponding TCI state.
[0040] In some aspects, if UL power control parameter identifier 306 is configured as part of a TCI configuration, the UL power control parameters being referenced may apply per serving cell. Otherwise, in some aspects, as described below, if UL power control parameter identifier 306 is configured within a BWP UL-related configuration (e.g., a BWP-UplinkDedicated information element) if not configured for any TCI state information element (e.g., whether a joint or separate unified TCI state type) of this serving cell. Further, in some aspects, UL power control parameter identifier 306 may be either configured in all BWP UL-related configurations or none of the BWP UL-related configurations of the serving cell.
[0041] In some aspects, while several UL power control parameters are discussed below relative to SBFD and non-SBFD operations, other UL power control parameters may be determined based on other information elements (e.g., PUSCH-PowerControl for the PUSCH and PUCCH-PowerControl for the PUCCH, which may be configured per BWP of the serving cell) .
[0042] FIGS. 3B through 3E illustrate examples in which separate UL power control parameters for SBFD and non-SBFD operations are provided when the unified TCI state type possesses a joint value and TCI state information element 302 references a single UL power control configuration (e.g. for SBFD operation or non-SBFD operation) .
[0043] For example, FIGS. 3B and 3C are textual block diagrams illustrating uplink power control and serving cell configuration information elements (IEs) providing power control parameters for SBFD and non-SBFD operation, according to various aspects of the present disclosure. In FIG. 3B, a UL power control IE 308A that is associated with UL power control parameter identifier 306 in TCI state IE 302 includes UL power control parameters for non-SBFD operation: PUSCH power control parameters 310A (e.g., P0AlphaSetforPUSCH-r17) , PUCCH power control parameters 310B (e.g., P0AlphaSetforPUCCH-r17) , and SRS power control parameters 310C (e.g., P0AlphaSetforSRS-r17) .
[0044] Moreover, in some aspects, each of PUSCH power control parameters 310A, PUCCH power control parameters 310B, and SRS power control parameters 310C is specified by an associated number of UL power control parameters 312 (e.g., P0AlphaSet-r17) for non-SBFD operation, as illustrated in FIG. 3B. Further, in some aspects, UL power control parameters 312 may include a P0 value (e.g., p0-r17) , an “alpha” value (e.g., alpha-r17) , and / or a closed loop index value (e.g., closedLoopIndex-r17) . Generally, in some aspects, the P0 value indicates a desired amount of received power at the receiver (e.g., base station 122) . Also, in some aspects, the alpha value indicates how much compensation (e.g., in terms of decibels (dB) ) UE 110 should apply to compensate for signal pathloss. In some aspects, the closed loop index is a value indicating how much the current transmission power at UE 110 should be changed upon reception of a transmission power control (TPC) command based on one of two adjustment states. In some aspects, UL power control parameters 312 may be employed as described in 3GPP Technical Specification (TS) 38.213, Section 7 (e.g., in Rel-17) .
[0045] In some aspects, UL power control parameters 312 include those UL power control parameters that may be different during SBFD operation and non-SBFD operation. Accordingly, other UL power control parameters, such as the pathloss reference signal identifier (e.g., pathlossReferenceRS-Id-r17 of FIG. 3A) is not included in UL power control parameters 312 because the reference signal identifier is the same in both SBFD and non-SBFD operation.
[0046] In the example of FIG. 3B, while UL power control IE 308A includes UL power control parameters 312 for non-SBFD operation, a serving cell configuration IE 314 includes offset UL power control parameters 316 (e.g., SBFD-UL-Power-Control) for SBFD operation. Accordingly, in some aspects, offset UL power control parameters 316 include a P0 offset value (e.g., p0-offset) , an alpha offset value (e.g., alpha-offset) , and a closed loop index offset value (e.g., closedLoopIndex) . In some aspects, each of offset UL power control parameters 316 provides an offset or other value that is relative to or based on the corresponding one of UL power control parameters 312 (e.g., p0AlphaSet-r17) provided in UL power control IE 308A.
[0047] In the example of FIG. 3B, in some aspects, the P0 offset value may be selected from a list of integers (e.g., -3, -1, 0, or 3) that is to be added to the P0 value used for non-SBFD operation to generate a P0 value for SBFD operation in the corresponding TCI state. Also, in some aspects, the alpha offset value may be selected from a list of integers (e.g., -0.3, 0, or 0.3) that is to be added to the alpha value employed for non-SBFD operation for SBFD operation. Further, the resulting alpha value may be constrained to an acceptable range of values (e.g., between 0 and 1 inclusive) . Additionally, in some aspects, the closed loop index offset value may be selected from two values indicating “same” or “complement” , indicating that are two possible adjustment states. For example, if the closed loop index offset indicates “same” , the closed loop adjustment state for SBFD operation is the same as that used for non-SBFD operation (e.g., 0 remains 0, or 1 remains 1) . Otherwise, if the closed loop index value is “complement” , the complement of the current closed loop index for SBFD operation is different than that used for non-SBFD operation (e.g., 0 becomes 1, or 1 becomes 0) .
[0048] Further, in the example of FIG. 3B, as offset UL power control parameters 316 are provided in serving cell configuration IE 314, the same offset UL power control parameters 316 may be employed for all TCI states associated with the serving cell.
[0049] While FIG. 3B depicts UL power control IE 308A as including UL power control parameters 312 for non-SBFD operation and serving cell configuration IE 314 as including offset UL power control parameters 316 for SBFD operation, FIG. 3C depicts opposing aspects. More specifically, in FIG. 3C, UL power control IE 308B includes UL power control parameters 322 for SBFD operation (e.g., for each of PUSCH power control parameters 320A, PUCCH power control parameters 320B, and SRS power control parameters 320C) and serving cell configuration IE 324 as including offset UL power control parameters 326 (e.g., as provided within TDD-UL-Power-Control) for non-SBFD operation. Other aspects described above in conjunction with FIG. 3B may be applicable to aspects associated with FIG. 3C.
[0050] In yet other aspects, UL power control parameters, or offsets thereof, for both non-SBFD and SBFD operation may be provided in a UL power control IE. For example, FIG. 3D illustrates a UL power control IE 308C (e.g., including PUSCH power control parameters 330A, PUCCH power control parameters 330B, and SRS power control parameters 330C) , each of which includes UL power control parameters 332 that include UL power control parameters (e.g., p0-r17, alpha-r17, and closedLoopIndex-r17) for non-SBFD operation and UL power control parameters (e.g., p0-SBFD, alpha-SBFD, and closedLoopIndex-SBFD) for SBFD operation. Alternatively, in other aspects, the UL power control parameters for SBFD operation may be provided as offsets relative to UL power control parameters for non-SBFD operation, as discussed above in connection with FIG. 3B.
[0051] Oppositely, FIG. 3E illustrates a UL power control IE 308D (e.g., including PUSCH power control parameters 340A, PUCCH power control parameters 340B, and SRS power control parameters 340C) , each of which includes UL power control parameters 342 that include UL power control parameters (e.g., p0-r17, alpha-r17, and closedLoopIndex-r17) for non-SBFD operation and UL power control parameters (e.g., p0-TDD, alpha-TDD, and closedLoopIndex-TDD) for non-SBFD operation. Alternatively, in yet other aspects, the UL power control parameters for non-SBFD operation may be provided as offsets relative to UL power control parameters for SBFD operation, as discussed above in connection with FIG. 3C.
[0052] Consequently, relative to aspects associated with FIGS. 3D and 3E, different UL power control parameters for SBFD operation in FIG. 3D and for non-SBFD operation in FIG. 3E may be specified for each TCI state, instead of a single set of UL power control parameters specified in serving cell configuration IE 314 or 324, as discussed above in FIGS. 3B and 3C, respectively.
[0053] In other aspects when the unified TCI state type is “joint” , a TCI state IE may include separate identifiers for the UL power control parameters for SBFD and non-SBFD operation. More specifically, FIG. 4A is a textual block diagram illustrating a TCI state IE 402 for a joint unified TCI state type that references power control parameters for non-SBFD operation (e.g., via a UL power control parameter identifier 306 (such as ul-powerControl-r17) and SBFD operation (e.g., via a UL power control parameter identifier 404 (such as ul-powerControl-SBFD) ) , according to various aspects of the present disclosure. Accordingly, each UL power control parameter identifier 306 and 404 may reference an associated UL power control IE (e.g., UL power control IE 308A of FIG. 3B or UL power control IE 308B of FIG. 3C) .
[0054] In some aspects in which none of the TCI state IEs 402 are associated with or reference UL power control parameters, such parameters may be specified in relation to bandwidth part (BWP) UL dedicated configurations. For example, FIG. 4B is a textual block diagram illustrating a BWP UL dedicated IE 412 referencing power control parameters for SBFD and non-SBFD operation, according to various aspects of the present disclosure. More specifically, BWP UL dedicated IE 412 may include UL power control parameter identifier 306 (e.g., ul-powerControl-r17) for non-SBFD UL power control parameters and UL power control parameter identifier 404 (e.g., ul-powerControl-SBFD) for SBFD power control parameters, in a manner similar to that discussed above in conjunction with FIG. 4A.
[0055] Further, in some aspects, alternative ways of providing two UL power control parameter identifiers may be implemented other than solely within TCI state IE 402 (e.g., as shown in FIG. 4A) and / or BWP uplink dedicated IE (e.g., as illustrated in FIG. 4B) . For example, first UL power control parameter identifier 306 (e.g., ul-powerControl-r17) for non-SBFD operation may reside within TCI state IE 402 (e.g., as shown in FIG. 3A) , while second UL power control parameter identifier 404 (e.g., ul-powerControl-SBFD) may be provided in serving cell configuration IE 414, as depicted in FIG. 4C. Further, as described above, when none of the TCI state IEs 402 are associated with or reference UL power control parameters for non-SBFD operation, such parameters (e.g., via first UL power control parameter identifier 306) may be referenced in a bandwidth part (BWP) UL dedicated configuration.
[0056] Similarly, in some aspects, first UL power control parameter identifier 306 (e.g., ul-powerControl-r17) for non-SBFD operation may reside within TCI state IE 402, while second UL power control parameter identifier 404 (e.g., ul-powerControl-SBFD) may be provided in an BWP uplink dedicated configuration IE 422 (e.g., BWP-UplinkDedicated IE) , as shown in FIG. 4D. Further, as described above, when none of the TCI state IEs 402 are associated with or reference UL power control parameters for non-SBFD operation, both a first UL power control parameter identifier 306 for non-SBFD operation and a second UL power control parameter identifier 404 for SBFD operation may be referenced in a bandwidth part (BWP) UL dedicated configuration IE, as shown in FIG. 4B.
[0057] In some aspects, instead of each TCI “codepoint” , as described in the 3GPP standards, being mapped to a TCI state that is associated with both SBFD and non-SBFD operations, each TCI codepoint may be mapped to separate first and second TCI states for SBFD and non-SBFD operations, respectively. In such cases, the TCI state associated with non-SBFD operation may include a UL power control parameter identifier 306 (e.g. ul-powerControl-r17, as shown in FIG. 4A) , and the TCI state associated with SBFD operation may include a separate UL power control parameter identifier 404 (e.g., ul-powerControl-SBFD of FIG. 4A) , where each of the UL power control parameter identifiers 306 and 404 may refer to different sets of UL power control parameters.
[0058] Further, with respect to any of the aspects discussed above, in some cases one or more TCI state IEs 302 or 402 may only include a single UL power control parameter identifier (e.g., UL power control parameter identifier 306 of FIG. 3A) without any indication of a second UL power control parameter identifier or set of parameters for that TCI state. In such cases, UE 110 may presume that the set of power control parameters referenced by the single UL power control parameter identifier are applicable during SBFD and non-SBFD operation.
[0059] Each of the aspects discussed above are particularly described with respect to a joint unified TCI state type. However, as mentioned earlier, a unified TCI state type may instead be set as “separate” . Consequently, each of the above aspects regarding the setting of UL power control parameters for both SBFD and non-SBFD operation may be applied to a separate unified TCI state type. For example, FIG. 5 is a textual block diagram illustrating a TCI state IE 502 (e.g., TCI-UL-State-r17) for a separate UnifiedTCI-StateType referencing power control parameters for both SBFD and non-SBFD operation, according to various aspects of the present disclosure. More specifically, TCI state IE 502 may include a first UL power control parameter identifier 306 (e.g., ul-powerControl-r17) for non-SBFD operation and a second UL power control parameter identifier 404 (e.g., ul-powerControl-SBFD) for SBFD operation, in a manner similar to that shown in FIG. 4A) . Other examples above, as described in conjunction with FIGS. 3A through 3E, FIGS. 4B through 4D, and FIG. 5, may be applicable with respect to TCI state UE 502 of FIG. 5.
[0060] FIG. 6 is a flow diagram illustrating a method 600 for a base station (e.g., base station 122 of FIGS. 1 and 2) to employ uplink power control for SBFD and non-SBFD operation, according to various aspects of the present disclosure. In method 600, at Act 602, at least one message may be generated that includes one or more sets of first UL transmission power control parameters for SBFD operation and one or more sets of second UL transmission power control parameters for non-SBFD operation. At Act 604, the at least one message may be transmitted to a UE (e.g., UE 110 of FIGS. 1 and 2) .
[0061] FIG. 7 is a flow diagram illustrating a method 700 for a UE (e.g. UE 110 of FIGS. 1 and 2) to employ uplink power control for SBFD and non-SBFD operation, according to various aspects of the present disclosure. In method 700, at Act 702, at least one message may be received via a transceiver of the UE, where the message includes one or more sets of first UL transmission power control parameters for SBFD operation and one or more sets of second UL transmission power control parameters for non-SBFD operation. At Act 704, first data may be transmitted via the transceiver in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters. At Act 706, second data may be transmitted via the transceiver in one or more non-SBFD slots using a second set of the one or more sets of second UL transmission power control parameters.
[0062] As can be seen from the foregoing disclosure, aspects of the present disclosure may provide low-latency, highly responsive communications between a UE and a base station via full-duplex (e.g., SBFD) operation by way of facilitating separate UL power control transmission parameters for non-full-duplex and full-duplex operation, thus potentially reducing the number of communication failures in the UL channels from the UE to the base station.
[0063] Above are several flow diagrams outlining example methods and exchanges of messages. In this description and the appended claims, use of the term “determine” with reference to some entity (e.g., parameter, variable, and so on) in describing a method step or function is to be construed broadly. For example, “determine” is to be construed to encompass, for example, receiving and parsing a communication that encodes the entity or a value of an entity. “Determine” should be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores the entity or value for the entity. “Determine” should be construed to encompass computing or deriving the entity or value of the entity based on other quantities or entities. “Determine” should be construed to encompass any manner of deducing or identifying an entity or value of the entity.
[0064] As used herein, the term “identify” , when used with reference to some entity or value of an entity, is to be construed broadly as encompassing any manner of determining the entity or value of the entity. For example, the term “identify” is to be construed to encompass, for example, receiving and parsing a communication that encodes the entity or a value of the entity. The term “identify” should be construed to encompass access. . . ing and reading memory (e.g., device queue, lookup table, register, device memory, remote memory, and so on) that stores the entity or value for the entity.
[0065] As used herein, the term “encode” , when used with reference to some entity or value of an entity, is to be construed broadly as encompassing any manner or technique for generating a data sequence or signal that communicates the entity to another component.
[0066] As used herein, the term “select” , when used with reference to some entity or value of an entity, is to be construed broadly as encompassing any manner of determining the entity or value of the entity from amongst a plurality or range of possible choices. For example, the term “select” is to be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores the entities or values for the entity and returning one entity or entity value from amongst those stored. The term “select” is to be construed as applying one or more constraints or rules to an input set of parameters to determine an appropriate entity or entity value. The term “select” is to be construed as broadly encompassing any manner of choosing an entity based on one or more parameters or conditions.
[0067] As used herein, the term “derive” , when used with reference to some entity or value of an entity, is to be construed broadly. “Derive” should be construed to encompass accessing and reading memory (e.g., lookup table, register, device memory, remote memory, and so on) that stores some initial value or foundational values and performing processing and / or logical / mathematical operations on the value or values to generate the derived entity or value for the entity. The term “derive” should be construed to encompass computing or calculating the entity or value of the entity based on other quantities or entities. The term “derive” should be construed to encompass any manner of deducing or identifying an entity or value of the entity.
[0068] As used herein, the term “indicate” , when used with reference to some entity (e.g., parameter or setting) or value of an entity, is to be construed broadly as encompassing any manner of communicating the entity or value of the entity, either explicitly or implicitly. For example, bits within a transmitted message may be used to explicitly encode an indicated value or may encode an index or other indicator that is mapped to the indicated value by prior configuration. The absence of a field within a message may implicitly indicate a value of an entity based on prior configuration.
[0069] Examples
[0070] Example 1 includes a baseband processor configured to perform operations including: receiving, via a transceiver of a user equipment (UE) , at least one message including: one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, and one or more sets of second UL transmission power control parameters for non-SBFD operation; configuring the transceiver for data transmission in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters; and configuring the transceiver for data transmission in one or more non-SBFD slots using a second set of the one or more sets of second UL transmission power control parameters.
[0071] Example 2 includes the subject matter of Example 1, including or omitting optional elements, wherein one of the one or more sets of first UL transmission power control parameters and one of the one or more sets of second UL transmission power control parameters correspond with a same transmission configuration indication (TCI) state.
[0072] Example 3 includes the subject matter of Example 1, including or omitting optional elements, wherein each of the one or more sets of first UL transmission power control parameters and the one or more sets of second UL transmission power control parameters corresponds with a different transmission configuration indication (TCI) state.
[0073] Example 4 includes the subject matter of Example 1, including or omitting optional elements, wherein the at least one message includes a transmission configuration indication (TCI) state information element based on a unified TCI state type.
[0074] Example 5 includes the subject matter of Example 4, including or omitting optional elements, wherein the unified TCI state type includes a joint unified TCI state type.
[0075] Example 6 includes the subject matter of Example 4, including or omitting optional elements, wherein the unified TCI state type includes a separate unified TCI state type.
[0076] Example 7 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a serving cell configuration information element including a single set of the one or more sets of first UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of second UL transmission power control parameters.
[0077] Example 8 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a bandwidth part (BWP) UL dedicated configuration information element including a single set of the one or more sets of first UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of second UL transmission power control parameters.
[0078] Example 9 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of first UL transmission power control parameters; and a serving cell configuration information element including a single set of the one or more sets of second UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of first UL transmission power control parameters.
[0079] Example 10 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of first UL transmission power control parameters; and a bandwidth part (BWP) UL dedicated configuration information element including a single set of the one or more sets of second UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of first UL transmission power control parameters.
[0080] Example 11 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including: one of the one or more sets of first UL transmission power control parameters; and one of the one or more sets of second UL transmission power control parameters including relative indications referring to the one of the one or more sets of first UL transmission power control parameters.
[0081] Example 12 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including: one of the one or more sets of second UL transmission power control parameters; and one of the one or more sets of first UL transmission power control parameters including relative indications referring to the one of the one or more sets of second UL transmission power control parameters.
[0082] Example 13 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including: one of the one or more sets of first UL transmission power control parameters; and one of the one or more sets of second UL transmission power control parameters.
[0083] Example 14 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a first UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a second UL power control information element corresponding to the TCI state information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0084] Example 15 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a first UL power control information element corresponding to the TCI state information element, the first UL power control information element including one of the one or more sets of second UL transmission power control parameters; a serving cell configuration information element; and a second UL power control information element corresponding to the serving cell configuration information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0085] Example 16 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a first UL power control information element corresponding to the TCI state information element, the first UL power control information element including one of the one or more sets of second UL transmission power control parameters; a bandwidth part (BWP) UL dedicated configuration information element; and a second UL power control information element corresponding to the BWP UL dedicated configuration information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0086] Example 17 includes the subject matter of Example 4, including or omitting optional elements, wherein the at least one message further includes: a bandwidth part (BWP) UL dedicated information element; a first UL power control information element corresponding to the BWP UL dedicated configuration information element, the first UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a second UL power control information element corresponding to the BWP UL dedicated configuration information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0087] Example 18 includes a method for a user equipment (UE) , the method including: receiving at least one message including: one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, and one or more sets of second UL transmission power control parameters for non-SBFD operation; transmitting first data in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters; and transmitting second data in one or more non-SBFD slots using a second set of the one or more sets of second UL transmission power control parameters.
[0088] Example 19 includes the subject matter of Example 18, including or omitting optional elements, wherein: the first set of the one or more sets of first UL transmission power control parameters and the second set of the one or more sets of the second UL transmission power control parameters correspond with a first transmission configuration indication (TCI) state; the at least one message further includes a third set of the one or more sets of second UL transmission power control parameters corresponding with a second TCI state; the second TCI state is not associated with any of the one or more sets of first UL transmission power control parameters; and the method further includes: transmitting third data in one or more SBFD slots and fourth data in one or more non-SBFD slots using the third set of the one or more sets of second UL transmission power control parameters corresponding with the second TCI state.
[0089] Example 20 includes a user equipment (UE) including: a transceiver, a memory storing instructions; and one or more processors coupled to the memory and the transceiver, wherein the one or more processors, when executing the instructions, cause the UE to perform operations including: receiving, via the transceiver, at least one message including: one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, and one or more sets of second UL transmission power control parameters for non-SBFD operation, wherein each of the one or more sets of first UL transmission power control parameters and the one or more sets of second UL transmission power control parameters corresponds with a different transmission configuration indication (TCI) state; transmitting, via the transceiver, first data in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters, wherein the first set is associated with a first TCI state; and transmitting, via the transceiver, second data in one or more non-SBFD slots using a second set of the one or more sets of the second UL transmission power control parameters, wherein the second set is associated with a second TCI state different from the first TCI state, and wherein a first TCI codepoint is mapped to the first TCI state and the second TCI state.
[0090] Example 21 includes a baseband processor configured to perform operations including: generating at least one message including: one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, and one or more sets of second UL transmission power control parameters for non-SBFD operation; and transmitting, via a transceiver of a base station (BS) to a user equipment (UE) , the at least one message.
[0091] Example 22 includes the subject matter of Example 21, including or omitting optional elements, wherein one of the one or more sets of first UL transmission power control parameters and one of the one or more sets of second UL transmission power control parameters correspond with a same transmission configuration indication (TCI) state.
[0092] Example 23 includes the subject matter of Example 21, including or omitting optional elements, wherein each of the one or more sets of first UL transmission power control parameters and the one or more sets of second UL transmission power control parameters corresponds with a different transmission configuration indication (TCI) state.
[0093] Example 24 includes the subject matter of Example 21, including or omitting optional elements, wherein the at least one message includes a transmission configuration indication (TCI) state information element based on a unified TCI state type.
[0094] Example 25 includes the subject matter of Example 24, including or omitting optional elements, wherein the unified TCI state type includes a joint unified TCI state type.
[0095] Example 26 includes the subject matter of Example 24, including or omitting optional elements, wherein the unified TCI state type includes a separate unified TCI state type.
[0096] Example 27 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a serving cell configuration information element including a single set of the one or more sets of first UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of second UL transmission power control parameters.
[0097] Example 28 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a bandwidth part (BWP) UL dedicated configuration information element including a single set of the one or more sets of first UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of second UL transmission power control parameters.
[0098] Example 29 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of first UL transmission power control parameters; and a serving cell configuration information element including a single set of the one or more sets of second UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of first UL transmission power control parameters.
[0099] Example 30 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of first UL transmission power control parameters; and a bandwidth part (BWP) UL dedicated configuration information element including a single set of the one or more sets of second UL transmission power control parameters, the single set including relative indications referring to the one of the one or more sets of first UL transmission power control parameters.
[0100] Example 31 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including: one of the one or more sets of first UL transmission power control parameters; and one of the one or more sets of second UL transmission power control parameters including relative indications referring to the one of the one or more sets of first UL transmission power control parameters.
[0101] Example 32 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including: one of the one or more sets of second UL transmission power control parameters; and one of the one or more sets of first UL transmission power control parameters including relative indications referring to the one of the one or more sets of second UL transmission power control parameters.
[0102] Example 33 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a UL power control information element corresponding to the TCI state information element, the UL power control information element including: one of the one or more sets of first UL transmission power control parameters; and one of the one or more sets of second UL transmission power control parameters.
[0103] Example 34 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a first UL power control information element corresponding to the TCI state information element, the UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a second UL power control information element corresponding to the TCI state information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0104] Example 35 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a first UL power control information element corresponding to the TCI state information element, the first UL power control information element including one of the one or more sets of second UL transmission power control parameters; a serving cell configuration information element; and a second UL power control information element corresponding to the serving cell configuration information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0105] Example 36 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a first UL power control information element corresponding to the TCI state information element, the first UL power control information element including one of the one or more sets of second UL transmission power control parameters; a bandwidth part (BWP) UL dedicated configuration information element; and a second UL power control information element corresponding to the BWP UL dedicated configuration information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0106] Example 37 includes the subject matter of Example 24, including or omitting optional elements, wherein the at least one message further includes: a bandwidth part (BWP) UL dedicated information element; a first UL power control information element corresponding to the BWP UL dedicated configuration information element, the first UL power control information element including one of the one or more sets of second UL transmission power control parameters; and a second UL power control information element corresponding to the BWP UL dedicated configuration information element, the second UL power control information element including one of the one or more sets of first UL transmission power control parameters.
[0107] Example 38 includes a method for a base station (BS) , wherein the method includes: generating at least one message including: one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, and one or more sets of second UL transmission power control parameters for non-SBFD operation; and transmitting the at least one message to a user equipment (UE) .
[0108] Example 39 includes the subject matter of Example 38, including or omitting optional elements, wherein: the first set of the one or more sets of first UL transmission power control parameters and the second set of the one or more sets of the second UL transmission power control parameters correspond with a first transmission configuration indication (TCI) state; the at least one message further includes a third set of the one or more sets of second UL transmission power control parameters corresponding with a second TCI state; the second TCI state is not associated with any of the one or more sets of first UL transmission power control parameters; and the third set corresponds with SBFD operation and non-SBFD operation associated with the second TCI state.
[0109] Example 40 includes a base station (BS) including: a transceiver, a memory storing instructions; and one or more processors coupled to the memory and the transceiver, wherein the one or more processors, when executing the instructions, cause the BS to perform operations including: transmitting, via the transceiver to a user equipment (UE) , at least one message including: one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, and one or more sets of second UL transmission power control parameters for non-SBFD operation, wherein each of the one or more sets of first UL transmission power control parameters and the one or more sets of second UL transmission power control parameters corresponds with a different transmission configuration indication (TCI) state; receiving, via the transceiver from the UE, first data in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters, wherein the first set is associated with a first TCI state; and receiving, via the transceiver from the UE, second data in one or more non-SBFD slots using a second set of the one or more sets of the second UL transmission power control parameters, wherein the second set is associated with a second TCI state different from the first TCI state, and wherein a first TCI codepoint is mapped to the first TCI state and the second TCI state.
[0110] FIG. 8 is a diagram of an example of components of a wireless communication device according to one or more implementations described herein. In some implementations, the device 800 can include application circuitry 802, baseband circuitry 804, RF circuitry 806, front-end module (FEM) circuitry 808, one or more antennas 810, and power management circuitry (PMC) 812 coupled together at least as shown. The components of the illustrated device 800 can be included in a UE or a RAN node. In some implementations, the device 800 can include fewer elements (e.g., a RAN node may not utilize application circuitry 802, and instead include a processor / controller to process IP data received from a CN or an Evolved Packet Core (EPC) ) . In some implementations, the device 800 can include additional elements such as, for example, memory / storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device 800, etc. ) , or input / output (I / O) interface. In other implementations, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
[0111] The application circuitry 802 can include one or more application processors. For example, the application circuitry 802 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor (s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) . The processors can be coupled with or can include memory / storage and can be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 800. In some implementations, processors of application circuitry 802 can process IP data packets received from an EPC.
[0112] The baseband circuitry 804 can include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 804 can include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806. Baseband circuitry 804 can interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806. For example, in some implementations, the baseband circuitry 804 can include a 3G baseband processor 804A, a 4G baseband processor 804B, a 5G baseband processor 804C, or other baseband processor (s) 804D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, etc. ) .
[0113] The baseband circuitry 804 (e.g., one or more of baseband processors 804A-D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 806. In other implementations, some or all of the functionality of baseband processors 804A-D can be included in modules (e.g., sets of executable instructions) stored in the memory 804G or other machine-readable or computer-readable medium (e.g., a non-transitory machine-readable or computer-readable storage medium) and executed via a Central Processing Unit (CPU) 804E or another type of processor (e.g., a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU) , a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC) , a radio-frequency integrated circuit (RFIC) , another processor, or any suitable combination thereof) .
[0114] The radio control functions can include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some implementations, modulation / demodulation circuitry of the baseband circuitry 804 can include Fast-Fourier Transform (FFT) , precoding, or constellation mapping / de-mapping functionality. In some implementations, encoding / decoding circuitry of the baseband circuitry 804 can include convolution, tail-biting convolution, turbo, Viterbi, or Low-Density Parity Check (LDPC) encoder / decoder functionality. Implementations of modulation / demodulation and encoder / decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.
[0115] In some implementations, the baseband circuitry 804 can include one or more audio digital signal processor (s) (DSP) 804F. The audio DSPs 804F can include elements for compression / decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of the baseband circuitry 804 can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of the baseband circuitry 804 and the application circuitry 802 can be implemented together such as, for example, on a system-on-a-chip (SOC) .
[0116] In some implementations, the baseband circuitry 804 can provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitry 804 can support communication with an NG-RAN, an E-UTRAN or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) , etc. Implementations in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.
[0117] RF circuitry 806 can embody an RF transceiver that enables communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, the RF circuitry 806 can include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 806 can include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804. RF circuitry 806 can also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.
[0118] In some implementations, the receive signal path of the RF circuitry 806 can include mixer circuitry 806A, amplifier circuitry 806B, and filter circuitry 806C. RF circuitry 806 can also include synthesizer circuitry 806D for synthesizing a frequency for use by the mixer circuitry 806A of the receive signal path and the transmit signal path.
[0119] The RF circuitry 806 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 804 can include a digital baseband interface to communicate with the RF circuitry 806.
[0120] Synthesizer circuitry 806D of the RF circuitry 806 can include a divider, a delay-locked loop (DLL) , a multiplexer, and a phase accumulator.
[0121] FEM circuitry 808 can include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals, and provide the amplified versions of the received signals to the RF circuitry 806 for further processing. FEM circuitry 808 can also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of the one or more antennas 810. In various implementations, the amplification through the transmit and / or receive signal paths can be done solely in the RF circuitry 806, solely in the FEM circuitry 808, or in both the RF circuitry 806 and the FEM circuitry 808.
[0122] In some implementations, the FEM circuitry 808 can include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806) . The transmit signal path of the FEM circuitry 808 can include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810) .
[0123] Processors of the application circuitry 802 and processors of the baseband circuitry 804 can be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 804, alone or in combination, can be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the baseband circuitry 804 can utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers) . As referred to herein, Layer 3 can include a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 can include a medium access control (MAC) layer, a radio link control (RLC) layer, and a PDCP layer, described in further detail below. As referred to herein, Layer 1 can include a physical (PHY) layer of a UE / RAN node.
[0124] In some implementations, the PMC 812 can manage power provided to the baseband circuitry 804. In particular, the PMC 812 can control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 812 can often be included when the device 800 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 812 can increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
[0125] While FIG. 8 shows the PMC 812 coupled only with the baseband circuitry 804, in other implementations, the PMC 812 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 802, RF circuitry 806, or FEM circuitry 808.
[0126] In some implementations, the PMC 812 can control, or otherwise be part of, various power saving mechanisms of the device 800. For example, if the device 800 is in an RRC_CONNECTED state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it can enter a state known as Discontinuous Reception (DRX) mode after a period of inactivity. During this state, the device 800 can power down for brief intervals of time and thus save power.
[0127] If there is no data traffic activity for an extended period of time, then the device 800 can transition off to an RRC_IDLE state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 800 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 800 may not receive data in this state; in order to receive data, it can transition back to the RRC_CONNECTED state.
[0128] The baseband circuitry 804, or the one or more baseband processors or control logic of the baseband circuitry 804, may stand alone as the UE 110 or the RAN node 122 of FIG. 1 perform signaling and operation in the meaning as described throughout this disclosure.
[0129] Examples herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor with memory, an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) , or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.
[0130] In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.
[0131] In particular regard to the various functions performed by the above-described components or structures (assemblies, devices, circuits, systems, etc. ) , the terms (including a reference to a “means” ) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent) , even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given application.
[0132] As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or” . That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B;or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including” , “includes” , “having” , “has” , “with” , or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising. ” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X” , a “second X” , etc. ) , in general the one or more numbered items can be distinct, or they can be the same, although in some situations the context may indicate that they are distinct or that they are the same.
[0133] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
Claims
1.A baseband processor configured to perform operations comprising:receiving, via a transceiver of a user equipment (UE) , at least one message comprising:one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, andone or more sets of second UL transmission power control parameters for non-SBFD operation;configuring the transceiver for data transmission in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters; andconfiguring the transceiver for data transmission in one or more non-SBFD slots using a second set of the one or more sets of second UL transmission power control parameters.2.The baseband processor of claim 1, wherein one of the one or more sets of first UL transmission power control parameters and one of the one or more sets of second UL transmission power control parameters correspond with a same transmission configuration indication (TCI) state.3.The baseband processor of claim 1, wherein each of the one or more sets of first UL transmission power control parameters and the one or more sets of second UL transmission power control parameters corresponds with a different transmission configuration indication (TCI) state.4.The baseband processor of claim 1, wherein the at least one message comprises:a transmission configuration indication (TCI) state information element based on a unified TCI state type.5.The baseband processor of claim 4, wherein the unified TCI state type comprises a joint unified TCI state type.6.The baseband processor of claim 4, wherein the unified TCI state type comprises a separate unified TCI state type.7.The baseband processor of claim 4, wherein the at least one message further comprises:a UL power control information element corresponding to the TCI state information element, the UL power control information element comprising one of the one or more sets of second UL transmission power control parameters; anda serving cell configuration information element comprising a single set of the one or more sets of first UL transmission power control parameters, the single set comprising relative indications referring to the one of the one or more sets of second UL transmission power control parameters.8.The baseband processor of claim 4, wherein the at least one message further comprises:a UL power control information element corresponding to the TCI state information element, the UL power control information element comprising one of the one or more sets of second UL transmission power control parameters; anda bandwidth part (BWP) UL dedicated configuration information element comprising a single set of the one or more sets of first UL transmission power control parameters, the single set comprising relative indications referring to the one of the one or more sets of second UL transmission power control parameters.9.The baseband processor of claim 4, wherein the at least one message further comprises:a UL power control information element corresponding to the TCI state information element, the UL power control information element comprising one of the one or more sets of first UL transmission power control parameters; anda serving cell configuration information element comprising a single set of the one or more sets of second UL transmission power control parameters, the single set comprising relative indications referring to the one of the one or more sets of first UL transmission power control parameters.10.The baseband processor of claim 4, wherein the at least one message further comprises:a UL power control information element corresponding to the TCI state information element, the UL power control information element comprising one of the one or more sets of first UL transmission power control parameters; anda bandwidth part (BWP) UL dedicated configuration information element comprising a single set of the one or more sets of second UL transmission power control parameters, the single set comprising relative indications referring to the one of the one or more sets of first UL transmission power control parameters.11.The baseband processor of claim 4, wherein the at least one message further comprises:a UL power control information element corresponding to the TCI state information element, the UL power control information element comprising:one of the one or more sets of first UL transmission power control parameters; andone of the one or more sets of second UL transmission power control parameters comprising relative indications referring to the one of the one or more sets of first UL transmission power control parameters.12.The baseband processor of claim 4, wherein the at least one message further comprises:a UL power control information element corresponding to the TCI state information element, the UL power control information element comprising:one of the one or more sets of second UL transmission power control parameters; andone of the one or more sets of first UL transmission power control parameters comprising relative indications referring to the one of the one or more sets of second UL transmission power control parameters.13.The baseband processor of claim 4, wherein the at least one message further comprises:a UL power control information element corresponding to the TCI state information element, the UL power control information element comprising:one of the one or more sets of first UL transmission power control parameters; andone of the one or more sets of second UL transmission power control parameters.14.The baseband processor of claim 4, wherein the at least one message further comprises:a first UL power control information element corresponding to the TCI state information element, the first UL power control information element comprising one of the one or more sets of second UL transmission power control parameters; anda second UL power control information element corresponding to the TCI state information element, the second UL power control information element comprising one of the one or more sets of first UL transmission power control parameters.15.The baseband processor of claim 4, wherein the at least one message further comprises:a first UL power control information element corresponding to the TCI state information element, the first UL power control information element comprising one of the one or more sets of second UL transmission power control parameters;a serving cell configuration information element; anda second UL power control information element corresponding to the serving cell configuration information element, the second UL power control information element comprising one of the one or more sets of first UL transmission power control parameters.16.The baseband processor of claim 4, wherein the at least one message further comprises:a first UL power control information element corresponding to the TCI state information element, the first UL power control information element comprising one of the one or more sets of second UL transmission power control parameters;a bandwidth part (BWP) UL dedicated configuration information element; anda second UL power control information element corresponding to the BWP UL dedicated configuration information element, the second UL power control information element comprising one of the one or more sets of first UL transmission power control parameters.17.The baseband processor of claim 1, wherein the at least one message comprises:a bandwidth part (BWP) UL dedicated configuration information element;a first UL power control information element corresponding to the BWP UL dedicated configuration information element, the first UL power control information element comprising one of the one or more sets of second UL transmission power control parameters; anda second UL power control information element corresponding to the BWP UL dedicated configuration information element, the second UL power control information element comprising one of the one or more sets of first UL transmission power control parameters.18.A method for a user equipment (UE) , the method comprising:receiving at least one message comprising:one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, andone or more sets of second UL transmission power control parameters for non-SBFD operation;transmitting first data in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters; andtransmitting second data in one or more non-SBFD slots using a second set of the one or more sets of second UL transmission power control parameters.19.The method of claim 18, wherein:the first set of the one or more sets of first UL transmission power control parameters and the second set of the one or more sets of the second UL transmission power control parameters correspond with a first transmission configuration indication (TCI) state;the at least one message further comprises a third set of the one or more sets of second UL transmission power control parameters corresponding with a second TCI state;the second TCI state is not associated with any of the one or more sets of first UL transmission power control parameters; andthe method further comprises:transmitting third data in one or more SBFD slots and fourth data in one or more non-SBFD slots using the third set of the one or more sets of second UL transmission power control parameters corresponding with the second TCI state.20.A user equipment (UE) , comprising:a transceiver;a memory storing instructions; andone or more processors coupled to the memory and the transceiver, wherein the one or more processors, when executing the instructions, cause the UE to perform operations comprising:receiving, via the transceiver, at least one message comprising:one or more sets of first uplink (UL) transmission power control parameters for sub-band full-duplex (SBFD) operation, andone or more sets of second UL transmission power control parameters for non-SBFD operation,wherein each of the one or more sets of first UL transmission power control parameters and the one or more sets of second UL transmission power control parameters corresponds with a different transmission configuration indication (TCI) state;transmitting, via the transceiver, first data in one or more SBFD slots using a first set of the one or more sets of first UL transmission power control parameters, wherein the first set is associated with a first TCI state; andtransmitting, via the transceiver, second data in one or more non-SBFD slots using a second set of the one or more sets of the second UL transmission power control parameters, wherein the second set is associated with a second TCI state different from the first TCI state, and wherein a first TCI codepoint is mapped to the first TCI state and the second TCI state.
Citation Information
Patent Citations
UL power control in full-duplex systems
US20240214943A1