Communication methods, devices, and systems

Abstract

This application relates to the field of wireless communications, and more specifically to full-duplex scenarios in wireless communication systems, and provides a communication method, apparatus, and system for better implementing power control when terminal devices perform uplink transmission in a scenario in order to ensure the performance of uplink transmission. The method may include: receiving first information, the first information indicating a first open-loop power control parameter and a second open-loop power control parameter; determining a first power and a second power based on the first information, wherein the first open-loop power control parameter used to determine the first power is different from the second open-loop power control parameter used to determine the second power, the first power is the transmission power of a first push, the second power is the transmission power of a second push, the symbol occupied by the first push is an SBFD symbol, and the symbol occupied by the second push is a non-SBFD symbol; and transmitting the first push over a first BWP using the first power and transmitting the second push over a first BWP using the second power.

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202310541448.3, titled "COMMUNICATION METHOD, APPARATUS, AND SYSTEM," filed with the State Intellectual Property Administration of China on 14 May 2023, which is incorporated herein by reference in its entirety.

[0002] Embodiments of this application relate to the field of communications, and more particularly to communications methods, apparatus, and systems. [Background technology]

[0003] In wireless communication systems, time division duplexing (TDD) is the primary communication mode. However, in TDD systems, most of the time resources are occupied by downlink (DL), resulting in a coverage imbalance between DL and uplink (UL). TDD systems have worse uplink coverage and higher uplink latency than frequency division duplexing (FDD) systems. To address the uplink coverage and latency issues in TDD systems, subband full duplex (SBFD) has been proposed. In the SBFD scheme, transmission and reception can occur simultaneously on a single SBFD symbol. This leads to interference between uplink and downlink, with SBFD symbols exhibiting greater interference intensity than non-SBFD symbols. Thus, uplink transmissions performed by terminal devices on these symbols are affected. Therefore, how to implement better power control to ensure the performance of uplink transmissions performed by terminal devices on the two types of symbols is a problem that needs to be solved. [Overview of the project]

[0004] This application provides a communication method, apparatus, and system for better implementing power control when terminal devices perform uplink transmission in an SBFD scenario in order to ensure the performance of uplink transmission. [Means for solving the problem]

[0005] According to a first embodiment, a communication method is provided. The method may be performed by a terminal device or by a component of the terminal device (e.g., a chip or circuit). This is not limited to the present application. For the sake of clarity, an example in which the method is performed by a terminal device is used below for illustrative purposes.

[0006] The method is a step of receiving first information, wherein the first information indicates a first open-loop power control parameter and a second open-loop power control parameter, and a step of determining a first power and a second power based on the first information, wherein the first open-loop power control parameter used to determine the first power is different from the second open-loop power control parameter used to determine the second power, the first power is the transmission power of a first physical uplink shared channel PUSCH, the second power is the transmission power of a second PUSCH, the symbol occupied by the first PUSCH is a subband full-duplex SBFD symbol, and the second PUSCH The steps include: the symbol occupied by the CH is a non-SBFD symbol; the first open-loop power control parameter includes at least one of a first cell-specific target received power parameter, a first terminal device-specific target received power parameter, or a first path loss compensation coefficient; and the second open-loop power control parameter includes at least one of a second cell-specific target received power parameter, a second terminal device-specific target received power parameter, or a second path loss compensation coefficient; and transmitting a first PUSCH with the first power at a first bandwidth portion BWP; and transmitting a second PUSCH with the second power at a first bandwidth portion BWP.

[0007] According to the above solution, when performing a transmission, the terminal device can select different open-loop power control parameters for SBFD symbols and non-SBFD symbols under different interference conditions to determine the transmission power of the uplink transmission on the two types of symbols, thereby ensuring the performance of the uplink transmission on the two types of symbols.

[0008] In one possible design, the first PUSCH and the second PUSCH are different parts of the same PUSCH transmission, the first PUSCH and the second PUSCH are PUSCH transmissions scheduled by different uplink scheduling grants, or the first PUSCH and the second PUSCH are different PUSCH transmissions within an iterative PUSCH transmission, or PUSCH transmissions in different slots within a PUSCH transmission spanning multiple slots, or different PUSCH transmissions within multiple PUSCH transmissions scheduled by the same uplink scheduling grant.

[0009] Different power control parameters may be used to ensure the transmission performance of terminal devices over two types of symbols, regardless of whether the PUSCH is scheduled by the same uplink grant and whether repetitive transmissions are performed over the PUSCH.

[0010] In a possible design, the first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, the first cell-specific target received power parameter includes at least one of the first preamble target received power parameter, the first message 3 target received power offset parameter, or the first message A target received power offset parameter, the second cell-specific target received power parameter includes at least one of the second preamble target received power parameter, the second message 3 target received power offset parameter, or the second message A target received power offset parameter, and the first cell-specific target received power parameter and the second cell-specific target received power parameter are subject to the following conditions, i.e., The first preamble target received power parameter is different from the second preamble target received power parameter. The first message 3 target received power offset parameter is different from the second message 3 target received power offset parameter, and The target received power offset parameter for the first message A is different from the target received power offset parameter for the second message A. It satisfies at least one of the following conditions.

[0011] According to the solution described above, for PUSCH in a random access procedure, at least one of the three parameters mentioned above is different, thereby allowing the terminal device to use different transmission powers on the two types of symbols in order to better adapt to interference on the two types of symbols.

[0012] In a possible design, the first and second PUSCHs are configured grant PUSCHs or dynamically scheduled PUSCHs, the first cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol, the second cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol, and the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol is different from the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol.

[0013] According to the solution described above, the cell-specific target received power parameters are set differently for configured grant pushers or dynamically scheduled pushers, and as a result, terminal devices can use different transmission powers on the two types of symbols to better adapt to interference on the two types of symbols.

[0014] In a possible design, the first and second pushes are random access message 3 pushes or random access message A pushes, the first terminal device-specific target received power parameter is greater than 0, and the second terminal device-specific target received power parameter is 0.

[0015] According to the above solution, terminal devices adapt better to interference on SBFD symbols and use high power values ​​on SBFD symbols to ensure the transmission performance of terminal devices on SBFD symbols.

[0016] In a possible design, the first and second pushes are scheduled pushes using the first downlink control information DCI, the first DCI includes an open-loop power control parameter set indicator field, the first information indicates the first open-loop power control parameters and the second open-loop power control parameters, the first information indicates the first open-loop power control parameter set and the second open-loop power control parameter set, and the first open-loop power control parameters and the second open-loop power control parameters belong to the first open-loop power control parameter set and the second open-loop power control parameter set. The open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set.

[0017] In a possible design, the first and second pushes are scheduled pushes using first downlink control information DCI, the first DCI including an open-loop power control parameter set indicator field, the first information including a first open-loop power control parameter set and a second open-loop power control parameter set, wherein the open-loop power control parameter set indicator field indicates that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0018] According to the solution described above, the terminal device can dynamically acquire power control parameters corresponding to two types of symbols, and only one instruction field is used within the DCI, resulting in reduced signaling overhead.

[0019] In a possible design, the first and second pushes are scheduled pushes using the first downlink control information DCI, the first DCI includes an open-loop power control parameter set indicator field, the first information indicates the first open-loop power control parameters and the second open-loop power control parameters, the first information indicates the first open-loop power control parameter set and the second open-loop power control parameter set, and the first open-loop power control parameters and the second open-loop power control parameters belong to the first open-loop power control parameter set and the second open-loop power control parameter set. The open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set.

[0020] In a possible design, the first PUSCH and the second PUSCH are PUSCH scheduled using the first DCI, the first DCI including an open-loop power control parameter set indicator field and a first indicator field, the first information including the first open-loop power control parameter set and the second open-loop power control parameter set, the open-loop power control parameter set indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the first indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, and the first indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0021] The two instruction fields provide more flexible indication of power control parameters corresponding to two types of symbols for the terminal device, and as a result, the terminal device performs power control.

[0022] In a possible design, the first and second pushes are pushes scheduled using a first downlink control information DCI, the first DCI including a first sounding reference signal resource indicator SRI indicator field and a second SRI indicator field, the first terminal device-specific target received power parameter is determined based on the first SRI indicator field and a first mapping relationship, the second terminal device-specific target received power parameter is determined based on the second SRI indicator field and a second mapping relationship, the first mapping relationship is a mapping relationship between the value of the first SRI indicator field and a candidate value for the first terminal device-specific target received power parameter, and the second mapping relationship is a mapping relationship between the value of the second SRI indicator field and a candidate value for the second terminal device-specific target received power parameter.

[0023] The two existing instruction fields provide more flexible indication of power control parameters corresponding to two types of symbols for terminal devices, resulting in the terminal device performing power control and reducing signaling overhead.

[0024] In a possible design, the first power control adjustment state parameter for determining the first power is different from the second power control adjustment state parameter for determining the second power.

[0025] The power control adjustment state parameters are set differently, and as a result, the terminal device can use different transmission powers on the two types of symbols to better adapt to interference on the two types of symbols.

[0026] In possible designs, the first and second power control adjustment state parameters are either predefined in the protocol, indicated by radio resource control (RRC), indicated by dynamic signaling, or indicated by an SRI instruction field within the DCI.

[0027] In a possible design, a second DCI is received, which includes a first transmission power control TPC command and a second TPC command, where the first TPC command indicates a first power control adjustment state parameter and the second TPC command indicates a second power control adjustment state parameter.

[0028] The two instruction fields flexibly indicate power control parameters corresponding to two types of symbols for the terminal device, and as a result, the terminal device performs power control.

[0029] In a possible design, the first PUSCH and the second PUSCH are configured grant PUSCHs or dynamically scheduled PUSCHs, and the first information includes the first terminal device-specific target received power parameters and the second terminal device-specific target received power parameters.

[0030] Different power control parameters are configured for the two types of symbols, and as a result, the terminal device uses different transmission powers on the two types of symbols to better adapt to interference on the two types of symbols.

[0031] According to a second aspect, a communication method is provided. The method may be performed by a network device or by a component of a network device (e.g., a chip or circuit). This is not limited to the present application. For the sake of clarity, an example in which the method is performed by a network device is used below for illustrative purposes.

[0032] The method is a step of transmitting first information, the first information indicating a first open-loop power control parameter and a second open-loop power control parameter, wherein the first open-loop power control parameter used to determine the first power is different from the second open-loop power control parameter used to determine the second power, the first power is the transmission power of a first physical uplink shared channel PUSCH, the second power is the transmission power of a second PUSCH, the symbol occupied by the first PUSCH is a subband full-duplex SBFD symbol, and the symbol occupied by the second PUSCH is The occupied symbol is a non-SBFD symbol, and the first open-loop power control parameter includes at least one of a first cell-specific target received power parameter, a first terminal device-specific target received power parameter, or a first path loss compensation coefficient, and the second open-loop power control parameter includes at least one of a second cell-specific target received power parameter, a second terminal device-specific target received power parameter, or a second path loss compensation coefficient, and the steps of receiving a first PUSCH at a first BWP and receiving a second PUSCH at a first BWP.

[0033] According to the above solution, when performing a transmission, the terminal device can select different open-loop power control parameters for SBFD symbols and non-SBFD symbols under different interference conditions to determine the transmission power of the uplink transmission on the two types of symbols, thereby ensuring the performance of the uplink transmission on the two types of symbols.

[0034] In one possible design, the first PUSCH and the second PUSCH are different parts of the same PUSCH transmission, the first PUSCH and the second PUSCH are PUSCH transmissions scheduled by different uplink scheduling grants, or the first PUSCH and the second PUSCH are different PUSCH transmissions within an iterative PUSCH transmission, or PUSCH transmissions in different slots within a PUSCH transmission spanning multiple slots, or different PUSCH transmissions within multiple PUSCH transmissions scheduled by the same uplink scheduling grant.

[0035] Different power control parameters may be used to ensure the transmission performance of terminal devices over two types of symbols, regardless of whether the PUSCH is scheduled by the same uplink grant and whether repetitive transmissions are performed over the PUSCH.

[0036] In a possible design, the first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, the first cell-specific target received power parameter includes at least one of the first preamble target received power parameter, the first message 3 target received power offset parameter, or the first message A target received power offset parameter, the second cell-specific target received power parameter includes at least one of the second preamble target received power parameter, the second message 3 target received power offset parameter, or the second message A target received power offset parameter, and the first cell-specific target received power parameter and the second cell-specific target received power parameter are subject to the following conditions, i.e., The first preamble target received power parameter is different from the second preamble target received power parameter. The first message 3 target received power offset parameter is different from the second message 3 target received power offset parameter, and The target received power offset parameter for the first message A is different from the target received power offset parameter for the second message A. It satisfies at least one of the following conditions.

[0037] According to the solution described above, for PUSCH in a random access procedure, at least one of the three parameters mentioned above is different, thereby allowing the terminal device to use different transmission powers on the two types of symbols in order to better adapt to interference on the two types of symbols.

[0038] In a possible design, the first and second PUSCHs are configured grant PUSCHs or dynamically scheduled PUSCHs, the first cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol, the second cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol, and the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol is different from the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol.

[0039] According to the solution described above, the cell-specific target received power parameters are set differently for configured grant pushers or dynamically scheduled pushers, and as a result, terminal devices can use different transmission powers on the two types of symbols to better adapt to interference on the two types of symbols.

[0040] In a possible design, the first and second pushes are random access message 3 pushes or random access message A pushes, the first terminal device-specific target received power parameter is greater than 0, and the second terminal device-specific target received power parameter is 0.

[0041] According to the above solution, terminal devices adapt better to interference on SBFD symbols and use high power values ​​on SBFD symbols to ensure the transmission performance of terminal devices on SBFD symbols.

[0042] In a possible design, the first and second pushes are scheduled pushes using the first downlink control information DCI, the first DCI includes an open-loop power control parameter set indicator field, the first information indicates the first open-loop power control parameters and the second open-loop power control parameters, the first information indicates the first open-loop power control parameter set and the second open-loop power control parameter set, and the first open-loop power control parameters and the second open-loop power control parameters belong to the first open-loop power control parameter set and the second open-loop power control parameter set. The open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set.

[0043] In a possible design, the first and second pushes are scheduled pushes using first downlink control information DCI, the first DCI including an open-loop power control parameter set indicator field, the first information including a first open-loop power control parameter set and a second open-loop power control parameter set, wherein the open-loop power control parameter set indicator field indicates that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0044] According to the solution described above, the terminal device can dynamically acquire power control parameters corresponding to two types of symbols, and only one instruction field is used within the DCI, resulting in reduced signaling overhead.

[0045] In a possible design, the first and second pushes are scheduled pushes using the first downlink control information DCI, the first DCI includes an open-loop power control parameter set indicator field, the first information indicates the first open-loop power control parameters and the second open-loop power control parameters, the first information indicates the first open-loop power control parameter set and the second open-loop power control parameter set, and the first open-loop power control parameters and the second open-loop power control parameters belong to the first open-loop power control parameter set and the second open-loop power control parameter set. The open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, and the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set.

[0046] In a possible design, the first PUSCH and the second PUSCH are PUSCH scheduled using the first DCI, the first DCI including an open-loop power control parameter set indicator field and a first indicator field, the first information including the first open-loop power control parameter set and the second open-loop power control parameter set, the open-loop power control parameter set indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the first indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, and the first indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0047] The two instruction fields provide more flexible indication of power control parameters corresponding to two types of symbols for the terminal device, and as a result, the terminal device performs power control.

[0048] In a possible design, the first and second pushes are pushes scheduled using the first downlink control information DCI, the first DCI including a first sounding reference signal resource indicator SRI indicator field and a second SRI indicator field, the first SRI indicator field and first mapping relationship indicating a first terminal device-specific target received power parameter, the second SRI indicator field and second mapping relationship indicating a second terminal device-specific target received power parameter, the first mapping relationship being a mapping relationship between the value of the first SRI indicator field and a candidate value for the first terminal device-specific target received power parameter, and the second mapping relationship being a mapping relationship between the value of the second SRI indicator field and a candidate value for the second terminal device-specific target received power parameter.

[0049] The two existing instruction fields provide more flexible indication of power control parameters corresponding to two types of symbols for terminal devices, resulting in the terminal device performing power control and reducing signaling overhead.

[0050] In a possible design, the first power control adjustment state parameter for determining the first power is different from the second power control adjustment state parameter for determining the second power.

[0051] The power control adjustment state parameters are set differently, and as a result, the terminal device can use different transmission powers on the two types of symbols to better adapt to interference on the two types of symbols.

[0052] In possible designs, the first and second power control adjustment state parameters are either predefined in the protocol, indicated by radio resource control (RRC), indicated by dynamic signaling, or indicated by an SRI instruction field within the DCI.

[0053] In a possible design, a second DCI is transmitted, which includes a first transmission power control TPC command and a second TPC command, where the first TPC command indicates a first power control adjustment state parameter and the second TPC command indicates a second power control adjustment state parameter.

[0054] The two instruction fields flexibly indicate power control parameters corresponding to two types of symbols for the terminal device, and as a result, the terminal device performs power control.

[0055] In a possible design, the first PUSCH and the second PUSCH are configured grant PUSCHs or dynamically scheduled PUSCHs, and the first information includes the first terminal device-specific target received power parameters and the second terminal device-specific target received power parameters.

[0056] Different power control parameters are configured for the two types of symbols, and as a result, the terminal device uses different transmission powers on the two types of symbols to better adapt to interference on the two types of symbols.

[0057] Accordingly, this application further provides a communication device. The device can implement a communication method according to any one of the embodiments described above. For example, the device may be a terminal device or a network device, or another device capable of implementing the communication method described above. The device can implement the method described above by software, hardware, or hardware running the corresponding software.

[0058] In possible designs, the device may include a processor. The processor is configured to support the device in performing the corresponding function in any of the embodiments described above. In possible designs, the device may further include memory. The memory is configured to be coupled to the processor and stores the program instructions and data required by the device. In possible designs, the device may further include a communication interface configured to support communication between the device and another device. The communication interface may be a transceiver or a transceiver circuit.

[0059] In another aspect, one embodiment of the present application provides a communication system. The system includes a communication device according to the above-described embodiment.

[0060] According to yet another aspect of this application, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions. When the instructions are executed on a computer, the computer becomes capable of performing the method according to the above-described aspect.

[0061] According to yet another aspect of this application, a computer program product including instructions is provided. When the computer program product is executed on a computer, the computer becomes capable of performing the method according to the above-described aspect.

[0062] This application further provides a chip system, which includes a processor configured to implement the method in any one of the embodiments described above. In possible designs, the chip system may further include memory configured to implement the method in any one of the embodiments described above.

[0063] Any device, computer storage medium, computer program product, chip system, or communication system provided above is configured to perform the corresponding method provided above. Therefore, for the beneficial effects that can be achieved by the device, computer storage medium, computer program product, chip system, or communication system, please refer to the beneficial effects of the corresponding solution in the corresponding method provided above. Further details are not provided here. [Brief explanation of the drawing]

[0064] [Figure 1] This is a diagram of a network architecture according to one embodiment of the present application. [Figure 2] This is a diagram of a TDD communication system according to one embodiment of the present application. [Figure 3] This is a diagram of an SBFD communication system according to one embodiment of the present application. [Figure 4] This is an interaction diagram of a communication method according to one embodiment of this application. [Figure 5] This is a diagram of a communication device according to one embodiment of the present application. [Figure 6] This is a diagram of another communication device according to one embodiment of the present application. [Figure 7] This is a diagram of yet another communication device according to one embodiment of the present application. [Figure 8] This is a diagram of a communication system according to one embodiment of the present application. [Modes for carrying out the invention]

[0065] The technical solution of this application will be described below with reference to the attached drawings.

[0066] Figure 1 is a diagram of a possible and non-limiting system. As shown in Figure 1, the communication system 1000 includes a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one RAN node (e.g., 110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (e.g., 120a to 120j in Figure 1, collectively referred to as 120). The RAN 100 may further include other RAN nodes, e.g., wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The terminal 120 is connected to the RAN node 110 wirelessly. The RAN node 110 is connected to the core network 200 wirelessly or wired. The core network devices in the core network 200 and the RAN nodes 110 in the RAN 100 may be different physical devices, or they may be the same physical device that integrates the core network logical functions and the wireless access network logical functions.

[0067] RAN 100 may be a cellular system associated with the 3rd generation partnership project (3GPP®), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). Alternatively, RAN 100 may be an open radio access network (open RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (Wi-Fi) system. Alternatively, RAN 100 may be a communication system that integrates two or more of the above systems.

[0068] Alternatively, RAN nodes 110 may be referred to as access network devices, RAN entities, access nodes, etc., and form part of a communication system to help terminals implement wireless access. Multiple RAN nodes 110 in the communication system 1000 may be of the same type of node or of different types of nodes. In some scenarios, the roles of RAN nodes 110 and terminals 120 are relative to each other. For example, network element 120i in Figure 1 may be a helicopter or unmanned aerial vehicle and may be configured as a mobile base station. For terminal 120j accessing RAN 100 through network element 120i, network element 120i is a base station. However, for base station 110a, network element 120i is a terminal. RAN nodes 110 and terminals 120 may be referred to as communication devices. For example, network elements 110a and 110b in Figure 1 may be understood as communication devices with base station functionality, and network elements 120a through 120j may be understood as communication devices with terminal functionality.

[0069] In possible scenarios, a RAN node may be a network device, base station, evolved NodeB (eNodeB), access point (AP), transmission reception point (TRP), next generation NodeB (gNB), next generation base station in a 6th generation (6G) mobile communication system, base station in a future mobile communication system, or access node in a Wi-Fi system. A RAN node may also be a macro base station (e.g., 110a in Figure 1), a micro base station or indoor station (e.g., 110b in Figure 1), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node may also be a server, wearable device, vehicle, or in-vehicle device. For example, an access network device in vehicle-to-everything (V2X) technology may be a roadside unit (RSU).

[0070] In another possible scenario, multiple RAN nodes cooperate to assist terminals in implementing radio access, with different RAN nodes implementing several base station functions separately. For example, RAN nodes could be a central unit (CU), a distributed unit (DU), a CU control plane (CP), a CU user plane (UP), a radio unit (RU), etc. CUs and DUs may be located separately or may be included in the same network element, for example, a baseband unit (BBU). RUs may be included in radio frequency devices or radio frequency units, for example, a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0071] In different systems, CU (or CU-CP and CU-UP), DU, or RU may also have different names, but their meanings will be understood by those skilled in the art. For example, in the ORAN system, CU may be referred to as O-CU (Open CU), DU as O-DU, CU-CP as O-CU-CP, CU-UP as O-CU-UP, and RU as O-RU. For ease of explanation, CU, CU-CP, CU-UP, DU, and RU are used as illustrative examples in this application. Any one of CU (or CU-CP or CU-UP), DU, and RU in this application may be implemented using a software module, a hardware module, or a combination of a software module and a hardware module.

[0072] Terminals are sometimes referred to as terminal devices, user equipment (UE), mobile stations, or mobile terminals. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals may include mobile phones, tablet computers, computers with wireless receiver functionality, wearable devices, vehicles, unmanned aerial vehicles, helicopters, airplanes, ships, robots, robotic arms, and smart home devices. The device form of a terminal is not limited to the embodiments of this application.

[0073] Below, we first provide definitions of technical terms that may appear in embodiments of this application. The terms used in the implementations of this application are used solely to describe specific embodiments of this application and are not intended to limit this application.

[0074] 1.Full duplex In a TDD system, as shown in Figure 2, the majority of time resources are typically occupied for downlink (DL) transmission, with less time resources occupied for uplink (UL) transmission. The symbol direction can be configured as uplink, downlink, or flexible. The symbol direction is configured for the entire component carrier (CC). In a subband full duplex (SBFD) scheme, one CC is divided into multiple subbands, and the transmission directions of different subbands may differ, i.e., some subbands are uplink subbands and some are downlink subbands. In this case, the symbol directions of different subbands within one CC are different. A typical SBFD scheme is shown in Figure 3, where the intermediate subband is the uplink subband, and the upper and lower subbands are the downlink subbands. This increases the time resources used for UL transmission compared to TDD. In an SBFD scheme, transmission and reception can occur simultaneously on a single SBFD symbol. For example, as shown in Figure 3, a symbol containing UL and DL subbands is an SBFD symbol. A regular symbol where reception and transmission do not occur simultaneously may be a non-SBFD symbol. For example, as shown in Figure 3, a symbol that has only the UL subband is a non-SBFD symbol. Single frequency full duplex (SFFD) means that simultaneous reception and transmission on a single symbol can be implemented across the entire CC. In SBFD, different frequency domain resources (subbands) are used for the uplink and downlink. In SFFD, the same frequency domain resources are used for the uplink and downlink.

[0075] 2. Power control The terminal device determines the transmission power of the transmitted physical uplink shared channel (PUSCH) based on a partial path loss compensation mechanism. Specifically, when the terminal device transmits a PUSCH on the active uplink bandwidth part (BWP) b of the carrier f of serving cell c, using a parameter set configuration with index j and a PUSCH power control adjustment state with index l, the terminal device determines the PUSCH transmission power P in the PUSCH transmission opportunity i according to the following formula. PUSCH,b,f,c (i,j,q d Determine l).

number

[0076] In the above formula, P O_PUSCH,b,f,c (j) and α b,f,c (j) is usually referred to as the open-loop power control parameter and is generally configured semi-statically by the network device through signaling, such as radio resource control (RRC) signaling or a system information block (SIB). b,f,c (i,l) is typically referred to as a closed-loop power control parameter and is dynamically communicated by network devices via signaling, such as downlink control information (DCI).

[0077] The following provides a detailed explanation of the meaning of the parameters in the above formula.

[0078] P CMAX,f,c (i) is the maximum output power set for the terminal device with respect to the carrier f of the serving cell c in a push transmission opportunity i.

[0079] P O_PUSCH,b,f,c(j) is the PUSCH target reception power configured by the network device with the active uplink BWP b of the carrier f of the serving cell c, and the parameter is P O_NOMINAL,PUSCH,f,c (j) and P O_UE_PUSCH,b,f,c (j), where j ∈ {0, 1,..., J - 1}. Generally, P O_NOMINAL,PUSCH,f,c (j) is considered a cell-specific parameter, and P O_UE_PUSCH,b,f,c (j) is a terminal device-specific parameter.

[0080] Specifically, for PUSCH transmission or retransmission corresponding to the uplink grant (UL grant) carried in the random access response (RAR), that is, in the case of PUSCH carrying message 3 (message 3, Msg3) in the random access procedure, j = 0, P O_UE_PUSCH,b,f,c (0) = 0, and when the terminal device uses a Type-1 random access procedure to establish a dedicated RRC connection, P O_NOMINAL,PUSCH,f,c (0) = P O_PRE + Δ PREAMBLE,Msg3 , where P O_PRE is the preamble target reception power configured by the network device in the Type-1 random access procedure, and Δ PREAMBLE,Msg3 is the offset configured or predefined by the network device for the Msg3 target reception power relative to the preamble target reception power. When the terminal device uses a Type-2 random access procedure to establish a dedicated RRC connection, P O_NOMINAL_PUSCH,f,c (0) = P O_PRE + Δ MsgA_PUSCH [[ID=�0]]where P O_PRE is the message A (message A, MsgA) preamble target reception power configured by the network device in the Type-2 random access procedure, and Δ MsgA_PUSCHThis is the offset of the MsgA PUSCH target received power to the MsgA preamble target received power, and is configured by the network device or predefined. Message 3 may be understood as the first scheduling transmission in a random access procedure, and Message A may be understood as the preamble and load transmission in a two-step random access procedure.

[0081] For configured grant type PUSCH transmission or retransmission, j=1. Network devices signal through upper layer signaling p0-NominalWithoutGrant. O_NOMINAL,PUSCH,f,c (1) may be constructed. If no value is constructed, P O_NOMINAL,PUSCH,f,c (1) = P O_NOMINAL,PUSCH,f,c (0). P O_UE_PUSCH,b,f,c (1) is configured by network devices via signaling.

[0082] For other PUSCHs, for example, PUSCHs dynamically scheduled using DCI, j∈{2,…,J-1}=S J J is a positive integer greater than or equal to 2. O_NOMINAL,PUSCH,f,c The value of (j) is for all j∈S J Applicable to: Network devices receive P through upper-layer signaling p0-NominalWithGrant. O_NOMINAL,PUSCH,f,c (1) may be constructed. If no value is constructed, P O_NOMINAL,PUSCH,f,c (j) = P O_NOMINAL,PUSCH,f,c (0). P O_UE_PUSCH,b,f,c (j) For the active UL BWPb of carrier f of serving cell c, the network device configures the set P0-PUSCH-AlphaSet by P O_UE_PUSCH A set of values ​​may be constructed, one P O_UE_PUSCH Value and one α b,f,c The (j) value may be configured in each P0-PUSCH-AlphaSet.

[0083] Furthermore, network devices can enable terminal devices to P by using signaling notifications or predefined rules. O_UE_PUSCH This allows you to decide which of the values ​​to use.

[0084] Network devices use the sounding reference signal resource indicator (SRI) field within the DCI to communicate the P used by terminal devices. O_UE_PUSCH,b,f,c This indicates the value of (j). Specifically, a network device can configure a mapping between an SRI and a set of P0-PUSCH-AlphaSets via the upper-layer signaling sri-PUSCH-MappingToAddModList. The signaling sri-PUSCH-MappingToAddModList includes multiple SRI-PUSCH-PowerControls, one SRI-PUSCH-PowerControl may be associated with one P0-PUSCH-AlphaSet, and the index of one SRI-PUSCH-PowerControl corresponds to one value in the SRI field.

[0085] Therefore, if one DCI for scheduling PUSCH transmissions includes an SRI field, the terminal device may obtain a mapping relationship from the sri-PUSCH-PowerControlId in the upper-layer signaling SRI-PUSCH-PowerControl between a set of SRI field values ​​in the DCI and the P0-PUSCH-AlphaSetId values ​​corresponding to a set of P0-PUSCH-AlphaSet values, and then the terminal device may use the SRI values ​​to obtain the P0-PUSCH-AlphaSetId associated with or corresponding to the SRI values. O_UE_PUSCH,b,f,c (j) and α b,f,c You may also determine the value of (j).

[0086]

number

[0087] α b,f,c (j) is the path loss compensation coefficient, and α b,f,c (j) is generally P O_UE_PUSCH,b,f,c Used with (j). α b,f,c For the value of (j), P O_UE_PUSCH,b,f,c Please refer to the process for determining (j).

[0088] PL b,f,c (q d ) is index q d This is a downlink path loss estimate (dB) calculated by a terminal device using a reference signal (RS) having the following characteristics. In this specification, the reference signal may be a channel state information reference signal (CSI-RS) or a synchronization signal block (SSB) transmitted by a network device.

[0089] Δ TF,b,f,c (i) is a power offset determined based on different modulation and coding scheme (MCS) levels.

[0090] f b,f,c (i,l) is the power control adjustment state, which is determined through two approaches: absolute and cumulative.

[0091] Cumulative formula:

number

[0092] Absolute formula: f b,f,c (i,l)=δ PUSCH,b,f,c (i,l).

[0093] δ PUSCH,b,f,c This is a transmit power control (TPC) command delivered by a network device, and TPC commands may be delivered using DCI for scheduling PUSCH, or DCI for scrambling cyclic redundancy checks (CRC) using TPC-PUSCH-radio network temporary identifier (RNTI).

[0094] In the SBFD scenario, the open-loop or closed-loop power control parameters used for uplink channels or signals on SBFD symbols and on non-SBFD symbols are the same. As a result, the transmission power of uplink channels or signals on the two types of symbols is the same. However, crosslink interference is present in SBFD symbols but not in non-SBFD symbols, resulting in a higher interference intensity on SBFD symbols than on non-SBFD symbols. Consequently, the link quality on SBFD symbols is worse than that on non-SBFD symbols, and the performance of uplink channels or signals transmitted on SBFD symbols is inferior to that on non-SBFD symbols.

[0095] To solve the above-mentioned problems, one embodiment of the present application provides a communication method. Different power control parameters are used for transmission on SBFD symbols and transmission on non-SBFD symbols, so that a terminal device can use appropriate transmission power when performing uplink transmission on the two types of symbols, and the transmission performance of the transmission performed by the terminal device on the two types of symbols is consistent.

[0096] Figure 4 illustrates an example of a communication method according to one embodiment of the present application. The method may be performed by a terminal device and a network device, or by a chip in the terminal device and a chip in the network device. It should be understood that Figure 4 illustrates steps or operations in the communication method. However, these steps or operations are merely examples. In this embodiment of the present application, other operations or variations of the operations in Figure 4 may be performed, or appropriate substitutions may be made between steps.

[0097] S410: The terminal device receives the first piece of information from the network device.

[0098] Accordingly, the network device transmits the first piece of information to the terminal device.

[0099] The first piece of information shows the first open-loop power control parameter and the second open-loop power control parameter.

[0100] S420: The terminal device determines the first power and the second power based on the first information.

[0101] Accordingly, the network device determines the first information based on the terminal device's requirements for the first and second power levels.

[0102] The first power is the transmission power of the first pusher, and the second power is the transmission power of the second pusher. The symbols occupied by the first pusher are subband full-duplex SBFD symbols, and the symbols occupied by the second pusher are non-SBFD symbols, uplink symbols, or flexible symbols.

[0103] The parameters used to determine the first power and the second power are: The first open-loop power control parameter used to determine the first power is different from the second open-loop power control parameter used to determine the second power, and At least one of the following conditions is met: the first closed-loop power control parameter used to determine the first power is different from the second closed-loop power control parameter used to determine the second power.

[0104] It should be understood that the parameters used to determine the first power and the second power in this specification are different. In a possible understanding, the parameters used to determine the first power and the second power are configured independently, i.e., there are two parameters or two sets of parameters. The two parameters or two sets of parameters are set for two types of pushes, thereby allowing the network device to independently configure power control parameters for pushes of different symbols based on actual conditions. In this case, there is no restriction on whether the values ​​of the two sets of parameters are the same or different. In another possible understanding, the parameter values ​​for determining the first power and the second power are different. Due to different interferences on the two types of symbols, the network device sets different parameter values ​​to help set different transmission powers, and as a result, the final receiving performance is consistent.

[0105] In this application, the difference between two parameters can also be understood as a change in at least one sub-parameter included in the two parameters.

[0106] S430: The terminal device transmits a first PUSCH to the network device on the first BWP by using the first power supply, and transmits a second PUSCH to the network device on the first BWP by using the second power supply.

[0107] Accordingly, the network device receives the first PUSCH and the second PUSCH in the first BWP.

[0108] The relationship between the first PUSCH and the second PUSCH can take the following possible forms:

[0109] Method 1: The first PUSCH and the second PUSCH are different parts of the same PUSCH transmission. For example, in a time-domain resource of a single PUSCH transmission, some symbols are SBFD symbols, and the PUSCH on SBFD symbols is referred to as the first PUSCH, while other symbols are non-SBFD symbols, and the PUSCH on non-SBFD symbols is referred to as the second PUSCH.

[0110] Method 2: The first and second PUSCH transmissions are scheduled by different uplink scheduling grants. For example, the first and second PUSCHs are dynamically scheduled by using multiple independent DCIs. In another example, the first and second PUSCHs are scheduled by multiple independent configured grants. In yet another example, the first PUSCH is dynamically scheduled by using DCIs and the second PUSCH is scheduled by configured grants, or vice versa. The time-domain resource for the first PUSCH is an SBFD symbol, and the time-domain resource for the second PUSCH is a non-SBFD symbol.

[0111] Method 3: The first PUSCH and the second PUSCH are different transmissions within a PUSCH iterative transmission. Alternatively, the first PUSCH and the second PUSCH are PUSCH transmissions in different slots within a PUSCH transmission spanning multiple slots. For example, a PUSCH is configured or scheduled for multiple iterative transmissions. In this case, the first PUSCH is a PUSCH transmission that occupies SBFD symbols among the multiple iterative transmissions, and the second PUSCH is a PUSCH transmission that occupies non-SBFD symbols among the multiple iterative transmissions. In another example, a PUSCH is configured or scheduled for multiple iterative transmissions, and the multiple iterative transmissions are in different slots. In this case, the first PUSCH is a PUSCH transmission that occupies SBFD symbols among the multiple iterative transmissions, and the second PUSCH is a PUSCH transmission that occupies non-SBFD symbols among the multiple iterative transmissions. A PUSCH iterative transmission is either a Type A PUSCH iterative transmission or a Type B PUSCH iterative transmission.

[0112] Method 4: The first PUSCH and the second PUSCH are different PUSCH transmissions among multiple PUSCH transmissions scheduled by the same uplink scheduling grant. For example, the first PUSCH and the second PUSCH are multiple PUSCH transmissions scheduled by using one DCI. In another example, the first PUSCH and the second PUSCH are multiple PUSCH transmissions scheduled by one configured grant.

[0113] In possible implementations, the open-loop power control parameters include at least one of a cell-specific target received power parameter, a terminal device-specific target received power parameter, or a path loss compensation coefficient. For example, the first open-loop power control parameter includes at least one of a first cell-specific target received power parameter, a first terminal device-specific target received power parameter, or a first path loss compensation coefficient, and the second open-loop power control parameter includes at least one of a second cell-specific target received power parameter, a second terminal device-specific target received power parameter, or a second path loss compensation coefficient. There are several implementations for the parameters included in the open-loop power control parameters.

[0114] Implementation form 1: The open-loop power control parameters include a cell-specific target received power parameter. It should be understood that the open-loop power control parameters are not limited to including other parameters as used herein. For example, the cell-specific target received power parameter may be P O_NOMINAL,PUSCH,f,c (1), P O_NOMINAL,PUSCH,f,c (0), or P O_NOMINAL,PUSCH,f,c (j).j ∈ {0, 1, ..., J-1}, where J is a positive integer. In possible schemes, the first cell-specific target received power parameter for determining the first power is different from the second cell-specific target received power parameter for determining the second power. For example, P O_NOMINAL,PUSCH,f,c If different values ​​of (j) are used for the first PUSCH and the second PUSCH, then for the active UL BWPb of the carrier f of serving cell c, for the same j, P O_NOMINAL,PUSCH This means that different values ​​are used for PUSCH transmission on SBFD symbols and non-SBFD symbols.

[0115] Implementation form 2: Open-loop power control parameters include terminal device-specific target received power parameters. It should be understood that terminal device-specific target received power parameters indicate that the power parameters are terminal device-level parameters. It should also be understood that the parameters may be the same or different for different terminal devices within the same cell. For example, the terminal device-specific target received power parameter is P O_UE_PUSCH,b,f,c (j).j ∈ {0, 1, ..., J-1}, where J is a positive integer. In possible schemes, the target received power parameter specific to the first terminal device for determining the first power is different from the target received power parameter specific to the second terminal device for determining the second power. For example, P O_UE_PUSCH,b,f,c If different values ​​of (j) are used for the first PUSCH and the second PUSCH, then for the active UL BWPb of the carrier f of serving cell c, for the same j, P O_UE_PUSCH,b,f,c (j) means that different values ​​are used for PUSCH transmission on SBFD symbols and non-SBFD symbols.

[0116] Implementation form 3: Open-loop power control parameters include a path loss compensation coefficient. For example, the path loss compensation coefficient is α b,f,c (j).j ∈ {0, 1, ..., J-1}, where J is a positive integer. In possible schemes, the first path loss compensation coefficient for determining the first power is different from the path loss compensation coefficient for determining the second power. For example, α b,f,c If different values ​​of (j) are used for the first PUSCH and the second PUSCH, then for the active UL BWPb of the carrier f of serving cell c, for the same j, α b,f,c (j) means that different values ​​are used for PUSCH transmission on SBFD symbols and non-SBFD symbols.

[0117] It should be understood that the above-described implementation configurations can be combined with each other. For example, the open-loop power control parameters may include terminal device-specific target received power parameters and path loss compensation coefficients. The terminal device-specific target received power parameters and path loss compensation coefficients of the first PUSCH may differ from those of the second PUSCH, or one of the terminal device-specific target received power parameters and path loss compensation coefficients of the first PUSCH may differ from those of the second PUSCH. This is not limited to the present application.

[0118] Based on the scheduling type of PUSCH or the type of data being transported by PUSCH, there are several possible cases for PUSCH.

[0119] Case 1: The first and second PUSCH messages are random access message 3 PUSCH or random access message A PUSCH. Here, the PUSCH can be the initial transmission or a retransmission.

[0120] Case 2: The first PUSCH and the second PUSCH are configured grant PUSCHs.

[0121] Case 3: The first and second PUSCHs are PUSCHs other than those in the two implementation forms described above, for example, dynamically scheduled PUSCHs.

[0122] In the three cases described above, PUSCH may be transmitted first or retransmitted. This is not limited to the present application.

[0123] In scenarios where the open-loop power control parameters include cell-specific target received power parameters, multiple implementation forms may exist based on the three cases described above for PUSCH.

[0124] If the first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, the cell-specific target received power parameter may include at least one of the preamble target received power parameter, the message 3 target received power offset parameter, or the MsgA target received power offset parameter.

[0125] For example, the first cell-specific target received power parameter includes at least one of the first preamble target received power parameter, the first message 3 target received power offset parameter, or the first MsgA target received power offset parameter, and the second cell-specific target received power parameter includes at least one of the second preamble target received power parameter, the second message 3 target received power offset parameter, or the second MsgA target received power offset parameter. In another example, the preamble target received power parameter is P O_PRE In another example, the message 3 target received power offset parameter is Δ PREAMBLE,Msg3 In another example, the MsgA target received power offset parameter is Δ MsgA_PUSCH That is the case.

[0126] The fact that the target received power parameter specific to the first cell is different from the target received power parameter specific to the second cell is that the target received power parameter specific to the first cell and the target received power parameter specific to the second cell meet the following conditions, namely, The first preamble target received power parameter is different from the second preamble target received power parameter. The first message 3 target received power offset parameter is different from the second message 3 target received power offset parameter, and This may be understood as satisfying at least one of the following conditions: the first message A target received power offset parameter is different from the second message A target received power offset parameter.

[0127] Specifically, there are several possible implementation forms, as follows:

[0128] Implementation form 1: The message 3 target received power offset parameter or MsgA target received power offset parameter used in the first PUSCH and the second PUSCH are different. For example, Δ PREAMBLE,Msg3 or Δ MsgA_PUSCH The two different values ​​are configured by the network device or predefined and used for the first PUSCH and the second PUSCH, respectively. As another example, the existing Δ for PUSCH on non-SBFD symbols PREAMBLE,Msg3 , or Δ MsgA_PUSCH A new Δ is used for PUSCH on the SBFD symbol. PREAMBLE,Msg3 , or Δ MsgA_PUSCH Either a power parameter is introduced or the other way around. In this way, the network device configures two power parameters so that different powers are used for transmission on SBFD symbols and non-SBFD symbols. Also, for example, for a first push, the network device has Δ PREAMBLE,Msg3 or Δ MsgA_PUSCH Configure or predefine and, for the second PUSCH, Δ PREAMBLE,Msg3 or Δ MsgA_PUSCH Relative values ​​may be constructed, or vice versa. In this way, a network device can construct absolute values ​​and then relative values ​​to represent power parameters on different symbols.

[0129] For example, if a terminal device establishes a dedicated RRC connection using a Type 1 random access procedure, then for the second PUSCH, the second cell-specific target received power parameter P O_NOMINAL,PUSCH,f,c (0) = P O_PRE +Δ PREAMBLE,Msg3 for NonSBFD And for the first PUSCH, the target received power parameter P, which is specific to the first cell. O_NOMINAL,PUSCH,f,c (0) = P O_PRE +Δ PREAMBLE,Msg3 for SBFD And Δ PREAMBLE,Msg3 for NonSBFD Δ is the second message 3 target received power offset parameter, PREAMBLE,Msg3 for SBFDis the first message 3 target received power offset parameter.

[0130] In another example, when the terminal device establishes a dedicated RRC connection by using a type 2 random access procedure, for the second PUSCH, the second cell-specific target received power parameter is

Number

Number

Number

Number

[0131] Implementation form 2: The preamble target received power parameters used for the first PUSCH and the second PUSCH are different. For example, two different values of P O_PRE are configured by the network device or pre-defined, and are used for the first PUSCH and the second PUSCH respectively. In this way, the network device configures two power parameters so that the preamble target received powers for transmissions on SBFD symbols and non-SBFD symbols are different. In another example, the existing P O_PRE is used for the PUSCH on non-SBFD symbols, and a new P O_PRE is introduced for the PUSCH on SBFD symbols, or vice versa. In another example, P O_PRE may be configured by the network device or pre-defined for the first PUSCH, and P O_PREThe relative value is configured for the second PUSCH or vice versa. In this way, the network device can configure the absolute value and then configure the relative value to indicate the power parameters on different symbols. It should be noted that in Implementation Form 2, different preamble target reception power parameters may be implemented independently of this solution. In other words, for the same random access preamble, the target reception power parameter may be different for transmissions on SBFD symbols and non-SBFD symbols.

[0132] Furthermore, the above two implementation forms may alternatively be combined. For example, the preamble target reception power parameters used for the first PUSCH and the second PUSCH are different, and the message 3 target reception power offset parameters used for the first PUSCH and the second PUSCH are different. In this case, two sets of power parameters, or one set of absolute values and one set of relative values, may be configured by the network device or predefined to indicate a plurality of different parameters.

[0133] When the first PUSCH and the second PUSCH are the configured grant PUSCH, there are the following possible implementation forms. In this case, the first cell-specific target reception power parameter may be different from the second cell-specific target reception power parameter. For example, two different cell-specific target reception power parameters may be configured by the network device or predefined. In this case, the cell-specific target reception power parameter may be P O_NOMINAL,PUSCH,f,c (1). For example, when the network device configures the value of P O_NOMINAL,PUSCH,f,c (1) by upper layer signaling, two values may be configured respectively for the transmissions of the first PUSCH and the second PUSCH. As another example, the value of P O_NOMINAL,PUSCH,f,c (1) is determined based on P O_NOMINAL,PUSCH (0), and P O_NOMINAL,PUSCH (0) corresponds to P O_NOMINAL,PUSCH for the message 3 PUSCH or MsgA PUSCH. P O_NOMINAL,PUSCHFor the value of (0), see the scenario where the first and second PUSCHs are random access message 3 PUSCH or random access message A PUSCH. For example, the target received power parameter specific to the first cell is P O_NOMINAL,PUSCH,f,c for SBFD (1) = P O_NOMINAL,PUSCH,f,c for SBFD (0) and the target received power parameter specific to the second cell is P O_NOMINAL,PUSCH,f,c for NonSBFD (1) = P O_NOMINAL,PUSCH,f,c for NonSBFD (0). P O_NOMINAL,PUSCH,f,c for SBFD (0) is the target received power parameter specific to the first cell in a scenario where the first PUSCH is random access message 3 PUSCH or random access message A PUSCH, and P O_NOMINAL,PUSCH,f,c for NonSBFD (0) is the target received power parameter specific to the second cell in a scenario where the second PUSCH is random access message 3 PUSCH or random access message A PUSCH.

[0134] If the first and second PUSCHs are PUSCHs other than those described in the two implementation forms above, the following possible implementation forms exist. In this case, the cell-specific target received power parameter of the first cell may be different from that of the second cell-specific target received power parameter. For example, the two different cell-specific target received power parameters are configured or predefined by the network device. In this case, the cell-specific target received power parameter is P O_NOMINAL,PUSCH,f,c (j)j ∈ {0, 1, ..., J-1}, where J is a positive integer. For example, a network device is P signaled by upper-layer signaling. O_NOMINAL,PUSCH,f,c When constructing the value of (j), two values ​​may be constructed for the transmission of the first PUSCH and the second PUSCH, respectively. As another example, P O_NOMINAL,PUSCH,f,c The value of (j) is P O_NOMINAL,PUSCH (0) is determined based on P O_NOMINAL,PUSCH (0) P corresponds to message 3 PUSCH or MsgA PUSCH. O_NOMINAL,PUSCH P O_NOMINAL,PUSCHFor the value of (0), see the scenario where the first and second PUSCHs are random access message 3 PUSCH or random access message A PUSCH. For example, the target received power parameter specific to the first cell is P O_NOMINAL,PUSCH,f,c for SBFD (j) = P O_NOMINAL,PUSCH,f,c for SBFD (0) and the target received power parameter specific to the second cell is P O_NOMINAL,PUSCH,f,c for NonSBFD (j) = P O_NOMINAL,PUSCH,f,c for NonSBFD (0). P O_NOMINAL,PUSCH,f,c for SBFD (0) is the target received power parameter specific to the first cell in a scenario where the first PUSCH is random access message 3 PUSCH or random access message A PUSCH, and P O_NOMINAL,PUSCH,f,c for NonSBFD (0) is the target received power parameter specific to the second cell in a scenario where the second PUSCH is random access message 3 PUSCH or random access message A PUSCH.

[0135] In scenarios where the open-loop power control parameters include terminal device-specific target received power parameters, there can be multiple implementation forms based on the three cases described above for PUSCH.

[0136] If the first and second PUSCH messages are random access message 3 PUSCH or random access message A PUSCH, they are analyzed as follows. In this case, the target received power parameter specific to the first terminal device may be different from the target received power parameter specific to the second terminal device. For example, the target received power parameter specific to the first terminal device may be greater than 0, and the target received power parameter specific to the second terminal device may be 0. For example, in the case of a PUSCH on a non-SBFD symbol, P O_UE_PUSCH,b,f,c The value of (0) is 0. In the case of PUSCH on the SBFD symbol, P O_UE_PUSCH,b,f,c The value of (0) may be greater than 0, may be predefined, or may be communicated by a network device via signaling.

[0137] If the first and second PUSCHs are configured grant PUSCHs or dynamically scheduled PUSCHs, they are analyzed as follows. In this case, the first terminal device-specific target received power parameter may differ from the second terminal device-specific target received power parameter. The network device can configure two terminal device-specific target received power parameters for terminal devices for power control on two types of symbols. For example, the first information transmitted by the network device includes the first terminal device-specific target received power parameter and the second terminal device-specific target received power parameter. In another example, P configured by the network device O_UE_PUSCH,b,f,c The two values ​​in (1) are used for the first PUSCH and the second PUSCH, respectively. O_UE_PUSCH,b,f,c Please understand that the two values ​​in (1) are for a single transmission reception point (TRP) scenario. In a multi-TRP scenario, P O_UE_PUSCH,b,f,c The two values ​​in (1) may be configured independently for each TRP and are used for the first PUSCH and the second PUSCH within each TRP, respectively.

[0138] In addition, the power control parameters of the first and second pushers can be further specified by using DCI. Specifically, there are several implementation forms, as follows:

[0139] Implementation form 1: The first DCI includes an open-loop power control parameter set indicator field. The first information indicates or includes a first open-loop power control parameter set and a second open-loop power control parameter set. The first open-loop power control parameters and the second open-loop power control parameters belong to the first open-loop power control parameter set and the second open-loop power control parameter set. For example, the first open-loop power control parameters belong to the first open-loop power control parameter set, and the second open-loop power control parameters belong to the second open-loop power control parameter set. In another example, the first open-loop power control parameters belong to the second open-loop power control parameter set, and the second open-loop power control parameters belong to the first open-loop power control parameter set. The open-loop power control parameter set indicator field indicates a set of candidate values ​​for terminal device-specific target received power parameters. For example, the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the first terminal device is either the first open-loop power control parameter set or the second open-loop power control parameter set. In another example, the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the second terminal device is either the first open-loop power control parameter set or the second open-loop power control parameter set. In yet another example, when the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, then the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set. In yet another example, when the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, then the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set.For example, a network device configures a set of P0-PUSCH-AlphaSet and a set of P0-PUSCH-Set for terminal devices, and then, by using the open-loop power control parameter set instruction field in the first DCI, the scheduled PUSCH is in P0-PUSCH-AlphaSet or P0-PUSCH-Set. O_UE_PUSCH,b,f,cThis indicates whether to use a particular value. For example, if the value of the open-loop power control parameter set indicator field in the first DCI is 1, the terminal device determines that the terminal device-specific target received power parameter corresponding to the first PUSCH is the first value in the P0-PUSCH-Set. Two open-loop power control parameter sets are configured, and as a result, the power control parameters of the first and second PUSCHs belong to different parameter sets, and different configured power control parameters may be used for the two types of PUSCHs to ensure that the open-loop power control parameters for determining the first and second powers are different. In another possible implementation, the network device indicates the power control parameter set via signaling and uses the DCI to indicate that the power control parameters of the first and second PUSCHs are two different values ​​in the power control parameter set. For example, the first information indicates or includes a third open-loop power control parameter set, and the second indicator field in the first DCI indicates the value of the terminal device-specific target received power parameter in the third open-loop power control parameter set. In another example, if the first information indicates or includes a third open-loop power control parameter set, and the second indicator field in the first DCI indicates that the target received power parameter specific to the first terminal device is a first value in the third open-loop power control parameter set, then the target received power parameter specific to the second terminal device is a second value in the third open-loop power control parameter set. Optionally, the first value is different from the second value. In another example, if the first information indicates or includes a third open-loop power control parameter set, and the second indicator field in the first DCI indicates that the target received power parameter specific to the second terminal device is a first value in the third open-loop power control parameter set, then the target received power parameter specific to the first terminal device is a second value in the third open-loop power control parameter set. Optionally, the first value is different from the second value. Different open-loop power control parameters may be used, resulting in appropriate transmission power being used for the first and second pushers, thereby ensuring performance.

[0140] Implementation form 2: The first DCI includes an open-loop power control parameter set indicator field and a first indicator field. The first information indicates or includes a first open-loop power control parameter set and a second open-loop power control parameter set. The open-loop power control parameter set indicator field and the first indicator field indicate candidate value sets for terminal device-specific target received power parameters. For example, the open-loop power control parameter set indicator field indicates that the candidate value set for the first terminal device-specific target received power parameter is either the first open-loop power control parameter set or the second open-loop power control parameter set, and the first indicator field indicates that the candidate value set for the second terminal device-specific target received power parameter is either the first open-loop power control parameter set or the second open-loop power control parameter set. In another example, the open-loop power control parameter set indicator field indicates that the candidate value set for the first terminal device-specific target received power parameter is the first open-loop power control parameter set. As another example, the first indicator field indicates that the candidate set of values ​​for the target received power parameter specific to the second terminal device is the second open-loop power control parameter set. In another example, the open-loop power control parameter set indicator field indicates that the candidate set of values ​​for the target received power parameter specific to the second terminal device is the first open-loop power control parameter set. In yet another example, the first indicator field indicates that the candidate set of values ​​for the target received power parameter specific to the first terminal device is the second open-loop power control parameter set. Two open-loop power control parameter sets are configured, and as a result, the power control parameters of the first and second pushers belong to different parameter sets, and different configured power control parameters may be used for the two types of pushers to ensure that the open-loop power control parameters for determining the first and second powerers are different. In another possible implementation, the network device indicates the power control parameter set via signaling and uses DCI to indicate that the power control parameters of the first and second pushers are two different values ​​within the power control parameter set.For example, the first information indicates or includes a third open-loop power control parameter set, and the first and second indicator fields in the first DCI indicate the values ​​of the terminal device-specific target received power parameters in the third open-loop power control parameter set. In another example, the first information indicates or includes a third open-loop power control parameter set, and the first indicator field in the first DCI indicates that the first terminal device-specific target received power parameter is a first value in the third open-loop power control parameter set, and the second indicator field indicates that the second terminal device-specific target received power parameter is a second value in the third open-loop power control parameter set. Optionally, the first value is different from the second value. In another example, the first information indicates or includes a third open-loop power control parameter set, where the first indicator field in the first DCI indicates that the target received power parameter specific to the second terminal device is a first value in the third open-loop power control parameter set, and the second indicator field indicates that the target received power parameter specific to the first terminal device is a second value in the third open-loop power control parameter set. Optionally, the first value is different from the second value. Different open-loop power control parameters may be used, resulting in appropriate transmission power being used for the first and second pushes, thereby ensuring performance.

[0141] Implementation form 3: The first DCI includes a first SRI indicator field and a second SRI indicator field. The terminal device determines a first terminal device-specific target received power parameter based on the first SRI indicator field and a first mapping relationship, and determines a second terminal device-specific target received power parameter based on the second SRI indicator field and a second mapping relationship. Accordingly, the network device indicates the first terminal device-specific target received power parameter based on the first SRI indicator field and a first mapping relationship, and indicates the second terminal device-specific target received power parameter based on the second SRI indicator field and a second mapping relationship. The first mapping relationship is a mapping relationship between the value of the first SRI indicator field and a candidate value for the first terminal device-specific target received power parameter, and the second mapping relationship is a mapping relationship between the value of the second SRI indicator field and a candidate value for the second terminal device-specific target received power parameter. The first and second mapping relationships may be predefined or transmitted to the terminal device by the network device through signaling. For example, a network device indicates a first mapping relationship and a second mapping relationship via RRC signaling. In another example, the first information includes a first mapping relationship and a second mapping relationship. For example, a network device uses the parameters sri-PUSCH-MappingToAddModList and sri-PUSCH-MappingToAddModList2-r17 to configure two sets of mapping relationships between the SRI instruction field and P0-PUSCH-AlphaSet, and then uses the two SRI instruction fields in the first DCI to determine the P0-PUSCH and P0-PUSCH-AlphaSet corresponding to the first PUSCH and the second PUSCH. O_UE_PUSCH,b,f,cThe value of (j) is shown. In possible implementations, the first open-loop power control parameter and the second open-loop power control parameter may belong to the same open-loop power control parameter set or to different open-loop power control parameter sets. For example, the first terminal device-specific target received power parameter and the second terminal device-specific target received power parameter may be mapped to, associated with, or belong to the same open-loop power control parameter set. See Implementation Mode 2 for details. Further details are not provided here.

[0142] In addition, in implementation form 3, the presence of an SRI instruction field necessitates consideration of the configuration of the sounding reference signal (SRS). In a possible configuration, the network device configures at least one set of SRS resources for use in codebook-based or non-codebook-based transmission for terminal devices. The first and second SRI instruction fields are associated with the same set of SRS resources within the at least one set of SRS resources, with the first SRI instruction field used for SRS resource instruction and power control parameter instruction, and the second SRI instruction field used for power control parameter instruction. In other words, in this case, the second SRI instruction field does not indicate an SRS resource. In another possible configuration, the network device configures at least two sets of SRS resources for use in codebook-based or non-codebook-based transmission for terminal devices, with the first and second SRI instruction fields associated with either one of the at least two sets of SRS resources, or with two of the at least two sets of SRS resources, respectively. In this case, both the first SRI instruction field and the second SRI instruction field may be used for SRS resource instruction and power control parameter instruction. In possible ways, the SRS resource set is included in the first information or RRC signaling.

[0143] In the implementation described above, the first DCI may be a DCI for scheduling at least one of the first or second PUSCH. Alternatively, the first DCI may be a common DCI or a terminal device group-level DCI. The network device transmits the first DCI to the terminal device. In response, the terminal device receives the first DCI. Furthermore, if the path loss compensation coefficients for the first and second PUSCHs are indicated by using the DCI, similar to how terminal device-specific target received power parameters are indicated in the implementation described above, the network device may configure two sets of path loss compensation coefficients and then dynamically indicate the first and second PUSCHs by using one or two indicator fields in the DCI. Further details are not described here again.

[0144] In possible configurations, closed-loop power control parameters include power control adjustment state parameters. For example, a first closed-loop power control parameter includes a first power control adjustment state parameter. For example, a second closed-loop power control parameter includes a second power control adjustment state parameter. The difference between the closed-loop power control parameters of a first PUSCH and a second PUSCH may be understood as a difference between the first power control adjustment state parameter for determining the first power and the second power control adjustment state parameter for determining the second power. Thus, different closed-loop power control parameters may be used for PUSCH transmissions on SBFD symbols and PUSCH transmissions on non-SBFD symbols to implement appropriate power control. The first and second power control adjustment state parameters may be predefined in the protocol, configured using RRC, indicated by dynamic signaling, or indicated by an SRI instruction field in DCI. For example, a network device may configure and enable two power control adjustment state parameters via RRC signaling. For example, the RRC signaling may be twoPUSCH-PC-AdjustmentStates. When a network device enables two PUSCH power adjustment state parameters, the two power adjustment state parameters may be associated with or used for PUSCH transmissions on two types of symbols, respectively. For example, in the case of an initial PUSCH transmission with configured grant type 1, the network device can configure the association between the two PUSCH power adjustment state parameters and the first and second PUSCH via RRC signaling. In another example, in the case of a PUSCH retransmission with configured grant type 1, or a PUSCH activation or retransmission with configured grant type 2, the network device can indicate the first and second power control adjustment state parameters for the first and second PUSCH by using DCI.In another example, for dynamically scheduled pushes, a network device can indicate a first power control adjustment state parameter and a second power control adjustment state parameter for a first push and a second push by using an RRC configuration or DCI. For example, the first DCI includes a first SRI instruction field and a second SRI instruction field, where the first SRI instruction field indicates the first power control adjustment state parameter for the first push and the second SRI instruction field indicates the second power control adjustment state parameter for the second push. For example, the network device transmits a second DCI to a terminal device, where the second DCI includes a first transmission power control TPC command and a second TPC command, where the first TPC command indicates the first power control adjustment state parameter and the second TPC command indicates the second power control adjustment state parameter.

[0145] In the solution described above, two different sets of open-loop power control parameters and / or closed-loop power control parameters are used for push transmission on SBFD symbols and non-SBFD symbols, respectively, thereby solving the problem of insufficient transmission performance on SBFD symbols and improving transmission performance on SBFD symbols.

[0146] The solutions described above only explain how to perform power control on PUCCH in an SBFD scenario. Power control for physical uplink control channels (PUCCH), physical random access channels (PRACH), and SRS in an SBFD scenario can also be implemented using the solutions described above. For example, two different sets of open-loop power control parameters and / or closed-loop power control parameters are used for transmission on PUCCH, PRACH, SRS, SBFD symbols, and non-SBFD symbols, respectively. The open-loop power control parameters may further include at least one of target received power parameters or path loss compensation coefficients. In another example, for PUCCH, the network device configures two sets of target received power parameters and / or path loss compensation coefficients for PUCCH transmission on two types of symbols for terminal devices via RRC signaling. In another example, for PRACH, the network device can configure two target power parameters for PRACH transmission on two types of symbols for terminal devices via SIB1 or RRC signaling. In the possible methods, the target power parameter here is P PRACH,target,f,c This may also be the case. In another possible implementation, the power ramping parameters for PRACH transmission on two types of symbols may differ. For example, the power ramping step for PRACH transmission on SBFD symbols may be larger than the power ramping step for PRACH transmission on non-SBFD symbols. In another example, for SRS, a network device may configure two SRS resource sets for terminal devices for each of the two types of SRS transmissions on the two types of symbols. Each SRS resource set has independent power control parameters. Power control parameters as used herein include open-loop power control parameters and / or closed-loop power control parameters. Further details are not described here.

[0147] To avoid excessive implementation complexity in terminal devices, time units are configured or predefined by the network device. When uplink transmission is performed within a time unit, the transmission power is not adjusted, or the transmission power does not change for different symbol types within the time unit. In possible schemes, different symbol types as used herein mean that SBFD symbols and non-SBFD symbols are present within the time unit. Different powers may be used for uplink transmission in different time units. A time unit as used herein may be one slot, or at least two symbols, or related to the configuration of SBFD symbols. Time units may be predefined in the protocol or indicated by the network device. In possible schemes, the network device may transmit a signaling to indicate whether a time unit is enabled. In possible schemes, the terminal device may alternatively transmit a support status for a time unit to the network device. In this way, the terminal device does not frequently change the transmission power due to changes in symbol types, simplifying the implementation by the terminal device.

[0148] Embodiments of the present invention can be used independently or in combination. Different steps in the embodiments may also be used independently or in combination. Different embodiments have similar steps, and the descriptions of the steps can be referenced to one another.

[0149] Corresponding to the method described above, one embodiment of the present application provides a communication device. Figures 5 to 7 illustrate the structure of a possible communication device according to an embodiment of the present application. The communication device may be configured to implement the functions of a terminal device or network device in the embodiment of the method described above. Thus, the beneficial effects of the embodiment of the method described above may also be implemented. In the embodiment of the present application, the communication device may be a RAN node, terminal device, core network device, or another network device shown in Figure 1, or a component (e.g., a chip) within these devices.

[0150] As shown in Figure 5, the communication device 500 includes a processing unit 510 and a transceiver unit 520. The communication device 500 is configured to implement the functions of a terminal device or network device in the embodiment of the method shown in Figure 4.

[0151] When the communication device 500 is configured to implement the functions in the embodiment of the method shown in Figure 4, the transceiver unit 520 is configured to receive first information, the first information comprising a first open-loop power control parameter and a second open-loop power control parameter, and the processing unit 510 is configured to determine first power and second power based on the first information, wherein the first open-loop power control parameter used to determine the first power is different from the second open-loop power control parameter used to determine the second power, the first power is the transmission power of the first physical uplink shared channel PUSCH, the second power is the transmission power of the second PUSCH, and the symbol occupied by the first PUSCH is sub A full-duplex SBFD symbol in the band, and a symbol occupied by a second PUSCH is a non-SBFD symbol; the first open-loop power control parameter includes at least one of a first cell-specific target received power parameter, a first terminal device-specific target received power parameter, or a first path loss compensation coefficient; the second open-loop power control parameter includes at least one of a second cell-specific target received power parameter, a second terminal device-specific target received power parameter, or a second path loss compensation coefficient; and the transceiver unit 520 is further configured to transmit a first PUSCH with a first bandwidth portion BWP using the first power and a second PUSCH with a second bandwidth portion BWP using the second power.

[0152] In one possible design, the first PUSCH and the second PUSCH are different parts of the same PUSCH transmission, the first PUSCH and the second PUSCH are PUSCH transmissions scheduled by different uplink scheduling grants, or the first PUSCH and the second PUSCH are different PUSCH transmissions within an iterative PUSCH transmission, or PUSCH transmissions in different slots within a PUSCH transmission spanning multiple slots, or different PUSCH transmissions within multiple PUSCH transmissions scheduled by the same uplink scheduling grant.

[0153] In a possible design, the first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, the first cell-specific target received power parameter includes at least one of the first preamble target received power parameter, the first message 3 target received power offset parameter, or the first message A target received power offset parameter, the second cell-specific target received power parameter includes at least one of the second preamble target received power parameter, the second message 3 target received power offset parameter, or the second message A target received power offset parameter, and the first cell-specific target received power parameter and the second cell-specific target received power parameter are subject to the following conditions, i.e., The first preamble target received power parameter is different from the second preamble target received power parameter. The first message 3 target received power offset parameter is different from the second message 3 target received power offset parameter, and The target received power offset parameter for the first message A is different from the target received power offset parameter for the second message A. It satisfies at least one of the following conditions.

[0154] In possible designs, the first and second PUSCHs are configured grant PUSCHs or dynamically scheduled PUSCHs, the first cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol, the second cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol, and the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol is different from the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol.

[0155] In a possible design, the first and second pushes are random access message 3 pushes or random access message A pushes, the first terminal device-specific target received power parameter is greater than 0, and the second terminal device-specific target received power parameter is 0.

[0156] In a possible design, the first and second pushes are scheduled pushes using first downlink control information DCI, the first DCI including an open-loop power control parameter set indicator field, the first information including a first open-loop power control parameter set and a second open-loop power control parameter set, wherein the open-loop power control parameter set indicator field indicates that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0157] In a possible design, the first PUSCH and the second PUSCH are PUSCH scheduled using the first DCI, the first DCI including an open-loop power control parameter set indicator field and a first indicator field, the first information including the first open-loop power control parameter set and the second open-loop power control parameter set, the open-loop power control parameter set indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the first indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, and the first indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0158] In a possible design, a first PUSCH and a second PUSCH are PUSCHs scheduled using a first downlink control information DCI, the first DCI including a first sounding reference signal resource indicator SRI indicator field and a second SRI indicator field, and the processing unit 510 is further configured to determine a first terminal device-specific target received power parameter based on the first SRI indicator field and a first mapping relationship, and to determine a second terminal device-specific target received power parameter based on a second SRI indicator field and a second mapping relationship, the first mapping relationship being a mapping relationship between the value of the first SRI indicator field and a candidate value for the first terminal device-specific target received power parameter, and the second mapping relationship being a mapping relationship between the value of the second SRI indicator field and a candidate value for the second terminal device-specific target received power parameter.

[0159] In a possible design, the first power control adjustment state parameter for determining the first power is different from the second power control adjustment state parameter for determining the second power.

[0160] In possible designs, the first and second power control adjustment state parameters are either predefined in the protocol, indicated by radio resource control (RRC), indicated by dynamic signaling, or indicated by an SRI instruction field within the DCI.

[0161] In a possible design, the transceiver unit 520 is further configured to receive a second DCI, the second DCI comprising a first transmission power control TPC command and a second TPC command, the first TPC command indicating a first power control adjustment state parameter and the second TPC command indicating a second power control adjustment state parameter.

[0162] In a possible design, the processing unit 510 is configured to control or indicate the transceiver unit 520 to perform receiving and to control or indicate the transceiver unit 520 to perform transmitting.

[0163] When the communication device 500 is configured to implement the functions of a network device in an embodiment of the method shown in Figure 4, the transceiver unit 520 is configured to transmit first information, the first information indicating a first open-loop power control parameter and a second open-loop power control parameter, the first open-loop power control parameter used to determine the first power being different from the second open-loop power control parameter used to determine the second power, the first power being the transmission power of a first physical uplink shared channel PUSCH, the second power being the transmission power of a second PUSCH, and the symbol occupied by the first PUSCH being a subband A full-duplex SBFD symbol, and a symbol occupied by a second PUSCH is a non-SBFD symbol; the first open-loop power control parameter includes at least one of a first cell-specific target received power parameter, a first terminal device-specific target received power parameter, or a first path loss compensation coefficient; the second open-loop power control parameter includes at least one of a second cell-specific target received power parameter, a second terminal device-specific target received power parameter, or a second path loss compensation coefficient; and the transceiver unit 520 is further configured to receive a first PUSCH at a first BWP and to receive a second PUSCH at a first BWP.

[0164] In a possible design, the processing unit 510 is configured to determine first information based on the requirements of the terminal device for first power and second power.

[0165] In one possible design, the first PUSCH and the second PUSCH are different parts of the same PUSCH transmission, the first PUSCH and the second PUSCH are PUSCH transmissions scheduled by different uplink scheduling grants, or the first PUSCH and the second PUSCH are different PUSCH transmissions within an iterative PUSCH transmission, or PUSCH transmissions in different slots within a PUSCH transmission spanning multiple slots, or different PUSCH transmissions within multiple PUSCH transmissions scheduled by the same uplink scheduling grant.

[0166] In a possible design, the first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, the first cell-specific target received power parameter includes at least one of the first preamble target received power parameter, the first message 3 target received power offset parameter, or the first message A target received power offset parameter, the second cell-specific target received power parameter includes at least one of the second preamble target received power parameter, the second message 3 target received power offset parameter, or the second message A target received power offset parameter, and the first cell-specific target received power parameter and the second cell-specific target received power parameter are subject to the following conditions, i.e., The first preamble target received power parameter is different from the second preamble target received power parameter. The first message 3 target received power offset parameter is different from the second message 3 target received power offset parameter, and The first message A target received power offset parameter is different from the second message A target received power offset parameter. It satisfies at least one of the following conditions.

[0167] In possible designs, the first and second PUSCHs are configured grant PUSCHs or dynamically scheduled PUSCHs, the first cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol, the second cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol, and the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on an SBFD symbol is different from the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on a non-SBFD symbol.

[0168] In a possible design, the first and second PUSCHs are random access message 3 PUSCH or random access message A PUSCH, the first terminal device-specific target received power parameter is greater than 0, and the second terminal device-specific target received power parameter is 0.

[0169] In a possible design, the first and second pushes are scheduled pushes using first downlink control information DCI, the first DCI including an open-loop power control parameter set indicator field, the first information including a first open-loop power control parameter set and a second open-loop power control parameter set, wherein the open-loop power control parameter set indicator field indicates that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicates that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0170] In a possible design, the first PUSCH and the second PUSCH are PUSCH scheduled using the first DCI, the first DCI including an open-loop power control parameter set indicator field and a first indicator field, the first information including the first open-loop power control parameter set and the second open-loop power control parameter set, the open-loop power control parameter set indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the first open-loop power control parameter set, the first indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the second open-loop power control parameter set, or the open-loop power control parameter set indicator field indicating that the candidate set of second terminal device-specific target received power parameters is the first open-loop power control parameter set, and the first indicator field indicating that the candidate set of first terminal device-specific target received power parameters is the second open-loop power control parameter set.

[0171] In a possible design, the first and second pushes are pushes scheduled using the first downlink control information DCI, the first DCI including a first sounding reference signal resource indicator SRI indicator field and a second SRI indicator field, the first SRI indicator field and first mapping relationship indicating a first terminal device-specific target received power parameter, the second SRI indicator field and second mapping relationship indicating a second terminal device-specific target received power parameter, the first mapping relationship being a mapping relationship between the value of the first SRI indicator field and a candidate value for the first terminal device-specific target received power parameter, and the second mapping relationship being a mapping relationship between the value of the second SRI indicator field and a candidate value for the second terminal device-specific target received power parameter.

[0172] In a possible design, the first power control adjustment state parameter for determining the first power is different from the second power control adjustment state parameter for determining the second power.

[0173] In possible designs, the first and second power control adjustment state parameters are either predefined in the protocol, indicated by radio resource control (RRC), indicated by dynamic signaling, or indicated by an SRI instruction field within the DCI.

[0174] In a possible design, the transceiver unit 520 is further configured to transmit a second DCI, the second DCI comprising a first transmission power control TPC command and a second TPC command, the first TPC command indicating a first power control adjustment state parameter and the second TPC command indicating a second power control adjustment state parameter.

[0175] In a possible design, the processing unit 510 is configured to control or indicate the transceiver unit 520 to perform receiving and to control or indicate the transceiver unit 520 to perform transmitting.

[0176] One embodiment of the present application provides a communication device 600. Figure 6 is a block diagram of another communication device according to one embodiment of the present application. The communication device 600 includes a processor 610 which may perform a method in any possible implementation of the embodiments of the present application. Optionally, the communication device 600 may further include at least one memory 620. The processor 610 is coupled to the at least one memory 620. The processor 610 is configured to read a computer program stored in the at least one memory 620 in order to perform a method in any possible implementation of the embodiments of the present application.

[0177] One embodiment of the present application further provides a communication device 700. As shown in Figure 7, the communication device 700 includes a processor 710 and an interface circuit 720. The processor 710 and the interface circuit 720 are connected to each other. It can be understood that the interface circuit 720 may be a transceiver or an input / output interface. Optionally, the communication device 700 may further include a memory 730 configured to store instructions executed by the processor 710, input data necessary for the processor 710 to execute the instructions, or data generated after the processor 710 has executed the instructions.

[0178] When the communication device 700 is configured to implement the method shown in Figure 4, the processor 710 is configured to implement the functions of the processing unit 510, and the interface circuit 720 is configured to implement the functions of the transceiver unit 520.

[0179] If the communication device is a chip used in a terminal device, the chip within the terminal device implements the functions of the terminal device in the embodiment of the method described above. The chip within the terminal device receives information from another module within the terminal device (e.g., a radio frequency module or an antenna), and the information is transmitted to the terminal device by the network device. Alternatively, the chip within the terminal device transmits information to another module within the terminal device (e.g., a radio frequency module or an antenna), and the information is transmitted to the network device by the terminal device.

[0180] If the communication device is a chip used in a network device, the chip within the network device implements the functions of the network device in the embodiments of the method described above. The chip within the network device receives information from another module within the network device (e.g., a radio frequency module or an antenna), and the information is transmitted to the network device by a terminal device. Alternatively, the chip within the network device transmits information to another module within the network device (e.g., a radio frequency module or an antenna), and the information is transmitted to the terminal device by the network device.

[0181] The processor in the embodiments of this application may be an integrated circuit chip having signal processing capabilities. In the implementation process, the steps in the embodiments of the method described above may be implemented by using hardware integrated logic circuits in the processor or by using instructions in the form of software. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The methods, steps, and logic block diagrams disclosed in the embodiments of this application may be implemented or executed. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps in the methods disclosed with reference to embodiments of this application may be performed and completed directly by a hardware decoding processor, or by using a combination of hardware and software modules in the decoding processor. The software modules may be placed in mature storage media in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. The storage medium is placed in memory, the processor reads the information in memory, and, in combination with the processor's hardware, completes the steps of the method described above.

[0182] The memory in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. Through an illustrative but non-limiting explanation, many forms of RAM may be used, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM).

[0183] One embodiment of this application provides a communication system 800 including a terminal device 810 and a network device 820 in a communication method provided in an embodiment of this application. Figure 8 is a block diagram of the communication system 800 according to one embodiment of this application.

[0184] The method steps in the embodiments of this application may be implemented in hardware or by a processor executing software instructions. The software instructions may include corresponding software modules. The software modules may be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disk drives, removable hard disk drives, CD-ROMs, or any other form of storage medium well known in the art. For example, the storage medium is coupled to the processor so that the processor can read information from and write information to the storage medium. Indeed, the storage medium may be a component of the processor. The processor and the storage medium may be located within an ASIC. In addition, the ASIC may be located within a network device or terminal device. Of course, the processor and the storage medium may alternatively exist as separate components within a network device or terminal device.

[0185] All or part of the embodiments described above may be implemented using software, hardware, firmware, or any combination thereof. If software is used to implement an embodiment, all or part of the embodiment may be implemented in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When a computer program or instruction is loaded into a computer and executed, all or part of the procedures or functions in the embodiments of this application are performed. The computer may be a general-purpose computer, a dedicated computer, a computer network, a network device, user equipment, or another programmable device. The computer program or instruction may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer program or instruction may be transmitted wirelessly or wired from one website, computer, server, or data center to another website, computer, server, or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device that integrates one or more available media, such as a server or data center. The usable media may be magnetic media, such as floppy disks, hard disk drives, or magnetic tapes; optical media, such as digital video discs; or semiconductor media, such as solid-state drives. The computer-readable storage medium may be volatile or non-volatile storage medium, or may include both types of storage media, such as volatile and non-volatile storage media.

[0186] In the embodiments of this application, it will be understood that the sequence numbers of the processes described above do not represent the execution sequence. The execution order of the processes should be determined based on the function and internal logic of the processes and should not constitute any limitation on the implementation processes of the embodiments of this application.

[0187] In this application, "when" and "in the case of" mean that the device performs the corresponding process under objective circumstances, and are not intended to imply a time limit. These terms do not imply that the device must have a decision operation during implementation, nor do they imply any other limitations.

[0188] Those skilled in the art will understand that the various numbers, such as the First and Second, in this application are used merely for illustrative purposes to facilitate explanation and are not intended to limit the scope of the embodiments of this application. The specific values ​​of the numbers (which may also be called indices), the specific values ​​of the quantities, and the positions in this application are used merely as examples and are not unique forms of expression and are not intended to limit the scope of the embodiments of this application. The various numbers, such as the First and Second, in this application are used merely for illustrative purposes to facilitate explanation and are not intended to limit the scope of the embodiments of this application.

[0189] In addition, the term "and / or" in this application describes only the association relationship for describing the related objects, indicating that three relationships may exist. For example, A and / or B may represent the following three cases: namely, A only exists, A and B both exist, and B only exists. Furthermore, the letter " / " in this specification generally indicates an "or" relationship between related objects. The term "at least one" in this application may represent "one" and "two or more". For example, at least one of A, B, and C may represent the following seven cases: namely, A only exists, B only exists, C only exists, A and B both exist, A and C both exist, C and B both exist, and A, B, and C exist.

[0190] In embodiments of this application, “instructions” may include direct and indirect instructions, or explicit and implicit instructions. Information indicated by one piece of information (sometimes referred to as instruction information) is referred to as information to be indicated. In a particular implementation process, information to be indicated may be indicated in multiple ways. For example, information to be indicated, such as information to be indicated or an index of information to be indicated, may be indicated directly. Alternatively, information to be indicated may be indicated indirectly by indicating other information, where there is a correlation between the other information and the information to be indicated. Alternatively, only a portion of the information to be indicated may be indicated, with the remainder being known or pre-agreed. For example, certain information may be indicated by using a pre-agreed (e.g., predefined in a protocol) arrangement sequence of information to reduce instruction overhead to some extent. Specific instruction methods are not limited in this application. To a sender of instruction information, it may be understood that instruction information may indicate information to be indicated, and to a receiver of instruction information, instruction information may be used to determine information to be indicated.

[0191] For the sake of a convenient and concise explanation, it will be readily apparent to those skilled in the art that the detailed operating processes of the above-described systems, apparatuses, and units are described by referring to the corresponding processes in the embodiments of the methods described above. Further details are not described here.

[0192] In the various embodiments provided in this application, it should be understood that the disclosed systems, apparatus, and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division. In actual implementations, there may be other division methods. For example, multiple units or components may be coupled or integrated into other systems, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling, or communication connection shown or discussed may be implemented by using some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented electronically, mechanically, or in other ways.

[0193] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed across multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solution of the embodiment.

[0194] In addition, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. [Explanation of Symbols]

[0195] 500 Communication devices 510 Processing Units 520 Transceiver Unit 600 Communication devices 610 Processor 620 memory 700 Communication equipment 710 Processor 720 Interface Circuit 730 memory 800 Communication Systems 810 Terminal devices 820 Network Devices

Claims

1. A method of communication, A step of receiving first information, wherein the first information indicates a first open-loop power control parameter and a second open-loop power control parameter, A step of determining a first power and a second power based on the first information, wherein the first open-loop power control parameter used to determine the first power is different from the second open-loop power control parameter used to determine the second power, the first power is the transmission power of the first physical uplink shared channel PUSCH, the second power is the transmission power of the second PUSCH, the symbol occupied by the first PUSCH is a subband full-duplex SBFD symbol, the symbol occupied by the second PUSCH is a non-SBFD symbol, the first open-loop power control parameter includes at least one of a first cell-specific target received power parameter, a first terminal device-specific target received power parameter, or a first path loss compensation coefficient, and the second open-loop power control parameter includes at least one of a second cell-specific target received power parameter, a second terminal device-specific target received power parameter, or a second path loss compensation coefficient, The steps include transmitting the first PUSCH in a first bandwidth portion BWP using the first power, and transmitting the second PUSCH in a first bandwidth portion BWP using the second power, Methods that include...

2. The first PUSCH and the second PUSCH are different parts of the same PUSCH transmission. The first PUSCH and the second PUSCH are PUSCH transmissions scheduled by different uplink scheduling grants, or The first PUSCH and the second PUSCH are different PUSCH transmissions within a repeating PUSCH transmission, or PUSCH transmissions within different slots within a PUSCH transmission spanning multiple slots, or different PUSCH transmissions within multiple PUSCH transmissions scheduled by the same uplink scheduling grant. The method according to claim 1.

3. The first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, The first cell-specific target received power parameter includes at least one of the first preamble target received power parameter, the first message 3 target received power offset parameter, or the first message A target received power offset parameter, and the second cell-specific target received power parameter includes at least one of the second preamble target received power parameter, the second message 3 target received power offset parameter, or the second message A target received power offset parameter. The first cell-specific target received power parameter and the second cell-specific target received power parameter are determined by the following conditions, namely: The first preamble target received power parameter is different from the second preamble target received power parameter. The first message 3 target received power offset parameter is different from the second message 3 target received power offset parameter, and The first message A target received power offset parameter is different from the second message A target received power offset parameter, satisfying at least one of the following conditions: The method according to claim 1 or 2.

4. The first PUSCH and the second PUSCH are configured grant PUSCHs or dynamically scheduled PUSCHs. The first cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on the SBFD symbol, and the second cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on the non-SBFD symbol. The cell-specific target received power parameter corresponding to the random access message 3 PUSCH or the random access message A PUSCH on the SBFD symbol is different from the cell-specific target received power parameter corresponding to the random access message 3 PUSCH or the random access message A PUSCH on the non-SBFD symbol. The method according to claim 1 or 2.

5. The first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, the first terminal device-specific target received power parameter is greater than 0, and the second terminal device-specific target received power parameter is 0. The method according to any one of claims 1 to 3.

6. The first PUSCH and the second PUSCH are PUSCH scheduled using the first downlink control information DCI, the first DCI including an open-loop power control parameter set instruction field. The first information indicates the first open-loop power control parameter and the second open-loop power control parameter, The first information indicates a first open-loop power control parameter set and a second open-loop power control parameter set, and the first open-loop power control parameter and the second open-loop power control parameter belong to the first open-loop power control parameter set and the second open-loop power control parameter set, When the open-loop power control parameter set instruction field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, then the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or When the open-loop power control parameter set instruction field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set, The method according to claim 1, 2, or 4.

7. The first PUSCH and the second PUSCH are PUSCH scheduled using a first DCI, the first DCI including an open-loop power control parameter set indicator field and a first indicator field. The first information indicates the first open-loop power control parameter and the second open-loop power control parameter, The first information indicates a first open-loop power control parameter set and a second open-loop power control parameter set, and the first open-loop power control parameter and the second open-loop power control parameter belong to the first open-loop power control parameter set and the second open-loop power control parameter set, The open-loop power control parameter set instruction field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, or the first instruction field indicates that the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or The open-loop power control parameter set instruction field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, and the first instruction field indicates that the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set. The method according to claim 1, 2, or 4.

8. The first PUSCH and the second PUSCH are PUSCH scheduled using a first downlink control information DCI, the first DCI including a first sounding reference signal resource indicator SRI indicator field and a second SRI indicator field. The first terminal device-specific target received power parameter is determined based on the first SRI indicator field and the first mapping relationship, the second terminal device-specific target received power parameter is determined based on the second SRI indicator field and the second mapping relationship, the first mapping relationship is the mapping relationship between the value of the first SRI indicator field and a candidate value for the first terminal device-specific target received power parameter, and the second mapping relationship is the mapping relationship between the value of the second SRI indicator field and a candidate value for the second terminal device-specific target received power parameter. The method according to claim 1, 2, or 4.

9. The first power control adjustment state parameter for determining the first power is different from the second power control adjustment state parameter for determining the second power. The method according to any one of claims 1 to 8.

10. The first power control adjustment state parameter and the second power control adjustment state parameter are predefined in the protocol, indicated by radio resource control (RRC), indicated by dynamic signaling, or indicated by an SRI instruction field in DCI. The method according to claim 9.

11. A step of receiving a second DCI, wherein the second DCI includes a first transmission power control TPC command and a second TPC command, the first TPC command indicating a first power control adjustment state parameter and the second TPC command indicating a second power control adjustment state parameter. The method according to claim 9.

12. A method of communication, A step of transmitting first information, wherein the first information includes a first open-loop power control parameter and a second open-loop power control parameter. The first open-loop power control parameter used to determine the first power differs from the second open-loop power control parameter used to determine the second power, wherein the first power is the transmission power of the first physical uplink shared channel PUSCH, the second power is the transmission power of the second PUSCH, the symbol occupied by the first PUSCH is a subband full-duplex SBFD symbol, the symbol occupied by the second PUSCH is a non-SBFD symbol, the first open-loop power control parameter includes at least one of a first cell-specific target received power parameter, a first terminal device-specific target received power parameter, or a first path loss compensation coefficient, and the second open-loop power control parameter includes at least one of a second cell-specific target received power parameter, a second terminal device-specific target received power parameter, or a second path loss compensation coefficient, step, The steps include receiving the first PUSCH with the first BWP and receiving the second PUSCH with the first BWP, Methods that include...

13. The first PUSCH and the second PUSCH are different parts of the same PUSCH transmission. The first PUSCH and the second PUSCH are PUSCH transmissions scheduled by different uplink scheduling grants, or The first PUSCH and the second PUSCH are different PUSCH transmissions within a repeating PUSCH transmission, or PUSCH transmissions within different slots within a PUSCH transmission spanning multiple slots, or different PUSCH transmissions within multiple PUSCH transmissions scheduled by the same uplink scheduling grant. The method according to claim 12.

14. The first PUSCH and the second PUSCH are random access message 3 PUSCH or random access message A PUSCH, The first cell-specific target received power parameter includes at least one of the first preamble target received power parameter, the first message 3 target received power offset parameter, or the first message A target received power offset parameter, and the second cell-specific target received power parameter includes at least one of the second preamble target received power parameter, the second message 3 target received power offset parameter, or the second message A target received power offset parameter. The first cell-specific target received power parameter and the second cell-specific target received power parameter are determined by the following conditions, namely: The first preamble target received power parameter is different from the second preamble target received power parameter. The first message 3 target received power offset parameter is different from the second message 3 target received power offset parameter, and The first message A target received power offset parameter is different from the second message A target received power offset parameter. The method according to claim 12 or 13, which satisfies at least one of the following:

15. The first PUSCH and the second PUSCH are configured grant PUSCHs or dynamically scheduled PUSCHs. The first cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on the SBFD symbol, and the second cell-specific target received power parameter is the cell-specific target received power parameter corresponding to random access message 3 PUSCH or random access message A PUSCH on the non-SBFD symbol. The cell-specific target received power parameter corresponding to the random access message 3 PUSCH or the random access message A PUSCH on the SBFD symbol is different from the cell-specific target received power parameter corresponding to the random access message 3 PUSCH or the random access message A PUSCH on the non-SBFD symbol. The method according to claim 12 or 13.

16. The first PUSCH and the second PUSCH are the random access message 3 PUSCH or the random access message A PUSCH, the first terminal device-specific target received power parameter is greater than 0, and the second terminal device-specific target received power parameter is 0. The method according to any one of claims 12 to 14.

17. The first PUSCH and the second PUSCH are PUSCH scheduled using the first downlink control information DCI, the first DCI including an open-loop power control parameter set instruction field. The first information indicates the first open-loop power control parameter and the second open-loop power control parameter, When the first information indicates a first open-loop power control parameter set and a second open-loop power control parameter set, and the first open-loop power control parameter and the second open-loop power control parameter belong to the first open-loop power control parameter set and the second open-loop power control parameter set, and the open-loop power control parameter set indicator field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, then the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or When the open-loop power control parameter set instruction field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set, The method according to claim 12, 13, or 15.

18. The first PUSCH and the second PUSCH are PUSCH scheduled using a first DCI, the first DCI including an open-loop power control parameter set indicator field and a first indicator field. The first information indicates the first open-loop power control parameter and the second open-loop power control parameter, The first information indicates a first open-loop power control parameter set and a second open-loop power control parameter set, and the first open-loop power control parameter and the second open-loop power control parameter belong to the first open-loop power control parameter set and the second open-loop power control parameter set, The open-loop power control parameter set instruction field indicates that the candidate set of target received power parameters specific to the first terminal device is the first open-loop power control parameter set, or the first instruction field indicates that the candidate set of target received power parameters specific to the second terminal device is the second open-loop power control parameter set, or The open-loop power control parameter set instruction field indicates that the candidate set of target received power parameters specific to the second terminal device is the first open-loop power control parameter set, and the first instruction field indicates that the candidate set of target received power parameters specific to the first terminal device is the second open-loop power control parameter set. The method according to claim 12, 13, or 15.

19. The first PUSCH and the second PUSCH are PUSCH scheduled using the first downlink control information DCI, the first DCI including a first SRI instruction field and a second SRI instruction field. The first SRI instruction field and the first mapping relationship indicate the target received power parameter specific to the first terminal device, the second SRI instruction field and the second mapping relationship indicate the target received power parameter specific to the second terminal device, the first mapping relationship is a mapping relationship between the value of the first SRI instruction field and a candidate value of the target received power parameter specific to the first terminal device, and the second mapping relationship is a mapping relationship between the value of the second SRI instruction field and a candidate value of the target received power parameter specific to the second terminal device. The method according to claim 12, 13, or 15.

20. The first power control adjustment state parameter for determining the first power is different from the second power control adjustment state parameter for determining the second power. The method according to any one of claims 12 to 19.

21. The first power control adjustment state parameter and the second power control adjustment state parameter are predefined in the protocol, indicated by radio resource control (RRC), indicated by dynamic signaling, or indicated by an SRI instruction field in DCI. The method according to claim 20.

22. A step of transmitting a second DCI, wherein the second DCI includes a first TPC command and a second TPC command, the first TPC command indicating a first power control adjustment state parameter and the second TPC command indicating a second power control adjustment state parameter. The method according to claim 20.

23. A terminal device comprising a processor, wherein the processor is configured to perform the method described in any one of claims 1 to 11.

24. A network device comprising a processor, wherein the processor is configured to perform the method described in any one of claims 12 to 22.

25. A communication device comprising at least one processor and an interface circuit, wherein the interface circuit is configured to provide the at least one processor with input or output of instructions and / or data, and when the at least one processor executes the instructions, the device becomes capable of implementing the method according to any one of claims 1 to 22.

26. A computer-readable storage medium containing an instruction, wherein when the instruction is executed on a computer, the computer becomes capable of performing the method according to any one of claims 1 to 11, or the computer becomes capable of performing the method according to any one of claims 12 to 22.

27. A computer program product comprising instructions, wherein when the instructions are executed on a computer, the computer becomes capable of performing the method described in any one of claims 1 to 11, or the computer becomes capable of performing the method described in any one of claims 12 to 22.

28. A chip comprising a processor and a communication interface, wherein the processor is configured to read instructions or computer programs and perform the method according to any one of claims 1 to 11, or to enable the computer to perform the method according to any one of claims 12 to 22.

29. A communication system comprising a terminal device according to claim 23 and a network device according to claim 24.

Images