Pusch transmitting method, pusch receiving method, apparatus and communication system

Abstract

Provided in the embodiments of the present application are a PUSCH transmitting method, a PUSCH receiving method, an apparatus and a communication system. The PUSCH transmitting method comprises: a terminal device determining a transmit power for a PUSCH; and transmitting the PUSCH, wherein the transmit power for the PUSCH is related to a time domain resource associated with or corresponding to a PUSCH transmission occasion, and the time domain resource associated with the PUSCH transmission occasion comprises a first time domain resource and / or a second time domain resource.

Description

PUSCH transmission and reception methods, apparatus, and communication systems Technical Field

[0001] This application relates to the field of communication technology. Background Technology

[0002] The Physical Uplink Shared Channel (PUSCH) is used to transmit uplink data and can be scheduled periodically, semi-persistently, or dynamically.

[0003] To ensure that the UE (User Equipment) transmits data at an appropriate power while avoiding interference with other users, the transmission power of the PUSCH needs to be controlled. PUSCH power control mainly 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 UE's transmit power through Transmit Power Control (TPC) commands. This adjustment method includes cumulative and absolute methods. When using the cumulative method, the UE needs to adjust the power cumulatively according to historical TPC commands, while when using the absolute method, the UE only adjusts the power according to the current TPC command.

[0004] 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

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

[0006] 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, Subband non-overlapping Full Duplex (SBFD), but is not limited to this. Under this operating mode, due to new self-interference and cross-interference problems, the PUSCH power control for time domain resources corresponding to full-duplex mode may differ from that for time domain resources not corresponding to full-duplex mode.

[0007] 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 time-domain resource PUSCH power control for different antennas may also be different.

[0008] However, there is currently no solution for how to support PUSCH transmission and reception in the presence of the aforementioned different time-domain resources, including how to specifically control / determine the PUSCH transmission power for different time-domain resources.

[0009] To address at least one of the above-mentioned problems, embodiments of this application provide a PUSCH transmission and reception method, apparatus, and communication system.

[0010] According to one aspect of the embodiments of this application, a PUSCH transmission method is provided, including:

[0011] The terminal equipment determines the transmit power for the PUSCH; and

[0012] The terminal device sends the PUSCH;

[0013] The transmission power of the PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission occasion, and the time-domain resources associated with the PUSCH transmission occasion include first time-domain resources and / or second time-domain resources.

[0014] According to another aspect of the embodiments of this application, a PUSCH transmitting apparatus is provided, comprising:

[0015] The processor, which determines the transmit power for PUSCH; and

[0016] A transmitter that sends the PUSCH;

[0017] The transmission power of the PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity. The time-domain resources associated with the PUSCH transmission opportunity include first time-domain resources and / or second time-domain resources.

[0018] According to another aspect of the embodiments of this application, a PUSCH receiving method is provided, including:

[0019] Network devices receive PUSCH;

[0020] The transmission power of the PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity. The time-domain resources associated with the PUSCH transmission opportunity include first time-domain resources and / or second time-domain resources.

[0021] According to another aspect of the embodiments of this application, a PUSCH receiving device is provided, comprising:

[0022] The receiver receives PUSCH;

[0023] The transmission power of the PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity. The time-domain resources associated with the PUSCH transmission opportunity include first time-domain resources and / or second time-domain resources.

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

[0025] A terminal device that determines the transmission power for the PUSCH and transmits the PUSCH;

[0026] Network device that receives the PUSCH;

[0027] The transmission power of the PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity. The time-domain resources associated with the PUSCH transmission opportunity include first time-domain resources and / or second time-domain resources.

[0028] One of the beneficial effects of the embodiments of this application includes: in the presence of different time-domain resources such as possible different beams, channel states, and frequency-domain resources for uplink, the transmission power of PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, which can support PUSCH transmission and reception in the presence of the above-mentioned different time-domain resources.

[0029] 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.

[0030] 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.

[0031] 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

[0032] 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.

[0033] 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:

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

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

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

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

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

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

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

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

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

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

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] 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.

[0049] 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.

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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)”.

[0056] 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)”.

[0057] 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 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.

[0058] 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).

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

[0060] 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.

[0061] In the embodiments of this application, "overlapping" includes complete / full overlap and / or partial overlap and / or at least partial overlap. "Located in" includes completely / full located in and / or partially located in and / or at least partially located in, and "located within" includes completely located within.

[0062] 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 unless there is confusion. For resources in the frequency domain, "carrier" and "resource grid" are interchangeable; "subcarrier spacing configuration (μ)" 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)" are interchangeable; "configuration / indication / providance / given" are interchangeable; "index" and "identifier (ID)" are interchangeable.

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

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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.

[0070] First aspect of the embodiments

[0071] This application provides a PUSCH transmission method, which is described from the perspective of the terminal device.

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

[0073] 201, The terminal equipment determines the transmission power for the PUSCH; and

[0074] 202, the terminal device sends the PUSCH;

[0075] The transmission power of the PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with (or corresponding to) the PUSCH transmission opportunity (specific symbol). The time-domain resources associated with the PUSCH transmission opportunity (specific symbol) include first time-domain resources (non-SBFD symbols) and / or second time-domain resources (SBFD symbols).

[0076] 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.

[0077] In some embodiments, the terminal device may be an SBFD-aware device; however, this application is not limited thereto. For example, in the initial access procedure (from RRC_IDLE to RRC_Connected state, including CBRA) and / or in the random access procedure (e.g., CBRA) and / or in the RRCSetupComplete message and / or in the capability information, the terminal device indicates to the network device that the terminal device is an SBFD-aware device (SBFD-aware UE) or indicates that the terminal device has the following SBFD operation-related capabilities.

[0078] For example, an SBFD-aware UE has SBFD operation-related capabilities, including one or more of the following: support for the configuration of time and frequency locations of (cell-specific) SBFD subbands (e.g., configuration of first time domain resources and / or second time domain resources and / or first frequency domain resources and / or second frequency domain resources as described below); support for UL transmission in a UL subband and DL reception in a DL subband within an SBFD symbol; and support for link direction determination and collision handling based on configured or scheduled transmissions or receptions.

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

[0080] 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.

[0081] 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.

[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 determines the DL / UL / Flexible symbol corresponding to the BWP based on the DL / UL / Flexible symbol configured according to the aforementioned reference Subcarrier Spacing (and assuming NCP). 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 and frequency resources. The following provides a further illustrative description of the embodiments of this application.

[0116] In some embodiments, the transmit power for a PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to a PUSCH transmit opportunity (a specific symbol of the PUSCH), including: the transmit power for a PUSCH is determined based on the time-domain resources associated with or corresponding to a PUSCH transmit opportunity.

[0117] For example, the transmission power for a PUSCH includes: the transmission power of (the PUSCH) during the PUSCH transmission opportunity.

[0118] In some embodiments, the terminal device determines the transmission power for the PUSCH, including: the terminal device determines the transmission power of (the PUSCH) during the PUSCH transmission opportunity.

[0119] In some embodiments, a PUSCH includes (or is associated with / corresponds to) one or more PUSCH transmission opportunities, and the transmission power in each PUSCH transmission opportunity is determined separately.

[0120] For example, one PUSCH is associated with / corresponds to three PUSCH transmission opportunities: transmission opportunity 1, transmission opportunity 2, and transmission opportunity 3, which correspond to transmission power 1, transmission power 2, and transmission power 3, respectively; wherein transmission power 1, transmission power 2, and transmission power 3 are determined separately, and any two of them can be the same or different.

[0121] For example, a PUSCH without repetition or TBoMS corresponds to one PUSCH transmission opportunity. For example, a PUSCH with repetition or TBoMS can correspond to one or more PUSCH transmission opportunities. For a PUSCH with repetition (with / without TBoMS), a PUSCH transmission opportunity is a repetition, where the repetition includes repetition Type A (first repetition type) and / or repetition Type B (second repetition type). For a PUSCH with TBoMS (and without repetition / first repetition type), a PUSCH transmission opportunity is a symbol allocation in a time slot (or a symbol allocated for that PUSCH in a time slot).

[0122] In some embodiments, the terms “PUSCH” and “PUSCH Sending Opportunity” may be used interchangeably.

[0123] In some embodiments, the terminal device determines the transmission power in PUSCH transmission opportunity i based on at least one of the following, wherein one or more of the above-mentioned factors relate to the time-domain resources associated with the PUSCH transmission opportunity:

[0124] Maximum output power P CMAX,f,c (i);

[0125] Target power P O_PUSCH,b,f,c (j);

[0126] Subcarrier spacing μ;

[0127] Number of RBs for the PUSCH transmission opportunity

[0128] Path loss compensation factor α b,f,c (j);

[0129] Path loss PL b,f,c (q d );

[0130] First power offset Δ TF,b,f,c (i);

[0131] PUSCH power control adjustment state b,f,c (i,l);

[0132] Second power offset Δ SBFD .

[0133] Table 1 provides an example of transmission power:

[0134] Table 1

[0135] For example, the PUSCH in cases where no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE's target power and / or path loss compensation factor set is provided (including: the PUSCH in cases where the UE establishes a connection using a Type 1 random access procedure (4-step RA or Type 1 random access procedure) and no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE's target power and / or path loss compensation factor set is provided, and / or the PUSCH in cases where the UE establishes a connection using a Type 2 random access procedure (2-step RA or Type 2 random access procedure) and no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE's target power and / or path loss compensation factor set is provided).

[0136] And / or, for the PUSCH ((re)transmission) corresponding to the RAR UL grant (including the RAR UL grant in response to Msg1 in the RAR and / or the RAR UL grant in response to MsgA in the fallback RAR) (e.g., referred to as Msg3 PUSCH),

[0137] And / or, for a Type 2 random access procedure PUSCH (e.g., called MsgA PUSCH) in the absence of a (higher-layer) parameter (msgA - preambleReceived TargetPower) indicating the preamble target received power for the Type 2 random access procedure (2-step RA), j = 0.

[0138] These PUSCHs can also be called PUSCHs corresponding to j=0.

[0139] For the Configuration Grant (CG) PUSCH (CG PUSCH), j=1. These PUSCHs can also be referred to as the PUSCHs corresponding to j=1.

[0140] For dynamic grant (DG)PUSCH(DG PUSCH), j∈{2,…,J-1}=S J These PUSCHs can also be called corresponding to j>1 or j∈{2,…,J-1}=SJ PUSCH.

[0141] In some embodiments, the PUSCH ((re)transmission) corresponding to the RAR UL grant includes: a PUSCH scheduled by the RAR(UL)grant, and / or a PUSCH scheduled by a DCI (format 0_0) scrambled by TC-RNTI.

[0142] In some embodiments, the PUSCH without the (higher-layer) parameter (P0-PUSCH-AlphaSet) for indicating the UE target power and / or path loss compensation factor set includes: the PUSCH without a dedicated RRC configuration, and / or the PUSCH without the UE receiving a dedicated RRC configuration, and / or the PUSCH without the (higher-layer) parameter (P0-PUSCH-AlphaSet) for indicating the UE target power and / or path loss compensation factor set and without the unifiedTCI-StateType.

[0143] In some embodiments, for a cell, if a unifiedTCI-StateType is provided, the (higher-layer) parameter (P0-PUSCH-AlphaSet) for indicating the UE target power and / or path loss compensation factor set is not provided.

[0144] In some embodiments, CG PUSCH includes PUSCH(re)transmission configured by ConfiguredGrantConfig. PUSCH retransmission includes retransmissions scheduled by DCI (with a CRC scrambled by CS-RNTI / G-CS-RNTI) (for scheduling retransmissions for CG PUSCH) and / or spontaneous retransmissions performed by the UE according to ConfiguredGrantConfig.

[0145] In some embodiments, DG PUSCH includes PUSCHs other than those described above (scheduled or activated by DCI). For example, PUSCHs used to carry SP-CSI (activated by DCI), and / or PUSCHs other than those described above scheduled by DCI (with CRC scrambled by C-RNTI / MCS-C-RNTI).

[0146] In some embodiments, the term "DG PUSCH" can be used with "corresponding to j>1 or j∈{2,…,J-1}=S". JThe "PUSCH" is interchangeable.

[0147] At least one of the above are embodiments of this application, and this application is not limited thereto; for example, other parameters may also be included. Furthermore, one of the above items relates to the time-domain resources associated with the PUSCH transmission opportunity, including: the item is determined based on the time-domain resources associated with the PUSCH transmission opportunity. Furthermore, when the transmission power in the PUSCH transmission opportunity is determined based on the item, the transmission power is also related to the time-domain resources associated with the PUSCH transmission opportunity.

[0148] In some embodiments, the maximum output power is related to the time-domain resources associated with the PUSCH transmission opportunity.

[0149] In some embodiments, for a PUSCH transmission opportunity associated with a first time domain resource (but not associated with a second time domain resource), the maximum output power is a first maximum output power, and / or, for a PUSCH transmission opportunity associated with a second time domain resource (but not associated with a first time domain resource), the maximum output power is a second maximum output power;

[0150] Wherein, the second maximum output power is determined based on a parameter (configured by the base station or set by the UE) that is not used to determine the first maximum output power, and / or, the first maximum output power is determined based on a parameter (configured by the base station or set by the UE) that is not used to determine the second maximum output power.

[0151] For example, the maximum output power configured for the UE should be less than or no greater than the upper bound, and / or greater than or no less than the lower bound.

[0152] For example, the above parameter is used to determine the upper and / or lower limit of the second maximum output power, but not to determine the upper and / or lower limit of the first maximum output power. As another example, when determining the upper and / or lower limit of the second maximum output power, the above parameter may not be equal to 0 or may be configured by the base station; when determining the upper and / or lower limit of the first maximum output power, this parameter should be equal to 0 or default to 0. That is, the maximum output power configured based on the upper and / or lower limit determined by this parameter is the second maximum output power, and the maximum output power configured based on the upper and / or lower limit not determined by this parameter (including cases where the parameter should be equal to 0 or default to 0) is the first maximum output power.

[0153] For example, the parameter mentioned above represents the offset between the first maximum output power and the second maximum output power. The second maximum output power is determined based on the first maximum output power and this parameter. For example, the second maximum output power = the first maximum output power - the offset.

[0154] For example, when this parameter is not provided, the maximum output power is independent of the time-domain resources of the PUSCH transmission opportunity; that is, the maximum output power is the first maximum output power regardless of whether the PUSCH transmission opportunity is for associated SBFD symbols or non-SBFD symbols.

[0155] In some embodiments, the target power includes a nominal target power (or a cell-specific target power) P. O_NOMINAL,PUSCH,f,c (j), or, including nominal target power (or cell-specific target power) and UE target power (or UE-specific target power) P O_UE_PUSCH,b,f,c The sum of (j).

[0156] For example, for the PUSCH corresponding to j=0, P O_UE_PUSCH,b,f,c (0) = 0. In this case, it can also be said that the target power only includes the nominal target power. For the PUSCH corresponding to j>0 (including j=1 and / or j>1), the target power includes the nominal target power and the UE target power P. O_UE_PUSCH,b,f,c The sum of (j), where, how to determine P O_UE_PUSCH,b,f,c (j) Explained / described in subsequent embodiments.

[0157] In some embodiments, the target power is associated with time-domain resources related to the PUSCH transmission opportunity, including: the nominal target power and / or the UE target power are associated with time-domain resources related to the PUSCH transmission opportunity. For example, the nominal target power and / or the UE target power are determined based on the time-domain resources associated with the PUSCH transmission opportunity.

[0158] In some embodiments, the nominal target power includes the leader target received power, or the sum of the leader target received power and the power offset.

[0159] For example, for a PUSCH in which no (higher-layer) parameters are provided to indicate the UE target power and / or the path loss compensation factor set, and / or for a PUSCH ((re)transmission) corresponding to a RAR UL grant, and / or for a Type II random access procedure in which no (higher-layer) parameters are provided to indicate the preamble target received power for a Type II random access procedure, and / or for a CG PUSCH in which no (higher-layer) parameters are provided to indicate the nominal target power for a CG PUSCH, and / or for a DG PUSCH in which no (higher-layer) parameters are provided to indicate the nominal target power for a DG PUSCH: the nominal target power includes the preamble target received power, or includes the sum of the preamble target received power and the power offset.

[0160] In some embodiments, the nominal target power is associated with time-domain resources related to the PUSCH transmission opportunity, including: the preamble target received power and / or power offset (used to determine the nominal target power) are associated with time-domain resources related to the PUSCH transmission opportunity.

[0161] In some embodiments, the leader target received power is a first leader target received power or a second leader target received power, and / or the power offset is a third power offset or a fourth power offset or equal to 0.

[0162] In some embodiments, RO (random access occasion), also known as PRACH occasion / resource or RACH occasion / resource, represents the time-frequency resource used to send PRACH or preamble.

[0163] In some embodiments, a first RO includes (at least partially) an RO overlapping with a DL SBFD symbol. A second RO includes (at least partially) an RO overlapping with an SBFD symbol. The ROs (at least partially) overlapping with DL SBFD symbols include: ROs within a DL SBFD symbol, and / or ROs spanning a DL SBFD symbol and a Flexible SBFD symbol, and / or ROs starting in a DL SBFD symbol and ending in a Flexible SBFD symbol, and / or ROs starting in a Flexible SBFD symbol and ending in a DL SBFD symbol. ROs (at least partially) overlapping with SBFD symbols include: ROs within an SBFD symbol, and / or ROs spanning a SBFD symbol and a non-SBFD symbol, and / or ROs starting in an SBFD symbol and ending in a non-SBFD symbol, and / or ROs starting in a non-SBFD symbol and ending in an SBFD symbol.

[0164] In some embodiments, the third or fourth RO (only) includes ROs that overlap with uplink symbols and / or flexible symbols, and / or excludes ROs that overlap with downlink symbols (at least partially). ROs overlapping with uplink symbols and / or flexible symbols include: ROs within uplink symbols, and / or ROs within flexible symbols, and / or ROs spanning uplink and flexible symbols. ROs (at least partially) overlapping with downlink symbols include: ROs overlapping with DL SBFD symbols, and / or ROs overlapping with DL non-SBFD symbols.

[0165] In some embodiments, the first RO, second RO, and third RO are used for / for a Type-1 random access procedure, and / or for transmitting a PRACH or preamble in a Type-1 random access procedure. The fourth RO is used for / for a Type-2 random access procedure, and / or for transmitting a PRACH or preamble in a Type-2 random access procedure. Specifically, in a Type-1 random access procedure, the UE transmits Msg1, which includes only a PRACH or preamble. In a Type-2 random access procedure, the UE transmits MsgA, which includes a PRACH or preamble (when the selected RO or the RO used to transmit the PRACH or preamble does not have an associated (MsgA)PUSCH occasion), or includes a PRACH or preamble, and (MsgA)PUSCH.

[0166] In some embodiments, the PRACH formats corresponding to the first RO and the third RO are (must be) the same (i.e., they can only be configured to be the same). The PRACH formats corresponding to the second RO and the third RO can be different (i.e., they can be configured to be the same, or they can be configured to be different).

[0167] In some embodiments, for a cell configured with a first RO, the second preamble target receive power includes the preamble target receive power configured for (or dedicated to) the first RO and / or the preamble target receive power configured by a first parameter (e.g., sbfd-RACHSingleConfig-preambleReceivedTargetPower or sbfd-preambleReceivedTargetPower or preambleReceivedTargetPowerSBFD), and / or

[0168] For a cell configured with the second RO, the second preamble target received power includes the preamble target received power configured for (or dedicated to) the second RO and / or the preamble target received power configured by a second parameter (e.g., preambleReceivedTargetPower, sbfd-RACHSingleConfig-preambleReceivedTargetPower, sbfd-preambleReceivedTargetPower, or preambleReceivedTargetPowerSBFD).

[0169] In some embodiments, (for a cell configured with a first RO or a second RO (and a third RO), or for a cell not configured with a first RO and not configured with a second RO (and a third RO),) the first preamble target received power includes the preamble target received power configured for (or dedicated to) the third RO and / or the preamble target received power configured by the third parameter (preambleReceivedTargetPower).

[0170] For example, a first parameter is included in the information used to configure the first RO, a second parameter is included in the information used to configure the second RO (e.g., sbfd-RACHDualConfig), and a third parameter is included in the information used to configure the third RO. The information used to configure the first RO is different from the information used to configure the second RO (e.g., sbfd-RACHDualConfig), and / or, the information used to configure the first RO includes parameters for enabling the first RO and / or RACH configuration Option 1 for SBFD random access operation (e.g., sbfd-RACHSingleConfig) and / or a third parameter (preambleReceivedTargetPower) for configuring the first preamble target received power (for / for the third RO), and / or, for a cell with the first RO configured, the information used to configure the first RO is also used to configure the third RO (i.e., this information is also used to configure the third RO). The information used to configure the second RO does not configure the third RO (i.e., this information is different from the information used to configure the third RO). For a cell that has been configured with the second RO, the third RO is configured by information different from the information used to configure the second RO. In this case, the first preamble target received power is configured by the third parameter (preambleReceivedTargetPower) in the information used to configure the third RO.

[0171] In some embodiments, the first preamble target received power includes the preamble target received power configured for (or dedicated to) the fourth RO and / or the preamble target received power configured by the fourth parameter (msgA-preambleReceivedTargetPower).

[0172] For example, the first and second ROs can be referred to as SBFD ROs or additional ROs. For instance, the first and second ROs are respectively first / second SBFD ROs or additional ROs. The third RO is referred to, for example, as a non-SBFD RO or legacy RO.

[0173] In some embodiments, a cell cannot be configured with a first RO and a second RO simultaneously.

[0174] In some embodiments, the cell is configured with at least a third RO.

[0175] In some embodiments, the cell is a Pcell or an Scell ​​(including a PScell ​​and / or a PUCCH Scell ​​and / or other Scells).

[0176] In some embodiments, whether the leader target received power is the first leader target received power or the second leader target received power depends on one or more of the following:

[0177] Is the community equipped with a first RO or a second RO?

[0178] PUSCH sends opportunity-related temporal resources;

[0179] The corresponding leading edge uses RO;

[0180] The value of the received power of the first forward target;

[0181] The value of the received power of the second forward target;

[0182] PUSCH type;

[0183] RO corresponds to the PRACH format;

[0184] Is the cell configured with (third power offset and) fourth power offset?

[0185] The above illustrations depict factors related to the received power of the forward target. This application is not limited to these factors and may include other factors, parameters, or information.

[0186] In some embodiments, for a cell that is neither configured with the first RO nor with the second RO, the preamble target received power is the first preamble target received power.

[0187] In some embodiments, for a cell configured with the first RO or the second RO, when the second fronting target receive power is not configured, the fronting target receive power is the first fronting target receive power.

[0188] In some embodiments, for a cell configured with a first RO (and configured with the second fronting target receive power) or a second RO (and configured with the second fronting target receive power), the fronting target receive power is the first fronting target receive power or the second fronting target receive power.

[0189] For example, for a cell that has been configured with a first RO or a second RO (and has been configured with a second preamble target receive power):

[0190] (For PUSCH in cases where no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation factor set is provided, and / or, in cases where the UE establishes a connection using a Type 1 random access procedure (4-step RA) and no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation factor set is provided (or, for PUSCH in such cases), and / or, for PUSCH ((re)transmission) corresponding to a RAR UL grant (including the RAR UL grant in response to Msg1 and / or the RAR UL grant in response to MsgA in fallback RAR) (e.g., referred to as Msg3) PUSCH), and / or, in the case where the UE establishes a connection using a Type 2 random access procedure and no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE's target power and / or path loss compensation factor set is provided (or, for the PUSCH in this case), and / or, for the Type 2 random access procedure (2-step RA) PUSCH (e.g., referred to as MsgA PUSCH) in the case where no (higher-layer) parameter (msgA-preambleReceivedTargetPower) indicating the preamble target received power for the Type 2 random access procedure is provided, and / or, for the CG PUSCH in the case where no (higher-layer) parameter (p0-NominalWithGrant) indicating the nominal target power for the CG PUSCH is provided, and / or, for the DG PUSCH in the case where no (higher-layer) parameter (p0-NominalWithoutGrant) indicating the nominal target power for the DG PUSCH is provided.

[0191] (For a cell configured with a second RO,) (where the PRACH format corresponding to the second RO is the same as that of the third RO,) (where a (third power offset and) a fourth power offset are provided,) (and / or, for a cell configured with a first RO,) for a PUSCH transmission opportunity associated with the first time domain resource (and not associated with the second time domain resource), the preamble target received power is the first preamble target received power; for a PUSCH transmission opportunity associated with the second time domain resource (and not associated with the first time domain resource), the preamble target received power is the second preamble target received power; and / or

[0192] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) for a PUSCH transmission opportunity associated with the first time domain resource (but not associated with the second time domain resource), the preamble target receive power is the second preamble target receive power; for a PUSCH transmission opportunity associated with the second time domain resource (but not associated with the first time domain resource), the preamble target receive power is the first preamble target receive power; and / or,

[0193] (For cells configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the corresponding preamble (or PRACH / Msg1) is transmitted using the third RO, the preamble target receive power is the first preamble target receive power; when the corresponding preamble (or corresponding PRACH transmission) is transmitted using the first RO or the second RO, the preamble target receive power is the second preamble target receive power (wherein, the corresponding preamble includes the most recently / last transmitted preamble (or latest / last PRACH transmission) before the PUSCH and / or the preamble responded to by the (most recently / last) RAR (UL grant) before the PUSCH and / or the first / first preamble (or first PRACH transmission) transmitted during random access); and / or,

[0194] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the corresponding preamble (or PRACH) is transmitted using the third RO, (for PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource,) the preamble target receive power is the first preamble target receive power; when the corresponding preamble is transmitted using the first RO or the second RO, for PUSCH transmission opportunities associated with the first time domain resource, the preamble target receive power is the first preamble target receive power; for PUSCH transmission opportunities associated with the second time domain resource, the preamble target receive power is the second preamble target receive power; and / or,

[0195] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the corresponding preamble (or PRACH) is transmitted using the first RO or the second RO, (for PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource,) the preamble target receive power is the second preamble target receive power; when the corresponding preamble is transmitted using the third RO, for PUSCH transmission opportunities associated with the first time domain resource, the preamble target receive power is the first preamble target receive power; for PUSCH transmission opportunities associated with the second time domain resource, the preamble target receive power is the second preamble target receive power; and / or,

[0196] (For cells configured with a second RO,) (where the PRACH format corresponding to the second RO differs from that of the third RO,) (where no (third power offset and) fourth power offset are provided,) when the first preamble target received power is greater than or less than or not greater than or not less than or equal to the second preamble target received power, the preamble target received power is the first preamble target received power, and / or, when the second preamble target received power is greater than or less than or not greater than or not less than or equal to the first preamble target received power, the preamble target received power is the second preamble target received power; and / or,

[0197] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the third RO is preferred for transmitting the preamble, the preamble target received power is the first preamble target received power; when either the first RO or the second RO is preferred for transmitting the preamble, the preamble target received power is the second preamble target received power; and / or,

[0198] (For a cell configured with a second RO,) (where the PRACH format corresponding to the second RO is the same as that of the third RO,) (where a (third power offset and) a fourth power offset are provided,) (and / or, for a cell configured with a first RO,) the preamble target received power is the first preamble target received power; and / or,

[0199] (For a cell configured with a second RO,) (where the PRACH format corresponding to the second RO is the same as that of the third RO,) (where a (third power offset and) fourth power offset are provided,) (and / or, for a cell configured with a first RO,) the preamble target received power is the second preamble target received power.

[0200] In some embodiments, different methods are used to determine whether the preamble target received power is the first preamble target received power or the second preamble target received power for different PUSCH types (including the PUSCH in the different cases described above).

[0201] For example, for a cell configured with a first RO or a second RO (and configured with a second preamble target receive power): when the UE establishes a connection using a first type random access procedure and no (higher-layer) parameters are provided to indicate the UE target power and / or path loss compensation factor set (or, for the PUSCH in this case), and / or, for the PUSCH ((re)transmission) corresponding to the RAR UL grant, the preamble target receive power is related to the time-domain resources of the PUSCH transmission opportunity: for a PUSCH transmission opportunity associated with the first time-domain resource (and not associated with the second time-domain resource), the preamble target receive power is the first preamble target receive power; for a PUSCH transmission opportunity associated with the second time-domain resource (and not associated with the first time-domain resource), the preamble target receive power is the second preamble target receive power.

[0202] For example, for a cell configured with a first RO or a second RO (and configured with a second preamble target received power): when the terminal device establishes a connection using a Type I random access procedure and is not provided with (higher-layer) parameters (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation set, and / or when the terminal device establishes a connection using a Type II random access procedure and is not provided with (higher-layer) parameters (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation set, and / or for a Type II random access procedure PUSCH without (higher-layer) parameters (msgA-preambleReceivedTargetPower) indicating the preamble target received power for the Type II random access procedure, and / or for a CG PUSCH without (higher-layer) parameters (p0-NominalWithGrant) indicating the nominal target power for the CG PUSCH, and / or for a CG PUSCH without (higher-layer) parameters (p0-NominalWithGrant) indicating the nominal target power for the DG. DG PUSCH in the case of the (higher-layer) parameter (p0-NominalWithoutGrant) of the nominal target power of PUSCH: the preamble target received power (default or predefined) is the first preamble target received power.

[0203] The above are just two examples, but this application is not limited to these and supports other combinations.

[0204] In some embodiments, for a PUSCH where a P0-PUSCH-AlphaSet is not provided, and / or for a CG PUSCH where a (higher-level) parameter indicating the nominal target power for the CG PUSCH is not provided, and / or for a DG PUSCH where a (higher-level) parameter indicating the nominal target power for the DG PUSCH is not provided:

[0205] (For cells / cases configured with a first or second RO (and a third RO) (or a fourth RO configured or not configured),) If a UE established a dedicated RRC connection using a Type-1 random access procedure: The preamble target received power used to determine the nominal target power is related to or unrelated to the time-domain resources associated with the PUSCH transmission opportunity. For example, (for cells / cases configured with a first RO), the preamble target received power is the first preamble target received power for PUSCH transmission opportunities associated with non-SBFD symbols, and the preamble target received power is the second preamble target received power for PUSCH transmission opportunities associated with SBFD symbols. For irrelevant cases, such as (for cells / cells configured with a second RO), when the corresponding preamble (or PRACH / Msg1) is transmitted using a third RO, the preamble target receive power used to determine the nominal target power is the first preamble target receive power; when the corresponding preamble (or corresponding PRACH transmission) is transmitted using either the first or second RO, the preamble target receive power is the second preamble target receive power. Alternatively, when the corresponding preamble (or PRACH) is transmitted using a third RO, (for PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource), the preamble target receive power is the first preamble target receive power; when the corresponding preamble is transmitted using either the first or second RO, the preamble target receive power is the second preamble target receive power associated with the first time domain resource. For a PUSCH transmission opportunity associated with the second time domain resource, the preamble receive power is a first preamble target receive power; for a PUSCH transmission opportunity associated with the second time domain resource, the preamble target receive power is a second preamble target receive power. Alternatively, if the corresponding preamble (or PRACH) is transmitted using a first RO or a second RO, (for both PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource), the preamble target receive power is a second preamble target receive power; if the corresponding preamble is transmitted using a third RO, for a PUSCH transmission opportunity associated with the first time domain resource, the preamble receive power is a first preamble target receive power; for a PUSCH transmission opportunity associated with the second time domain resource, the preamble target receive power is a second preamble target receive power.

[0206] (For cells / cases where a fourth RO is configured (and a third RO is configured) (or a first or second RO is configured but not configured),) If a UE established a dedicated RRC connection using a Type-2 random access procedure: The preamble target receive power used to determine the nominal target power is related to or unrelated to the time-domain resources associated with the PUSCH transmission opportunity. For related, for example: when a third preamble target receive power is not provided, the preamble target receive power is, for example, the first preamble target receive power for a PUSCH transmission opportunity associated with a non-SBFD symbol, and the second preamble target receive power for a PUSCH transmission opportunity associated with an SBFD symbol. For unrelated, for example: by default or predefined, (when a third preamble target receive power is provided), the preamble target receive power is the third preamble target receive power, or (when a third preamble target receive power is not provided), the preamble target receive power is the first preamble target receive power.

[0207] In some embodiments, for a PUSCH where a P0-PUSCH-AlphaSet is not provided, and / or for a CG PUSCH where a (higher-level) parameter indicating the nominal target power for the CG PUSCH is not provided, and / or for a DG PUSCH where a (higher-level) parameter indicating the nominal target power for the DG PUSCH is not provided:

[0208] (For cells / situations where a second RO is configured (and a third RO is configured) (or a fourth RO is configured but not configured),) If a UE established a dedicated RRC connection using a Type-1 random access procedure:

[0209] When the corresponding preamble (or PRACH / Msg1) is transmitted using the third RO, the preamble target received power used to determine the nominal target power is the first preamble target received power; when the corresponding preamble (or corresponding PRACH transmission) is transmitted using either the first RO or the second RO, the preamble target received power is the second preamble target received power, or...

[0210] When the corresponding preamble (or PRACH) is transmitted using the third RO, (for PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource), the preamble target receive power is the first preamble target receive power; when the corresponding preamble is transmitted using the first RO or the second RO, for PUSCH transmission opportunities associated with the first time domain resource, the preamble target receive power is the first preamble target receive power; for PUSCH transmission opportunities associated with the second time domain resource, the preamble target receive power is the second preamble target receive power; or...

[0211] When the corresponding preamble (or PRACH) is transmitted using the first RO or the second RO, (for PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource), the preamble target receive power is the second preamble target receive power. When the corresponding preamble is transmitted using the third RO, for PUSCH transmission opportunities associated with the first time domain resource, the preamble target receive power is the first preamble target receive power. For PUSCH transmission opportunities associated with the second time domain resource, the preamble target receive power is the second preamble target receive power.

[0212] In some embodiments, for a cell configured with a first RO or a second RO and / or a second preamble target received power, (for a Type II random access procedure,) the UE does not expect msgA-preambleReceivedTargetPower to be NOT configured / provided.

[0213] In some embodiments, for cells configured with a first RO or a second RO and / or a second preamble target receive power, (for CG PUSCH,) the UE does not expect p0-NominalWithoutGrant to be NOT configured / provided.

[0214] In some embodiments, for cells configured with a first RO or a second RO and / or a second preamble target receive power, (for DG PUSCH,) the UE does not expect p0-NominalWithoutGrant to be NOT configured / provided.

[0215] The preceding target received power was introduced above for determining the target power. The following further explains / describes the power offset used to determine the target power.

[0216] In some embodiments, when the third power offset and the fourth power offset are provided, the power offset is either the third power offset or the fourth power offset.

[0217] For example, the power offset is related to the time-domain resource associated with the PUSCH transmission opportunity. For example, for a PUSCH transmission opportunity associated with the first time-domain resource (but not with the second time-domain resource), the power offset is the third power offset, and / or, for a PUSCH transmission opportunity associated with the second time-domain resource (but not with the first time-domain resource), the power offset is the fourth power offset.

[0218] In some embodiments, the power offset is the third power offset when the third power offset is provided (and the fourth power offset is not provided).

[0219] In some embodiments, the power offset is equal to 0 if the third power offset and / or the fourth power offset are not provided.

[0220] In some embodiments, the fourth power offset may be provided for cells configured with a second RO, and / or the fourth offset power may not be provided for cells not configured with a second RO.

[0221] In some embodiments, if a third power offset is not provided, a fourth power offset is also not provided.

[0222] In some embodiments, for a PUSCH where a P0-PUSCH-AlphaSet is not provided, and / or for a CG PUSCH where a (higher-level) parameter indicating the nominal target power for the CG PUSCH is not provided, and / or for a DG PUSCH where a (higher-level) parameter indicating the nominal target power for the DG PUSCH is not provided:

[0223] (For cells / cases where a fourth power offset is configured (and a third power offset is configured) (or a fifth power offset is configured but not configured),) If a UE established a dedicated RRC connection using a Type-1 random access procedure: the power offset used to determine the nominal target power is related to or unrelated to the time-domain resources associated with the PUSCH transmission opportunity. For example, it is related to: the third power offset for a PUSCH transmission opportunity associated with a non-SBFD symbol, and the fourth power offset for a PUSCH transmission opportunity associated with an SBFD symbol.

[0224] (For cells / cases where a fifth power offset is configured (or a third power offset is configured or not) (or a fourth power offset is configured or not),) If a UE established a dedicated RRC connection using a Type-2 random access procedure: The power offset used to determine the nominal target power is related to or unrelated to the time-domain resources associated with the PUSCH transmission opportunity. For related, e.g., when a fifth power offset is not provided, the power offset is, for example, the third power offset for a PUSCH transmission opportunity associated with a non-SBFD symbol, and the fourth power offset for a PUSCH transmission opportunity associated with an SBFD symbol. For unrelated, e.g., by default or predefined, (when a fifth power offset is provided), the power offset is the fifth power offset; or (when a fifth power offset is not provided and a third power offset is provided), the power offset is the third power offset; or (when neither a fifth nor a third power offset is provided), the power offset is equal to 0.

[0225] In some embodiments, for a PUSCH transmission opportunity associated with the first time-domain resource (but not associated with the second time-domain resource), the number of RBs for the PUSCH transmission opportunity. This includes the number of valid RBs (in RBs) allocated or the number of allocated RBs, and / or, for a PUSCH transmission opportunity associated with the second time domain resource (and not associated with the first time domain resource), the number of RBs for the PUSCH transmission opportunity includes the number of allocated RBs.

[0226] Valid RBs refer to PRBs that are within the UL usable PRBs or PRBs that are not outside the UL usable PRBs. For example, for a PUSCH transmission opportunity i associated with an SBFD symbol, suppose it is allocated 50 RBs, of which 10 RBs are outside the UL usable PRBs and the remaining 40 RBs are within the UL usable PRBs.

[0227] In some embodiments, the first power offset Δ is determined based on the number of RBs for a PUSCH transmission opportunity. TF,b,f,c (i).

[0228] In some embodiments, for a PUSCH transmission opportunity associated with the first time domain resource (but not associated with the second time domain resource), the transmission power is not determined based on / without using the second power offset, and / or, for a PUSCH transmission opportunity associated with the second time domain resource (but not associated with the first time domain resource), the transmission power is determined based on / with the second power offset.

[0229] For example, for a PUSCH transmission opportunity associated with a non-SBFD symbol, the transmission power is determined according to formula (1) in Table 1, and for a PUSCH transmission opportunity associated with a SBFD symbol, the transmission power is determined according to formula (2) in Table 1.

[0230] In some embodiments, (for PUSCH corresponding to j>0), the path loss reference signal, and / or the UE target power (or UE-specific target power) P O_UE_PUSCH,b,f,c (j), and / or, path loss compensation factor α b,f,c (j), and / or, PUSCH power control adjustment state f b,f,c (i,l) or l, is determined based on the power parameter set associated with / included by the indicated TCI state and / or UL TCI state and / or candidate TCI state and / or candidate UL TCI state and / or candidate UL TCI state and / or path loss reference signal. The power parameter set includes the first power parameter set and / or the second power parameter set described below.

[0231] For example, when the unified TCI state type is joint, the PUSCH transmit power is calculated based on the set of power control parameters (for PUSCH / PUCCH / SRS) associated with the indicated TCI state and / or the path loss reference signal. When the unified TCI state type is separate, the PUSCH transmit power is calculated based on the set of power control parameters (for PUSCH / PUCCH / SRS) associated with the indicated UL TCI state and / or the path loss reference signal.

[0232] In some embodiments, the TCI status of a cell is configured separately for each DL BWP, and the UL TCI status is configured separately for each UL BWP.

[0233] In some embodiments, if the serving cell configuration of a cell includes a unified TCI state type (unifiedTCI-StateType-r17), it indicates that the cell is configured with a unified TCI state, and unifiedTCI-StateType-r17 can be configured as either separate or joint.

[0234] For example, when configured as independent, the TCI state applies to the downlink and the UL TCI state applies to the uplink. For instance, the configuration information of the DL BWP (in the PDSCH-Config) includes dl-OrJointTCI-StateList(-r17), which can include one or more TCI-States (IEs). Similarly, the configuration information of the UL BWP includes ul-TCI-StateList(-r17), which can include one or more TCI-UL-States (IEs).

[0235] For example, when configured as joint, the TCI state applies to both downlink and uplink. For instance, the configuration information of the DL BWP (in its PDSCH-Config) includes dl-OrJointTCI-StateList-r17, and its configured TCI state also applies to the UL BWP paired with it. The configuration information of the UL BWP does not include ul-TCI-StateList (-r17).

[0236] In some embodiments, DL BWPs and UL BWPs with the same BWP ID are paired. For example, each DL BWP includes a higher-layer parameter bwp-Id for configuring its BWP ID, which uniquely identifies a DL BWP within a cell, and each UL BWP's configuration information includes a higher-layer parameter bwp-Id for configuring its BWP ID, which uniquely identifies a UL BWP within a cell. If a DL BWP and a UL BWP have the same configured BWP ID value, they are paired. For example, a DL BWP with bwp-Id = 0 is paired with a UL BWP with bwp-Id = 0, a DL BWP with bwp-Id = 1 is paired with a UL BWP with bwp-Id = 1, and so on.

[0237] In some embodiments, the TCI-State IE and TCI-UL-State IE may each include parameters such as pathlossReferenceRS-Id-r17 (configuring the first path loss reference signal), pathlossReferenceRS-Id-r19 / pathlossReferenceRS-Id-SBFD / (configuring the second path loss reference signal)ul-powerControl-r17. Specifically, when the unified TCI state type is independent, the TCI-State IE does not include / does not contain pathlossReferenceRS-Id-r17 (and pathlossReferenceRS-Id-r19), while the TCI-UL-State IE includes pathlossReferenceRS-Id-r17 (optionally present). When the unified TCI state type is joint, the TCI-State IE includes (forces to exist) pathlossReferenceRS-Id-r17 (optionally present) pathlossReferenceRS-Id-r19.

[0238] In some embodiments, the TCI status and / or UL TCI status indicated (for an active DL BWP and / or an active UL BWP) refers to the TCI status or UL TCI status indicated by RRC signaling or MAC CE or DCI.

[0239] For example, when dlOrJointTCI-StateList-r17 includes only one TCI-State, that TCI-State can be used as the indicating TCI-State; when ul-TCI-StateList-r17 includes only one TCI-UL-State, that TCI-UL-State can be used as the indicating TCI-UL-State. For example, (when dlOrJointTCI-StateList includes multiple TCI-States, and / or ul-TCI-StateList-r17 includes multiple TCI-UL-States), when the activation command (MAC CE) maps a TCI-State and / or a TCI-UL-State to only one TCI codepoint (or in other words, only one TCI-State and / or TCI-UL-State is activated), that TCI-State and / or TCI-UL-State is used as the indicating TCI-State and / or TCI-UL-State. For example, (when dlOrJointTCI-StateList-r17 includes multiple TCI-States, and / or ul-TCI-StateList-r17 includes multiple TCI-UL-States, and / or when the activation command (MAC CE) maps TCI-States and / or TCI-UL-States to multiple TCI codepoints (or multiple TCI-States and / or TCI-UL-States are activated, and / or the DCI includes information fields for indicating TCI-States and / or TCI-UL-States),) the TCI-States and / or TCI-UL-States indicated by the DCI (format 1_1 / 1_2 / 1_3) can be used as the indicated TCI-States and / or TCI-UL-States.

[0240] In some embodiments, the indicated candidate TCI state (CandidateTCI-State) includes the candidateTCI-State indicated in the LTM Cell Switch Command MAC CE. The indicated candidate UL TCI state (CandidateTCI-UL-State) includes the candidateTCI-UL-State indicated in the LTM Cell Switch Command MAC CE.

[0241] In some embodiments, the TCI state and / or UL TCI state and / or candidate TCI state and / or candidate UL TCI state may be associated with / include a set of power control parameters.

[0242] In some embodiments, the serving cell configuration includes a higher-layer parameter uplink-PowerControlToAddModList-r17 for configuring power control parameters for PUSCH / PUCCH / SRS. Uplink-PowerControlToAddModList-r17 may include one or more uplink power control information elements.

[0243] In some embodiments, the "uplink power control information element" includes power control parameters for uplink signals. For example, the "uplink power control information element" is an Uplink-PowerControl IE, which configures (UE-specific) power control parameters for PUSCH and / or PUCCH and / or SRS.

[0244] In some embodiments, the uplink power control information element includes an uplink power control identifier (e.g., ul-powercontrolId-r17 / Uplink-powerControlId-r17), which corresponds to a set of power control parameters in the uplink power control information element. The set of power control parameters in the uplink power control information element includes a set of power control parameters for the PUSCH and / or a set of power control parameters for the PUCCH and / or a set of power control parameters for the SRS. This uplink power control identifier is used to uniquely identify an uplink power control information element and / or the set of power control parameters for the PUSCH and / or the set of power control parameters for the PUCCH and / or the set of power control parameters for the SRS included in the uplink power control information element within the cell.

[0245] In some embodiments, the power control parameter set may include a (UE-specific) target power and / or a (UE-specific) path loss compensation factor and / or a (UE-specific) closed-loop index. For example, the (UE-specific) target power includes p0-r17 in the P0AlphaSet-r17 IE, or the (UE-specific) target power is configured by p0-r17 in the P0AlphaSet-r17 IE. The (UE-specific) path loss compensation factor includes alpha-r17 in the P0AlphaSet-r17 IE, or the (UE-specific) path loss compensation factor is configured by alpha-r17 in the P0AlphaSet-r17 IE. The (UE-specific) closed-loop index includes closedLoopIndex-r17 in the P0AlphaSet-r17 IE, or the (UE-specific) closed-loop index is configured by closedLoopIndex-r17 in the P0AlphaSet-r17 IE.

[0246] In some embodiments, the uplink power control information element may include (or indicate) two sets of power control parameters for the PUSCH and / or may include (or indicate) two sets of power control parameters for the PUCCH and / or may include (or indicate) two sets of power control parameters for the SRS. For example, the two sets of power control parameters for the PUSCH include a first set of power control parameters (for the PUSCH) and a second set of power control parameters (for the PUSCH).

[0247] In some embodiments, the first power control parameter set includes p0AlphaSetforPUSCH-r17 or P0AlphaSet-r17 provided by p0AlphaSetforPUSCH-r17, or the first power control parameter set is configured by p0AlphaSetforPUSCH-r17. The second power control parameter set includes p0AlphaSetforPUSCH-r19 or p0AlphaSetforPUSCH-SBFD or P0AlphaSet-r17 provided by p0AlphaSetforPUSCH-r19 or p0AlphaSetforPUSCH-SBFD, or the second power control parameter set is configured by p0AlphaSetforPUSCH-r19 or p0AlphaSetforPUSCH-SBFD. P0AlphaSet-r17 may optionally include p0-r17, alpha-r17, and closedLoopIndex-r17.

[0248] In the embodiments of this application, "the uplink power control information element can include two sets of power control parameters for PUSCH", "the uplink power control information element can include two sets of power control parameters for PUCCH", and "the uplink power control information element can include two sets of power control parameters for SRS" respectively indicate that the uplink power control information element has the ability to carry / include / indicate two sets of power control parameters for PUSCH / PUCCH / SRS, which can be understood as one of the following: "the uplink power control information element can include one set of power control parameters for PUSCH / PUCCH / SRS, or the uplink power control information element can include two sets of power control parameters for PUSCH / PUCCH / SRS, or the uplink power control information element must include two sets of power control parameters for PUSCH / PUCCH / SRS".

[0249] In some embodiments, the indicated TCI state and / or UL TCI state and / or candidate TCI state and / or candidate UL TCI state is one of the cell's (active DL BWP) TCI state and / or candidate TCI state and / or (NUL / non-SUL) (carrier) (active UL BWP) UL TCI state and / or candidate UL TCI state.

[0250] In some embodiments, all TCI states and / or candidate TCI states of the cell (active DL BWP) or all UL TCI states and / or candidate UL TCI states of the carrier (active UL BWP) are associated with / include two sets of power control parameters for the PUSCH (including a first set of power control parameters and a second set of power control parameters).

[0251] In some embodiments, all TCI states and / or candidate TCI states of the cell (active UL BWP) or all UL TCI states and / or candidate UL TCI states of the carrier (active UL BWP) are associated with / include a set of power control parameters for the PUSCH (including a first set of power control parameters or a second set of power control parameters).

[0252] In some embodiments, the set of power control parameters associated with / included in a TCI state (for PUSCH) includes: a set of power control parameters (for PUSCH) corresponding to the uplink power control identifier in the UL BWP that is paired with the DL BWP where the TCI state is located; or, a set of power control parameters (for PUSCH) corresponding to the uplink power control identifier in the TCI state.

[0253] In some embodiments, the set of power control parameters associated with / included in a candidate TCI state (for PUSCH) includes: a set of power control parameters (for PUSCH) corresponding to the uplink power control identifier in the UL BWP that is paired with the DL BWP where the candidate TCI state is located; or, a set of power control parameters (for PUSCH) corresponding to the uplink power control identifier in the candidate TCI state.

[0254] In some embodiments, the set of power control parameters associated with / included in a UL TCI state (for PUSCH) includes: the set of power control parameters corresponding to the uplink power control identifier in the UL BWP where the UL TCI state is located (for PUSCH), or the set of power control parameters corresponding to the uplink power control identifier in the UL TCI state (for PUSCH).

[0255] In some embodiments, the set of power control parameters associated with / included in a candidate UL TCI state (for PUSCH) includes: the set of power control parameters corresponding to the uplink power control identifier in the UL BWP where the candidate UL TCI state is located (for PUSCH), or the set of power control parameters corresponding to the uplink power control identifier in the candidate UL TCI state (for PUSCH).

[0256] For example, there are two ways to configure the set of power control parameters associated with or included in the TCI state or UL TCI state.

[0257] Method 1: The configuration information of the UL BWP includes a higher-layer parameter ul-powerControl-r17 that indicates the power control parameters for PUSCH / PUCCH / SRS of the UL BWP. The uplink power control identifier provided by this higher-layer parameter points to the uplink power control information element with the same uplink power control identifier in the uplink-PowerControlToAddModList-r17 of the corresponding cell and / or the set of power control parameters for PUSCH / PUCCH / SRS included in the uplink power control information element.

[0258] Therefore, when the unified TCI state type is independent, all UL TCI states of this UL BWP are associated with / including the power control parameter set for PUSCH / PUCCH / SRS pointed to / corresponding to by the uplink power control identifier. When the unified TCI state type is joint, all TCI states of the DL BWP paired with this UL BWP are associated with / including the power control parameter set for PUSCH / PUCCH / SRS pointed to / corresponding to by the uplink power control identifier.

[0259] Method 2: The configuration information of the UL BWP does not include the high-level parameter ul-powerControl-r17, which is used to indicate the power control parameters for PUSCH / PUCCH / SRS of the UL BWP.

[0260] When the unified TCI state type is independent, the TCI-UL-State (IE) includes the higher-layer parameter ul-powerControl-r17 of the power control parameters for PUSCH / PUCCH / SRS for that (UL) TCI state. The uplink power control identifier provided by this higher-layer parameter points to the uplink power control information element with the same uplink power control identifier in the corresponding cell's uplink-PowerControlToAddModList-r17 and / or the set of power control parameters for PUSCH / PUCCH / SRS included in that uplink power control information element. Therefore, the UL TCI state is associated with / includes the set of power control parameters for PUSCH / PUCCH / SRS pointed to / corresponding to by the uplink power control identifier.

[0261] When the unified TCI state type is joint, the TCI-State (IE) includes the higher-layer parameter ul-powerControl-r17, which contains the power control parameters for PUSCH / PUCCH / SRS for that TCI state. The uplink power control identifier provided by this higher-layer parameter points to the uplink power control information element with the same uplink power control identifier in the corresponding cell's uplink-PowerControlToAddModList-r17 and / or the set of power control parameters for PUSCH / PUCCH / SRS included in that uplink power control information element. Therefore, this TCI state is associated with / includes the set of power control parameters for PUSCH / PUCCH / SRS pointed to / corresponding to by the uplink power control identifier.

[0262] In some embodiments, (for PUSCH corresponding to j>0), the UE target power (or UE-specific target power) P O_UE_PUSCH,b,f,c (j) Related to time-domain resources associated with PUSCH transmission opportunities.

[0263] For example, when (the indicated TCI state or UL TCI state) is configured / provided (a first set of power control parameters and) a second set of power control parameters, and / or when the indicated TCI state or UL TCI state is associated with / includes two sets of power control parameters for PUSCH, and / or, (the indicated TCI-state or UL-TCI-state is associated with / included) the second set of power control parameters including (UE) target power p0-r17, for PUSCH transmission opportunities associated with associated SBFD symbols, P O_UE_PUSCH,b,f,c The value of (j) is provided by the (UE) target power p0-r17 in the second power control parameter set (as indicated by the TCI-state or UL-TCI-state), for the PUSCH transmission opportunity associated with the non-SBFD symbol. O_UE_PUSCH,b,f,c The value of (j) is provided by the (UE) target power p0-r17 in the first set of power control parameters (associated with the indicated TCI-state or UL-TCI-state).

[0264] In some embodiments, (for PUSCH corresponding to j>0), the UE target power (or UE-specific target power) P O_UE_PUSCH,b,f,c (j) Time-domain resources unrelated to the PUSCH transmission opportunity. For example, when (the indicated TCI-state or UL-TCI-state) is not configured / provided with a second set of power control parameters, and / or, the indicated TCI state or UL TCI state is associated with / includes only one set of power control parameters for PUSCH (e.g., a first set of power control parameters or a second set of power control parameters), and / or, the second set of power control parameters (as associated with the indicated TCI-state or UL-TCI-state) does not include the (UE) target power p0-r17, by default / predefined, the UE target power (or UE-specific target power) P. O_UE_PUSCH,b,f,c (j) The target power p0-r17 of the (UE) is provided by the first set of power control parameters (or the second set of power control parameters) (as indicated by the TCI-state or UL-TCI-state), regardless of the time-domain resources associated with the PUSCH transmission opportunity.

[0265] In some embodiments, (for PUSCH corresponding to j>0), the path loss compensation factor α b,f,c(j) Time-domain resources associated with PUSCH transmission opportunities. For example, when (the indicated TCI state or UL TCI state) is configured / provided with (a first set of power control parameters and) a second set of power control parameters, and / or when the indicated TCI state or UL TCI state is associated with / includes two sets of power control parameters for PUSCH, and / or, (the indicated TCI-state or UL-TCI-state is associated with / included with) the second set of power control parameters includes a path loss compensation factor alpha-r17, for PUSCH transmission opportunities associated with associated SBFD symbols, α b,f,c The value of (j) is provided by the path loss compensation factor alpha-r17 in the second set of power control parameters (associated with the indicated TCI-state or UL-TCI-state), for PUSCH transmission opportunities associated with non-SBFD symbols. b,f,c The value of (j) is provided by the path loss compensation factor alpha-r17 in the first set of power control parameters (associated with the indicated TCI-state or UL-TCI-state).

[0266] In some embodiments, (for PUSCH corresponding to j>0), the path loss compensation factor α b,f,c (j) Time-domain resources unrelated to the PUSCH transmission opportunity. For example, when (the indicated TCI-state or UL-TCI-state) is not configured / provided with a second set of power control parameters, and / or, the indicated TCI state or UL TCI state is associated with / includes only one set of power control parameters for PUSCH (e.g., a first set of power control parameters or a second set of power control parameters), and / or, the second set of power control parameters (as associated with the indicated TCI-state or UL-TCI-state) does not include the path loss compensation factor alpha-r17, which is defaulted / predefined. b,f,c The value of (j) is provided by the path loss compensation factor alpha-r17 in the first power control parameter set (or the second power control parameter set) (associated with the indicated TCI-state or UL-TCI-state), regardless of the time-domain resources associated with the PUSCH transmission opportunity.

[0267] In some embodiments, the PUSCH power control adjustment state is... b,f,c (i,l) is a cumulative closed-loop power control adjustment value (e.g., determined according to formula (3), but not limited thereto) or an absolute closed-loop power control adjustment value (e.g., determined according to formula (4), but not limited thereto).

[0268] Or f b,f,c (i,l)=δPUSCH,b,f,c(i,l) (4)

[0269] 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.

[0270] In some embodiments, f b,f,c (i,l) corresponds to l, and the term f b,f,c (i,l) and l are interchangeable, or the terms "closed-loop index" and "PUSCH power control adjustment state" are interchangeable. For example, "PUSCH power control adjustment state f" b,f,c "(i,l)" and "PUSCH power control adjustment state l" or "closed-loop index l" can be interchanged.

[0271] In some embodiments, if the UE is not configured with two power control adjustment states (two PUSCH-PC-AdjustmentStates) and / or the UE is not configured with P0-PUSCH-AlphaSet, or if the PUSCH is scheduled by a RAR UL grant, l = 0.

[0272] In some embodiments, if the UE is configured with two power control adjustment states (two PUSCH-PC-AdjustmentStates), l∈{0,1}. For example, closedLoopIndex-r17 in the first power control parameter set and / or the second power control parameter set can be configured with l=0 or l=1, respectively.

[0273] In some embodiments, (for PUSCH corresponding to j>0), the closed-loop power control adjustment value fb,f,c (i,l) is related to the time-domain resources associated with the PUSCH transmission opportunity.

[0274] For example, when (the indicated TCI state or UL TCI state) is configured / provided (a first set of power control parameters and) a second set of power control parameters, and / or, the indicated TCI state or UL TCI state is associated with / includes two sets of power control parameters for PUSCH, and / or, the second set of power control parameters (as associated with the indicated TCI-state or UL-TCI-state) includes a closed-loop index closedLoopIndex-r17. For PUSCH transmission opportunities associated with an associated SBFD symbol, the value of closed-loop index l is provided by closed-loop index closedLoopIndex-r17 in the second set of power control parameters (as associated with the indicated TCI-state or UL-TCI-state). For PUSCH transmission opportunities associated with a associated non-SBFD symbol, the value of closed-loop index l is provided by closed-loop index closedLoopIndex-r17 in the first set of power control parameters (as associated with the indicated TCI-state or UL-TCI-state).

[0275] In some embodiments, (for PUSCH corresponding to j>0), the closed-loop power control adjustment value f b,f,c (i,l) is independent of the time-domain resources associated with the PUSCH transmission opportunity.

[0276] For example, when the indicated TCI-state or UL-TCI-state is not configured / provided with a second set of power control parameters, and / or the indicated TCI-state or UL-TCI-state is associated with / includes only one set of power control parameters for PUSCH (e.g., a first set of power control parameters or a second set of power control parameters), and / or the second set of power control parameters (as associated with the indicated TCI-state or UL-TCI-state) does not include the closed-loop index closedLoopIndex-r17, by default / predefined, the value of l is provided by the closed-loop index closedLoopIndex-r17 in the first set of power control parameters (as associated with the indicated TCI-state or UL-TCI-state), regardless of the time-domain resources associated with the PUSCH transmission opportunity.

[0277] For example, Table 2 provides an example of power control parameters:

[0278] Table 2

[0279] In some embodiments, for the PUSCH corresponding to j=0, αb,f,c (0) Related to time-domain resources associated with PUSCH transmission opportunities.

[0280] For example, for PUSCH in cases where no (higher-layer) parameters are provided to indicate the UE target power and / or path loss compensation factor set, and / or for PUSCH ((re)transmission) corresponding to the RAR UL grant, α b,f,c (0) Related to the time-domain resources associated with the PUSCH transmission opportunity. For example, (when a first path loss compensation factor (for non-SBFD symbols) is provided, e.g., msg3-Alpha,) (and a second path loss compensation factor (for SBFD symbols) is provided, e.g., msg3-Alpha-SBFD,) for the PUSCH transmission opportunity associated with an SBFD symbol, α b,f,c (0) is the value of msg3-Alpha-SBFD, α, for the PUSCH transmission opportunity associated with a non-SBFD symbol. b,f,c (0) is the value of msg3-Alpha.

[0281] For example, (for the PUSCH corresponding to j=0), for the PUSCH in which the UE establishes a connection using a Type II random access procedure and no (higher-layer) parameters are provided to indicate the UE's target power and / or path loss compensation factor set, when no third path loss compensation factor is provided, e.g., msgA-Alpha, α b,f,c (0) Related to the time-domain resources associated with the PUSCH transmission opportunity. For example, (when a first path loss compensation factor (for non-SBFD symbols) is provided) (and a second path loss compensation factor (for SBFD symbols) is provided), α for the PUSCH transmission opportunity associated with SBFD symbols. b,f,c (0) is the value of msg3-Alpha-SBFD, α, for the PUSCH transmission opportunity associated with a non-SBFD symbol. b,f,c (0) is the value of msg3-Alpha. When a third path loss compensation factor is provided, α... b,f,c (0) Not related to the time-domain resources associated with the PUSCH transmission opportunity. For example, by default / predefined, α b,f,c (0) is the value of msgA-Alpha, regardless of the time-domain resource associated with the PUSCH sending opportunity.

[0282] In some embodiments, for the PUSCH corresponding to j=0, α b,f,c (0) is unrelated to the time-domain resources associated with the PUSCH transmission opportunity.

[0283] For example, (for the PUSCH corresponding to j=0,) for the PUSCH in cases where no (higher-layer) parameters are provided to indicate the UE target power and / or path loss compensation factor set, and / or for the PUSCH ((re)transmission) corresponding to the RAR UL grant, α b,f,c (0) Not related to time-domain resources associated with PUSCH transmission opportunities. For example, (when a first path loss compensation factor (for non-SBFD symbols) is provided, (and a second path loss compensation factor (for SBFD symbols) is not provided), α by default / predefined. b,f,c (0) is the value of msg3-Alpha, regardless of the time-domain resources associated with the PUSCH transmission opportunity. For example, (when no first path loss compensation factor (for non-SBFD symbols) is provided,) (and no second path loss compensation factor (for SBFD symbols) is provided,) by default / predefined, α b,f,c (0) = 1, regardless of the time-domain resources associated with the PUSCH sending opportunity.

[0284] For example, (for the PUSCH corresponding to j=0), for the PUSCH in cases where the UE establishes a connection using a Type 2 random access procedure and no (higher-layer) parameters are provided to indicate the UE's target power and / or path loss compensation factor set, and / or for the PUSCH of a Type 2 random access procedure in cases where no (higher-layer) parameters are provided to indicate the preamble target received power for a Type 2 random access procedure (2-step RA), α b,f,c (0) Not related to time-domain resources associated with PUSCH transmission opportunities. For example, (when a third path loss compensation factor is provided) (and a first and / or second path loss compensation factor is provided), α by default / predefined. b,f,c (0) is the value of msgA-Alpha, regardless of the temporal resources associated with the PUSCH transmission opportunity. For example, (when no third path loss compensation factor is provided), (and a first and / or second path loss compensation factor is provided), α is by default / predefined. b,f,c (0) is the value of msg3-Alpha, regardless of the time-domain resources associated with the PUSCH transmission opportunity. For example, when no third path loss compensation factor is provided (and no first and / or second path loss compensation factors are provided), α is defaulted / predefined. b,f,c (0) = 1, regardless of the time-domain resources associated with the PUSCH sending opportunity.

[0285] In some embodiments, (for PUSCH corresponding to j=0,) l=0.

[0286] In some embodiments, for the PUSCH corresponding to j=0, f b,f,c (i,l) is related to the time-domain resources associated with the PUSCH transmission opportunity.

[0287] For example, for PUSCH ((re)transmission) corresponding to RAR UL grant, or if the UE receives a random access response message in response to a PRACH transmission or a MsgA transmission on active UL BWP b of carrier f of serving cell c, then it can be as described in Table 3:

[0288] Table 3

[0289] In other words, for the PUSCH (scheduled by the RAR grant) associated with the SBFD symbol, It refers to the bandwidth of the PUSCH (scheduled by the RAR grant) for the first associated SBFD symbol in this UL BWP, and / or, Δ TF,b,f,c (0) is the power adjustment for the PUSCH (scheduled by the RAR grant) of the first associated SBFD symbol in this UL BWP.

[0290] For PUSCH (scheduled by the RAR grant) associated with non-SBFD symbols, It refers to the bandwidth of the PUSCH (scheduled by the RAR grant) for the first associated non-SBFD symbol in this UL BWP, and / or, Δ TF,b,f,c (0) is the power adjustment for the PUSCH (scheduled by the RAR grant) of the first associated non-SBFD symbol in this UL BWP.

[0291] In some embodiments, for the PUSCH corresponding to j=0, f b,f,c(i,l) is independent of the time-domain resources associated with the PUSCH transmission opportunity. For example, for the PUSCH ((re)transmission) corresponding to the RAR UL grant, or, if the UE receives a random access response message in response to a PRACH transmission or a MsgA transmission on active UL BWP b of carrier f of serving cell c, the above and Δ TF,b,f,c (0) Determine the time-domain resource associated with the PUSCH (scheduled by the RAR grant) in accordance with Table 4 below.

[0292] Table 4

[0293] In some embodiments, the PUSCH transmission opportunity is associated with a first time-domain resource (and not with a second time-domain resource), including:

[0294] The PUSCH transmission opportunity is in the first time domain resource, and / or, the PUSCH transmission opportunity begins in the first time domain resource, and / or, the PUSCH transmission opportunity ends in the first time domain resource, and / or, the PUSCH transmission opportunity spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat is in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat begins in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat ends in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or, the specific symbol of the PUSCH transmission opportunity is associated with the first time domain resource.

[0295] In some embodiments, the PUSCH transmission opportunity is associated with a second time-domain resource (and not with a first time-domain resource), including:

[0296] The PUSCH transmission opportunity is in the second time domain resource, and / or, the PUSCH transmission opportunity begins in the second time domain resource, and / or, the PUSCH transmission opportunity ends in the second time domain resource, and / or, the PUSCH transmission opportunity spans the first time domain resource and the second time domain resource (or overlaps with both the first and second time domain resources), and / or, the PUSCH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition (e.g., the first / last actual repetition) is in the second time domain resource, and / or, the PUSCH transmission opportunity is nominally repeated and a specific actual repetition of the nominal repetition (e.g., the first / last actual repetition) is in the second time domain resource, and / or, the PUSCH transmission opportunity is in the second time domain resource. The CH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition begins in the second time domain resource, and / or the PUSCH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition ends in the second time domain resource, and / or the PUSCH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or a specific symbol of the PUSCH transmission opportunity (e.g., the first / last symbol) is associated with the second time domain resource.

[0297] In some embodiments, the PUSCH sending opportunity is associated with a first time-domain resource and a second time-domain resource, including:

[0298] The PUSCH transmission opportunity spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or the PUSCH transmission opportunity is nominally repeated and a specific actual repetition of the nominally repeated spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource).

[0299] In some embodiments, the specific symbol of the PUSCH transmission opportunity is associated with the first time-domain resource, including: the specific symbol of the PUSCH transmission opportunity is the first time-domain resource or is in the first time-domain resource, and / or, the specific symbol of the PUSCH transmission opportunity is associated with the second time-domain resource, including: the specific symbol of the PUSCH transmission opportunity is the second time-domain resource or is in the first time-domain resource.

[0300] In some embodiments, for a PUSCH having a second repetition type (repetition Type B), (or when the PUSCH has a second repetition type), the PUSCH transmission opportunity is a nominal repetition (or includes symbol assignment for the nominal repetition) or a real repetition (or includes symbol assignment for the real repetition).

[0301] In some embodiments, the PUSCH transmission opportunity is nominal repetition when no first information is provided, and / or, when the first information is provided, the PUSCH transmission opportunity is nominal repetition or actual repetition, and / or, for cells with SBFD enabled and / or UL BWPs with third frequency domain resources (UL usable PRBs), the PUSCH transmission opportunity is nominal repetition or actual repetition.

[0302] For example, the first piece of information includes one or more of the following:

[0303] Information used to configure the first time-domain resource and / or the second time-domain resource;

[0304] Information used to configure the first frequency domain resource (UL subband) and / or the second frequency domain resource (DL subband);

[0305] Information used to configure (dedicated) power parameters for the second time domain resource (or information used to configure (dedicated) power parameters for (calculating) the PUSCH transmission opportunity (in the transmission power) associated with the second time domain resource);

[0306] Information used to configure whether the PUSCH sending opportunity is nominally duplicated or actually duplicated.

[0307] The information used to configure the power parameters (dedicated) to the second time-domain resource includes, for example, one or more of the information described above used to configure the parameters for determining the transmission power of the PUSCH associated with the second time-domain resource, such as information for indicating the determination of the second maximum output power, information for indicating the second set of power control parameters, etc.

[0308] In some embodiments, the transmit power for a PUSCH is related to the PUSCH transmit opportunity associated with or corresponding to the time-domain resources (or time-domain resource type, or symbol type), or the transmit power for a PUSCH is determined based on the PUSCH transmit opportunity associated with or corresponding to the time-domain resources, including:

[0309] The transmission power in the PUSCH transmission opportunity (or associated / corresponding to the PUSCH transmission opportunity) is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmission opportunity.

[0310] Alternatively, the transmission power for the PUSCH may be determined based on the PUSCH transmission opportunity associated with or corresponding time-domain resources (for the PUSCH).

[0311] In some embodiments, the terminal device transmits the PUSCH by: transmitting the PUSCH according to the transmission power in the PUSCH transmission opportunity during the PUSCH transmission opportunity.

[0312] In some embodiments, the PUSCH transmission opportunity includes: (continuous) symbol allocation (or allocated symbols) within a time slot (for the PUSCH), or (continuous) symbol allocation (or allocated symbols) across multiple time slots (for the PUSCH).

[0313] For example, Table 5 shows an example of a PUSCH sending opportunity:

[0314] Table 5

[0315] 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.

[0316] 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.

[0317] As can be seen from the above embodiments, in the presence of different time-domain resources such as beams, channel states, and frequency-domain resources for uplink, the transmission power of PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, and can support PUSCH transmission and reception in the presence of the above-mentioned different time-domain resources.

[0318] Second aspect of the embodiments

[0319] This application provides a PUSCH receiving method, which is 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.

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

[0321] 601, The network device receives a PUSCH sent by the terminal device;

[0322] The transmission power of the PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmission opportunity (a specific symbol of the PUSCH), or the transmission power of the PUSCH is determined according to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, wherein the time-domain resources associated with the PUSCH transmission opportunity include a first time-domain resource (non-SBFD symbols) and / or a second time-domain resource (SBFD symbols).

[0323] As shown in Figure 6, the method may further include:

[0324] 600, the network device sends configuration information to the terminal device.

[0325] 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.

[0326] 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).

[0327] 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.

[0328] 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.

[0329] As can be seen from the above embodiments, in the presence of different time-domain resources such as beams, channel states, and frequency-domain resources for uplink, the transmission power of PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, and can support PUSCH transmission and reception in the presence of the above-mentioned different time-domain resources.

[0330] Third aspect of the embodiments

[0331] This application provides a PUSCH transmitting 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.

[0332] Figure 7 is a schematic diagram of a PUSCH 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 PUSCH transmitting device 700 includes: a processor 701 and a transmitter 702; it may also include a receiver 703.

[0333] Processor 701 determines the transmission power for PUSCH; and transmitter 702 transmits the PUSCH;

[0334] The transmission power of the PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmission opportunity (a specific symbol of the PUSCH), or the transmission power of the PUSCH is determined according to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, wherein the time-domain resources associated with the PUSCH transmission opportunity include a first time-domain resource (non-SBFD symbols) and / or a second time-domain resource (SBFD symbols).

[0335] In some embodiments, the transmission power for the PUSCH includes: the transmission power of the PUSCH in the PUSCH transmission opportunity, or the transmission power of the PUSCH associated with / corresponding to the PUSCH transmission opportunity.

[0336] In some embodiments, determining the transmit power for a PUSCH includes: determining the transmit power of (the PUSCH) during the PUSCH transmit opportunity (of the PUSCH).

[0337] In some embodiments, the PUSCH includes (or is associated with / corresponds to) one or more PUSCH transmission opportunities, and the transmission power in different PUSCH transmission opportunities is determined separately.

[0338] In some embodiments, the transmission power in the PUSCH transmission opportunity is determined based on at least one of the following, wherein one or more of the above-mentioned factors relate to the time-domain resources associated with the PUSCH transmission opportunity.

[0339] The transmission power in the PUSCH transmission opportunity is determined based on one or more of the following, or at least one of the one or more is determined based on the time-domain resources associated with the PUSCH transmission opportunity, and the transmission power is then determined accordingly:

[0340] Maximum output power;

[0341] Target power;

[0342] Subcarrier spacing;

[0343] The number of RBs for the PUSCH transmission opportunity;

[0344] Path loss compensation factor;

[0345] Path loss;

[0346] First power offset;

[0347] PUSCH power control adjustment state;

[0348] Second power offset.

[0349] In some embodiments, for a PUSCH transmission opportunity associated with a first time domain resource (but not associated with a second time domain resource), the maximum output power is a first maximum output power, and / or, for a PUSCH transmission opportunity associated with a second time domain resource (but not associated with a first time domain resource), the maximum output power is a second maximum output power;

[0350] Wherein, the second maximum output power is determined based on a parameter (configured by the base station or set by the UE) that is not used to determine the first maximum output power, and / or, the first maximum output power is determined based on a parameter (configured by the base station or set by the UE) that is not used to determine the second maximum output power.

[0351] In some embodiments, the target power includes a nominal target power (or a cell-specific target power), or the sum of the nominal target power (or the cell-specific target power) and the UE target power (or the UE-specific target power).

[0352] In some embodiments, the PUSCH in cases where no (higher-layer) parameters (P0-PUSCH-AlphaSet) for indicating the UE target power and / or path loss compensation factor set are provided includes: the PUSCH in cases where the UE establishes a connection using a Type 1 random access procedure (4-step RA) and no (higher-layer) parameters (P0-PUSCH-AlphaSet) for indicating the UE target power and / or path loss compensation factor set are provided, and / or the PUSCH in cases where the UE establishes a connection using a Type 2 random access procedure and no (higher-layer) parameters (P0-PUSCH-AlphaSet) for indicating the UE target power and / or path loss compensation factor set are provided.

[0353] And / or, for the PUSCH ((re)transmission) corresponding to the RAR UL grant (including the RAR UL grant in response to Msg1 in the RAR and / or the RAR UL grant in response to MsgA in the fallback RAR) (e.g., referred to as Msg3 PUSCH),

[0354] And / or, for a Type 2 random access procedure (RA) PUSCH (e.g., referred to as MsgA PUSCH) in cases where a (higher-layer) parameter (msgA - preambleReceived TargetPower) indicating the preamble target received power for the RA is not provided.

[0355] And / or, for CG PUSCHs where no (higher-level) parameter (p0-NominalWithGrant) is provided to indicate the nominal target power for the CG PUSCH,

[0356] And / or, for DG PUSCHs where no (higher-level) parameter (p0 - Nominal Without Grant) is provided to indicate the nominal target power for the DG PUSCH,

[0357] The nominal target power includes the leader target received power, or the sum of the leader target received power and the power offset; the leader target received power is the first leader target received power, the second leader target received power, or the third leader target received power, and / or the power offset is the third power offset, the fourth power offset, or the fifth power offset, or equal to 0.

[0358] In some embodiments, whether the leader target received power is the first leader target received power or the second leader target received power depends on one or more of the following:

[0359] Is the community equipped with a first RO or a second RO?

[0360] PUSCH sends opportunity-related temporal resources;

[0361] The corresponding leading edge uses RO;

[0362] The value of the received power of the first forward target;

[0363] The value of the received power of the second forward target;

[0364] PUSCH type;

[0365] RO corresponds to the PRACH format;

[0366] Is the cell configured with (third power offset and) fourth power offset?

[0367] In some embodiments, for a cell configured with the first RO (and configured with the second preamble target receive power) or the second RO (and configured with the second preamble target receive power), the preamble target receive power is the first preamble target receive power, the second preamble target receive power, or the third preamble target receive power, and / or,

[0368] For cells that are neither configured with the first RO nor with the second RO, the preamble target received power is either the first preamble target received power or the third preamble target received power, and / or...

[0369] For a cell configured with the first RO or the second RO, if the second preamble target receive power is not configured, the preamble target receive power is the first preamble target receive power or the third preamble target receive power.

[0370] In some embodiments, for a cell configured with the first RO, the second fronting target receive power includes the fronting target receive power configured for (or dedicated to) the first RO and / or the fronting target receive power configured by a first parameter (included in information for configuring the first RO, which also includes parameters for configuring the first fronting target receive power), and / or,

[0371] For a cell configured with the second RO, the second preamble target receive power includes the preamble target receive power configured for (or dedicated to) the second RO and / or the preamble target receive power configured by the second parameter (included in the information used to configure the second RO) (wherein, a cell cannot be configured with both the first RO and the second RO at the same time).

[0372] In some embodiments, for a cell configured with the first RO or the second RO (and configured with the second preamble target receive power):

[0373] (For PUSCH in cases where no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation factor set is provided, and / or, in cases where the UE establishes a connection using a Type 1 random access procedure (4-step RA) and no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation factor set is provided (or, for PUSCH in such cases), and / or, for PUSCH ((re)transmission) corresponding to a RAR UL grant (including the RAR UL grant in response to Msg1 and / or the RAR UL grant in response to MsgA in fallback RAR) (e.g., referred to as Msg3) PUSCH), and / or, in the case where the UE establishes a connection using a Type 2 random access procedure and no (higher-layer) parameter (P0-PUSCH-AlphaSet) indicating the UE's target power and / or path loss compensation factor set is provided (or, for the PUSCH in this case), and / or, for the Type 2 random access procedure (2-step RA) PUSCH (e.g., referred to as MsgA PUSCH) in the case where no (higher-layer) parameter (msgA-preambleReceivedTargetPower) indicating the preamble target received power for the Type 2 random access procedure is provided, and / or, for the CG PUSCH in the case where no (higher-layer) parameter (p0-NominalWithGrant) indicating the nominal target power for the CG PUSCH is provided, and / or, for the DG PUSCH in the case where no (higher-layer) parameter (p0-NominalWithoutGrant) indicating the nominal target power for the DG PUSCH is provided.

[0374] (For a cell configured with a second RO,) (where the PRACH format corresponding to the second RO is the same as that of the third RO) (where a (third power offset and) fourth power offset are provided), and / or, for a cell configured with a first RO,) for a PUSCH transmission opportunity associated with the first time domain resource (and not associated with the second time domain resource), the preamble target receive power is the first preamble target receive power; for a PUSCH transmission opportunity associated with the second time domain resource (and not associated with the first time domain resource), the preamble target receive power is the second preamble target receive power; and / or

[0375] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) for a PUSCH transmission opportunity associated with the first time domain resource (but not associated with the second time domain resource), the preamble target receive power is the second preamble target receive power; for a PUSCH transmission opportunity associated with the second time domain resource (but not associated with the first time domain resource), the preamble target receive power is the first preamble target receive power; and / or,

[0376] (For cells configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the corresponding preamble (or PRACH / Msg1) is transmitted using the third RO, the preamble target received power is the first preamble target received power; when the corresponding preamble is transmitted using either the first RO or the second RO, the preamble target received power is the second preamble target received power (wherein, the corresponding preamble includes the most recently / last transmitted preamble (before the PUSCH) and / or the preamble responded to by the (most recently / last) RAR (UL grant) (before the PUSCH) and / or the first / first preamble transmitted during random access); and / or,

[0377] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the corresponding preamble (or PRACH) is transmitted using the third RO, (for PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource,) the preamble target receive power is the first preamble target receive power; when the corresponding preamble is transmitted using the first RO or the second RO, for PUSCH transmission opportunities associated with the first time domain resource, the preamble target receive power is the first preamble target receive power; for PUSCH transmission opportunities associated with the second time domain resource, the preamble target receive power is the second preamble target receive power; and / or,

[0378] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the corresponding preamble (or PRACH) is transmitted using the first RO or the second RO, (for PUSCH transmission opportunities associated with the first time domain resource and PUSCH transmission opportunities associated with the second time domain resource,) the preamble target receive power is the second preamble target receive power; when the corresponding preamble is transmitted using the third RO, for PUSCH transmission opportunities associated with the first time domain resource, the preamble target receive power is the first preamble target receive power; for PUSCH transmission opportunities associated with the second time domain resource, the preamble target receive power is the second preamble target receive power; and / or,

[0379] (For cells configured with a second RO,) (where the PRACH format corresponding to the second RO differs from that of the third RO,) (where no (third power offset and) fourth power offset are provided,) when the first preamble target received power is greater than or less than or not greater than or not less than or equal to the second preamble target received power, the preamble target received power is the first preamble target received power, and / or, when the second preamble target received power is greater than or less than or not greater than or not less than or equal to the first preamble target received power, the preamble target received power is the second preamble target received power; and / or,

[0380] (For a cell configured with a second RO,) (when the PRACH format corresponding to the second RO is different from that of the third RO,) (when no (third power offset and) fourth power offset are provided,) when the third RO is preferred for transmitting the preamble, the preamble target received power is the first preamble target received power; when either the first RO or the second RO is preferred for transmitting the preamble, the preamble target received power is the second preamble target received power; and / or,

[0381] (For a cell configured with a second RO,) (where the PRACH format corresponding to the second RO is different from that of the third RO,) (where no (third power offset and) fourth power offset are provided,) the preamble target received power is the first preamble target received power; and / or,

[0382] (For a cell configured with a second RO,) (in the case where the PRACH format corresponding to the second RO is different from that of the third RO,) (in the case where (the third power offset and) the fourth power offset are not provided,) the received power of the preamble target is the received power of the second preamble target.

[0383] In some embodiments, for a cell configured with a first RO or a second RO (and configured with a second preamble target received power):

[0384] When the terminal device establishes a connection using a Type I random access procedure and is not provided with (higher-layer) parameters (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation set, and / or when the terminal device establishes a connection using a Type II random access procedure and is not provided with (higher-layer) parameters (P0-PUSCH-AlphaSet) indicating the UE target power and / or path loss compensation set, and / or for the Type II random access procedure PUSCH without the (higher-layer) parameter (msgA-preambleReceivedTargetPower) indicating the preamble target received power for the Type II random access procedure, and / or for the CG PUSCH without the (higher-layer) parameter (p0-NominalWithGrant) indicating the nominal target power for the CG PUSCH, and / or for the DG PUSCH without the (higher-layer) parameter (p0-NominalWithoutGrant) indicating the nominal target power for the DG PUSCH. PUSCH, wherein the receiving power of the leading target is the receiving power of the first leading target.

[0385] In some embodiments, when the third power offset and the fourth power offset are provided, the power offset is either the third power offset or the fourth power offset, and / or,

[0386] In the case where the third power offset is provided (and the fourth power offset is not provided), the power offset is the third power offset, and / or,

[0387] If the third power offset and / or the fourth power offset are not provided, the power offset is equal to 0.

[0388] In some embodiments, where the third power offset and the fourth power offset are provided:

[0389] For a PUSCH transmission opportunity associated with the first time-domain resource (but not associated with the second time-domain resource), the power offset is the third power offset, and / or,

[0390] For a PUSCH transmission opportunity associated with the second time domain resource (but not associated with the first time domain resource), the power offset is the fourth power offset.

[0391] In some embodiments, the fourth power offset may be provided for cells configured with a second RO, and / or the fourth offset power may not be provided for cells not configured with a second RO.

[0392] In some embodiments, for a PUSCH transmission opportunity associated with the first time-domain resource (but not associated with the second time-domain resource), the number of RBs for the PUSCH transmission opportunity includes the number of valid RBs allocated (among the allocated RBs) or the number of allocated RBs, and / or,

[0393] For a PUSCH transmission opportunity associated with the second time-domain resource (but not associated with the first time-domain resource), the number of RBs for the PUSCH transmission opportunity includes the number of allocated RBs.

[0394] In some embodiments, the first power offset is determined based on the number of RBs for a PUSCH transmission opportunity.

[0395] In some embodiments, for a PUSCH transmission opportunity associated with the first time-domain resource (but not associated with the second time-domain resource), the transmission power is not determined based on / without using the second power offset, and / or,

[0396] For a PUSCH transmission opportunity associated with the second time-domain resource (but not associated with the first time-domain resource), the transmission power is determined based on / using the second power offset.

[0397] In some embodiments, the PUSCH transmission opportunity is associated with the first time-domain resource (and not with the second time-domain resource), including:

[0398] The PUSCH transmission opportunity is in the first time domain resource, and / or, the PUSCH transmission opportunity begins in the first time domain resource, and / or, the PUSCH transmission opportunity ends in the first time domain resource, and / or, the PUSCH transmission opportunity spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat is in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat begins in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat ends in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or, the specific symbol of the PUSCH transmission opportunity is associated with the first time domain resource.

[0399] In some embodiments, the PUSCH transmission opportunity is associated with the second time-domain resource (and not with the first time-domain resource), including:

[0400] The PUSCH transmission opportunity is in the second time domain resource, and / or, the PUSCH transmission opportunity begins in the second time domain resource, and / or, the PUSCH transmission opportunity ends in the second time domain resource, and / or, the PUSCH transmission opportunity spans the first time domain resource and the second time domain resource (or overlaps with both the first and second time domain resources), and / or, the PUSCH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition (e.g., the first / last actual repetition) is in the second time domain resource, and / or, the PUSCH transmission opportunity is nominally repeated and a specific actual repetition of the nominal repetition (e.g., the first / last actual repetition) is in the second time domain resource, and / or, the PUSCH transmission opportunity is in the second time domain resource. The CH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition begins in the second time domain resource, and / or the PUSCH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition ends in the second time domain resource, and / or the PUSCH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or a specific symbol of the PUSCH transmission opportunity (e.g., the first / last symbol) is associated with the second time domain resource.

[0401] In some embodiments, the PUSCH transmission opportunity is associated with the first time-domain resource and the second time-domain resource, including:

[0402] The PUSCH transmission opportunity spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or the PUSCH transmission opportunity is nominally repeated and a specific actual repetition of the nominally repeated spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource).

[0403] In some embodiments, the association of a specific symbol of the PUSCH transmission opportunity with the first time-domain resource includes: the specific symbol of the PUSCH transmission opportunity being the first time-domain resource or being in the first time-domain resource, and / or,

[0404] The specific symbol of the PUSCH transmission opportunity is associated with the second time-domain resource, including: the specific symbol of the PUSCH transmission opportunity is the second time-domain resource or is in the first time-domain resource.

[0405] In some embodiments, for a PUSCH having a second repetition type (repetition Type B), (or when the PUSCH has a second repetition type), the PUSCH transmission opportunity is a nominal repetition (or includes symbol assignment for the nominal repetition) or a real repetition (or includes symbol assignment for the real repetition).

[0406] In some embodiments, when no first information is provided, the PUSCH transmission opportunity is nominally repeated, and / or,

[0407] When the first information is provided, the PUSCH transmission opportunity is either a nominal duplicate or a real duplicate, and / or,

[0408] For cells with SBFD enabled and / or UL BWPs with third frequency domain resources (UL usable PRBs), the PUSCH transmission opportunity is nominal repetition or actual repetition.

[0409] In some embodiments, the first information includes one or more of the following:

[0410] Information used to configure the first time-domain resource and / or the second time-domain resource;

[0411] Information used to configure the first frequency domain resource (UL subband) and / or the second frequency domain resource (DL subband) (the third frequency domain resource of the UL BWP includes the intersection of the first frequency domain resource and the UL BWP);

[0412] Information used to configure (dedicated) power parameters for the second time domain resource (or information used to configure (dedicated) power parameters for (calculating) the PUSCH transmission opportunity (in the transmission power) associated with the second time domain resource);

[0413] Information used to configure whether the PUSCH sending opportunity is nominally duplicated or actually duplicated.

[0414] In some embodiments, the transmit power for the PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmit opportunity, or the transmit power for the PUSCH is determined based on the time-domain resources associated with or corresponding to the PUSCH transmit opportunity, including:

[0415] The transmission power in the PUSCH transmission opportunity (or associated / corresponding to the PUSCH transmission opportunity) is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmission opportunity.

[0416] Alternatively, the transmission power for the PUSCH may be determined based on the PUSCH transmission opportunity associated with or corresponding time-domain resources (for the PUSCH).

[0417] In some embodiments, the terminal device transmits the PUSCH by: transmitting the PUSCH according to the transmission power in the PUSCH transmission opportunity during the PUSCH transmission opportunity.

[0418] In some embodiments, the PUSCH transmission opportunity includes: (continuous) symbol allocation (or allocated symbols) within a time slot (for the PUSCH), or (continuous) symbol allocation (or allocated symbols) across multiple time slots (for the PUSCH).

[0419] 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 PUSCH transmitting device 700 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0420] 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.

[0421] 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.

[0422] As can be seen from the above embodiments, in the presence of different time-domain resources such as beams, channel states, and frequency-domain resources for uplink, the transmission power of PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, and can support PUSCH transmission and reception in the presence of the above-mentioned different time-domain resources.

[0423] Fourth aspect of the embodiment

[0424] This application provides a PUSCH 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.

[0425] Figure 8 is a schematic diagram of a PUSCH 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 PUSCH device 800 includes: a receiver 801 and a transmitter 802; it may also include a processor 803.

[0426] Receiver 801 is used to receive PUSCH; wherein the transmission power for the PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmission opportunity (a specific symbol of the PUSCH), or the transmission power for the PUSCH is determined according to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, wherein the time-domain resources associated with the PUSCH transmission opportunity include a first time-domain resource (non-SBFD symbols) and / or a second time-domain resource (SBFD symbols).

[0427] Transmitter 802 is used to send configuration information / instruction information.

[0428] 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 PUSCH receiving device 800 of this application embodiment may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0429] 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.

[0430] 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.

[0431] As can be seen from the above embodiments, in the presence of different time-domain resources such as beams, channel states, and frequency-domain resources for uplink, the transmission power of PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity, and can support PUSCH transmission and reception in the presence of the above-mentioned different time-domain resources.

[0432] Fifth aspect of the embodiment

[0433] 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.

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

[0435] A terminal device that determines the transmission power for the PUSCH and transmits the PUSCH;

[0436] Network device that receives the PUSCH;

[0437] The transmission power of the PUSCH is related to the time-domain resources associated with or corresponding to the PUSCH transmission opportunity. The time-domain resources associated with the PUSCH transmission opportunity include first time-domain resources and / or second time-domain resources.

[0438] 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.

[0439] 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.

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

[0441] 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.

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

[0443] 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.

[0444] For example, processor 1010 can be configured to execute a program to implement the method as described in the embodiment of the first aspect.

[0445] 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.

[0446] 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.

[0447] 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.

[0448] 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.

[0449] 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.

[0450] 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.

[0451] 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.

[0452] 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.

[0453] 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.

[0454] 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.

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

[0456] 1. A method for sending a PUSCH, comprising:

[0457] The terminal equipment determines the transmit power for the PUSCH; and

[0458] The terminal device sends the PUSCH;

[0459] The transmission power of the PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmission opportunity (a specific symbol of the PUSCH). The time-domain resources associated with the PUSCH transmission opportunity include first time-domain resources (non-SBFD symbols) and / or second time-domain resources (SBFD symbols).

[0460] 2. A PUSCH receiving method, comprising:

[0461] Network devices receive PUSCH;

[0462] The transmission power of the PUSCH is related to the time-domain resources (or time-domain resource type, or symbol type) associated with or corresponding to the PUSCH transmission opportunity (a specific symbol of the PUSCH). The time-domain resources associated with the PUSCH transmission opportunity include first time-domain resources (non-SBFD symbols) and / or second time-domain resources (SBFD symbols).

[0463] 3. The method according to Appendix 2, wherein the PUSCH includes (or is associated with / corresponds to) one or more PUSCH transmission opportunities, and the transmission power in different PUSCH transmission opportunities is determined separately.

[0464] 4. The method according to Appendix 2, wherein the transmission power in the PUSCH transmission opportunity is determined according to at least one of the following, wherein one or more of the at least one are related to the time-domain resources associated with the PUSCH transmission opportunity:

[0465] Maximum output power;

[0466] Target power;

[0467] Subcarrier spacing;

[0468] The number of RBs for the PUSCH transmission opportunity;

[0469] Path loss compensation factor;

[0470] Path loss;

[0471] First power offset;

[0472] PUSCH power control adjustment state;

[0473] Second power offset.

[0474] 5. The method according to Appendix 2, wherein the PUSCH transmission opportunity is associated with the first time-domain resource (and not with the second time-domain resource), includes:

[0475] The PUSCH transmission opportunity is in the first time domain resource, and / or,

[0476] The PUSCH transmission opportunity originates in the first time domain resource, and / or,

[0477] The PUSCH transmission opportunity ends in the first time domain resource, and / or,

[0478] The PUSCH transmission opportunity spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or,

[0479] The PUSCH transmission opportunity is nominally repeated and the specific actual repetition of the nominally repeated occurs in the first time-domain resource, and / or,

[0480] The PUSCH transmission opportunity is nominally repeated and the specific actual repetition of the nominally repeated event originates in the first time-domain resource, and / or,

[0481] The PUSCH transmission opportunity is a nominal repetition and the specific actual repetition of the nominal repetition ends in the first time domain resource, and / or,

[0482] The PUSCH transmission opportunity is nominally repeated and the specific actual repetition of the nominally repeated event spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or,

[0483] The specific symbol associated with the PUSCH transmission opportunity is the first time-domain resource.

[0484] 6. The method according to Appendix 2, wherein the PUSCH transmission opportunity is associated with the second time-domain resource (and not with the first time-domain resource), includes:

[0485] The PUSCH transmission opportunity is in the second time domain resource, and / or,

[0486] The PUSCH transmission opportunity originates in the second time-domain resource, and / or,

[0487] The PUSCH transmission opportunity ends in the second time domain resource, and / or the PUSCH transmission opportunity spans both the first and second time domain resources (or overlaps with both the first and second time domain resources), and / or,

[0488] The PUSCH transmission opportunity is a nominal repetition and a specific actual repetition of the nominal repetition (e.g., the first / last actual repetition) is in the second time-domain resource, and / or,

[0489] The PUSCH transmission opportunity is a nominal repetition, and a specific actual repetition of the nominal repetition originates in the second time-domain resource, and / or,

[0490] The PUSCH transmission opportunity is a nominal repetition and the specific actual repetition of the nominal repetition ends in the second time-domain resource, and / or,

[0491] The PUSCH transmission opportunity is nominally repeated and the specific actual repetition of the nominally repeated event spans the first time domain resource and the second time domain resource (or overlaps with both the first time domain resource and the second time domain resource), and / or,

[0492] The specific symbol (e.g., the first / last symbol) of the PUSCH transmission opportunity is associated with the second time-domain resource.

[0493] 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 PUSCH transmission method as described in Appendix 1.

[0494] 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 PUSCH receiving method as described in any one of Appendices 2 to 6.

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

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

Claims

1. A PUSCH transmitting device, comprising: The processor determines the transmit power for the PUSCH; as well as A transmitter that sends the PUSCH; The transmission power of the PUSCH is related to the time-domain resources associated with the PUSCH transmission opportunity, which include first time-domain resources and / or second time-domain resources.

2. The apparatus of claim 1, wherein, The transmission power for the PUSCH includes the transmission power during the PUSCH transmission opportunity; Determining the transmission power for PUSCH includes: the processor determining the transmission power during the PUSCH transmission opportunity.

3. The apparatus of claim 1, wherein, The PUSCH includes one or more PUSCH transmission opportunities, and the transmission power in each PUSCH transmission opportunity is determined separately.

4. The apparatus of claim 1, wherein, The processor determines the transmission power in the PUSCH transmission opportunity based on at least one of the following, wherein one or more of the at least one are related to the time-domain resources associated with the PUSCH transmission opportunity: Maximum output power; Target power; Subcarrier spacing; The number of resource blocks for the PUSCH transmission opportunity; Path loss compensation factor; Path loss; First power offset; PUSCH power control adjustment status; Second power offset.

5. The apparatus of claim 4, wherein, For a PUSCH transmission opportunity associated with a first time domain resource, the maximum output power is a first maximum output power, and / or, for a PUSCH transmission opportunity associated with a second time domain resource, the maximum output power is a second maximum output power; Wherein, the second maximum output power is determined according to a parameter not used to determine the first maximum output power, and / or, the first maximum output power is determined according to a parameter not used to determine the second maximum output power.

6. The apparatus of claim 4, wherein, The target power includes the nominal target power, or the sum of the nominal target power and the UE target power.

7. The apparatus according to claim 6, wherein, The nominal target power includes the leader target received power, or the sum of the leader target received power and the power offset; the leader target received power is the first leader target received power, the second leader target received power, or the third leader target received power, and / or the power offset is the third power offset, the fourth power offset, or the fifth power offset, or equal to 0.

8. The apparatus according to claim 7, wherein, For a cell configured with a first RO or a second RO, the preamble target received power is the first preamble target received power, the second preamble target received power, or the third preamble target received power, and / or... For cells that are neither configured with the first RO nor with the second RO, the preamble target received power is either the first preamble target received power or the third preamble target received power, and / or... For a cell configured with the first RO or the second RO, if the second preamble target receive power is not configured, the preamble target receive power is the first preamble target receive power or the third preamble target receive power.

9. The apparatus according to claim 7, wherein, For a cell configured with a first RO, the second preamble target received power includes the preamble target received power configured for the first RO and / or the preamble target received power configured by the first parameter, and / or... For a cell configured with a second RO, the second preamble target received power includes the preamble target received power configured for the second RO and / or the preamble target received power configured by the second parameter.

10. The apparatus of claim 7, wherein, For cells that have been configured with a first RO or a second RO: For a PUSCH transmission opportunity associated with the first time-domain resource, the preamble target receive power is a first preamble target receive power; for a PUSCH transmission opportunity associated with the second time-domain resource, the preamble target receive power is a second preamble target receive power; and / or For a PUSCH transmission opportunity associated with the first time-domain resource, the preamble target receive power is the second preamble target receive power; for a PUSCH transmission opportunity associated with the second time-domain resource, the preamble target receive power is the first preamble target receive power; and / or, When the corresponding preamble is transmitted using the third RO, the target received power of the preamble is the first target received power; when the corresponding preamble is transmitted using the first RO or the second RO, the target received power of the preamble is the second target received power. And / or, When the corresponding preamble is transmitted using a third RO, the preamble target received power is the first preamble target received power; when the corresponding preamble is transmitted using either the first RO or the second RO, for a PUSCH transmission opportunity associated with the first time domain resource, the preamble target received power is the first preamble target received power; for a PUSCH transmission opportunity associated with the second time domain resource, the preamble target received power is the second preamble target received power; and / or, When the corresponding preamble is transmitted using a first RO or a second RO, the target receive power of the preamble is the second target receive power; when the corresponding preamble is transmitted using a third RO, for a PUSCH transmission opportunity associated with a first time domain resource, the target receive power of the preamble is the first target receive power; for a PUSCH transmission opportunity associated with a second time domain resource, the target receive power of the preamble is the second target receive power; and / or, When the received power of the first frontier target is greater than or less than, or not greater than, or not less than, or equal to the received power of the second frontier target, the received power of the frontier target is the received power of the first frontier target; and / or, when the received power of the second frontier target is greater than or less than, or not greater than, or not less than, or equal to the received power of the first frontier target, the received power of the frontier target is the received power of the second frontier target; and / or, When the third RO is preferentially used to transmit the preamble, the preamble target received power is the first preamble target received power; when the first RO or the second RO is preferentially used to transmit the preamble, the preamble target received power is the second preamble target received power; and / or, The received power of the leading target is the received power of the first leading target; and / or, The received power of the leading target is the received power of the second leading target.

11. The apparatus according to claim 7, wherein, When the third power offset and the fourth power offset are provided, the power offset is either the third power offset or the fourth power offset, and / or, When the third power offset is provided, the power offset is the third power offset, and / or, If the third power offset and / or the fourth power offset are not provided, the power offset is equal to 0.

12. The apparatus of claim 11, wherein, With the third power offset and the fourth power offset provided: For a PUSCH transmission opportunity associated with the first time-domain resource, the power offset is the third power offset, and / or, For a PUSCH transmission opportunity associated with the second time-domain resource, the power offset is the fourth power offset.

13. The apparatus according to claim 4, wherein, For a PUSCH transmission opportunity associated with the first time-domain resource, the number of RBs for the PUSCH transmission opportunity includes the number of allocated valid RBs or the number of allocated RBs, and / or, For a PUSCH transmission opportunity associated with the second time-domain resource, the number of RBs for the PUSCH transmission opportunity includes the number of allocated RBs.

14. The apparatus according to claim 4, wherein, For a PUSCH transmission opportunity associated with the first time-domain resource, the transmission power is not determined based on / without using the second power offset, and / or, For a PUSCH transmission opportunity associated with the second time-domain resource, the transmission power is determined based on / using the second power offset.

15. The apparatus of claim 1, wherein, The PUSCH transmission opportunity is associated with the first time-domain resource, including: The PUSCH transmission opportunity is in the first time domain resource, and / or, the PUSCH transmission opportunity begins in the first time domain resource, and / or, the PUSCH transmission opportunity ends in the first time domain resource, and / or, the PUSCH transmission opportunity spans the first time domain resource and the second time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat is in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat begins in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat ends in the first time domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and the specific actual repeat of the nominal repeat spans the first time domain resource and the second time domain resource, and / or, the specific symbol of the PUSCH transmission opportunity is associated with the first time domain resource.

16. The apparatus of claim 1, wherein, The PUSCH transmission opportunity is associated with the second time-domain resource, including: The PUSCH transmission opportunity is in the second time-domain resource, and / or, the PUSCH transmission opportunity begins in the second time-domain resource, and / or, the PUSCH transmission opportunity ends in the second time-domain resource, and / or, the PUSCH transmission opportunity spans the first time-domain resource and the second time-domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and a specific actual repeat of the nominal repeat is in the second time-domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and a specific actual repeat of the nominal repeat begins in the second time-domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and a specific actual repeat of the nominal repeat ends in the second time-domain resource, and / or, the PUSCH transmission opportunity is a nominal repeat and a specific actual repeat of the nominal repeat spans the first time-domain resource and the second time-domain resource, and / or, a specific symbol of the PUSCH transmission opportunity is associated with the second time-domain resource.

17. The apparatus according to claim 1, wherein, The association of a specific symbol of a PUSCH transmission opportunity with the first time-domain resource includes: the specific symbol of the PUSCH transmission opportunity being the first time-domain resource or being in the first time-domain resource, and / or, The specific symbol of the PUSCH transmission opportunity is associated with the second time-domain resource, including: the specific symbol of the PUSCH transmission opportunity is the second time-domain resource or is in the first time-domain resource.

18. The apparatus of claim 1, wherein, For a PUSCH with a second repetition type, the PUSCH transmission opportunity is either a nominal repetition or a real repetition.

19. A PUSCH receiving device, comprising: The receiver receives PUSCH; The transmission power of the PUSCH is related to the time-domain resources associated with the PUSCH transmission opportunity, which include a first time-domain resource and / or a second time-domain resource.

20. A communication system, comprising: A terminal device that determines the transmission power for the PUSCH; and transmits the PUSCH; Network device that receives the PUSCH; The transmission power of the PUSCH is related to the time-domain resources associated with the PUSCH transmission opportunity, which include a first time-domain resource and / or a second time-domain resource.

Images