Uplink transmission method and apparatus, uplink reception method and apparatus, and communication system

By receiving the transmit power control command in the downlink control information, the uplink transmission transmit power of different time domain resources is determined and a power margin report is generated. This solves the problems of small coverage, low capacity and large latency of uplink transmission in full-duplex mode, and achieves effective power control and interference management.

WO2026233386A1PCT designated stage Publication Date: 2026-11-121FINITY INC +2
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/095315
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In existing technologies, due to differences in antenna configuration and channel conditions within the time-division duplex frequency band, uplink transmission suffers from problems such as small coverage, low capacity, and large latency. Furthermore, there is a lack of uplink power control methods for different time domain resources, especially since self-interference and cross-interference problems in full-duplex mode have not been effectively resolved.

Method used

By receiving the transmit power control command in the downlink control information, the uplink transmission transmit power associated with the first time domain resource and the second time domain resource is determined, and a power margin report is generated to support uplink transmission and reception under different time domain resources.

Benefits of technology

It achieves effective power control of different time domain resources in full-duplex mode, improves uplink transmission capacity and coverage, reduces latency, and solves the problems of self-interference and cross-interference.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026095315_12112026_PF_FP_ABST
    Figure CN2026095315_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments of the present application provide an uplink transmission method and apparatus, an uplink reception method and apparatus, and a communication system. The uplink transmission method comprises: a terminal device receives downlink control information (DCI), wherein the DCI comprises a transmit power control command (TPC command), and the TPC command is used for determining transmit power of an uplink transmission associated with a first time-domain resource and / or transmit power of an uplink transmission associated with a second time-domain resource; and the terminal device transmits the uplink transmission associated with the first time-domain resource and / or the uplink transmission associated with the second time domain resource, and transmits a power headroom report.
Need to check novelty before this filing date? Find Prior Art

Description

Uplink transmission and reception method, apparatus, and communication system TECHNICAL FIELD

[0001] The present application relates to the field of communication technology. BACKGROUND

[0002] Uplink transmission includes Physical Uplink Shared Channel (PUSCH) and / or Physical Uplink Control Channel (PUCCH) and / or Sounding Reference signal (SRS) and / or Physical Random Access Channel (PRACH) transmission, etc.

[0003] Uplink power control determines the power for uplink transmission, so that the UE (User Equipment) transmits data at appropriate power while avoiding interference to other users. Uplink power control includes open-loop power control (Open-Loop PC) and closed-loop power control (Closed-Loop PC). Open-loop power control is based on path loss (PL) and base station configuration parameters, and does not rely on dynamic feedback. Closed-loop power control dynamically adjusts the transmit power of the UE through transmit power control (TPC) commands, which includes cumulative and absolute. When cumulative is used, the UE needs to adjust the power according to the historical TPC command, and when absolute is used, the UE only adjusts the power according to the current TPC command.

[0004] Power headroom report (PHR) is a process in which a terminal device reports its uplink power headroom to a network device (e.g., a base station). The main role of the power headroom report includes providing the network device with the uplink power usage of the terminal device, so that the network device can effectively perform resource scheduling and power control. The power headroom, for example, refers to the difference between the maximum transmit power of the terminal device and the uplink transmission power.

[0005] The power headroom report can be triggered in the following ways:

[0006] Periodic triggering: triggered by a timer (such as phr-PeriodicTimer) configured by RRC (Radio Resource Control) and reported periodically.

[0007] Event triggering: When the path loss (path loss) changes beyond the configured threshold (such as phr-Tx-PowerFactorChange), when the PHR function is configured or reconfigured, or when the secondary cell (SCell) is activated, the terminal device will trigger a power margin report.

[0008] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention

[0009] Different uplink power control may be required for different time-domain resources due to differences in antenna configuration and channel conditions (such as interference).

[0010] For example, in traditional technologies, uplink transmission can only occur during uplink time slots in Time Division Duplex (TDD) bands. When limited or few uplink time slots are allocated, there are problems with small uplink coverage, low capacity, and high latency. To improve uplink capacity and coverage, reduce uplink latency, and increase spectral efficiency, simultaneous uplink (UL) and downlink (DL) transmissions within the same TDD band can be allowed. For example, network devices can operate in full-duplex mode at certain time points, where they simultaneously receive and transmit on different frequency domain resources within the corresponding carrier in the TDD band. This operating mode is called, for example, Sub-Band non-overlapping Full Duplex (SBFD), but is not limited to these. Under this operating mode, due to new self-interference and cross-interference problems, the uplink power control requirements for time domain resources corresponding to full-duplex mode may differ from those for time domain resources not corresponding to full-duplex mode.

[0011] For example, in order to improve network capacity, multiple antennas may be deployed in the same cell, and different antennas transmit in a time-division manner. Under this working mode, the uplink power control requirements of the time domain resources corresponding to different antennas may also be different.

[0012] However, there is currently no solution for supporting uplink transmission and reception in the presence of different time-domain resources, including how to specifically control / determine the uplink transmission power for different time-domain resources. For example, there is currently no closed-loop power control method or power margin reporting method for supporting uplink transmission for different time-domain resources.

[0013] To address at least one of the aforementioned problems, embodiments of this application provide an uplink transmission and reception method, apparatus, and communication system.

[0014] According to one aspect of the embodiments of this application, an uplink transmission method is provided, including:

[0015] The terminal device receives downlink control information (DCI), which includes a transmit power control command (TPC command). The TPC command is used to determine the transmit power of uplink transmissions associated with a first time-domain resource and / or the transmit power of uplink transmissions associated with a second time-domain resource; and

[0016] The terminal device sends uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and sends a power margin report.

[0017] According to another aspect of the embodiments of this application, an uplink transmitting apparatus is provided, comprising:

[0018] A receiver that receives downlink control information (DCI), the downlink control information including a transmit power control command (TPC command) for determining the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource; and

[0019] The transmitter transmits uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and transmits a power margin report.

[0020] According to another aspect of the embodiments of this application, an uplink receiving method is provided, including:

[0021] The network device sends downlink control information, including a transmit power control command (TPC command), which is used to determine the transmit power of uplink transmission associated with a first time domain resource and / or the transmit power of uplink transmission associated with a second time domain resource; and

[0022] The network device receives uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and receives a power margin report.

[0023] According to another aspect of the embodiments of this application, an uplink receiving device is provided, comprising:

[0024] A transmitter that transmits downlink control information (DCI), the downlink control information including a transmit power control command (TPC command) for determining the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource; and

[0025] The receiver receives uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and receives power margin reports.

[0026] According to another aspect of the embodiments of this application, a communication system is provided, including:

[0027] A network device that transmits downlink control information (DCI), the downlink control information including a transmit power control command (TPC command), the transmit power control command being used to determine the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource; and to receive the uplink transmissions associated with the first time domain resource and / or the uplink transmissions associated with the second time domain resource, and to receive a power headroom report;

[0028] The terminal device receives the downlink control information (DCI); and sends uplink transmissions of the associated first time domain resources and / or the associated second time domain resources, and sends the power margin report.

[0029] One of the beneficial effects of the embodiments of this application includes: in the presence of different time-domain resources, such as beams, channel states, and frequency-domain resources for uplink that may correspond to different beams, channel states, and uplink resources, a transmit power control command (TPC command) is used to determine the transmit power of uplink transmission associated with the first time-domain resource and / or the transmit power of uplink transmission associated with the second time-domain resource. Thus, it is possible to support uplink transmission and reception in the presence of the aforementioned different time-domain resources.

[0030] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0031] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with or replacing features in other embodiments.

[0032] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0033] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0034] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without creative effort. In the drawings:

[0035] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application;

[0036] Figure 2 is a schematic diagram of an uplink transmission method according to an embodiment of this application;

[0037] Figure 3 is an example diagram of time-domain resources according to an embodiment of this application;

[0038] Figure 4 is an example diagram of uplink available PRB according to an embodiment of this application;

[0039] Figure 5 is an example diagram of downlink available PRB according to an embodiment of this application;

[0040] Figure 6 is a schematic diagram of an uplink receiving method according to an embodiment of this application;

[0041] Figure 7 is a schematic diagram of an uplink transmitting device according to an embodiment of this application;

[0042] Figure 8 is a schematic diagram of an uplink receiving device according to an embodiment of this application;

[0043] Figure 9 is a schematic diagram of a network device according to an embodiment of this application;

[0044] Figure 10 is a schematic diagram of a terminal device according to an embodiment of this application. Detailed Implementation

[0045] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0046] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0047] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly interpreted as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," the term "based on" should be understood as "at least partially based on…," and the term "related to…" should be understood as "at least partially related to…," unless the context explicitly indicates otherwise. In some embodiments, "according to," "based on," and "related to…" can be used interchangeably, but this application is not limited thereto.

[0048] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0049] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), 6G, etc., and / or other currently known or future communication protocols.

[0050] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transceiver node (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0051] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" can include some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0052] In the embodiments of this application, the term "User Equipment" (UE) refers to a device that accesses a communication network and receives network services through a network device, and can also be called "Terminal Equipment" (TE). Terminal equipment can be fixed or mobile, and can also be called a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, mobile terminal (MT), etc.

[0053] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0054] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0055] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0056] In the following description, without causing confusion, the terms “uplink control signal” and “uplink control information (UCI)” or “physical uplink control channel (PUCCH)” are used interchangeably, as are the terms “uplink data signal” and “uplink data information” or “physical uplink shared channel (PUSCH)”.

[0057] The terms “downlink control signal” and “downlink control information (DCI)” or “physical downlink control channel (PDCCH)” are interchangeable, as are the terms “downlink data signal” and “downlink data information (PDSCH)” or “physical downlink shared channel (PDSCH)”.

[0058] Additionally, uplink signals can include uplink data signals and / or uplink control signals and / or PRACH and / or SRS, etc., and can also be referred to as uplink transmission (UL transmission), uplink information, or uplink channel. Sending / receiving uplink transmission on uplink resources can be understood as using that uplink resource to send / receive the uplink transmission. Downlink signals can include downlink data signals and / or downlink control signals and / or synchronization signals (SS, such as PSS / SSS) and / or broadcast channel (PBCH) and / or SSB (SS / PBCH block, including PSS, SSS, and PBCH and their DMRS) and / or channel state information reference signal (CSI-RS), etc., and can also be referred to as downlink transmission (DL transmission), downlink information, or downlink channel. Sending / receiving downlink transmission on downlink resources can be understood as using that downlink resource to send / receive the downlink transmission.

[0059] In some embodiments, uplink transmission and the (time) resource (used for transmission) of uplink transmission can be interchanged. For example, for PUCCH, "PUCCH transmission" and "PUCCH resource for PUSCH transmission" can be interchanged, and the same applies to other uplink signals.

[0060] In the embodiments of this application, higher-layer signaling may be, for example, Radio Resource Control (RRC) signaling; RRC signaling may include, for example, RRC messages, such as broadcast / public RRC messages / signaling (e.g., Master Information Block (MIB), system information), dedicated RRC messages / signaling; or RRC information elements (RRC IE); or information fields (or information fields included in information fields) included in RRC messages or RRC information elements. Higher-layer signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as MAC control elements (MAC CE). However, this application is not limited to these. The names of signaling (e.g., RRC messages, information elements IE, information fields, higher-layer parameters, etc.) used in the embodiments of this application are only examples and may be other names, which are not intended to limit the scope of this application. The '-rN' (e.g., -r17, etc.) in the higher-layer parameter names may be omitted (without causing ambiguity).

[0061] In the embodiments of this application, "multiple" refers to at least two, or two or more.

[0062] In the embodiments of this application, "predefined" refers to what is specified by the protocol or determined according to the rules specified by the protocol, and does not require additional configuration. "Configuration / instruction / providement" refers to what the network device directly or indirectly configures / instructs / provides through higher-layer signaling and / or physical layer signaling. Configuration / instruction can be achieved by introducing higher-layer parameters into the higher-layer signaling. Higher-layer parameters refer to information fields and / or information elements / information units / information cells (IE) / control elements (CE) in the higher-layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical downlink control channel or control information carried by the sequence, but is not limited to these.

[0063] In the embodiments of this application, "overlapping" includes complete / full overlap and / or partial overlap and / or at least partial overlap.

[0064] For ease of description, the following description uses a base station as an example of an access network device. In the following descriptions, "if…", "in the case of…", and "when…" are used interchangeably without causing confusion. For resources in the frequency domain, "carrier" and "resource grid" are interchangeable; "subcarrier spacing configuration (R)" and "subcarrier spacing (SCS) (Δf)" are interchangeable; "subcarrier spacing" and "numerology" are interchangeable; "resource block", "RB" and "PRB", "physical resource block", and "common resource block (CRB, Common RB)" are interchangeable; "configuration / indication / providing / given" are interchangeable; "index" and "identifier (ID)" are interchangeable.

[0065] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0066] Figure 1 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 1, the communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, Figure 1 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0067] In this embodiment of the application, network device 101 and terminal devices 102 and 103 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0068] Terminal device 102 can send data to network device 101, for example, using authorized or unauthorized transmission methods. Network device 101 can receive data sent by one or more terminal devices 102 and provide feedback to terminal devices 102, such as ACK / NACK confirmation information. Based on the feedback information, terminal device 102 can confirm the end of the transmission process, or can initiate new data transmission, or can retransmit the data.

[0069] Network device 101 can send data to terminal device 102 and / or terminal device 103 using unicast, multicast, or broadcast. Terminal device 102 can receive data sent by one or more network devices (e.g., dual-connection or multi-connection) via a downlink or by terminal device 103 via a sidelink.

[0070] It is worth noting that Figure 1 shows that both terminal devices 102 and 103 are within the coverage area of ​​network device 101, but this application is not limited to this. Both terminal devices 102 and 103 may be outside the coverage area of ​​network device 101, or one terminal device 102 may be within the coverage area of ​​network device 101 while the other terminal device 103 may be outside the coverage area of ​​network device 101.

[0071] In the embodiments of this application, the content within parentheses is explanatory, exemplary, or optional. For example, in some embodiments, the expressions or limitations within parentheses may be included, while in other embodiments, the expressions or limitations within parentheses may be omitted. " / " represents "and / or," and this application is not limited thereto. Various implementations of the embodiments of this application will be described below with reference to the accompanying drawings. These implementations are merely exemplary and not intended to limit the scope of this application.

[0072] First aspect of the embodiments

[0073] This application provides an uplink transmission method, which will be described from the perspective of the terminal device.

[0074] Figure 2 is a schematic diagram of an uplink transmission method according to an embodiment of this application. As shown in Figure 2, the method includes:

[0075] 201. The terminal device receives downlink control information (DCI), which includes a transmit power control command (TPC command) for determining the transmit power of uplink transmission associated with a first time domain resource (in a cell / (uplink) carrier / (uplink) BWP with SBFD enabled) and / or the transmit power of uplink transmission associated with a second time domain resource (in a cell / (uplink) carrier with SBFD enabled); and

[0076] 202, the terminal device sends uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and sends a power margin report.

[0077] It is worth noting that Figure 2 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 2 above.

[0078] The following describes the first time domain resources and / or the second time domain resources.

[0079] In some embodiments, for a cell or carrier, in the second time domain resources, different frequency domain resources are respectively (only) used for (network device receiving) uplink (e.g., corresponding to the first frequency domain resources and / or the third frequency domain resources described below) and (only) used for (network device transmitting) downlink (e.g., corresponding to the second frequency domain resources and / or the fourth frequency domain resources described below). For example, the network device can simultaneously receive (uplink signals) in the frequency domain resources (only) used for uplink and transmit (downlink signals) in the frequency domain resources (only) used for downlink. The first time domain resources are outside the second time domain resources. For example, in the first time domain resources, different frequency domain resources are all used for uplink or all used for downlink. That is, the frequency domain resources are not divided into frequency domain resources (only) used for uplink and (only) used for downlink, and the network device does not receive and transmit at the same time.

[0080] In some embodiments, the time-domain resource type includes a first time-domain resource and a second time-domain resource. The first and second time-domain resources also include a first symbol and a second symbol, respectively; that is, the symbol type includes a first symbol and a second symbol. For example, SBFD symbol (second symbol) and non-SBFD symbol (first symbol). However, this application is not limited to this and can also be applied to other scenarios. For example, the first and second time-domain resources can respectively refer to different time-domain resources defined in other ways. For convenience, "SBFD symbol" and "non-SBFD symbol" will be used below for description.

[0081] In some embodiments, for TDD carriers, Subband Full-Duplex (SBFD) operation is supported, enabling downlink transmission and uplink reception to occur simultaneously on their respective subbands at the base station side. From the UE's perspective, full-duplex is not supported (i.e., the UE cannot simultaneously perform downlink reception and uplink transmission). Cell-specific SBFD time (SBFD symbols) and frequency resources (UL / DL subbands) are configured via SIB1 or dedicated signaling.

[0082] In some embodiments, SBFD symbols and / or non-SBFD symbols are configured separately for different cells / carriers. For example, a cell / carrier is configured with SBFD symbols and / or non-SBFD symbols using corresponding information for configuring SBFD symbols and / or non-SBFD symbols.

[0083] For example, the information used to configure SBFD symbols and / or non-SBFD symbols is provided by higher-layer signaling. For example, the higher-layer parameters used to configure SBFD symbols may optionally exist in a TDD-UL-DL-Pattern IE. For example, this IE may be included in a Common TDD-UL-DL-ConfigCommon IE, which may be included in SIB1 and / or in a ServingCellConfigCommonSIB IE and / or a ServingCellConfigCommon IE, but is not limited to these and may be other IEs.

[0084] In some embodiments, a cell / carrier can be configured with one or more (e.g., two) TDD uplink / downlink patterns by (system information (e.g., SIB1) / public service cell configuration / serving cell configuration / information element for configuring random access resources) (the corresponding TDD-UL-DL-ConfigCommon). Different patterns are configured by different TDD uplink / downlink pattern (TDD-UL-DL-Pattern) IEs. When multiple patterns are configured, different patterns may or may not have corresponding SBFD symbols. Different patterns are independently configured with corresponding SBFD symbols. For example, different TDD uplink / downlink pattern (TDD-UL-DL-Pattern) IEs may or may not contain higher-layer parameters for configuring SBFD symbols.

[0085] For example, for each pattern with SBFD symbols, the configured SBFD symbols are continuous within the corresponding period of the pattern (e.g., referred to as the TDD-UL-DL-Pattern period). The high-level parameters for configuring SBFD symbols mentioned above include, for example, one or more parameters for configuring SBFD symbols in that period or for the pattern, such as: the start slot index (SBFD-StartingSlotIndex), the start symbol index (SBFD-StartingSymbolIndex) (in the start slot), the end slot index (SBFD-EndingSlotIndex), and the end symbol index (SBFD-EndingSymbolIndex) (in the end slot).

[0086] For example, the start and end slots are the first and last slots containing SBFD symbols, respectively. The start and end symbols are the first and last SBFD symbols in the start slot and the last SBFD symbol in the end slot, respectively. From the start symbol of the start slot to the end symbol of the end slot, all symbols are SBFD symbols or include SBFD symbols and / or interval symbols. The remaining symbols include non-SBFD symbols and / or interval symbols, or the remaining symbols are non-SBFD symbols. The slot index is the number of the slots included in the period / pattern, which increments by 1, for example, starting from 0 or 1. For example, when the start slot index is 0, the start slot is the first slot in the period / pattern; when the start slot index is 1, the start slot is the second slot in the period / pattern, and so on. Similarly, the symbol index is the number of the symbols within the slot. The aforementioned slots / symbols use the SCS configured in the reference subcarrier spacing field of the Common TDD Uplink / Downlink Configuration (TDD-UL-DL-Config Common) IE.

[0087] For example, each / different pattern is configured with a period independently, for example, by the corresponding ((TDD-UL-DL-Pattern)IE)dl-UL-TransmissionPeriodicity. When only one pattern is configured, the period of the SBFD symbol is the same as the period corresponding to that pattern; when multiple patterns (e.g., two) are configured, the period of the SBFD symbol is the same as the sum of the periods corresponding to all patterns.

[0088] In some embodiments, a cell configured with SBFD symbols and / or SBFD subbands is, for example, a cell with SBFD enabled, referred to as an SBFD-enabled cell or cell with SBFD operation.

[0089] In some embodiments, a downlink symbol is, for example, a symbol indicated as downlink by the first uplink / downlink configuration, an uplink symbol is, for example, a symbol indicated as uplink by the first uplink / downlink configuration, and a flexible symbol is, for example, a symbol that is neither indicated as downlink nor as uplink by the first uplink / downlink configuration, or a symbol indicated as flexible by the configuration. The first uplink / downlink configuration is used to provide cell-specific uplink / downlink configurations, such as tdd-UL-DL-ConfigurationCommon, or the common TDD uplink / downlink configuration (TDD-UL-DL-ConfigCommon)IE or (TDD-UL-DL-Pattern)IE, but is not limited thereto.

[0090] In some embodiments, the UE (based on the DL / UL / Flexible symbol configured according to the aforementioned reference Subcarrier Spacing (and assuming NCP)) determines the DL / UL / Flexible symbol corresponding to a portion of the bandwidth (BWP). For example, it determines the DL / UL / Flexible symbol corresponding to the BWP based on the reference Subcarrier Spacing and the SCS and / or CP type (NCP or ECP) ​​of the BWP.

[0091] In some embodiments, the DL / UL / Flexible symbol refers to the DL / UL / Flexible symbol configured based on the reference SubcarrierSpacing or the DL / UL / Flexible symbol corresponding to the BWP.

[0092] In some embodiments, the UE determines the SBFD / non-SBFD symbol corresponding to the BWP based on the SBFD / non-SBFD symbol configured based on the aforementioned reference Subcarrier Spacing (and assuming NCP). For example, it determines the SBFD / non-SBFD symbol corresponding to the BWP based on the reference Subcarrier Spacing and the SCS and / or CP type (NCP or ECP) ​​of the BWP.

[0093] In some embodiments, SBFD / non-SBFD symbols refer to SBFD / non-SBFD symbols configured based on reference SubcarrierSpacing or SBFD / non-SBFD symbols corresponding to BWP.

[0094] In some embodiments, the UE does not expect the CP type of the BWP to be ECP.

[0095] In some embodiments, the UE does not expect the SBFD symbols configured (as described above by the higher-layer parameters) to overlap with the uplink symbols, or if the SBFD symbols configured (as described above by the higher-layer parameters) overlap with the uplink symbols, the UE considers the SBFD symbols overlapping with the uplink symbols to be non-SBFD symbols.

[0096] In some embodiments, the SBFD symbol overlaps with the downlink symbol or the flexible symbol, or in other words, the SBFD symbol is configured within the scope of the downlink symbol and / or the flexible symbol.

[0097] In some embodiments, SBFD symbols include DL SBFD symbols and / or Flexible SBFD symbols, and non-SBFD symbols include Full-DL symbols (or non-SBFD DL symbols) and / or Full-Flexible symbols (or (non-SBFD) flexible symbols) and / or Full-UL symbols (or (non-SBFD) UL symbols). Other representations of these symbols are also possible and are not limited thereto.

[0098] Figure 3 is an example diagram of time-domain resources according to an embodiment of this application. As shown in Figure 3, a period (e.g., the period corresponding to a pattern) may include multiple different symbols. Among them, SBFD symbols are within the range of downlink symbols and flexible symbols. SBFD symbols that overlap with DL symbols, or downlink symbols configured as SBFD symbols, or SBFD symbols indicated as downlink by the first uplink / downlink configuration are represented as DL SBFD symbols. SBFD symbols that overlap with flexible symbols, or flexible symbols configured as SBFD symbols, or SBFD symbols indicated as flexible by the first uplink / downlink configuration (i.e., SBFD symbols not indicated as downlink (or uplink) by the first uplink / downlink configuration) are represented as Flexible SBFD symbols. Downlink symbols that do not overlap with SBFD symbols, or downlink symbols not configured as SBFD symbols, or non-SBFD symbols indicated as downlink by the first uplink / downlink configuration are represented as Full-DL symbols (or non-SBFD DL symbols or DL ​​symbols). A flexible symbol that does not overlap with an SBFD symbol, or a flexible symbol that is not configured as an SBFD symbol, or a non-SBFD symbol indicated as flexible by the first uplink / downlink configuration, is represented as a Full-Flexible symbol (or a (non-SBFD) flexible symbol or a flexible (non-SBFD) symbol). A UL symbol that does not overlap with an SBFD symbol, or an uplink symbol that is not configured as an SBFD symbol, or a (non-SBFD) symbol indicated as uplink by the first uplink / downlink configuration, is represented as a Full-UL symbol (or a (non-SBFD) UL symbol or a UL (non-SBFD) symbol). Figure 3 illustrates the temporal resources of an embodiment of this application, but is not limited thereto.

[0099] The frequency domain resources involved in the embodiments of this application are illustrated below.

[0100] The first frequency domain resources include the uplink subband (UL subband), and the second frequency domain resources include the downlink subband (DL subband). Other names may also be used, and are not limited to these. For convenience, the following descriptions will use UL subband and DL subband.

[0101] In some embodiments, the UE receives information for configuring SBFD subbands (including UL subband and / or DL ​​subband). For example, the uplink subband and downlink subband each include an integer number of PRBs, and the information for configuring the UL subband and DL subband includes information indicating the corresponding starting PRB and bandwidth / size (the number of PRBs included).

[0102] In some embodiments, information for configuring the UL subband and DL subband is provided by higher-level signaling.

[0103] For example, higher-layer parameters used to configure the DL subband may optionally exist in SIB1 (the SIB ServingCellConfigCommonSIB IE, the SIB DownlinkConfigCommonSIB IE, the SIB DownlinkFrequencyInfoDL-SIB IE, and the SCS-SpecificCarrier IE), and the inclusion relationship of the above parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > DownlinkConfigCommonSIB > FrequencyInfoDL-SIB > SCS-SpecificCarrier; and / or,

[0104] The higher-layer parameters used to configure the DL subband may optionally exist in the ServingCellConfigCommon IE (which contains the DownlinkConfigCommon IE, which contains the DownlinkFrequencyInfoDL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > DownlinkConfigCommon > FrequencyInfoDL > SCS-SpecificCarrier, and / or, optionally, in the ServingCellConfig. That is, the higher-layer parameters used to configure the DL subband may optionally exist in one or more of the above parameters.

[0105] For example, the higher-layer parameters used to configure the UL subband may optionally exist in SIB1 (the SIB ServingCellConfigCommonSIB IE, the SIB UplinkConfigCommonSIB IE, the SIB UplinkFrequencyInfoUL-SIB IE, and the SCS-SpecificCarrier IE). For instance, the inclusion relationship of these parameters can be expressed as: SIB1 > ServingCellConfigCommonSIB > UplinkConfigCommonSIB > FrequencyInfoUL-SIB > SCS-SpecificCarrier, and / or...

[0106] The higher-layer parameters used to configure the UL subband may optionally exist in the ServingCellConfigCommon IE (which contains the CommonUplinkConfigCommon IE, which contains the UplinkFrequencyInfoUL IE, which contains the SCS-SpecificCarrier IE)). For example, the inclusion relationship of the above parameters can be represented as: ServingCellConfigCommon > UplinkConfigCommon > FrequencyInfoUL > SCS-SpecificCarrier, and / or, optionally, in the ServingCellConfig. That is, the higher-layer parameters used to configure the UL subband may optionally exist in one or more of the above parameters.

[0107] In some embodiments, the high-level parameters for configuring the UL subband and the high-level parameters for configuring the DL subband include one or more parameters for providing the RIV (resource indication value) and / or (the SCS corresponding to the UL / DL subband), that is, indicating the starting RB (RB) of the UL subband and the DL subband respectively based on the RIV. start ) and bandwidth (including the number of RBs, L RBs )).

[0108] In some embodiments, in the second time domain resource, the first frequency domain resource and / or the third frequency domain resource (UL usable PRBs for the active UL BWP) are used for uplink and the second frequency domain resource and / or the fourth frequency domain resource (DL usable PRBs for the active DL BWP) are used for downlink, and the first time domain resource is outside the second time domain resource. For convenience, UL usable PRBs and DL usable PRBs will be used in the following description.

[0109] In some embodiments, for a UL BWP, its UL usable PRBs include / are determined as (in the SBFD symbol / corresponding to the SBFD symbol,) the intersection of (PRBs in the UL subband) and (PRBs in the uplink BWP) with (the SCS configured for the uplink BWP, or, corresponding to the SCS of the UL BWP), or, the PRBs in the intersection are referred to as UL usable PRBs.

[0110] For example, for a UL BWP, the intersection is determined based on the uplink subband corresponding to the SCS of that UL BWP. For instance, if the SCS of a UL BWP is 15kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz. If the SCS of a UL BWP is 30kHz, then its corresponding UL available PRB is the intersection of that UL BWP and the corresponding uplink subband with SCS = 15kHz.

[0111] Figure 4 is an example diagram of uplink usable PRBs according to an embodiment of this application. As shown in Figure 4, the UL BWP and UL subband overlap, and the UL usable PRBs are the intersection between them. The UL subband, for example, represents the uplink subband corresponding to the SCS of the UL BWP, but this application is not limited to this.

[0112] In some embodiments, for a DL BWP, its DL usable PRBs include / are determined as (in SBFD symbols / corresponding to SBFD symbols,) the intersection of (PRBs in the DL subband) and (PRBs in the downlink BWP) with (the SCS configured for the downlink BWP, or, corresponding to the SCS of the DL BWP), or, the PRBs in the intersection are referred to as DL usable PRBs.

[0113] For example, for a DL BWP, the intersection is determined based on the downlink subband corresponding to the SCS of that DL BWP. For instance, if the SCS of a DL BWP is 15kHz, then its corresponding DL can be represented by the PRB as the intersection of the DL BWP with the corresponding downlink subband of SCS = 15kHz. If the SCS of a DL BWP is 30kHz, then its corresponding DL can be represented by the PRB as the intersection of the DL BWP with the corresponding uplink subband of SCS = 15kHz.

[0114] Figure 5 is an example diagram of downlink usable PRBs according to an embodiment of this application. As shown in Figure 5, DL BWP and DL subband overlap, and DL usable PRBs are the intersection of the two. The DL subband, for example, represents the downlink subband corresponding to the SCS of the DL BWP, but this application is not limited thereto.

[0115] The above provides an illustrative description of time-frequency resources. This application is not limited to this; for more information on SBFD symbols and sub-band configurations, please refer to Table 1.

[0116] Table 1

[0117] The embodiments of this application are further illustrated below.

[0118] In some embodiments, the UE receives DCI, including: the UE listens to PDCCH (candidate). This listening means receiving (each) PDCCH candidate and decoding it according to the listened DCI formats.

[0119] In some embodiments, different DCI formats can carry different information to support different uses. For example, DCI formats include: DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_3, DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 1_3, DCI format 2_3, DCI format 2_2, etc., and this application is not limited thereto. The first nine DCI formats can be used to schedule uplink transmissions; for example, DCI format 0_0, DCI format 0_1, DCI format 0_2, and DCI format 0_3 can be used to schedule PUSCH, DCI format 1_0, DCI format 1_1, DCI format 1_2, and DCI format 1_3 can be used to schedule PUCCH, and DCI format 2_3 can be used to schedule SRS. DCI format 2_2 is not used to schedule uplink transmissions. For DCI format 2_3, if an SRS request field is included / exists, then SRS can be scheduled (the system has the capability to schedule SRS); otherwise, SRS cannot be scheduled / the system does not have the capability to schedule SRS.

[0120] In some embodiments, the terms DCI and DCI format are interchangeable. For example, DCI format refers to a DCI that uses a certain DCI format, or a DCI that uses / has a certain DCI format can be simply referred to as that DCI format. For example, DCI format 0_0 refers to a DCI that uses DCI format 0_0, or if a DCI uses DCI format 0_0, the DCI can be called DCI format 0_0. For example, DCI format 0_1 ​​refers to a DCI that uses DCI format 0_1, or if a DCI uses DCI format 0_1, the DCI can be called DCI format 0_1.

[0121] In some embodiments, the DCI may include one or more (N, N≥1) TPC commands, wherein at least one TPC command (M, 1≤M≤N) is used to determine the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource in a cell / (uplink) carrier / (uplink) BWP with SBFD enabled. For example, all (N) TPC commands in the DCI may have this purpose, i.e., to determine the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource in a cell / (uplink) carrier / (uplink) BWP with SBFD enabled; or, a portion of the TPC commands in the DCI (the aforementioned M TPC commands) may have this purpose (while another portion of the TPC commands (e.g., NM TPC commands other than the aforementioned M TPC commands) may not have this purpose, for example, only have other purposes).

[0122] For example, for a DCI that includes a TPC command and schedules uplink transmissions, when the DCI schedules uplink transmissions in a cell / (uplink)carrier with SBFD enabled, and / or, when all (valid) uplink transmissions scheduled by the DCI that meet specific conditions are in a cell / (uplink)carrier with SBFD enabled, all (applied / not ignored) TPC commands in the DCI have this purpose (other TPC commands do not have this purpose).

[0123] For example, for a DCI that includes TPC commands and schedules uplink transmissions, if the DCI schedules uplink transmissions in cells / (uplink)carriers where SBFD is not enabled, and / or, if (all) (valid) uplink transmissions that meet specific conditions are not in cells / (uplink)carriers where SBFD is enabled, then all (applied / not ignored) TPC commands in the DCI are not used for this purpose.

[0124] For example, for a DCI that includes a TPC command and schedules uplink transmissions, when the DCI schedules uplink transmissions in cells / (uplink)carriers with SBFD enabled as well as uplink transmissions in cells / (uplink)carriers without SBFD enabled, the corresponding / used / targeted / applied (applied / not ignored) TPC command in the DCI has this purpose, while other TPC commands do not.

[0125] For example, for a DCI that includes TPC commands but does not schedule uplink transmissions, a TPC command has this purpose if it corresponds to / is used for / is applied to / is used for a cell / (uplink) carrier with SBFD enabled; otherwise, it does not.

[0126] In some embodiments, a DCI that includes TPC commands and schedules uplink transmissions includes: DCI format 0_0, DCI format 0_1, DCI format 0_2, and DCI format 0_3 for scheduling PUSCH; DCI format 1_0, DCI format 1_1, DCI format 1_2, and DCI format 1_3 for scheduling PUCCH; and DCI format 2_3 for scheduling SRS. A DCI that includes TPC commands but does not schedule uplink transmissions includes: DCI format 2_2 (including TPC commands for PUCCH or PUSCH), and DCI format 2_3 (including TPC commands for SRS) without scheduling SRS.

[0127] In some embodiments, the TPC command is used to determine the transmit power of uplink transmissions associated with a first time-domain resource (in an SBFD-enabled cell / uplink carrier / uplink BWP) and / or the transmit power of uplink transmissions associated with a second time-domain resource (in an SBFD-enabled cell / uplink carrier), including: the TPC command corresponds to / is used for / for / applies to uplink power control applied to uplink transmissions (in an SBFD-enabled cell / uplink carrier / uplink BWP), and / or, the TPC command is used to determine the transmit power of uplink transmissions in an SBFD-enabled cell (uplink carrier / uplink BWP). Wherein, an SBFD-enabled cell / uplink carrier includes cells / uplink carriers configured with SBFD subbands and / or SBFD symbols. An SBFD-enabled uplink carrier includes the uplink carrier of an SBFD-enabled cell. An uplink BWP with SBFD enabled includes an uplink BWP of a cell / uplink carrier with SBFD enabled (and overlapping UL subbands / with UL usable PRBs / the corresponding UL usable PRBs include PRBs that meet the quantity requirements).

[0128] In some embodiments, a DCI includes one or more TPC command fields, where each TPC command field corresponds to / includes one or more TPC commands. For example, DCI format 0_0 / DCI format 1_0 includes one TPC command field, which corresponds to / includes one TPC command; DCI format 0_1 / DCI format 0_2 / DCI format 1_1 / DCI format 1_2 / DCI format 1_3 includes one or two TPC command fields, each corresponding to / including one TPC command; or, a TPC command field includes one or more blocks, and each block includes one TPC command; DCI format 0_3 includes one TPC command field, which includes one or more blocks, and each block includes one TPC command.

[0129] For example, a TPC command field or each block in a TPC command field consists of 2 bits. The correspondence between the TPC command field / the above block and the TPC command value for PUSCH, SRS and PUCCH are shown in Table 2 and Table 3, respectively.

[0130] For example, Table 2 shows an example for PUSCH:

[0131] Table 2

[0132] (Mapping of TPC Command Field in a DCI format scheduling a PUSCH transmission,or in DCI format 2_2with CRC scrambled by TPC-PUSCH-RNTI,or in DCI format 2_3,to absolute and accumulatedδPUSCH,b,f,cvalues ​​orδ SRS,b,f,c values)

[0133] For example, Table 3 shows examples for PUCCH:

[0134] Table 3

[0135] (Mapping of TPC Command Field in a DCI format to accumulatedδP UCCH,b,f,c values)

[0136] In some embodiments, the UE receives signaling from the network device indicating the number of TPC commands included in the DCI format. For example, for DCI format 0_1 / DCI format 0_2 / DCI format 1_1 / DCI format 1_2, higher-layer parameters are used to indicate whether it includes 2 TPC commands, 2 TPC command fields, or a second TPC command field.

[0137] For example, the same high-level parameter can be used to indicate this for two or more DCI formats, and / or, different high-level parameters can be used (independently) for each of the two or more DCI formats. For example, secondTPCFieldDCI-0-1-r17, secondTPCFieldDCI-0-2-r17, secondTPCFieldDCI-1-1-r17, and secondTPCFieldDCI-1-2-r17 can be used to indicate whether a second TPC command is included for the aforementioned DCI formats.

[0138] For example, for a DCI format, if the UE is provided with the corresponding (active UL BWP of the cell where the DCI format is located) higher-layer parameters, then the DCI format includes two TPC commands (including the first TPC command and the second TPC command) and / or two TPC command fields (including the first TPC command field and the second TPC command field, each corresponding to one or more TPC commands); otherwise, it only includes one TPC command (including the first TPC command) and / or one TPC command field (corresponding to one or more TPC commands).

[0139] For example, the DCI format described above can be configured to include two TPC commands, two TPC command fields, or a second TPC command field only if the UE is provided with a specific higher-level parameter (sbfd-Configuration2-Transmission) for (an active UL BWP) (for an SBFD-enabled cell). For instance, if the UE is not provided with the specific higher-level parameter (sbfd-Configuration2-Transmission), the UE is also not provided with the aforementioned higher-level parameter indicating that the DCI format(s) includes two TPC commands, two TPC command fields, or a second TPC command field (the higher-level parameter may exist if the UE is provided with the specific higher-level parameter, otherwise it does not exist).

[0140] In some embodiments, DCI format 0_0 / DCI format 0_1 / DCI format 0_2 / DCI format 1_0 / DCI format 1_1 / DCI format 1_2 each (by default) include a first TPC command.

[0141] In some embodiments, the block / TPC command / TPC command values ​​in the TPC command field can be interchanged.

[0142] In some embodiments, an uplink transmission occurs in a time slot, and the corresponding / used time domain resources do not cross time slot boundaries, but this application is not limited thereto.

[0143] For example, for PUSCH with repetition Type B, if an uplink transmission is a nominal repetition, it may cross a slot boundary; if an uplink transmission is an actual repetition, it will not cross a slot boundary.

[0144] In some embodiments, an uplink transmission includes a PUSCH transmission opportunity, a PUCCH transmission opportunity, or an SRS transmission opportunity, but this application is not limited thereto. For example, the definitions of PUSCH / PUCCH / SRS transmission opportunities are shown in Table 4, but are not limited thereto.

[0145] Table 4

[0146] In some embodiments, the UE determines the transmit power for each uplink transmission, but is not limited thereto.

[0147] In some embodiments, for PUSCH with repetition Type B, if the SBFD symbol and non-SBFD symbol of the (cell / carrier)BWP where the PUSCH resides correspond to different power control parameters, for example, if the UE is provided with the (cell / carrier)BWP (associated with the indicated TCI-State or TCI-UL-State) (first parameter and) (second parameter), the UE determines the transmit power and / or PUSCH transmission as actual repetition for each actual repetition; otherwise (including but not limited to: if the SBFD symbol and non-SBFD symbol of the (cell / carrier)BWP where the PUSCH resides correspond to the same power control parameters, for example, if the UE is not provided with the (cell / carrier)BWP (associated with the indicated TCI-State or TCI-UL-State) (first parameter and) (second parameter), the UE determines the transmit power and / or PUSCH transmission as actual repetition for each actual repetition.

[0148] In some embodiments, the terms “PUSCH” / “PUSCH transmission” / “PUSCH transmission / transmission opportunity” are interchangeable, the terms “PUCCH” / “PUCCH transmission” / “PUCCH transmission / transmission opportunity” are interchangeable, and the terms “SRS” / “SRS transmission” / “SRS transmission / transmission opportunity” are interchangeable.

[0149] In some embodiments, uplink transmission associated with a first time domain resource includes: uplink transmission within the first time domain resource, and / or, uplink transmission originating in the first time domain resource, and / or, uplink transmission ending in the first time domain resource, and / or, uplink transmission across the first and second time domain resources.

[0150] In some embodiments, uplink transmission associated with a second time domain resource includes: uplink transmission within the second time domain resource, and / or, uplink transmission originating in the second time domain resource, and / or, uplink transmission ending in the second time domain resource, and / or, uplink transmission across the first and second time domain resources.

[0151] In some embodiments, for PUSCH with repetition Type B, if a PUSCH transmission is a nominal repetition, a nominal repetition in an SBFD symbol and / or a nominal repetition across SBFD symbols and / or a nominal repetition originating in an SBFD symbol is determined by the UE as / considered a PUSCH transmission in an SBFD symbol, and / or a nominal repetition in a non-SBFD symbol and / or a nominal repetition across SBFD symbols and / or a nominal repetition originating in a non-SBFD symbol is determined by the UE as / considered a PUSCH transmission in a non-SBFD symbol.

[0152] In some embodiments, a power control command is used to determine the transmission power of an uplink transmission associated with a first time domain resource and / or the transmission power of an uplink transmission associated with a second time domain resource, including: the power control command is applied to a power control adjustment state associated with the uplink transmission associated with the first time domain resource (for the uplink transmission of the associated first time domain resource) and / or to a power control adjustment state associated with the uplink transmission associated with the second time domain resource (for the uplink transmission of the associated second time domain resource);

[0153] The power control adjustment state associated with the uplink transmission of the associated first time domain resource is the same as the power control adjustment state associated with the uplink transmission of the associated second time domain resource, or the power control adjustment state associated with the uplink transmission of the associated first time domain resource is different from the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

[0154] In some embodiments, the power control adjustment state associated with the uplink transmission includes the power control adjustment state corresponding to the time-domain resource type associated with the uplink transmission (for the time-domain resource type of the uplink transmission), and / or, the power control adjustment state associated with the uplink transmission is related to the closed-loop index configuration (closedLoopIndex) corresponding to the uplink transmission or to the closed-loop index configuration (closedLoopIndex) corresponding to the time-domain resource type associated with the uplink transmission (or, the time-domain resource type of the uplink transmission, or for the time-domain resource type of the uplink transmission).

[0155] For example, for PUSCH transmissions in non-SBFD symbols, the (corresponding / associated) PUSCH power control adjustment state l is provided by the closedLoopIndex in p0AlphaSetforPUSCH (e.g., referred to as the first parameter) (associated with the indicated TCI-State or TCI-UL-State), and for PUSCH transmissions in SBFD symbols, the (corresponding / associated) PUSCH power control adjustment state l is provided by the closedLoopIndex in p0AlphaSetforPUSCH (associated with the indicated TCI-State or TCI-UL-State) or p0AlphaSetforPUSCH-SBFD (e.g., referred to as the second parameter) (associated with the indicated TCI-State or TCI-UL-State). For example, if the parameter closedLoopIndex in p0AlphaSetforPUSCH or p0AlphaSetforPUSCH-SBFD is set to 'i0', then the corresponding PUSCH transport association l = 0; if the parameter is set to 'i1', then the corresponding PUSCH transport association l = 1.

[0156] When the PUSCH power control adjustment states for PUSCH transmissions in non-SBFD symbols and PUSCH transmissions in SBFD symbols are provided by p0AlphaSetforPUSCH and p0AlphaSetforPUSCH-SBFD (with closedLoopIndex) respectively, and the values ​​of p0AlphaSetforPUSCH and p0AlphaSetforPUSCH-SBFD (with closedLoopIndex) are different, for example, set to 'i0' and 'i1' respectively, then the power control adjustment states associated with the two types of PUSCH transmissions are different; otherwise, the power control adjustment states associated with the two types of PUSCH transmissions are the same.

[0157] For example, for PUCCH transmissions in non-SBFD symbols, the (corresponding / associated) PUCCH power control adjustment state l is provided by the closedLoopIndex in p0AlphaSetforPUCCH (associated with the indicated TCI-State or TCI-UL-State), and for PUSCH transmissions in SBFD symbols, the (corresponding / associated) PUCCH power control adjustment state l is provided by the closedLoopIndex in p0AlphaSetforPUCCH (associated with the indicated TCI-State or TCI-UL-State) or p0AlphaSetforPUCCH-SBFD (associated with the indicated TCI-State or TCI-UL-State), which is also referred to as the fourth parameter. For example, if the parameter closedLoopIndex in p0AlphaSetforPUCCH or p0AlphaSetforPUCCH-SBFD is set to 'i0', then the corresponding PUCCH transmission association l = 0; if the parameter is set to 'i1', then the corresponding PUCCH transmission association l = 1.

[0158] When the PUCCH power control adjustment states for PUCCH transmissions in non-SBFD symbols and PUCCH transmissions in SBFD symbols are provided by p0AlphaSetforPUCCH and p0AlphaSetforPUCCH-SBFD (with closedLoopIndex) respectively, and the values ​​of p0AlphaSetforPUCCH and p0AlphaSetforPUCCH-SBFD (with closedLoopIndex) are different, for example, set to 'i0' and 'i1' respectively, then the power control adjustment states associated with the two types of PUCCH transmissions are different; otherwise, the power control adjustment states associated with the two types of PUCCH transmissions are the same.

[0159] For example, for SRS transmissions in non-SBFD symbols, the (corresponding / associated) SRS power control adjustment state l is provided by the closedLoopIndex in p0AlphaSetforSRS (e.g., referred to as the fifth parameter) associated with the indicated TCI-State or TCI-UL-State. For PUSCH transmissions in SBFD symbols, the (corresponding / associated) SRS power control adjustment state l is provided by p0AlphaSetforSRS (associated with the indicated TCI-State or TCI-UL-State or the TCI-State or TCI-UL-State of the SRS resource with the lowest / smallest SRS-ResourceId in the SRS resource set) or p0AlphaSetforSRS-SBFD (e.g., referred to as the sixth parameter) (associated with the indicated TCI-State or TCI-UL-State or the TCI-State or TCI-UL-State of the SRS resource with the lowest / smallest SRS-ResourceId in the SRS resource set). For example, if the parameter closedLoopIndex in p0AlphaSetforSRS or p0AlphaSetforSRS-SBFD is set to 'i0', then the corresponding SRS transmission association l = 0; if the parameter is set to 'i1', then the corresponding SRS transmission association l = 1.

[0160] For example, for an SRS resource set that is provided with followUnifiedTCI-StateSRS (e.g., referred to as the seventh parameter) / applied with an indication of TCI-State or TCI-UL-State, or if followUnifiedTCI-StateSRS is provided for an SRS resource set and / or an indication of TCI-State or TCI-UL-State is applied to an SRS resource set, the above p0AlphaSetforSRS and p0AlphaSetforSRS-SBFD are respectively associated with the indicated TCI-State or TCI-UL-State. For example, for an SRS resource set for which a followUnifiedTCI-StateSRS is not provided or an instruction is not applied to a TCI-State or TCI-UL-State, or otherwise (if a followUnifiedTCI-StateSRS is not provided for the SRS resource set and / or an instruction is not applied to a TCI-State or TCI-UL-State for the SRS resource set), the above p0AlphaSetforSRS and p0AlphaSetforSRS-SBFD are respectively associated with the TCI-State or TCI-UL-State of the SRS resource in the SRS resource set that has the lowest / smallest SRS-ResourceId.

[0161] In some embodiments, the transmission power control command is used to determine the transmission power of the uplink transmission associated with the first time domain resource and / or the transmission power of the uplink transmission associated with the second time domain resource, and further includes: the terminal device determining the transmission power of the uplink transmission associated with the first time domain resource based on a power control adjustment state associated with the uplink transmission associated with the first time domain resource, and / or determining the transmission power of the uplink transmission associated with the second time domain resource based on a power control adjustment state associated with the uplink transmission associated with the second time domain resource.

[0162] For example, the UE determines the transmit power according to the methods described in Tables 5 to 7 below. Specifically, for PUSCH / PUCCH / SRS transmissions in non-SBFD symbols and PUSCH / PUCCH / SRS transmissions in SBFD symbols, the associated PUSCH power control adjustment state is used respectively. b,f,c (i,l), PUCCH power control adjustment stateg b,f,c (i,l), SRS power control adjustment stateh b,f,c (i,l) determines the transmission power.

[0163] For example, for PUSCH in SBFD notation, if the association l = 0, then f is used. b,f,c (i,0), if l=1, then use f b,f,c (i,1). For PUSCH in non-SBFD symbols, if the association l=0, then f is used. b,f,c (i,0), if l=1, then use f b,f,c (i,1). The cases for PUCCH and SRS are similar, and will not be listed here.

[0164] Table 5

[0165] Table 6

[0166] Table 7

[0167] In some embodiments, the PUSCH power control adjustment state f b,f,c (i,l) is the cumulative closed-loop power control adjustment value. For example, when tpc-Accumulation (for PUSCH) is not provided (this parameter is used to indicate whether the UE cumulatively applies the TPC command is enabled (when this parameter is not present / not enabled, the UE cumulatively applies the TPC command), it is determined according to formula (1), but is not limited thereto.

[0168] In other embodiments, the PUSCH power control adjustment state f b,f,c(i,l) is an absolute closed-loop power control adjustment value. For example, when tpc-Accumulation is provided (for PUSCH) (when this parameter is present / deactivated / not enabled, the UE does not cumulatively apply the TPC command or does not accumulate when the UE applies the TPC command), it is determined according to formula (2), but is not limited thereto.

[0169] or

[0170] f b,f,c (i,l)=δPUSCH,b,f,c(i,l) (2)

[0171] Where δPUSCH,b,f,c(i,l) are TPC command values, which are included, for example, in the DCI format for scheduling PUSCH or in DCI format 2_2 (with TPC-PUSCH-RNTI scrambling), f b,f,c (i-i0,l) represents the closed-loop power control adjustment value for PUSCH transmission opportunity i-i0. D represents the set of TPC command values i The sum of (all) TPC command values ​​in the set, where l represents the closed-loop index. How to determine set D? i The TPC command value in this application can be referenced from relevant technologies, but other methods can also be used, and this application is not limited to this.

[0172] In some embodiments, PUCCH power control adjustment stateg b,f,c (i,l) is the cumulative closed-loop power control adjustment value, SRS power control adjustment state. b,f,c (i,l) is the cumulative or absolute closed-loop power control adjustment value. For specific determination methods, please refer to relevant technologies, but other methods may also be used; this application is not limited to these.

[0173] In some embodiments, f b,f,c (i,l) / g b,f,c (i,l) / h b,f,c (i,l) (respectively) and (for PUSCH / PUCCH and SRS) l correspondences, term f b,f,c (i,l) / g b,f,c (i,l) / h b,f,c(i,l) and l are interchangeable, or the terms "closed-loop index" and "PUSCH / PUCCH / SRS power control adjustment state" for PUSCH / PUCCH / SRS are interchangeable. For example, "PUSCH power control adjustment state" b,f,c "(i,l)" and "PUSCH power control adjustment statel" or "closed-loop index l" for PUSCH can be interchanged. The situation is similar for PUCCH and SRS, and will not be listed here.

[0174] In some embodiments, the TPC command is applied to the PUSCH power control adjustment state l, including: the TPC command value is represented as δPUSCH,b,f,c(i,l) / used to determine the PUSCH power control adjustment state f. b,f,c (i,l). The TPC command is applied to PUCCH power control adjustment state l, including: the TPC command value is represented as δPUSCH,b,f,c(i,l) / used to determine the PUCCH power control adjustment state g. b,f,c (i,l). The TPC command is applied to SRS power control adjustment state l, including: the TPC command value is represented as δPUCCH,b,f,c(i,l) / used to determine SRS power control adjustment state h. b,f,c (i,l).

[0175] For example, if a TPC command is applied to the PUSCH power control adjustment state l = 0, then the TPC command value is δPUSCH,b,f,c(i,0), and / or, used to determine the PUSCH power control adjustment state f. b,f,c (i,0). If the TPC command is applied to the PUSCH power control adjustment state l=1, then the TPC command value is δPUSCH,b,f,c(i,1), and / or, used to determine the PUSCH power control adjustment state f. b,f,c (i,1). The cases for PUCCH and SRS are similar, and will not be listed here.

[0176] In some embodiments, the DCI for scheduled uplink transmissions includes: a DCI for activating / triggering (Type 2) CG PUSCH, and / or a DCI for activating / triggering a PUSCH that transmits SP-CSI or carries SP-CSI via PUSCH (e.g., a DCI belonging to the scheduling PUSCH), and / or a DCI for dynamically scheduling PUSCH / PUCCH.

[0177] In some embodiments, for a DCI that schedules a PUSCH including a TPC command, the TPC command in the DCI is applied to the PUSCH power control adjustment state (l=0 and / or l=1), and / or the SRS power control adjustment state (l=0 and / or l=1); for a DCI that schedules a PUCCH including a TPC command, the TPC command in the DCI is applied to the PUCCH power control adjustment state (l=0 and / or l=1).

[0178] In some embodiments, for DCI scheduling uplink transmissions including TPC commands, the UE determines which / which power control adjustment states (l=0 and / or l=1) the TPC commands are applied to, and / or whether the TPC commands are applied or ignored, based on the uplink transmissions scheduled by the DCI (meeting specific conditions). For example, for DCI scheduling PUSCHs including TPC commands, the UE determines which / which PUSCH power control adjustment states (l=0 and / or l=1) the TPC commands are applied to, based on the PUSCH transmissions scheduled by the DCI (meeting specific conditions). For example, for DCI scheduling PUCCHs including TPC commands, the UE determines which / which PUCCH power control adjustment states (l=0 and / or l=1) the TPC commands are applied to, based on the PUCCH transmissions scheduled by the DCI (meeting specific conditions).

[0179] In some embodiments, a DCI schedules one or more uplink transmissions. A DCI scheduling more than one uplink transmission includes: the DCI (dynamically) scheduling more than one PUSCH (different PUSCHs are used to carry different TBs); or, the DCI scheduling PUSCHs have (Type A or Type B) repetition (one uplink transmission corresponds to one PUSCH repetition, where, for Type B repetition, one uplink transmission corresponds to one nominal repetition or actual repetition); or the DCI scheduling PUSCHs have TBoMS (i.e., one TB is transmitted across multiple time slots, one uplink transmission corresponds to one PUSCH transmission in one time slot); or, the DCI activates / triggers a (Type 2) CG PUSCH; or, the DCI activates / triggers a PUSCH that transmits SP-CSI or carries SP-CSI; or, the DCI scheduling PUCCHs have repetition (one uplink transmission corresponds to one PUCCH repetition). For the above different scheduling scenarios, the TPC command usage method in the DCI can be the same, or the TPC command usage method in the DCI can be different for the above different scheduling scenarios.

[0180] In some embodiments, the power control adjustment states associated with more than one uplink transmission scheduled by the DCI include more than one power control adjustment state (e.g., different scheduled uplink transmissions are associated with l=0 and l=1 respectively), or, the power control adjustment states associated with more than one uplink transmission scheduled by the DCI that meets a specific condition include more than one power control adjustment state (e.g., different scheduled uplink transmissions that meet a specific condition are associated with l=0 and l=1 respectively), or, the power control adjustment states associated with one or more uplink transmissions scheduled by the DCI (only) include one power control adjustment state (e.g., all scheduled uplink transmissions are associated with l=0 or all are associated with l=1), or, the power control adjustment states associated with one or more uplink transmissions scheduled by the DCI that meet a specific condition (only) include one power control adjustment state (e.g., all scheduled uplink transmissions that meet a specific condition are associated with l=0 or all are associated with l=1).

[0181] In some embodiments, the DCI schedules one or more uplink transmissions, and the power control adjustment states associated with the uplink transmissions scheduled by the DCI include all power control adjustment states associated with any one of the uplink transmissions scheduled by the DCI, and / or, the power control adjustment states associated with uplink transmissions scheduled by the DCI that meet specific conditions include all power control adjustment states associated with any one of the uplink transmissions scheduled by the DCI that meets specific conditions.

[0182] In some embodiments, uplink transmissions that meet specific conditions include:

[0183] - The valid uplink transmission scheduled / indicated by the DCI, or,

[0184] -(Without configuring sbfd-Configuration2-Transmission,) the uplink transmission of the associated valid time-domain resource type scheduled / indicated by the DCI, or,

[0185] -(With sbfd-Configuration2-Transmission configured,) the downlink control information schedules uplink transmissions in the first time domain resource and / or uplink transmissions in the second time domain resource, or,

[0186] - The DCI schedules / indicates (in chronological order) uplink transmissions with specific sequence numbers (e.g., the first or last uplink transmission), or,

[0187] - The DCI schedules / indicates (in chronological order) valid uplink transmissions with specific sequence numbers (e.g., the first or last valid uplink transmission), or,

[0188] - The DCI schedules / instructs (in chronological order) uplink transmissions of associated valid time-domain resource types with specific sequence numbers (e.g., the first or last uplink transmission of an associated valid time-domain resource type).

[0189] For DCI scheduling PUSCH and DCI scheduling PUCCH, uplink transmissions that meet specific conditions may include the same or different situations described above.

[0190] In some embodiments, a valid uplink transmission satisfies one or more of the following conditions: it does not overlap with a symbol indicated as downlink by TDD-UL-DL-ConfigCommon / tdd-UL-DL-ConfigurationDedicated (excluding the symbol indicated as downlink), it does not overlap with a symbol for an SSB (within the active DL BWP by ssb-PositionsInBurst in SIB1 or in ServingCellConfigCommon (or by NonCellDefiningSSB)) (excluding the symbol for that SSB), and it does not overlap with an invalid time-domain resource type or is in a valid time-domain resource type (only if no specific information / specific higher-level parameter (sbfd-Configuration2-Transmission) is provided).

[0191] In some embodiments, for uplink transmissions scheduled by DCI, the valid time-domain resource type is determined based on the symbol type of the first uplink transmission indicated / scheduled by DCI or by higher-layer signaling (whether it is an SBFD symbol or a non-SBFD symbol), while the other time-domain resource type is an invalid time-domain resource type. For example, if the first uplink transmission is in an SBFD symbol (the symbol type of the first uplink transmission is SBFD), then the valid symbol type is SBFD; if the first uplink transmission is in a non-SBFD symbol (the symbol type of the first uplink transmission is non-SBFD), then the valid symbol type is non-SBFD.

[0192] In some embodiments, uplink transmissions associated with valid time-domain resource types include uplink transmissions in valid symbol types (the corresponding symbol type is an uplink transmission of a valid symbol type).

[0193] In some embodiments, for a DCI that schedules an uplink transmission including a TPC command, the TPC command in the DCI is applied to all power control adjustment states associated with the uplink transmission scheduled by the DCI. The TPC command may be applied to (all) power control adjustment states associated with uplink transmissions that meet specific conditions scheduled by the DCI, or the TPC command may be applied to (all) power control adjustment states associated with valid time-domain resource types corresponding to uplink transmissions scheduled by the DCI, or the TPC command may be applied to all (configured / UE-maintained) power control adjustment states, or the TPC command may be applied to the default power control adjustment state (e.g., l=0, or l=1, or power control adjustment state associated with non-SBFD symbols (uplink transmissions), or power control adjustment state associated with SBFD symbols (uplink transmissions), or the power control adjustment state to which the TPC command is applied (e.g., l=0 and / or l=1) is determined (indicated / configured / provided) by another information sent by the network device.

[0194] The following example illustrates how to use a TPC command in a DCI that includes a TPC command to schedule uplink transmissions.

[0195] For example, in this DCI, the TPC command is applied to all power control adjustment states l associated with the (valid) uplink transmission scheduled by the DCI.

[0196] For example, for a DCI that schedules PUSCH, assuming the PUSCH transmission association (PUSCH power control adjustment state) l = 0 in an SBFD symbol and l = 1 in an SBFD symbol: When a DCI schedules one (valid) PUSCH transmission, if the (valid) PUSCH transmission scheduled by the DCI is in a non-SBFD symbol, then the TPC command value in the DCI is applied to l = 0; if the (valid) PUSCH transmission scheduled by the DCI is in an SBFD symbol, then the TPC command value in the DCI is applied to l = 1. When a DCI schedules more than one (valid) PUSCH transmission, if all (valid) PUSCH transmissions scheduled by the DCI are in non-SBFD symbols, then the TPC command value in the DCI is applied to l = 0; if all (valid) PUSCH transmissions scheduled by the DCI are in SBFD symbols, then the TPC command value in the DCI is applied to l = 1. If the (valid) PUSCH transmission scheduled by the DCI includes PUSCH transmissions in both non-SBFD symbols and SBFD symbols, then the TPC command value in the DCI applies to l=0 and l=1. (The method is similar if the PUSCH transmission associated with (PUSCH power control adjustment state) l=0 in SBFD symbols and l=1 in SBFD symbols, and will not be elaborated here.)

[0197] For example, assuming both PUSCH transmissions in an SBFD symbol and PUSCH transmissions in a non-SBFD symbol are associated (PUSCH power control adjustment state) l=0: the TPC command value in the DCI applies to l=0, regardless of whether the scheduled (valid) PUSCH transmission is in an SBFD symbol or a non-SBFD symbol. For example, assuming both PUSCH transmissions in an SBFD symbol and PUSCH transmissions in a non-SBFD symbol are associated (PUSCH power control adjustment state) l=1: the TPC command value in the DCI applies to l=1, regardless of whether the scheduled (valid) PUSCH transmission is in an SBFD symbol or a non-SBFD symbol.

[0198] For example, for a DCI that schedules PUCCHs, assuming the PUCCH transmission association (PUCCH power control adjustment state) l = 0 in SBFD symbols and l = 1 in SBFD symbols: When a DCI schedules one (valid) PUCCH transmission, if the (valid) PUCCH transmission scheduled by the DCI is in a non-SBFD symbol, then the TPC command value in the DCI is applied to l = 0; if the (valid) PUCCH transmission scheduled by the DCI is in an SBFD symbol, then the TPC command value in the DCI is applied to l = 1. When a DCI schedules more than one (valid) PUCCH transmission, if all (valid) PUCCH transmissions scheduled by the DCI are in non-SBFD symbols, then the TPC command value in the DCI is applied to l = 0; if all (valid) PUCCH transmissions scheduled by the DCI are in SBFD symbols, then the TPC command value in the DCI is applied to l = 1. If the (valid) PUCCH transmission scheduled by the DCI includes PUCCH transmissions in both non-SBFD symbols and SBFD symbols, then the TPC command value in the DCI applies to l=0 and l=1. (The method is similar if the PUCCH transmission in the SBFD symbol is associated with (PUCCH power control adjustment state) l=0 and the PUCCH transmission in the SBFD symbol is associated with (PUCCH power control adjustment state) l=1, and will not be elaborated here.)

[0199] For example, assuming both PUCCH transmissions in an SBFD symbol and PUCCH transmissions in a non-SBFD symbol are associated (PUCCH power control adjustment state) l=0: the TPC command value in this DCI applies to l=0, regardless of whether the scheduled (valid) PUCCH transmission is in an SBFD symbol or a non-SBFD symbol. For example, assuming both PUCCH transmissions in an SBFD symbol and PUCCH transmissions in a non-SBFD symbol are associated (PUCCH power control adjustment state) l=1: the TPC command value in this DCI applies to l=1, regardless of whether the scheduled (valid) PUCCH transmission is in an SBFD symbol or a non-SBFD symbol.

[0200] For example, the TPC command is applied to (all) power control adjustment states associated with the valid time-domain resource type corresponding to the uplink transmission scheduled by the DCI. For example, if the DCI schedules a PUSCH, and if the valid time-domain resource type is an SBFD symbol, the TPC command is applied to the power control adjustment states for the SBFD symbol and / or for the PUSCH within the SBFD symbol.

[0201] For example, this TPC command is applied to all power control adjustment states (configured / maintained by the UE). For instance, if the DCI schedules a PUSCH, the UE is provided with twoPUSCH-PC-AdjustmentStates, which instruct the UE to maintain two PUSCH power control states. b,f,c (i,0) and f b,f,c (i,1)), the TPC command is applied to the two power control adjustment states. If the UE is not provided with the higher-layer parameter, the TPC command is applied to the one PUSCH power control adjustment state. b,f,c (i,0). For example, if the DCI schedules PUCCH, the UE is provided with twoPUCCH-PC-AdjustmentStates, which instruct the UE to maintain two PUCCH power control states, g b,f,c (,0) and g b,f,c (i,1)), the TPC command is applied to the two power control adjustment states. If the UE does not provide this higher-layer parameter, the TPC command is applied to the one PUCCH power control adjustment state. b,f,c (i,0).

[0202] For example, the TPC command is applied to the power control adjustment state associated with a specific sequence number of a (valid) uplink transmission (e.g., the first or last (valid) uplink transmission) scheduled / indicated by the DCI. For instance, if the DCI schedules a PUSCH, the TPC command is applied to the PUSCH power control adjustment state associated with the first (valid) PUSCH transmission; if the DCI schedules a PUCCH, the TPC command is applied to the PUCCH power control adjustment state associated with the first (valid) PUCCH transmission.

[0203] In some embodiments, for a DCI that schedules uplink transmissions including more than one TPC command / more than one TPC command field (e.g., two or more), such as DCI format 0_1 / DCI format 0_2 for scheduling PUSCH, and DCI format 1_1 / DCI format 1_2 for scheduling PUCCH, at least one of the more than one TPC command is applied, and / or at least one of the more than one TPC command is ignored.

[0204] In some embodiments, the application of a first TPC command among the more than one TPC commands includes: the first TPC command being applied to a first power control adjustment state; and / or, the application of a second TPC command among the more than one TPC commands includes: the first TPC command being applied to a second power control adjustment state.

[0205] In some embodiments, the first power control adjustment state and the second power control adjustment state respectively correspond to a default closed-loop index, and / or, the closed-loop index corresponding to the first power control adjustment state is less than the closed-loop index corresponding to the second power control adjustment state, or the closed-loop index corresponding to the first power control adjustment state is greater than the closed-loop index corresponding to the second power control adjustment state.

[0206] For example, the first power control adjustment state corresponds to closed-loop index 0, and the second power control adjustment state corresponds to closed-loop index 1. As another example, the first power control adjustment state corresponds to closed-loop index 1, and the second power control adjustment state corresponds to closed-loop index 0.

[0207] In some embodiments, the first power control adjustment state includes (all) power control adjustment states associated with uplink transmissions that meet specific conditions scheduled by the DCI, and / or the second power control adjustment state includes other power control adjustment states (configured / maintained by the UE).

[0208] In some embodiments, the second power control adjustment state includes all power control adjustment states associated with uplink transmissions that meet specific conditions as scheduled by the DCI, and / or the first power control adjustment state includes other power control adjustment states (configured / maintained by the UE).

[0209] In some embodiments, in a DCI that includes more than one TPC command, (according to the order of the corresponding bits) the first TPC command (field) precedes the second TPC command (field), or the first TPC command (field) follows the second TPC command (field). For example, in DCI format 0_1 / DCI format 0_2, the first TPC command (field) corresponds to / is the TPC command for scheduled PUSCH (field), and the second TPC command (field) corresponds to / is the Second TPC command for scheduled PUSCH (field); in DCI format 1_1 / DCI format 1_2, the first TPC command (field) corresponds to / is the TPC command for scheduled PUCCH (field), and the second TPC command (field) corresponds to / is the Second TPC command for scheduled PUCCH (field). Other names are also possible and are not limited thereto.

[0210] In some embodiments, a first TPC command (domain) and a second TPC command (domain) from more than one TPC command (domain) are applied.

[0211] In some embodiments, for a DCI that includes a scheduled uplink transmission (PUSCH / PUCCH transmission) comprising more than one TPC command (domain), a first transmit power control command and a second transmit power control command (both) of the DCI / more than one transmit power control command are applied.

[0212] For example, the first and second transmit power control commands in the DCI / more than one transmit power control command are applied if one or more of the following conditions are met:

[0213] - The DCI scheduled more than one (meeting specific conditions) uplink transmission (PUSCH / PUCCH transmission);

[0214] - (The DCI schedules) (more than one) (meeting specific conditions) uplink transmission (PUSCH / PUCCH transmission) associated with more than one (PUSCH / PUCCH) power control adjustment state;

[0215] --For example, (the DCI schedules) (more than one) (meeting specific conditions) uplink transmission (PUSCH / PUCCH transmission) is associated with PUSCH / PUCCH power control adjustment state l=0 and PUSCH / PUCCH power control adjustment state l=1. (The DCI schedules) (more than one) (meeting specific conditions) uplink transmission (PUSCH / PUCCH transmission) includes PUSCH / PUCCH transmissions associated with PUSCH / PUCCH power control adjustment state l=0 and PUSCH / PUCCH transmissions associated with PUSCH / PUCCH power control adjustment state l=1;

[0216] - (UE) is provided with two higher-level parameters to indicate (for PUSCH / PUCCH) closed loops;

[0217] -(UE) is provided with (first parameter and) second parameter / (third parameter and) fourth parameter;

[0218] - PUSCH / PUCCH transmissions in SBFD symbols and PUSCH / PUCCH transmissions in non-SBFD symbols are associated with different PUSCH / PUCCH power control adjustment states;

[0219] - The UE is provided with transmit power control cumulative parameters (for PUSCH / PUCCH);

[0220] - The UE is provided with specific higher-layer parameters (sbfd-Configuration2-Transmission) for the activation of the UL BWP and / or the UL BWP indicated by the DCI and / or the UL BWP where the uplink transmission is located.

[0221] Specifically, the DCI for scheduling PUSCH and the DCI for scheduling PUCCH must each satisfy one or more of the above requirements, or they may not each satisfy one or more of the above requirements, or the required requirements may differ. Alternatively, the DCI for scheduling PUSCH may satisfy one or more of the above requirements, while the DCI for scheduling PUCCH may not satisfy one or more of the above requirements, or vice versa.

[0222] For example, (where one or more of the above conditions are met), for a DCI that schedules uplink transmissions including two TPC commands (fields), the first TPC command value / field and the second TPC command value of the two TPC command values / fields are applied to different power control adjustment states. For example, for a DCI that schedules PUSCH / PUCCH transmissions, the first TPC command is applied to PUSCH / PUCCH power control adjustment state l=0, and the second TPC command is applied to PUSCH / PUCCH power control adjustment state l=1; or, the first TPC command is applied to PUSCH / PUCCH power control adjustment state l=1, and the second TPC command is applied to PUSCH / PUCCH power control adjustment state l=0; or, the first TPC command is applied to the PUSCH / PUCCH power control adjustment state for (in) non-SBFD symbols / SBFD symbols (PUSCH / PUCCH transmissions), and the second TPC command is applied to the PUSCH / PUCCH power control adjustment state for (in) non-SBFD symbols / SBFD symbols (PUSCH / PUCCH transmissions), and the second TPC command is applied to the PUSCH / PUCCH power control adjustment state for (in) non-SBFD symbols / SBFD symbols (PUSCH / PUCCH transmissions), and the second TPC command is applied to the PUSCH / PUCCH power control adjustment state for (in) non-SBFD symbols / SBFD symbols (PUSCH / PUCCH transmissions), and the second TPC command is applied to the PUSCH / PUCCH power control adjustment state for PUSCH / PUCCH transmissions. For PUSCH / PUCCH power control adjustment states (in SBFD symbols / non-SBFD symbols), or, a first TPC command is applied to a PUSCH / PUCCH power control adjustment state associated with a DCI-scheduled PUSCH / PUCCH transmission that meets specific conditions, and a second TPC command is applied to another PUSCH / PUCCH power control adjustment state; or, a second TPC command is applied to a PUSCH / PUCCH power control adjustment state associated with a DCI-scheduled PUSCH / PUCCH transmission that meets specific conditions, and a first TPC command is applied to another PUSCH / PUCCH power control adjustment state.

[0223] In some embodiments, for a DCI that schedules uplink transmissions (PUSCH / PUCCH transmissions) that include more than one TPC command (domain), a first TPC command in the DCI / more than one TPC command is applied and a second TPC command in the more than one TPC command is ignored; or, the second TPC command is applied and the first TPC command is ignored.

[0224] For example, if one or more of the following conditions are met, the first TPC command in the DCI / more than one TPC command is applied and the second TPC command in the more than one TPC command is ignored, or the second TPC command is applied and the first TPC command is ignored:

[0225] - This DCI only schedules one uplink transmission (PUSCH / PUCCH transmission) that meets specific conditions;

[0226] - (The DCI-scheduled) (one or more) (meeting specific conditions) uplink transmission (PUSCH / PUCCH transmission) is associated with only one (PUSCH / PUCCH) power control adjustment state; or, the power control adjustment state associated with (one or more) uplink transmissions scheduled by the DCI (only) includes only one power control adjustment state; or, the power control adjustment state associated with (one or more) uplink transmissions scheduled by the DCI (meeting specific conditions) (only) includes only one power control adjustment state.

[0227] --For example, (one or more) uplink transmissions (PUSCH / PUCCH transmissions) (meeting specific conditions) scheduled by the DCI are all associated with PUSCH / PUCCH power control adjustment state l=0 or all with PUSCH / PUCCH power control adjustment state l=1. (One or more) uplink transmissions (PUSCH / PUCCH transmissions) (meeting specific conditions) scheduled by the DCI include only PUSCH / PUCCH transmissions associated with PUSCH / PUCCH power control adjustment state l=0 or only PUSCH / PUCCH transmissions associated with PUSCH / PUCCH power control adjustment state l=1;

[0228] - (UE) No higher-level parameters are provided to indicate the two closed loops (for PUSCH / PUCCH);

[0229] -(UE) No (first and) second or (third and) fourth parameters were provided;

[0230] - PUSCH / PUCCH transmissions in SBFD symbols and PUSCH / PUCCH transmissions in non-SBFD symbols are associated with the same PUSCH / PUCCH power control adjustment state;

[0231] - (UE) No transmit power control accumulation parameters (for PUSCH / PUCCH) were provided;

[0232] - (UE) was not provided with specific higher-layer parameters (sbfd-Configuration2-Transmission) for the UL BWP that is activated and / or the UL BWP where the uplink transmission is located (as indicated by the DCI).

[0233] Specifically, the DCI for scheduling PUSCH and the DCI for scheduling PUCCH must each satisfy one or more of the above requirements, or they may not each satisfy one or more of the above requirements, or the required requirements may differ. Alternatively, the DCI for scheduling PUSCH may satisfy one or more of the above requirements, while the DCI for scheduling PUCCH may not satisfy one or more of the above requirements, or vice versa.

[0234] In some embodiments, (where one or more of the above conditions are met) for a DCI that schedules uplink transmissions including two TPC command (domains), either the first or second TPC command value / domain of the two TPC command values / domains is applied, and the other TCP command value / domain (either the second or first TPC command value / domain) is ignored.

[0235] In some embodiments, for a DCI that schedules an uplink transmission including two TPC commands (domains), (one of which is ignored), the applied (first or second) TPC command is applied to (all) power control adjustment states associated with the uplink transmission scheduled by the DCI; or, the applied TPC command is applied to (all) power control adjustment states associated with an uplink transmission scheduled by the DCI that meets specific conditions; or, the applied TPC command is applied to (all) power control adjustment states associated with the valid time domain resource type corresponding to the uplink transmission scheduled by the DCI; or, the applied TPC command is applied to all (configured / UE-maintained) power control adjustment states; or, the applied TPC command is applied to the default power control adjustment state; or, the power control adjustment state to which the applied TPC command is applied is determined (indicated / configured / provided) by other information sent by the network device.

[0236] In some embodiments, for DCI scheduling PUSCH / PUCCH transmissions, a first TPC command is applied to the PUSCH / PUCCH power control adjustment state l = 0 and / or l = 1, and a second TPC command is ignored; or, the first TPC command is ignored, and a second TPC command is applied to the PUSCH / PUCCH power control adjustment state l = 0 and / or l = 1; or, the first TPC command is applied to the PUSCH / PUCCH power control adjustment state for (in) non-SBFD symbols / SBFD symbols (PUSCH / PUCCH transmissions), and the second TPC command is ignored; or, the first TPC command... The PC command is ignored, and the second TPC command is applied to the PUSCH / PUCCH power control adjustment state for PUSCH / PUCCH transmissions (in SBFD symbols / non-SBFD symbols); or, the first TPC command is applied to the PUSCH / PUCCH power control adjustment state associated with a PUSCH / PUCCH transmission that meets specific conditions and is scheduled by DCI, and the second TPC command is ignored; or, the second TPC command is applied to the PUSCH / PUCCH power control adjustment state associated with a PUSCH / PUCCH transmission that meets specific conditions and is scheduled by DCI, and the first TPC command is ignored.

[0237] In some embodiments, the two TPC commands in a DCI (for scheduling uplink transmissions) may ignore which TPC command is associated with the uplink transmission scheduled by that DCI. For example, assuming the first TPC command corresponds to l=0 and the second TPC command corresponds to l=1, if one or more PUSCH / PUCCH transmissions scheduled by the DCI are associated with a PUSCH / PUCCH power control adjustment state l=0, then the first TPC command is applied to l=0, and the second TPC command is ignored. If one or more PUSCH / PUCCH transmissions scheduled by the DCI are associated with a PUSCH / PUCCH power control adjustment state l=1, then the first TPC command is ignored, and the second TPC command is applied to l=1.

[0238] The following examples illustrate how to use TPC commands in a DCI that schedules uplink transmissions, including more than one TPC command.

[0239] For example, for a DCI that schedules a PUSCH, assuming the PUSCH transmission association (PUSCH power control adjustment state) l = 0 in the SBFD symbol and l = 1 in the SBFD symbol, and the first TPC command (only) corresponds to / applies to l = 0, and the second TPC command (only) corresponds to / applies to l = 1: When a DCI schedules a (valid) PUSCH transmission, if the (valid) PUSCH transmission scheduled by the DCI is in a non-SBFD symbol, then the first TPC command value in the DCI is applied to l = 0, and the second TPC command value is ignored; if the (valid) PUSCH transmission scheduled by the DCI is in an SBFD symbol, then the first TPC command value in the DCI is ignored, and the second TPC command value is applied to l = 1. When a DCI schedules more than one (valid) PUSCH transmission, if all (valid) PUSCH transmissions scheduled by the DCI are in non-SBFD symbols, then the first TPC command value in the DCI is applied as l=0, and the second TPC command value is ignored. If all (valid) PUSCH transmissions scheduled by the DCI are in SBFD symbols, then the first TPC command value in the DCI is ignored, and the second TPC command value is applied as l=1. If the (valid) PUSCH transmissions scheduled by the DCI include PUSCH transmissions in both non-SBFD and SBFD symbols, then the first TPC command value in the DCI is applied as l=0, and the second TPC command value is applied as l=1. (If the PUSCH transmission association (PUSCH power control adjustment state) l = 0 in the SBFD symbol, and the PUSCH transmission association (PUSCH power control adjustment state) l = 1 in the SBFD symbol, and / or, the first TPC command (only) corresponds to / targets l = 1, and the second TPC command (only) corresponds to / targets l = 0, the method is similar and will not be repeated here.)

[0240] For example, (assuming the first TPC command corresponds only to / applies to l=0, and the second TPC command corresponds only to / applies to l=1): If all (satisfied) PUSCH transmissions scheduled by the DCI are associated with PUSCH power control adjustment status (l=0), the first TPC command value in the DCI is applied to l=0, and the second TPC command value is ignored. If all (satisfied) PUSCH transmissions scheduled by the DCI are associated with PUSCH power control adjustment status (l=1), the second TPC command value in the DCI is applied to l=1, and the first TPC command value is ignored.

[0241] For example, for a DCI that schedules a PUCCH, assuming the PUCCH transmission association (PUCCH power control adjustment state) l = 0 in the SBFD symbol and l = 1 in the SBFD symbol, and the first TPC command (only) corresponds to / applies to l = 0, and the second TPC command (only) corresponds to / applies to l = 1: When a DCI schedules a (valid) PUCCH transmission, if the (valid) PUCCH transmission scheduled by the DCI is in a non-SBFD symbol, then the first TPC command value in the DCI is applied to l = 0, and the second TPC command value is ignored; if the (valid) PUCCH transmission scheduled by the DCI is in an SBFD symbol, then the first TPC command value in the DCI is ignored, and the second TPC command value is applied to l = 1. When a DCI schedules more than one (valid) PUCCH transmission, if all (valid) PUCCH transmissions scheduled by the DCI are in non-SBFD symbols, then the first TPC command value in the DCI is applied as l=0, and the second TPC command value is ignored. If all (valid) PUCCH transmissions scheduled by the DCI are in SBFD symbols, then the first TPC command value in the DCI is ignored, and the second TPC command value is applied as l=1. If the (valid) PUCCH transmissions scheduled by the DCI include PUCCH transmissions in both non-SBFD and SBFD symbols, then the first TPC command value in the DCI is applied as l=0, and the second TPC command value is applied as l=1. (If the PUCCH transmission association (PUCCH power control adjustment state) l = 0 in the SBFD symbol, and the PUCCH transmission association (PUCCH power control adjustment state) l = 1 in the SBFD symbol, and / or, the first TPC command (only) corresponds to / targets l = 1, and the second TPC command (only) corresponds to / targets l = 0, the method is similar and will not be repeated here.)

[0242] For example, (assuming the first TPC command corresponds only to / for l=0, and the second TPC command corresponds only to / for l=1): If all PUCCH transmissions (meeting specific conditions) scheduled by this DCI are associated with PUCCH power control adjustment status (l=0), the first TPC command value in this DCI is applied to l=0, and the second TPC command value is ignored. If all PUCCH transmissions (meeting specific conditions) scheduled by this DCI are associated with PUCCH power control adjustment status (l=1), the second TPC command value in this DCI is applied to l=1, and the first TPC command value is ignored.

[0243] In some embodiments, the SRS power control adjustment state h b,f,c (i,l)=fb,f,c (i,l). For example, if the higher-level parameter srs-PowerControlAdjustmentStates indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions, then h b,f,c (i,l)=f b,f,c (i,l).

[0244] In some embodiments, for an SRS resource set, the corresponding high-level parameter srs-PowerControlAdjustmentStates can be set to sameAsFci2 or separateClosedLoop to indicate the SRS power control adjustment state of the SRS resource set (corresponding to the SRS transmission) and f. b,f,c (i,0) are the same (i.e., equal to f) b,f,c (i,0)) or with f b,f,c (i,1) are the same (i.e., equal to f) b,f,c (i,1)) or independent of the PUSCH power control adjustment state. For example, if set to sameAsFci2, with f b,f,c (i,1) is the same; if set to separateClosedLoop, it is independent of the PUSCH power control adjustment state; if it does not exist or is released, it is the same as f. b,f,c (i,0) are the same.

[0245] In some embodiments, for an SRS resource set, if the SRS power control adjustment state corresponding to the (corresponding) SRS transmission is the same as the PUSCH power control adjustment state: if the SRS resource set is associated with SBFD symbols, it should be the same as the PUSCH power control adjustment state associated with the PUSCH transmission for the associated SBFD symbols; if the SRS resource set is associated with non-SBFD symbols, it should be the same as the PUSCH power control adjustment state associated with the PUSCH transmission for the associated non-SBFD symbols. For example, suppose the PUSCH transmission associated with SBFD symbols corresponds to f b,f,c (i,1), the PUSCH transmission corresponding to the associated SBFD symbol f b,f,c (i,0), if the SRS resource set is associated with the SBFD symbol, the corresponding h b,f,c (i,0) or h b,f,c(i,1)=f b,f,c (i,1), if the SRS resource set is associated with a non-SBFD symbol, the corresponding h b,f,c (i,0) or h b,f,c (i,1)=f b,f,c (i,0).

[0246] In some embodiments, for an SRS resource set associated with a non-SBFD symbol, the corresponding SRS transmission is associated with an SRS power control adjustment state l configured by a fifth parameter, and for an SRS resource set associated with a SBFD symbol, the corresponding SRS transmission is associated with an SRS power control adjustment state l configured by a sixth parameter.

[0247] In some embodiments, two or more of the values ​​set in the first / third / fifth parameter should be the same (both 'i0' or both 'i1'), and two or more of the values ​​set in the second / fourth / sixth parameter should be the same (both 'i0' or both 'i1'). For example, (if the higher-layer parameter srs-PowerControlAdjustmentStates indicates a same power control adjustment state for SRS transmissions and PUSCH transmissions, and / or, if SRS and PUSCH transmissions use the same power control adjustment state), when the SRS power control adjustment state l configured in the fifth parameter should have the same value as the PUSCH power control adjustment state l configured in the first parameter (both l=0 or both l=1), or when the values ​​set in the fifth and first parameters are the same, the SRS power control adjustment state l configured in the sixth parameter should have the same value as the PUSCH power control adjustment state l configured in the second parameter (both l=0 or both l=1), the UE does not expect to configure different values.

[0248] The above adaptations explain the TPC command of this application. The following section will explain the relevant content of the power margin report.

[0249] In some embodiments, the power headroom report includes a first power headroom (report) or a second power headroom (report), the first power headroom being for PUSCH (valid) and the second power headroom being for SRS (valid). For example, the first and second power headrooms are as described in Table 8:

[0250] Table 8

[0251] In some embodiments, determining the first or second power margin for a (activated) cell is based on actual transmission (actual PUSCH transmission (for the first power margin) or actual SRS transmission (for the second power margin)) or a reference format (reference PUSCH transmission (for the first power margin) or reference SRS transmission (for the second power margin)). Table 9 shows an example of an embodiment of this application:

[0252] Table 9

[0253] In some embodiments, when the first power margin for a cell is based on a reference PUSCH and the UE is provided with a first parameter (e.g., p0AlphaSetforPUSCH) and a second parameter (e.g., p0AlphaSetforPUSCH-SBFD) (for the cell's (carrier) (activated uplink BWP) (indicated uniform TCI state), the UE determines the first power margin according to the first parameter or the second parameter.

[0254] For example, the UE determines the first power margin based on either the first parameter or the second parameter, depending on the symbol type of the reference symbol, the first reference slot, the reference PUSCH, or the second reference PUSCH. For instance, when the symbol type is a first symbol (non-SBFD symbol), the UE determines the first power margin based on the first parameter; when the symbol type is a second symbol (SBFD symbol), the UE determines the first power margin based on the second parameter.

[0255] In some examples, the reference symbol includes one or more symbols (the first symbol in the cell) that overlap or fully overlap with the PUSCH transmission providing / carrying the first power margin (on the active uplink BWP), or the reference symbol includes one or more symbols (the first symbol in the first reference slot or the reference PUSCH or the second reference PUSCH), and / or the symbol type of the reference PUSCH or the second reference PUSCH is predefined (e.g., always assumed to be the first symbol or the second symbol) or configured.

[0256] For example, the reference symbol is the first symbol of the cell (carrier) (on the active uplink BWP) that overlaps or completely overlaps with the PUSCH transmission providing / carrying the first power margin. As another example, the reference symbol is the first symbol of the first reference slot, the reference PUSCH, or the second reference PUSCH.

[0257] In some examples, the first reference time slot includes one or more time slots (e.g., the first time slot) that overlap or completely overlap with the second reference time slot or reference subframe (on the active uplink BWP) of the cell (carrier), and the second reference time slot or reference subframe includes one or more time slots or subframes (on the active uplink BWP) of another cell (e.g., the UE transmits the power margin report in that other cell).

[0258] For example, the cell has the same (carrier) (active uplink BWP) subcarrier spacing and / or CP type (Normal CP or Extended CP) as the other cell, or the cell has different (carrier) (active uplink BWP) subcarrier spacing and / or CP type (Normal CP or Extended CP) as the other cell. For example, the first reference time slot is the first time slot (of one or more time slots) that overlaps or completely overlaps with the second reference time slot or reference subframe (on the active uplink BWP of the cell).

[0259] In some examples, the UE provides the first power margin in a PUSCH in the second reference time slot, and / or, when the UE provides the first power margin in a PUSCH with repetition (PUSCH repetition Type B) and a nominal repetition spans multiple time slots, the second reference time slot includes the multiple time slots (i.e., the first reference time slot is one or more time slots (e.g., the first time slot) that overlap or completely overlap with the multiple time slots (one or more time slots) of the cell (carrier) (on the active uplink BWP).

[0260] In some embodiments, when the first power margin for the cell is based on a reference PUSCH and the cell is a secondary cell (Scell) and the cell is not configured with a preamble target receive power, the first power margin is determined by applying the first preamble target receive power in the first RACH configuration (e.g., rach-ConfigCommon) of the primary cell.

[0261] In some embodiments, the first RACH configuration further includes a second preamble target received power (e.g., sbfd-RACH-SingleConfig-preambleReceivedTargetPower), or the primary cell is further configured with a second RACH configuration (e.g., sbfd-RACH-DualConfig), which includes another first preamble target received power.

[0262] In some embodiments, when the second power margin for a cell is based on a reference SRS and the UE is provided with a fifth parameter (p0AlphaSetforSRS) and a sixth parameter (p0AlphaSetforSRS-SBFD) for the (carrier-based) (activated uplink BWP-based) (indicating unified TCI state) for the cell, the UE determines the second power margin according to the fifth parameter or the sixth parameter.

[0263] For example, the UE determines the second power margin based on either the fifth parameter or the sixth parameter, depending on the symbol type of the reference symbol, the first reference slot, the reference SRS, the second reference PUSCH, or the second reference SRS. For instance, when the symbol type is the first symbol (non-SBFD symbol), the UE determines the second power margin based on the fifth parameter; when the symbol type is the second symbol (SBFD symbol), the UE determines the second power margin based on the sixth parameter.

[0264] In some examples, the reference symbol includes one or more symbols (the first symbol among) that overlap or fully overlap with the PUSCH transmission providing / carrying the second power margin of the cell (carrier) (on the active uplink BWP), or the reference symbol includes one or more symbols (the first symbol among) of the first reference slot or the reference SRS or the second reference PUSCH or the second reference SRS, and / or the symbol type of the reference SRS or the second reference PUSCH or the second reference SRS is predefined (e.g., always assumed to be the first symbol or the second symbol) or configured.

[0265] For example, the reference symbol is the first symbol of the cell (carrier) (on the active uplink BWP) that overlaps or completely overlaps with the PUSCH transmission providing / carrying the second power margin. For example, the reference symbol is the first symbol of the first reference slot or the reference SRS or the second reference PUSCH or the second reference SRS.

[0266] In some examples, the first reference time slot includes one or more time slots (e.g., the first time slot) that overlap or completely overlap with the second reference time slot or reference subframe (on the active uplink BWP) of the cell (carrier), and the second reference time slot or reference subframe includes one or more time slots or subframes (on the active uplink BWP) of another cell (e.g., the UE transmits the power margin report in that other cell).

[0267] In some examples, the UE provides the second power margin in the PUSCH in the second reference time slot, and / or, when the UE provides the second power margin in the PUSCH with repetition (PUSCH repetition Type B) and a nominal repetition spans multiple time slots, the second reference time slot includes the multiple time slots (i.e., the first reference time slot is one or more time slots (e.g., the first time slot) of the cell / carrier that overlap or completely overlap with the multiple time slots).

[0268] In some embodiments, the UE determines whether to determine the second power margin based on the fifth parameter or the sixth parameter according to the symbol type of the reference symbol or the first reference slot or the reference SRS or the second reference PUSCH or the second reference SRS or the reference SRS resource set (e.g., the SRS resource set corresponding to SRS-ResourceSetId=0 on the active uplink BWP of the cell's (carrier)).

[0269] For example, when a reference SRS resource set is configured with symbolType, if it is configured as 'sbfd', the symbol type of the reference SRS resource set is the first symbol; if it is configured as 'non-sbfd', the symbol type of the reference SRS resource set is the second symbol. For example, the symbol type of the reference SRS, the second reference PUSCH, the second reference SRS, or the reference SRS resource set (e.g., when the reference SRS resource set is configured with symbolType) is predefined (e.g., the UE assumes the symbol type is either the first symbol or the second symbol).

[0270] For example, when the symbol type is a first symbol, the processor determines the second power margin according to the fifth parameter; when the symbol type is a second symbol, the processor determines the second power margin according to the sixth parameter.

[0271] Table 10 shows an example of how the first power margin is determined in an embodiment of this application:

[0272] Table 10

[0273] The above provides an illustrative explanation of the power margin report. The following section will explain the relevant UE capabilities.

[0274] In some embodiments, the terminal device instructs the network device (by sending higher-layer signaling) that it supports more than one TPC command (for independent closed-loop power control for different time-domain resource types / for SBFD) (for a specific DCI format), and / or instructs the terminal device to support a second TPC command (for independent closed-loop power control for different time-domain resource types) (for a specific DCI format).

[0275] For example, sending sbfd-PUSCH-secondTPC-r19 (a higher-level parameter different from mTRP-PUSCH-secondTPC-r17, e.g., referred to as the seventh parameter) indicates support for DCI format 0_1 ​​(for PUSCH) and / or DCI format 0_2, including more than one TPC command or a second TPC command (for independent closed-loop power control for different time-domain resource types / for SBFD). Sending sbfd-PUCCH-secondTPC-r19 (a higher-level parameter different from mTRP-PUCCH-secondTPC-r17, e.g., referred to as the eighth parameter) indicates support for DCI format 1_1 (for PUCCH) and / or DCI format 1_2, including more than one TPC command or a second TPC command (for independent closed-loop power control for different time-domain resource types / for SBFD).

[0276] In some embodiments, the UE sends higher-layer signaling to the network device indicating that it supports two different TPC loops for PUCCH / PUSCH. For example, it sends "twoDifferentTPC-Loop-PUSCH" to indicate "whether the UE supports two different TPC loops for PUSCH closed loop power control". Another example is "twoDifferentTPC-Loop-PUCCH" to indicate "(whether) the UE supports two different TPC loops for PUCCH closed loop power control".

[0277] In some embodiments, a terminal device that supports more than one TPC command and / or a second TPC command (for independent closed-loop power control for different time-domain resource types / for SBFD) of DCI format 0_1 ​​and / or DCI format 0_2 (for PUSCH) also (indicates) supports one or more of the following capabilities:

[0278] - (Maintain) (two closed loops) (for PUSCH) / two different TPC loops (two Different TPC-Loop-PUSCH);

[0279] - Independent uplink power control (parameters) in the first and second time domain resources (based on the unified transport configuration indication (TCI) framework);

[0280] - Transmission and / or reception across first and second time domain resources;

[0281] - Independent SRS resource set configurations in the first and second time domain resources;

[0282] -Independent PUCCH frequency resource configuration in the first and second time domain resources;

[0283] -Independent frequency hopping offsets in the first and second time domain resources;

[0284] -Community configuration of time-frequency location of the SBFD sub-band;

[0285] - Uplink transmission in one uplink subband and downlink reception in one or two downlink subbands;

[0286] - Link direction determination based on configuration or scheduling for sending or receiving and for conflict resolution;

[0287] - Uplink transmission or downlink reception across first and second time domain resources in different time slots, wherein the uplink transmission or downlink reception is restricted to the first or second time domain resource;

[0288] - Separate CSI reports for the first and second time domain resources.

[0289] In some embodiments, a terminal device that supports more than one TPC command and / or a second TPC command (for independent closed-loop power control for different time-domain resource types / for SBFD) of DCI format 1_1 and / or DCI format 1_2 (for PUCCH) also (indicates) supports one or more of the following capabilities:

[0290] - (Maintain) two closed loops (two different TPC loops for PUCCH);

[0291] - Independent uplink power control (parameters) in the first and second time domain resources (based on the unified transport configuration indication (TCI) framework);

[0292] - Transmission and / or reception across first and second time domain resources;

[0293] - Independent SRS resource set configurations in the first and second time domain resources;

[0294] -Independent PUCCH frequency resource configuration in the first and second time domain resources;

[0295] -Independent frequency hopping offsets in the first and second time domain resources;

[0296] -Community configuration of time-frequency location of the SBFD sub-band;

[0297] - Uplink transmission in one uplink subband and downlink reception in one or two downlink subbands;

[0298] - Link direction determination based on configuration or scheduling for sending or receiving and for conflict resolution;

[0299] - Uplink transmission or downlink reception across first and second time domain resources in different time slots, wherein the uplink transmission or downlink reception is restricted to the first or second time domain resource;

[0300] - Separate CSI reports for the first and second time domain resources.

[0301] The above illustrations depict some UE capabilities related to this application, but this application is not limited thereto.

[0302] In some embodiments, for a DCI that includes a non-scheduled uplink transmission, one TPC command in the DCI is applied to all power control adjustment states (configured / maintained by the UE), or the TPC command is applied to the default power control adjustment state, or which power control adjustment state the TPC command is applied to is determined (indicated / configured / provided) by other information sent by the network device.

[0303] In some embodiments, the terminal device is provided with one or more of the following information:

[0304] Information used to configure more than one TPC command and / or a second TPC command for a specific DCI format, and / or information used to configure more than one (PUSCH / PUCCH) power control adjustment state, and / or information used to configure a first time domain resource and / or a second time domain resource, and / or information used to configure uplink subbands and / or downlink subbands, and / or information used to configure (as associated with the indicated uniform TCI state) a set of power control parameters (first parameter and / or third parameter and / or fifth parameter) for uplink transmissions for associated first time domain resources, and / or information used to configure (as associated with the indicated uniform TCI state (TCI-State or TCI-UL-State)) a set of power control parameters (second parameter and / or fourth parameter and / or sixth parameter) for uplink transmissions for associated second time domain resources, and / or information used to configure two SRS resource sets (srs-ResourceSetToAddModList or srs-resourceSetToAddModList) for codebook or non-codebook purposes (for the first time domain resource and the second time domain resource respectively). srs-ResourceSetToAddModListDCI-0-2), and / or, specific information (specific higher-level parameter sbfd-Configuration2-Transmission) for the UL BWP that is activated and / or (the DCI) that indicates the UL BWP and / or the UL BWP where the uplink transmission is located.

[0305] For example, the function of sbfd-Configuration2-Transmission is as follows:

[0306] Table 11

[0307] For example, the corresponding symbolType is set to / to indicate the SRS resource set of the SBFD symbol for / associated SBFD symbol, and the corresponding symbolType is set to / to indicate the SRS resource set of the non-SBFD symbol for / associated non-SBFD symbol.

[0308] In some embodiments, the closed-loop indexes in the power control parameter set for uplink transmission associated with the first time domain resource and the power control parameter set for uplink transmission associated with the second time domain resource are different; or, the closed-loop indexes for uplink transmission associated with the first time domain resource and the uplink transmission associated with the second time domain resource are different; or, the closed-loop indexes corresponding to the first time domain resource and the second time domain resource are different.

[0309] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0310] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0311] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the transmit power control command (TPC command) is used to determine the transmit power of uplink transmission associated with the first time-domain resource and / or the transmit power of uplink transmission associated with the second time-domain resource. Thus, uplink transmission and reception can be supported in the presence of the aforementioned different time-domain resources.

[0312] Second aspect of the embodiments

[0313] This application provides an uplink receiving method, which will be described from the perspective of the network device. The content that is the same as that in the first aspect of the embodiment will not be repeated.

[0314] Figure 6 is a schematic diagram of an uplink receiving method according to an embodiment of this application. As shown in Figure 6, the method includes:

[0315] 601, The network device transmits downlink control information (DCI), the downlink control information including a transmit power control command (TPC command), the transmit power control command being used to determine the transmit power of uplink transmission associated with a first time domain resource (in a cell / (uplink) carrier / (uplink) BWP with SBFD enabled) and / or the transmit power of uplink transmission associated with a second time domain resource (in a cell / (uplink) carrier with SBFD enabled); and

[0316] 602, the network device receives the uplink transmission of the associated first time domain resource and / or the uplink transmission of the associated second time domain resource.

[0317] It is worth noting that Figure 6 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 6 above.

[0318] In some embodiments, the DCI transmitted by the network device can be different DCI formats, including: DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 0_3, DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 1_3, DCI format 2_3, DCI format 2_2, etc., and this application is not limited thereto. Furthermore, the network device can also send various configuration information / instruction information to the terminal device; reference can be made to related technologies regarding this configuration information / instruction information.

[0319] In some embodiments, information for configuring the first time-domain resources and / or the second time-domain resources may (optionally) be stored in system information (e.g., SIB1) (broadcast or transmitted via dedicated signaling) and / or in the (public) serving cell configuration and / or in information elements for configuring random access resources (at least including RO).

[0320] In some embodiments, the transmit power control command is used to determine the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource, including:

[0321] The power control command is applied to the power control adjustment state associated with the uplink transmission of the associated first time domain resource (for the uplink transmission of the associated first time domain resource) and / or the power control adjustment state associated with the uplink transmission of the associated second time domain resource (for the uplink transmission of the associated second time domain resource).

[0322] The power control adjustment state associated with the uplink transmission of the associated first time domain resource is the same as the power control adjustment state associated with the uplink transmission of the associated second time domain resource, or the power control adjustment state associated with the uplink transmission of the associated first time domain resource is different from the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

[0323] In some embodiments, the transmit power control command is used to determine the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource, and further includes:

[0324] The terminal device determines the transmission power of the uplink transmission of the associated first time domain resource based on the power control adjustment state associated with the uplink transmission of the associated first time domain resource, and / or determines the transmission power of the uplink transmission of the associated second time domain resource based on the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

[0325] In some embodiments, the power control adjustment state associated with the uplink transmission includes the power control adjustment state corresponding to the time-domain resource type associated with the uplink transmission (for the time-domain resource type associated with the uplink transmission), and / or, the power control adjustment state associated with the uplink transmission is related to the closed-loop index configuration (closedLoopIndex) corresponding to the uplink transmission or to the closed-loop index configuration (closedLoopIndex) corresponding to the time-domain resource type associated with the uplink transmission.

[0326] In some embodiments, for a DCI that schedules an uplink transmission including a TPC command, the TPC command in the DCI is applied to (all) power control adjustment states associated with the uplink transmission scheduled by the DCI, or the TPC command is applied to (all) power control adjustment states associated with an uplink transmission scheduled by the DCI that meets specific conditions, or the TPC command is applied to (all) power control adjustment states associated with the valid time-domain resource type corresponding to the uplink transmission scheduled by the DCI, or the TPC command is applied to all (configured / UE-maintained) power control adjustment states, or the TPC command is applied to the default power control adjustment state, or the power control adjustment state to which the TPC command is applied is determined (indicated / configured / provided) by other information sent by the network device.

[0327] In some embodiments, for a DCI that includes a non-scheduled uplink transmission, one TPC command in the DCI is applied to all power control adjustment states (configured / maintained by the UE), or the TPC command is applied to the default power control adjustment state, or which power control adjustment state the TPC command is applied to is determined (indicated / configured / provided) by other information sent by the network device.

[0328] The above description only covers the steps or processes relevant to this application, but this application is not limited thereto. The methods in the embodiments of this application may also include other steps or processes, and for details of these steps or processes, please refer to related technologies.

[0329] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0330] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the transmit power control command (TPC command) is used to determine the transmit power of uplink transmission associated with the first time-domain resource and / or the transmit power of uplink transmission associated with the second time-domain resource. Thus, uplink transmission and reception can be supported in the presence of the aforementioned different time-domain resources.

[0331] Third aspect of the embodiments

[0332] This application provides an uplink transmission device. This device may be, for example, a terminal device, or one or more components or parts configured within a terminal device; details identical to those in the first aspect of the embodiment will not be repeated.

[0333] Figure 7 is a schematic diagram of an uplink transmitting device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method of the embodiment of the first aspect, its specific implementation can refer to the embodiment of the first aspect, and the contents that are the same will not be described again. As shown in Figure 7, the uplink transmitting device 700 includes: a receiver 701 and a transmitter 702; it may also include a processor 703.

[0334] Receiver 701 receives downlink control information (DCI), which includes a transmit power control command (TPC command) for determining the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource; and

[0335] Transmitter 702 transmits the uplink transmission of the associated first time domain resource and / or the uplink transmission of the associated second time domain resource.

[0336] In some embodiments, the transmit power control command is used to determine the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource, including:

[0337] The power control command is applied to the power control adjustment state associated with the uplink transmission of the associated first time domain resource (for the uplink transmission of the associated first time domain resource) and / or the power control adjustment state associated with the uplink transmission of the associated second time domain resource (for the uplink transmission of the associated second time domain resource).

[0338] The power control adjustment state associated with the uplink transmission of the associated first time domain resource is the same as the power control adjustment state associated with the uplink transmission of the associated second time domain resource, or the power control adjustment state associated with the uplink transmission of the associated first time domain resource is different from the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

[0339] In some embodiments, the processor 703 determines the transmit power of the uplink transmission of the associated first time domain resource based on the power control adjustment state associated with the uplink transmission of the associated first time domain resource, and / or determines the transmit power of the uplink transmission of the associated second time domain resource based on the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

[0340] In some embodiments, the power control adjustment state associated with the uplink transmission includes the power control adjustment state corresponding to the time-domain resource type associated with the uplink transmission (for the time-domain resource type associated with the uplink transmission), and / or, the power control adjustment state associated with the uplink transmission is related to the closed-loop index configuration (closedLoopIndex) corresponding to the uplink transmission or to the closed-loop index configuration (closedLoopIndex) corresponding to the time-domain resource type associated with the uplink transmission.

[0341] In some embodiments, for a DCI that schedules an uplink transmission including a TPC command, the TPC command in the DCI is applied to (all) power control adjustment states associated with the uplink transmission scheduled by the DCI, or the TPC command is applied to (all) power control adjustment states associated with an uplink transmission scheduled by the DCI that meets specific conditions, or the TPC command is applied to (all) power control adjustment states associated with the valid time-domain resource type corresponding to the uplink transmission scheduled by the DCI, or the TPC command is applied to all (configured / UE-maintained) power control adjustment states, or the TPC command is applied to the default power control adjustment state, or the power control adjustment state to which the TPC command is applied is determined (indicated / configured / provided) by other information sent by the network device.

[0342] In some embodiments, the DCI schedules one or more uplink transmissions, and the power control adjustment states associated with the uplink transmissions scheduled by the DCI include all power control adjustment states associated with any one of the uplink transmissions scheduled by the DCI, and / or, the power control adjustment states associated with uplink transmissions scheduled by the DCI that meet specific conditions include all power control adjustment states associated with any one of the uplink transmissions scheduled by the DCI that meets specific conditions.

[0343] In some embodiments, uplink transmissions that meet specific conditions include:

[0344] The effective uplink transmission scheduled by the DCI, or,

[0345] (Without sbfd-Configuration2-Transmission configured) the uplink transmission of the associated valid time-domain resource type scheduled by the DCI, or,

[0346] (When sbfd-Configuration2-Transmission is configured), the downlink control information schedules uplink transmissions in the first time domain resource and / or uplink transmissions in the second time domain resource, or,

[0347] The first uplink transmission scheduled by the DCI, or,

[0348] The first valid uplink transmission scheduled by the DCI, or

[0349] The first uplink transmission of the associated valid time-domain resource type scheduled by DCI.

[0350] In some embodiments, for a DCI that schedules uplink transmissions including more than one TPC command, at least one of the more than one TPC command is applied, and / or at least one of the more than one TPC command is ignored.

[0351] In some embodiments, a first TPC command and a second TPC command are applied from among the more than one TPC command.

[0352] In some embodiments, the power control adjustment states associated with more than one uplink transmission scheduled by the DCI include more than one power control adjustment state; or, the power control adjustment states associated with more than one uplink transmission scheduled by the DCI that meets certain conditions include more than one power control adjustment state; or, the power control adjustment states associated with one or more uplink transmissions scheduled by the DCI (only) include one power control adjustment state; or, the power control adjustment states associated with one or more uplink transmissions scheduled by the DCI that meet certain conditions (only) include one power control adjustment state.

[0353] In some embodiments, a first TPC command among the more than one TPC commands is applied, and a second TPC command among the more than one TPC commands is ignored; or, the second TPC command is applied, and the first TPC command is ignored.

[0354] In some embodiments, the power control adjustment state associated with one or more uplink transmissions scheduled by the DCI (only) includes one power control adjustment state, or the power control adjustment state associated with one or more uplink transmissions scheduled by the DCI that meet certain conditions (only) includes one power control adjustment state.

[0355] In some embodiments, the applied TPC command is applied to one power control adjustment state, or the applied TPC command is applied to (all) power control adjustment states associated with the uplink transmission scheduled by the DCI, or the applied TPC command is applied to (all) power control adjustment states associated with the uplink transmission scheduled by the DCI that meets specific conditions, or the applied TPC command is applied to (all) power control adjustment states associated with the valid time-domain resource type corresponding to the uplink transmission scheduled by the DCI, or the applied TPC command is applied to all (configured / UE-maintained) power control adjustment states, or the applied TPC command is applied to the default power control adjustment state, or which power control adjustment state the applied TPC command is applied to is determined (indicated / configured / provided) by other information sent by the network device.

[0356] In some embodiments, the application of a first TPC command among the more than one TPC commands includes: the first TPC command being applied to a first power control adjustment state; and / or,

[0357] The application of a second TPC command in the more than one TPC command includes: the first TPC command being applied to a second power control adjustment state.

[0358] In some embodiments, the first power control adjustment state and the second power control adjustment state respectively correspond to default closed-loop indices, and / or, the closed-loop index corresponding to the first power control adjustment state is less than the closed-loop index corresponding to the second power control adjustment state, or the closed-loop index corresponding to the first power control adjustment state is greater than the closed-loop index corresponding to the second power control adjustment state; or...

[0359] The first power control adjustment state includes (all) power control adjustment states associated with uplink transmissions that meet specific conditions scheduled by the DCI, and / or, the second power control adjustment state includes other power control adjustment states (configured / maintained by the UE); or,

[0360] The second power control adjustment state includes all power control adjustment states associated with uplink transmissions that meet specific conditions as scheduled by the DCI, and / or the first power control adjustment state includes other power control adjustment states (configured / maintained by the UE).

[0361] In some embodiments, transmitter 702 instructs the network device that the terminal device supports more than one TPC command (for independent closed-loop power control for different time-domain resource types) (for a specific DCI format), and / or instructs the terminal device to support a second TPC command (for independent closed-loop power control for different time-domain resource types) (for a specific DCI format).

[0362] In some embodiments, a terminal device that supports more than one TPC command and / or a second TPC command also supports one or more of the following capabilities:

[0363] (Maintain) two closed loops;

[0364] Independent uplink power control (parameters) in the first and second time domain resources (based on the same TCI framework);

[0365] Transmission and / or reception across first and second time domain resources;

[0366] Independent SRS resource set configurations in the first and second time domain resources;

[0367] Independent PUCCH frequency resource configurations in the first and second time domain resources;

[0368] Independent frequency hopping offsets in the first and second time domain resources;

[0369] The common configuration of the cell for the time-frequency location of the SBFD sub-band;

[0370] Uplink transmission in one uplink subband and downlink reception in one or two downlink subbands;

[0371] Link direction determination based on configuration or scheduling for sending or receiving and for conflict resolution;

[0372] Uplink transmission or downlink reception across first and second time domain resources in different time slots, wherein the uplink transmission or downlink reception is restricted to the first or second time domain resources;

[0373] Independent CSI reports for the first and second time domain resources.

[0374] In some embodiments, the power headroom report includes a first power headroom (report) or a second power headroom (report), the first power headroom being valid for PUSCH and the second power headroom being valid for SRS.

[0375] In some embodiments, the processor 703 determines a first power margin or a second power margin for a (activated) cell based on actual transmission or a reference format.

[0376] In some embodiments, when the first power margin for the cell is based on a reference PUSCH and (with a unified TCI state indicating the (carrier-based) (active uplink BWP) state for the cell), the terminal device is provided with a first parameter and a second parameter, and the processor 703 determines the first power margin based on the first parameter or the second parameter, and / or,

[0377] When the second power margin for the cell is based on the reference SRS and (the unified TCI state indicating (carrier-based) (active uplink BWP) for the cell), the terminal device is provided with a fifth parameter and a sixth parameter, and the processor 703 determines the second power margin according to the fifth parameter or the sixth parameter.

[0378] In some embodiments, the processor 703 determines whether to determine the first power margin based on the first parameter or the second parameter, according to the symbol type of the reference symbol or the first reference time slot or the reference PUSCH or the second reference PUSCH.

[0379] In some embodiments, when the symbol type is a first symbol, the processor 703 determines the first power margin according to a first parameter; when the symbol type is a second symbol, the processor 703 determines the first power margin according to a second parameter.

[0380] In some embodiments, the reference symbols include one or more symbols (e.g., the first symbol) that overlap or fully overlap with the PUSCH transmission providing / carrying the first power margin (on the active uplink BWP) of the cell (carrier), or the reference symbols include one or more symbols of the first reference slot or the reference PUSCH or the second reference PUSCH, and / or the symbol type of the reference PUSCH or the second reference PUSCH is predefined or configured.

[0381] In some embodiments, the first reference time slot includes one or more time slots (on the active uplink BWP) of the cell that overlap or completely overlap with the second reference time slot or reference subframe, and the second reference time slot or reference subframe includes one or more time slots or subframes (on the active uplink BWP) of another cell.

[0382] In some embodiments, the terminal device provides the first power margin in a PUSCH in the second reference time slot, and / or, when the terminal device provides the first power margin in a PUSCH with repetition and a nominal repetition spans multiple time slots, the second reference time slot includes the multiple time slots.

[0383] In some embodiments, when the first power margin for the cell is based on a reference PUSCH and the cell is a secondary cell (Scell) and the cell is not configured with a preamble target receive power, the first power margin is determined by applying the first preamble target receive power in the first RACH configuration (e.g., rach-ConfigCommon) of the primary cell.

[0384] In some embodiments, the first RACH configuration further includes a second preamble target received power (e.g., sbfd-RACH-SingleConfig-preambleReceivedTargetPower), or the primary cell is further configured with a second RACH configuration (e.g., sbfd-RACHDualConfig), which includes another first preamble target received power.

[0385] In some embodiments, the processor 703 determines whether to determine the second power margin based on the fifth parameter or the sixth parameter, according to the symbol type of the reference symbol or the first reference slot or the reference SRS or the second reference PUSCH or the second reference SRS or the reference SRS resource set (e.g., the SRS resource set corresponding to SRS-ResourceSetId=0 on the active uplink BWP of the cell).

[0386] In some embodiments, when the symbol type is a first symbol, the processor 703 determines the second power margin according to a fifth parameter, and when the symbol type is a second symbol, the processor 703 determines the second power margin according to a sixth parameter.

[0387] In some embodiments, the terminal device is provided with one or more of the following information:

[0388] Information for configuring more than one TPC command and / or a second TPC command for a specific DCI format, and / or information for configuring more than one power control adjustment state, and / or information for configuring a first time domain resource and / or a second time domain resource, and / or information for configuring uplink subbands and / or downlink subbands, and / or information for configuring (as associated with the indicated uniform TCI state) a set of power control parameters for uplink transmissions for associated first time domain resources, and / or information for configuring (as associated with the indicated uniform TCI state) a set of power control parameters for uplink transmissions for associated second time domain resources, and / or information for configuring two sets of SRS resources (for the first and second time domain resources respectively) for codebook or non-codebook purposes, and / or specific information for activating the UL BWP and / or (the DCI) indicated UL BWP and / or the UL BWP where the uplink transmission is located.

[0389] In some embodiments, the closed-loop indexes in the power control parameter set for uplink transmission associated with the first time domain resource and the power control parameter set for uplink transmission associated with the second time domain resource are different; or, the closed-loop indexes for uplink transmission associated with the first time domain resource and the uplink transmission associated with the second time domain resource are different; or, the closed-loop indexes corresponding to the first time domain resource and the second time domain resource are different.

[0390] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The uplink transmitting device 700 in the embodiments of this application may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0391] Furthermore, for simplicity, Figure 7 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0392] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0393] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the transmit power control command (TPC command) is used to determine the transmit power of uplink transmission associated with the first time-domain resource and / or the transmit power of uplink transmission associated with the second time-domain resource. Thus, uplink transmission and reception can be supported in the presence of the aforementioned different time-domain resources.

[0394] Fourth aspect of the embodiment

[0395] This application provides an uplink receiving device. This device may be, for example, a network device, or one or more components or parts configured within a network device; details identical to those in the first and second aspects will not be repeated.

[0396] Figure 8 is a schematic diagram of an uplink receiving device according to an embodiment of this application. Since the principle of this device in solving the problem is the same as the method of the embodiment of the second aspect, its specific implementation can refer to the embodiment of the second aspect, and the contents that are the same will not be repeated. As shown in Figure 8, the uplink receiving device 800 includes: a transmitter 801 and a receiver 802; it may also include a processor 803.

[0397] Transmitter 801 transmits downlink control information (DCI), which includes a transmit power control command (TPC command) for determining the transmit power of uplink transmissions associated with a first time-domain resource and / or the transmit power of uplink transmissions associated with a second time-domain resource; and

[0398] Receiver 802 receives uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and receives a power margin report.

[0399] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The uplink receiving device 800 in the embodiments of this application may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0400] Furthermore, for simplicity, Figure 8 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0401] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0402] As can be seen from the above embodiments, in the presence of different time-domain resources such as potentially different beams, channel states, and frequency-domain resources used for uplink, the transmit power control command (TPC command) is used to determine the transmit power of uplink transmission associated with the first time-domain resource and / or the transmit power of uplink transmission associated with the second time-domain resource. Thus, uplink transmission and reception can be supported in the presence of the aforementioned different time-domain resources.

[0403] Fifth aspect of the embodiment

[0404] This application also provides a communication system, which can be referred to FIG1. ​​The contents that are the same as those in the embodiments of the first to fourth aspects will not be repeated.

[0405] In some embodiments, the communication system 100 may include at least:

[0406] A network device that transmits downlink control information (DCI), the downlink control information including a transmit power control command (TPC command), the transmit power control command being used to determine the transmit power of uplink transmissions associated with a first time domain resource and / or the transmit power of uplink transmissions associated with a second time domain resource; and to receive the uplink transmissions associated with the first time domain resource and / or the uplink transmissions associated with the second time domain resource, and to receive a power headroom report;

[0407] The terminal device receives the downlink control information (DCI); and sends uplink transmissions of the associated first time domain resources and / or the associated second time domain resources, and sends a power margin report.

[0408] This application also provides a network device, such as a base station, but this application is not limited to this and may also include other network devices.

[0409] Figure 9 is a schematic diagram of the network device according to an embodiment of this application. As shown in Figure 9, the network device 900 may include: a processor 910 (e.g., a central processing unit CPU) and a memory 920; the memory 920 is coupled to the processor 910. The memory 920 can store various data; in addition, it also stores an information processing program 930, and executes the program 930 under the control of the processor 910.

[0410] For example, processor 910 can be configured to execute a program to implement the method as described in the embodiments of the second aspect.

[0411] In addition, as shown in Figure 9, the network device 900 may also include a transceiver 940 and an antenna 950, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that the network device 900 does not necessarily have to include all the components shown in Figure 9; in addition, the network device 900 may also include components not shown in Figure 9, which can be referred to in the prior art.

[0412] This application also provides a terminal device, but the application is not limited to this and may also include other devices.

[0413] Figure 10 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 10, the terminal device 1000 may include a processor 1010 and a memory 1020; the memory 1020 stores data and programs and is coupled to the processor 1010. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0414] For example, processor 1010 may be configured to execute a program to implement the method as described in the embodiments of the first aspect.

[0415] As shown in Figure 10, the terminal device 1000 may further include: a communication module 1030, an input device 1040, a display 1050, and a power supply 1060. The functions of these components are similar to those in the prior art and will not be described in detail here. It is worth noting that the terminal device 1000 does not necessarily include all the components shown in Figure 10; these components are not essential. Furthermore, the terminal device 1000 may also include components not shown in Figure 10, which can be referred to in the prior art.

[0416] This application also provides a computer-readable program, wherein when the program is executed in a network device, the program causes the computer to perform the method described in the second aspect of the embodiment in the network device.

[0417] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a network device to perform the methods described in the second aspect of the embodiments.

[0418] This application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program causes the computer to perform the method described in the first aspect of the embodiment in the terminal device.

[0419] This application also provides a storage medium storing a computer-readable program, wherein the computer-readable program causes a computer in a terminal device to perform the method described in the first aspect of the embodiments.

[0420] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. Logic components include, for example, field-programmable logic devices (FPGAs), microprocessors, and processors used in computers. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, and flash memory.

[0421] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0422] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0423] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0424] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0425] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0426] 1. An uplink transmission method, comprising:

[0427] The terminal device receives downlink control information (DCI), which includes a transmit power control command (TPC command). The TPC command is used to determine the transmit power of uplink transmission associated with a first time domain resource (in a cell / (uplink) carrier / (uplink) BWP with SBFD enabled) and / or the transmit power of uplink transmission associated with a second time domain resource (in a cell / (uplink) carrier with SBFD enabled).

[0428] The terminal device sends uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and sends a power margin report.

[0429] 2. An uplink receiving method, comprising:

[0430] The network device transmits downlink control information (DCI), which includes a transmit power control command (TPC command) for determining the transmit power of uplink transmissions associated with a first time domain resource (in a cell / (uplink) carrier / (uplink) BWP with SBFD enabled) and / or the transmit power of uplink transmissions associated with a second time domain resource (in a cell / (uplink) carrier with SBFD enabled); and

[0431] The network device receives uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and receives a power margin report.

[0432] 3. The method according to Appendix 2, wherein the transmit power control command is used to determine the transmit power of the uplink transmission associated with the first time domain resource and / or the transmit power of the uplink transmission associated with the second time domain resource, including:

[0433] The power control command is applied to the power control adjustment state associated with the uplink transmission of the associated first time domain resource (for the uplink transmission of the associated first time domain resource) and / or the power control adjustment state associated with the uplink transmission of the associated second time domain resource (for the uplink transmission of the associated second time domain resource).

[0434] The power control adjustment state associated with the uplink transmission of the associated first time domain resource is the same as the power control adjustment state associated with the uplink transmission of the associated second time domain resource, or the power control adjustment state associated with the uplink transmission of the associated first time domain resource is different from the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

[0435] 4. The method according to Appendix 2, wherein the transmit power control command is used to determine the transmit power of the uplink transmission associated with the first time domain resource and / or the transmit power of the uplink transmission associated with the second time domain resource, further comprising:

[0436] The transmit power of the uplink transmission of the associated first time domain resource is determined based on the power control adjustment state associated with the uplink transmission of the associated first time domain resource, and / or the transmit power of the uplink transmission of the associated second time domain resource is determined based on the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

[0437] 5. The method according to Appendix 2, wherein, for a DCI that schedules uplink transmissions including a TPC command, the TPC command in the DCI is applied to (all) power control adjustment states associated with the uplink transmission scheduled by the DCI, or the TPC command is applied to (all) power control adjustment states associated with uplink transmissions scheduled by the DCI that meet specific conditions, or the TPC command is applied to (all) power control adjustment states associated with the valid time-domain resource type corresponding to the uplink transmission scheduled by the DCI, or the TPC command is applied to all (configured / UE-maintained) power control adjustment states, or the TPC command is applied to the default power control adjustment state, or which power control adjustment state the TPC command is applied to is determined (indicated / configured / provided) by other information sent by the network device.

[0438] 6. The method according to Appendix 2, wherein, for a DCI that does not schedule uplink transmissions including a TPC command, one TPC command in the DCI is applied to all power control adjustment states (configured / maintained by the UE), or the TPC command is applied to the default power control adjustment state, or which power control adjustment state the TPC command is applied to is determined (indicated / configured / provided) by another information sent by the network device.

[0439] 7. A terminal device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the uplink transmission method as described in Appendix 1.

[0440] 8. A network device comprising a memory and a processor, the memory storing a computer program and the processor being configured to execute the computer program to implement the uplink receiving method as described in any one of Appendices 2 to 6.

[0441] 9. A computer program product comprising at least a computer program that, when executed by a processor, causes a terminal device to perform the uplink transmission method as described in Appendix 1.

[0442] 10. A computer program product comprising at least a computer program that, when executed by a processor, causes a network device to perform the uplink receiving method as described in any one of Appendices 2 to 6.

Claims

1. An uplink transmitting device configured in a terminal device, the device comprising: A receiver receives downlink control information, the downlink control information including a transmit power control command, the transmit power control command being used to determine the transmit power of uplink transmission associated with a first time domain resource and / or the transmit power of uplink transmission associated with a second time domain resource; as well as The transmitter transmits uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and transmits a power margin report.

2. The apparatus according to claim 1, wherein, The transmit power control command is used to determine the transmit power of uplink transmission associated with the first time domain resource and / or the transmit power of uplink transmission associated with the second time domain resource, including: The power control command is applied to the power control adjustment state associated with the uplink transmission of the associated first time domain resource and / or the power control adjustment state associated with the uplink transmission of the associated second time domain resource. The power control adjustment state associated with the uplink transmission of the associated first time domain resource is the same as the power control adjustment state associated with the uplink transmission of the associated second time domain resource, or the power control adjustment state associated with the uplink transmission of the associated first time domain resource is different from the power control adjustment state associated with the uplink transmission of the associated second time domain resource.

3. The apparatus according to claim 1, wherein, The device further includes: The processor determines the transmit power of the uplink transmission of the associated first time domain resource based on a power control adjustment state associated with the uplink transmission of the associated first time domain resource, and / or determines the transmit power of the uplink transmission of the associated second time domain resource based on a power control adjustment state associated with the uplink transmission of the associated second time domain resource.

4. The apparatus according to claim 1, wherein, The power control adjustment status associated with uplink transmission includes the power control adjustment status corresponding to the time-domain resource type associated with the uplink transmission, and / or the power control adjustment status associated with uplink transmission is related to the closed-loop index configuration corresponding to the uplink transmission or the closed-loop index configuration corresponding to the time-domain resource type associated with the uplink transmission.

5. The apparatus according to claim 1, wherein, For a downlink control information that includes a transmit power control command for a scheduled uplink transmission, the transmit power control command in the downlink control information is applied to a power control adjustment state associated with an uplink transmission that meets specific conditions scheduled by the downlink control information.

6. The apparatus according to claim 5, wherein, The downlink control information schedules one or more uplink transmissions, and the power control adjustment state associated with the uplink transmission that meets specific conditions according to the downlink control information schedule includes the power control adjustment state associated with any uplink transmission that meets specific conditions according to the downlink control information schedule.

7. The apparatus according to claim 5, wherein, The uplink transmission that meets specific conditions includes: The uplink transmission of the associated valid time-domain resource type scheduled by the downlink control information, or, The downlink control information schedules uplink transmissions in the first time domain resources and / or uplink transmissions in the second time domain resources.

8. The apparatus according to claim 1, wherein, The power headroom report includes a first power headroom or a second power headroom, wherein the first power headroom is valid for PUSCH and the second power headroom is valid for SRS.

9. The apparatus according to claim 8, wherein, The device further includes: The processor determines whether the first or second power margin for a cell is based on actual transmission or a reference format.

10. The apparatus according to claim 9, wherein, When the first power margin for the cell is based on a reference PUSCH and the terminal device is provided with a first parameter and a second parameter, the processor determines the first power margin according to the first parameter or the second parameter, and / or, When the second power margin for the cell is based on the reference SRS and the terminal device is provided with a fifth parameter and a sixth parameter, the processor determines the second power margin according to the fifth parameter or the sixth parameter.

11. The apparatus according to claim 10, wherein, The processor determines whether to determine the first power margin based on the first parameter or the second parameter according to the symbol type of the reference symbol or the first reference time slot or the reference PUSCH or the second reference PUSCH. Wherein, when the symbol type is a first symbol, the processor determines the first power margin according to the first parameter; when the symbol type is a second symbol, the processor determines the first power margin according to the second parameter.

12. The apparatus according to claim 11, wherein, The reference symbols include one or more symbols of the cell that overlap or completely overlap with the PUSCH transmission providing / carrying the first power margin, or the reference symbols include one or more symbols of the first reference slot, the reference PUSCH, or the second reference PUSCH, and / or the symbol type of the reference PUSCH or the second reference PUSCH is predefined or configured.

13. The apparatus according to claim 11, wherein, The first reference time slot includes one or more time slots of the cell that overlap or completely overlap with the second reference time slot or reference subframe, and the second reference time slot or reference subframe includes one or more time slots or subframes of another cell.

14. The apparatus according to claim 13, wherein, The terminal device provides the first power margin in the PUSCH in the second reference time slot, and / or, when the terminal device provides the first power margin in a PUSCH with repetition and a nominal repetition spans multiple time slots, the second reference time slot includes the multiple time slots.

15. The apparatus according to claim 10, wherein, When the first power margin for the cell is based on a reference PUSCH and the cell is a secondary cell and the cell is not configured with a preamble target receive power, the first power margin is determined by applying the first preamble target receive power in the first RACH configuration of the primary cell.

16. The apparatus according to claim 15, wherein, The first RACH configuration also includes a second preamble target received power, or the main cell is also configured with a second RACH configuration, which includes another first preamble target received power.

17. The apparatus according to claim 1, wherein, The terminal device is provided with one or more of the following information: Information for configuring more than one power control adjustment state, and / or information for configuring a first time domain resource and / or a second time domain resource, and / or information for configuring an uplink subband and / or a downlink subband, and / or information for configuring a set of power control parameters for an uplink transmission associated with the first time domain resource, and / or information for configuring a set of power control parameters for an uplink transmission associated with the second time domain resource, and / or information for configuring two SRS resource sets used as codebooks or non-codebooks, and / or specific information for activating the UL BWP and / or indicating the UL BWP and / or the UL BWP where the uplink transmission is located.

18. The apparatus according to claim 1, wherein, The closed-loop indices in the power control parameter set for uplink transmission of the associated first time domain resource and the power control parameter set for uplink transmission of the associated second time domain resource are different; or, the closed-loop indices for uplink transmission of the associated first time domain resource and the associated second time domain resource are different; or, the closed-loop indices corresponding to the first time domain resource and the second time domain resource are different.

19. An uplink receiving device configured in a network device, the device comprising: A transmitter that transmits downlink control information, the downlink control information including a transmit power control command, the transmit power control command being used to determine the transmit power of uplink transmission associated with a first time domain resource and / or the transmit power of uplink transmission associated with a second time domain resource; as well as The receiver receives uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and receives power margin reports.

20. A communication system, comprising: A network device that sends downlink control information, the downlink control information including a transmit power control command, the transmit power control command being used to determine the transmit power of uplink transmission associated with a first time domain resource and / or the transmit power of uplink transmission associated with a second time domain resource; And receive uplink transmissions of the associated first time domain resource and / or the associated second time domain resource, and receive power margin reports; The terminal device receives the downlink control information; and sends the uplink transmission of the associated first time domain resource and / or the uplink transmission of the associated second time domain resource, and sends the power margin report.