Communication method and device

Abstract

The invention relates to the technical field of communication, in particular to a communication method and device, and aims to support independent power control of PUSCHs (Physical Uplink Shared Channel) in different time domain units, improve the performance of the PUSCHs in a random access process and reduce the initial access delay of terminal equipment. The method may be executed by a terminal device, the method comprising: receiving first information, the first information indicating a first power offset corresponding to a PRACH in an SBFD time domain unit and a PUSCH in a non-SBFD time domain unit, and / or a second power offset corresponding to a PRACH in the non-SBFD time domain unit and a PUSCH in the SBFD time domain unit; and sending the first PUSCH, wherein the sending power of the first PUSCH is determined according to the first information.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] Time division duplex (TDD) separates uplink and downlink transmissions by time, typically on different time slots or symbols of the same carrier. Frequency division duplex (FDD) separates uplink and downlink transmissions by frequency, on different carriers. Compared to FDD, TDD usually occupies less frequency domain resources. However, because uplink and downlink transmissions cannot occur simultaneously in TDD (e.g., only downlink transmission can occur in slot 0), uplink transmission delay increases. To address the delay issue of TDD, flexible duplexing, also known as subband full duplex (SBFD), complementary TDD (C-TDD), or full duplex, is being discussed in standards. The core idea is that uplink and downlink transmission resources can be configured simultaneously on a specific symbol or time slot in TDD. For example, within the downlink bandwidth part (BWP) of time slot 0, there exists a frequency domain resource on which uplink transmission can be performed. This allows uplink transmission to be performed on time slot 0, reducing uplink transmission latency. This frequency domain resource can be called the uplink subband.

[0003] The duplex mode of SBFD differs from that of TDD and FDD. The channel environment of the physical uplink shared channel (PUSCH) in the duplex mode of SBFD also differs from that of TDD and FDD. Therefore, how to control the power of PUSCH in processes such as random access is an issue that needs to be considered. Summary of the Invention

[0004] This application provides a communication method and apparatus to support separate power control of PUSCH in SBFD time domain units and in non-SBFD time domain units, thereby improving the performance of PUSCH in random access procedures and reducing the initial access latency of terminal devices.

[0005] Firstly, embodiments of this application provide a communication method that can be executed by a terminal device. The terminal device can refer to the terminal device itself, or to a processor, module, or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) within the terminal device that implements the method. It can also be a logic module or software capable of implementing all or part of the terminal device's functions. Taking the application of this method to a terminal device as an example, the method includes: receiving first information, the first information indicating a first power offset between the physical random access channel (PRACH) in the SBFD time domain unit and the PUSCH in a non-SBFD time domain unit, and / or a second power offset between the PRACH in a non-SBFD time domain unit and the PUSCH in the SBFD time domain unit; and transmitting a first PUSCH, wherein the transmission power of the first PUSCH is determined according to the first information.

[0006] Through the above design, a first power offset can be configured for PRACH in the SBFD time domain unit and PUSCH in the non-SBFD time domain unit, and a second power offset can be configured for PRACH in the non-SBFD time domain unit and PUSCH in the SBFD time domain unit. Thus, after the introduction of SBFD, if PRACH and PUSCH are in different time domain units, the transmission power of PUSCH can be determined based on the first power offset or the second power offset. This supports individual power control of PUSCH in different time domain units, making the determined transmission power more compatible with the channel environment of PUSCH transmission. This is beneficial to improving the performance of PUSCH in random access procedures and reducing the initial access latency of terminal equipment.

[0007] In one possible design, the value of the first power offset is X, and the value of the second power offset is -X, where X is an integer.

[0008] With the above design, the value of the second power offset can be determined by the value of the first power offset, and the value of the first power offset can be determined by the value of the second power offset. The network device can indicate (or configure) only one power offset to the terminal device, which can save signaling overhead.

[0009] In one possible design, the first information also indicates a fourth power offset, which is the power offset between PRACH in a non-SBFD time domain cell and PUSCH in a non-SBFD time domain cell.

[0010] With the above design, if both PRACH and PUSCH are in non-SBFD time domain units, the transmission power of PUSCH can be determined by the fourth power offset. This allows for separate power control of PUSCH when both PRACH and PUSCH are in non-SBFD time domain units, making the determined transmission power more compatible with the channel environment of PUSCH transmission, which is beneficial to improving the performance of PUSCH in random access procedures.

[0011] In one possible design, the method further includes: receiving second information, the second information indicating a first PRACH target receive power and / or a second PRACH target receive power; wherein the first PRACH target receive power is the target receive power of the PRACH in the SBFD time domain unit, the second target receive power is the target receive power of the PRACH in the non-SBFD time domain unit, and the transmit power of the first PUSCH can be determined based on the first information and the second information.

[0012] Optionally, the network device may also send second information indicating the target receive power of the first PRACH and / or the target receive power of the second PRACH to the terminal device without sending the first information. The terminal device may also determine the transmit power of the first PUSCH based on the second information.

[0013] Through the above design, network devices can indirectly indicate the transmit power of PUSCH in SBFD time domain units and non-SBFD time domain units by instructing terminal devices on the target receive power of PRACH in SBFD time domain units and the target receive power of PRACH in non-SBFD time domain units. This supports individual power control of PUSCH in different time domain units, making the determined transmit power more compatible with the channel environment of PUSCH transmission, which is beneficial to improving PUSCH performance.

[0014] In one possible design, the first PUSCH is the PUSCH in the random access procedure.

[0015] In one possible design, the method further includes: transmitting a second PUSCH, wherein the transmission power of the second PUSCH is determined based on the target receive power of the PUSCH in the random access procedure most recent to the second PUSCH in the time domain. Optionally, the second PUSCH includes at least one of the following: a configured grant (CG) PUSCH or a dynamic grant (DG) PUSCH.

[0016] The above design clarifies the method for determining the transmission power of the CG / DG PUSCH, which is beneficial for network devices to control the transmission power of the CG / DG PUSCH.

[0017] In one possible design, the PUSCH in the random access procedure closest to the second PUSCH is of the same time-domain unit type as the second PUSCH.

[0018] Through the above design, the transmission power of the second PUSCH can be determined based on the target reception power of the PUSCH in the nearest random access procedure in the time domain and of the same time domain unit type as it. This makes the determined transmission power more compatible with the channel environment of the second PUSCH transmission, which is beneficial to improving the performance of the second PUSCH.

[0019] In one possible design, the target receive power of the second PUSCH is not configured by the network.

[0020] With the above design, even if the target receive power of the second PUSCH is not configured by the network (such as network devices), the terminal device can determine the transmit power of the second PUSCH based on the target receive power of the PUSCH in the nearest random access procedure in the time domain. This helps to align the understanding of the transmit power of the second PUSCH between the terminal device and the network device, and facilitates the network device to control the transmit power of the second PUSCH.

[0021] In one possible design, the method further includes transmitting a power headroom report (PHR), wherein the power headroom indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit, or based on the target received power of the PUSCH in a non-SBFD time domain unit.

[0022] The above design aligns the understanding of the power margin indicated by the PHR between terminal devices and network devices, facilitating accurate scheduling of PUSCH transmissions by network devices and thereby improving uplink throughput.

[0023] In one possible design, if the third PUSCH carrying the PHR is in a non-SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain cell; if the third PUSCH carrying the PHR is in an SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain cell.

[0024] Optionally, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit during the random access procedure; the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit during the random access procedure.

[0025] The above design aligns the understanding of the power margin indicated by the PHR between terminal devices and network devices, facilitating accurate scheduling of PUSCH transmission power by network devices and thereby improving uplink throughput.

[0026] Secondly, embodiments of this application provide a communication method, which can be executed by a network device. This network device can refer to the network device itself, a processor, module, chip, or chip system within the network device that implements the method, or a logic module or software capable of implementing all or part of the network device's functions. The method includes: sending first information, the first information indicating a first power offset between a PRACH in an SBFD time-domain unit and a PUSCH in a non-SBFD time-domain unit, and / or a second power offset between a PRACH in a non-SBFD time-domain unit and a PUSCH in an SBFD time-domain unit; and receiving a first PUSCH, wherein the transmission power of the first PUSCH is determined based on the first information.

[0027] In one possible design, the value of the first power offset is X, the value of the second power offset is -X, and X is an integer.

[0028] In one possible design, the first information also indicates a fourth power offset, which is the power offset between PRACH in a non-SBFD time domain cell and PUSCH in a non-SBFD time domain cell.

[0029] In one possible design, the method further includes sending second information to the terminal device, the second information indicating a first PRACH target receive power and / or a second PRACH target receive power; wherein the first PRACH target receive power is the target receive power of the PRACH in the SBFD time domain unit, the second target receive power is the target receive power of the PRACH in the non-SBFD time domain unit, and the transmit power of the first PUSCH can be determined based on the first information and the second information.

[0030] Optionally, the network device may also send second information indicating the target receive power of the first PRACH and / or the target receive power of the second PRACH to the terminal device without sending the first information. The transmit power of the first PUSCH can also be determined based on the second information.

[0031] In one possible design, the first PUSCH is the PUSCH in the random access procedure.

[0032] In one possible design, the method further includes receiving a second PUSCH, wherein the transmit power of the second PUSCH is determined based on the target receive power of the PUSCH in the random access procedure most recent to the second PUSCH in the time domain.

[0033] In one possible design, the PUSCH in the random access procedure closest to the second PUSCH is of the same time-domain unit type as the second PUSCH.

[0034] In one possible design, the second PUSCH includes at least one of the following: CG PUSCH or DG PUSCH.

[0035] In one possible design, the target receive power of the second PUSCH is not configured by the network.

[0036] In one possible design, the method further includes: receiving a PHR, wherein the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit, or based on the target received power of the PUSCH in a non-SBFD time domain unit.

[0037] In one possible design, if the third PUSCH carrying the PHR is in a non-SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain cell; if the third PUSCH carrying the PHR is in an SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain cell.

[0038] In one possible design, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit during the random access procedure; the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit during the random access procedure.

[0039] Thirdly, embodiments of this application provide a communication method that can be executed by a terminal device. The terminal device can refer to the terminal device itself, a processor, module, chip, or chip system implementing the method within the terminal device, or a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: transmitting a second PUSCH, wherein the transmission power of the second PUSCH is determined based on the target reception power of the PUSCH in the random access procedure most recently accessed by the second PUSCH in the time domain. The PUSCH in this random access procedure can be a first PUSCH, and the second PUSCH includes at least one of the following: CG PUSCH or DG PUSCH.

[0040] In one possible design, the PUSCH in the random access procedure closest to the second PUSCH is of the same time-domain unit type as the second PUSCH.

[0041] In one possible design, the target receive power of the second PUSCH is not configured by the network.

[0042] In one possible design, the first PUSCH is the PUSCH that is closest to the second PUSCH in the time domain during the random access procedure described above.

[0043] Fourthly, embodiments of this application provide a communication method that can be executed by a network device. This network device can refer to the network device itself, a processor, module, chip, or chip system within the network device that implements the method, or a logic module or software capable of implementing all or part of the network device's functions. The method includes: receiving a second PUSCH, wherein the transmission power of the second PUSCH is determined based on the target reception power of the PUSCH in the random access procedure most recently accessed by the second PUSCH in the time domain. The PUSCH in this random access procedure can be a first PUSCH, and the second PUSCH includes at least one of the following: CG PUSCH or DG PUSCH.

[0044] In one possible design, the PUSCH in the random access procedure closest to the second PUSCH is of the same time-domain unit type as the second PUSCH.

[0045] In one possible design, the target receive power of the second PUSCH is not configured by the network.

[0046] In one possible design, the first PUSCH is the PUSCH that is closest to the second PUSCH in the time domain during the random access procedure described above.

[0047] Fifthly, embodiments of this application provide a communication method that can be executed by a terminal device. The terminal device can refer to the terminal device itself, a processor, module, chip, or chip system within the terminal device that implements the method, or a logic module or software capable of implementing all or part of the terminal device's functions. The method includes: transmitting a Power Headroom (PHR), wherein the power headroom indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit, or based on the target received power of the PUSCH in a non-SBFD time domain unit.

[0048] In one possible design, if the third PUSCH carrying the PHR is in a non-SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain cell; if the third PUSCH carrying the PHR is in an SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain cell.

[0049] In one possible design, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit during the random access procedure; the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit during the random access procedure.

[0050] Sixthly, embodiments of this application provide a communication method that can be executed by a network device. This network device can refer to the network device itself, a processor, module, chip, or chip system within the network device that implements the method, or a logic module or software capable of implementing all or part of the network device's functions. The method includes: receiving a Power Headroom (PHR), wherein the power headroom indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit, or based on the target received power of the PUSCH in a non-SBFD time domain unit.

[0051] In one possible design, if the third PUSCH carrying the PHR is in a non-SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain cell; if the third PUSCH carrying the PHR is in an SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain cell.

[0052] In one possible design, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit during the random access procedure; the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit during the random access procedure.

[0053] In a seventh aspect, embodiments of this application provide a communication device that has the function of implementing the method of any one of the first to sixth aspects described above. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, such as an interface unit and a processing unit.

[0054] In one possible design, the device can be a chip or an integrated circuit.

[0055] In one possible design, the device includes a memory and a processor, the memory for storing instructions executed by the processor, and when the instructions are executed by the processor, the device can perform the methods of any one of the first to sixth aspects.

[0056] Eighthly, embodiments of this application provide a communication device including an interface circuit and a processor, wherein the processor and the interface circuit are coupled to each other. The interface circuit is used for inputting and / or outputting signals, and the processor is used to implement the methods of any one of the first to sixth aspects described above through logic circuits or executing instructions. It is understood that the interface circuit can be a transceiver, a transceiver device, or an input / output interface.

[0057] Optionally, the communication device may also include a memory for storing instructions executed by the processor, or storing input data required by the processor to execute instructions, or storing data generated after the processor executes instructions. The memory may be a physically independent unit, or it may be coupled to the processor, or the processor may include the memory (i.e., the processor and the memory are integrated together).

[0058] In one possible implementation, the communication device is a chip or chip system.

[0059] Ninthly, embodiments of this application provide a communication system, which includes a terminal device and a network device. The terminal device is used to implement the method of the first aspect described above, and the network device is used to implement the method of the second aspect described above; or the terminal device is used to implement the method of the third aspect described above, and the network device is used to implement the method of the fourth aspect described above; or the terminal device is used to implement the method of the fifth aspect described above, and the network device is used to implement the method of the sixth aspect described above.

[0060] In a tenth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions that, when executed by a processor, can implement the methods of any one of the first to sixth aspects described above.

[0061] Eleventhly, embodiments of this application also provide a computer program product, including a computer program or instructions, which, when executed by a processor, can implement the methods of any one of the first to sixth aspects described above.

[0062] In a twelfth aspect, embodiments of this application also provide a chip system including a processor, the processor being coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, the methods of any one of the first to sixth aspects described above can be implemented.

[0063] The technical effects achievable by the second to twelfth aspects mentioned above are similar to those achievable by the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0064] Figure 1 A schematic diagram of the architecture of the communication network provided in the embodiments of this application;

[0065] Figure 2A , Figure 2B and Figure 2C A schematic diagram of the duplex mode provided for the embodiments of the application;

[0066] Figure 3 A schematic diagram of the four-step random access process provided for the application embodiment;

[0067] Figure 4 A schematic diagram of a two-step random access process provided for the application embodiment;

[0068] Figure 5 , Figure 7 , Figure 8 A schematic diagram of the communication method provided in the application embodiment;

[0069] Figure 6 A schematic diagram of the time slot distribution of PRACH and the first PUSCH provided for the application embodiment;

[0070] Figure 9 A schematic diagram of the transmission of the second PUSCH provided for the application embodiment;

[0071] Figure 10 A schematic diagram illustrating the determination of the transmission power of the second PUSCH provided in the application embodiment;

[0072] Figure 11 This is a schematic diagram of the PHR sending process provided in an embodiment of this application;

[0073] Figure 12 and Figure 13 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0074] Figure 14 This is a block diagram of a baseband chip provided in an embodiment of this application. Detailed Implementation

[0075] This application provides a communication method and apparatus. The method and apparatus are based on the same inventive concept. Since the principles by which the method and apparatus solve problems are similar, their implementations can be mutually referenced, and repeated details will not be repeated.

[0076] Figure 1 A schematic diagram of a possible, non-limiting communication network is shown. (e.g.) Figure 1 As shown, the communication network 10 includes a radio access network (RAN) 100 and a core network (CN) 200. RAN 100 includes at least one RAN node (e.g., ...). Figure 1 110a and 110b (collectively referred to as RAN node 110) and at least one terminal device (such as Figure 1 120a-120j in RAN 100 are collectively referred to as terminal equipment 120. RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment. Figure 1 (Not shown in the image). Terminal device 120 is connected to RAN node 110 wirelessly. RAN node 110 is connected to core network 200 wirelessly or via wired connection. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0077] RAN 100 can be a cellular network related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication networks, or future communication networks. RAN 100 can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) network. RAN 100 can also be a communication network that integrates two or more of the above systems.

[0078] Understandable, Figure 1 This application only illustrates one possible communication network that can be applied to an embodiment of this application. In other possible scenarios, the communication network may also include other devices.

[0079] RAN node 110, sometimes also referred to as access network equipment, RAN entity, access node, network equipment, etc., constitutes part of the communication network and is used to help terminal devices achieve wireless access. Multiple RAN nodes 110 in the communication network 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal device 120 are relative, for example, Figure 1 Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminal devices 120j that access RAN 100 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal device. RAN node 110 and terminal device 120 are sometimes referred to as communication devices, for example... Figure 1 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal equipment functions.

[0080] In one possible scenario, a RAN node can be a base station (BS), an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future communication network, or an access node in a WiFi network, etc. A RAN node can also be a macro base station (such as...). Figure 1 110a), micro base stations or indoor stations (such as Figure 1The RAN node can be a relay node or donor node (as described in section 110b), or a wireless controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the RAN node in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0081] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0082] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an O-RAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0083] Terminal devices, also known as terminals, user equipment (UE), mobile stations, mobile terminals, etc., are devices used to provide voice or data connectivity to users, and can also be Internet of Things (IoT) devices. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), 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. Terminal devices can be: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, smart glasses, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, smart point of sale (POS) machines, customer-premises equipment (CPE), light user equipment (UE), reduced capability user equipment (REDCAP UE), wireless terminals in industrial control, smart home devices (such as refrigerators, televisions, air conditioners, electricity meters, etc.), smart robots, robotic arms, workshop equipment, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, and flying equipment (such as smart robots, hot air balloons, drones, airplanes), etc. The terminal device can also be a vehicle device, such as a complete vehicle device, an in-vehicle module, an in-vehicle chip, an onboard unit (OBU), or a telematics box (T-BOX). The terminal device can also be other devices with terminal functions; for example, it can be a device that performs terminal functions in D2D communication. The embodiments of this application do not limit the form of the terminal device.

[0084] Communication between wireless access network devices and terminal devices, as well as between terminal devices, can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication between wireless access network devices and terminal devices, as well as between terminal devices, can also be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used between wireless access network devices and terminal devices.

[0085] To facilitate understanding by those skilled in the art, some terms used in this application are explained below.

[0086] 1) Duplex mode.

[0087] The duplex modes available in new radio (NR) include FDD and TDD. Figure 2A , Figure 2B and Figure 2C The diagram illustrates the duplex mode provided in the application embodiment, where D represents downlink, U represents uplink, F represents flexible, f represents the frequency domain, and t represents the time domain. For FDD, refer to... Figure 2A The diagram shown illustrates the duplex mode. In slot 0, downlink transmission can occur on the DL BWP, and uplink transmission can occur on the UL BWP in slot 0. The DL BWP and UL BWP are located on different carriers and are separate in the frequency domain.

[0088] For TDD, refer to Figure 2BThe diagram illustrates duplex mode. The DL BWP and UL BWP share the same center frequency. Their bandwidths can be the same or different. At any given time, the terminal device can only perform uplink or downlink transmission. For example, in time slot 0, only downlink transmission is possible; in time slot 4, only uplink transmission is possible; and time slot 3 is a flexible time slot, meaning it can be used for either uplink or downlink transmission, but not simultaneously. The smallest granularity of uplink / downlink transmission handover is a symbol. For example, time slot 3 is a flexible time slot, consisting of 14 or 12 orthogonal frequency division multiplexing (OFDM) symbols. The first M symbols are downlink symbols, the last N symbols are uplink symbols, and the middle 14-MN (or 12-MN) symbols are flexible symbols. 0 <= M <= 14 (or 0 <= M <= 12), 0 <= N <= 14 (or 0 <= N <= 12), M+N <= 14 (or M+N <= 12). Downlink symbols can be used for downlink transmission, uplink symbols can be used for uplink transmission, and flexible symbols can be used for both uplink and downlink transmission. The specific transmission direction can be notified to the terminal device by the network device through radio resource control (RRC) signaling or downlink control information (DCI) scheduling.

[0089] Compared to FDD, TDD typically occupies less frequency domain resources. However, because uplink and downlink transmissions cannot occur simultaneously in TDD (for example, only downlink transmission can occur in time slot 0, and uplink transmission cannot occur), uplink transmission delay will increase.

[0090] To address the latency issue of TDD, the standard is discussing flexible duplex, which can be understood as subband full duplex (SBFD), or complementary TDD (C-TDD), or full duplex, etc. Its core idea is that uplink and downlink transmission resources can be configured simultaneously on a certain symbol or time slot of TDD.

[0091] For SBFD, refer to Figure 2CThe diagram illustrates a duplex mode where, within a time slot (e.g., time slot 0), a frequency domain resource exists within the DLBWP. Uplink transmission can occur on this frequency domain resource, allowing uplink transmission to take place on time slot 0, thus reducing uplink latency. This frequency domain resource is typically called the uplink subband. Downlink transmission can also occur on time slot 0. Network devices can perform simultaneous uplink and downlink transmissions on time slot 0 (limited to either the uplink or downlink subband). Terminal devices (such as full-duplex terminal devices) can also perform simultaneous uplink and downlink transmissions on time slot 0. Conversely, terminal devices (such as half-duplex terminal devices) can perform only uplink or downlink transmissions. Compared to TDD, SBFD provides more uplink resources, increasing uplink coverage and reducing uplink latency.

[0092] 2) Random access (RA).

[0093] Random access is divided into 4-step random access and 2-step random access. (See reference...) Figure 3 The diagram illustrates a four-step random access process. The terminal device receives configuration information from the network device and can determine the PRACH time-frequency resources based on this information. Step 1: The terminal device sends a random access preamble (message msg1) to the network device on a determined PRACH time-frequency resource. Step 2: After receiving the random access preamble, the network device sends a random access response (RAR) to the terminal device (message 2). The RAR may include parameters such as the random access preamble, uplink data timing advance, and uplink resource configuration information for sending PUSCH (i.e., uplink data). Step 3: If the random access preamble indicated by the sequence number in the RAR is the same as the random access preamble sent by the terminal device to the network device in Step 1, the terminal device determines that the random access response is for it. The terminal device then sends the PUSCH to the network device based on the PUSCH time-frequency resources indicated in the RAR for scheduled transmission. Step 4: The network device receives the PUSCH sent by the terminal device and sends a contention resolution message to the terminal device, i.e., message 4 (msg4). The network device will carry a unique identifier in the contention resolution message to specify the terminal device that has successfully accessed the network, while other terminal devices that have not successfully accessed the network will re-initiate random access.

[0094] Reference Figure 4The diagram illustrates a two-step random access procedure. The terminal device receives configuration information from the network device, which determines the PRACH and PUSCH time-frequency resources. Step 1: The terminal device sends message A (msgA) to the network device based on the configured PRACH and PUSCH time-frequency resources. msgA contains the random access preamble and PUSCH (i.e., uplink data), which can be understood as equivalent to steps 1 and 3 in a four-step random access procedure. After receiving msgA from the terminal device, the network device sends msgB to the terminal device. msgB can be used to send a random access response and / or conflict resolution information, which can be understood as equivalent to steps 2 and 4 in a four-step random access procedure.

[0095] 3) Power control of PUSCH.

[0096] The transmission power (also known as transmit power or transmit power) of a PUSCH can be expressed as P PUSCH,b,f,c (i,j,q d ,l), where b is the activated UL BWP, f is the carrier, c is the serving cell, i is the transmission occasion of the PUSCH, j is the parameter set configuration with index j, q d l is the reference signal index, and l is the power control adjustment state index (PUSCH power control adjustment state with index l).

[0097]

[0098] P CMAX,f,c (i) represents the maximum output power configured for the terminal device (e.g., UE), P O_PUSCH,b,f,c (j) can be understood as the expected received power of PUSCH, P O_PUSCH,b,f,c (j)=P O_NOMINAL_PUSCH,f,c (j)+P O_UE_PUSCH,b,f,c (j).

[0099] (1) If the terminal device establishes an RRC connection with the network (such as a network device) using a 4-step random access procedure (also known as a 4-step random access channel (RACH)) and does not configure a P0-PUSCH alpha set (P0-PUSCH-AlphaSet); or, for the initial transmission and retransmission of msg3 PUSCH.

[0100] j = 0, P O_UE_PUSCH,b,f,c (0) = 0, PO_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3

[0101] P O_PRE This can be understood as the PRACH power that the network device expects to receive, or the target receive power of the PRACH, which can be configured through the signaling preambleReceivedTargetPower. PREAMBLE,Msg3 This is configured using either Message3-DeltaPreamble or DeltaPreamble. If not configured, it defaults to 0. Δ PREAMBLE,Msg3 This can be understood as the power difference between PRACH and PUSCH.

[0102] (2) If the terminal device uses a 2-step random access procedure (i.e., 2-step RACH) to establish an RRC connection and does not configure P0-PUSCH-AlphaSet; or, for msgA PUSCH.

[0103] j = 0, P O_UE_PUSCH,b,f,c (0) = 0, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH

[0104] P O_PRE This is configured by Message A - Preamble Target Power (msgA-preambleReceivedTargetPower). If msgA-preambleReceivedTargetPower is not configured, then it is configured by preambleReceivedTargetPower. Δ MsgA_PUSCH It is configured using the message A-delta preamble (msgA-DeltaPreamble) or deltaPreamble. If not configured, then Δ MsgA_PUSCH =Δ PREAMBLE,Msg3 .

[0105] (3) j=1 corresponds to the initial transmission and retransmission of the configured grant (CG)PUSCH.

[0106] P O_PUSCH,b,f,c (1) = P O_NOMINAL_PUSCH,f,c (1)+P O_UE_PUSCH,b,f,c (1)

[0107] P O_NOMINAL,PUSCH,f,c (1) is configured with p0 nominal without grant (p0-NominalWithoutGrant). If not configured, then PO_NOMINAL,PUSCH,f,c (1) = P O_NOMINAL,PUSCH,f,c (0).

[0108] P O_UE_PUSCH,b,f,c (1) is configured for network devices.

[0109] (4) j≥2 corresponds to dynamic grant (DG)PUSCH.

[0110] P O_PUSCH,b,f,c (j)=P O_NOMINAL_PUSCH,f,c (j)+P O_UE_PUSCH,b,f,c (j)

[0111] At this time, P O_NOMINAL,PUSCH,f,c (j) is configured by p0 nominal authorization (p0-NominalWithGrant). If not configured, it is equal to P. O_NOMINAL,PUSCH,f,c (0).

[0112] P O_UE_PUSCH,b,f,c (j) refers to the network device configuration.

[0113] In addition, the above α b,f,c (j) represents the road loss compensation factor; PUSCH bandwidth, which is the number of resource blocks (RBs) it contains; PL b,f,c (q d ) represents the downlink path loss; Δ TF,b,f,c (i) are parameters related to the transmission format (such as modulation method); f b,f,c (i,l) represents the power control adjustment state.

[0114] 4) In the description of this application, terms such as "first" and "second" are used only to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects. For example, "first PUSCH" and "second PUSCH" do not indicate a difference in priority or importance between the two PUSCHs.

[0115] 5) In the embodiments of this application, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0116] 6) In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logic module within a device sending information to another logic module. For example, "device A sending information" can be understood as device A sending information to another device (device B), or it can be understood as logic module 1 in device A sending information to logic module 2 in device A. In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as one logic module within a device receiving information from another logic module. For example, "device A receiving information" can be understood as device A receiving information from another device (such as device B), or it can be understood as logic module 1 in device A receiving information from logic module 2 in device A. In this application, "sending information to… (e.g., device B)" or the relevant illustrations in the accompanying drawings can be understood as the destination of the information being device B. This can include sending information directly or indirectly to device B. The phrases "receiving information from... (e.g., device A)," "receiving information from... (e.g., device A)," or "receiving information sent by (e.g., device A)," or the relevant illustrations in the accompanying drawings, can be understood as indicating that the source of the information is device A, which may include receiving information directly or indirectly from device A. The information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be repeated here.

[0117] In addition, in the embodiments of this application, the term "transmitting PUSCH" can refer to transmitting data carried by PUSCH, or it can be described as transmitting uplink data or transmitting uplink transmission; "receiving PUSCH" can refer to receiving data carried by PUSCH, or it can be described as receiving uplink data or receiving uplink transmission.

[0118] As can be seen from the above introduction to duplex modes, the duplex mode of SBFD is different from that of TDD and FDD. The channel environment of PUSCH in the duplex mode of SBFD is also different from that of TDD and FDD. Therefore, how to control the power of PUSCH in random access and other processes is a problem that needs to be considered.

[0119] Based on this, embodiments of this application provide a communication method and apparatus to support separate power control of PUSCH in SBFD time domain units and in non-SBFD time domain units, thereby improving the performance of PUSCH in random access procedures and reducing the initial access latency of terminal devices. The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0120] Figure 5 This is one of the schematic diagrams of a communication method provided in an embodiment of this application. Figure 5 This application illustrates the method using terminal devices and network devices (such as access network devices) as the execution subjects of this interaction, but it does not limit the execution subjects of this interaction. For example, a terminal device can also be a module applied to a terminal device, such as a circuit, chip, chip system, or processor; it can also be a logical node, logical module, or software that can implement all or part of the functions of the terminal device. Similarly, a network device can also be a module applied to an access network device, such as a circuit, chip, chip system, or processor; it can also be a logical node, logical module, or software that can implement all or part of the functions of the access network device. Figure 5 As shown, the method includes:

[0121] S501: The network device sends the first information, and the terminal device receives the first information accordingly.

[0122] The first information indicates a first power offset corresponding to the PRACH in the SBFD time domain cell and the PUSCH in the non-SBFD time domain cell, and / or a second power offset corresponding to the PRACH in the non-SBFD time domain cell and the PUSCH in the SBFD time domain cell.

[0123] The first power offset corresponding to PRACH in an SBFD time-domain cell and PUSCH in a non-SBFD time-domain cell can be understood as follows: when PRACH is in an SBFD time-domain cell and PUSCH is in a non-SBFD time-domain cell, the first power offset is used to determine the transmission power of PUSCH, or to determine the transmission power of PUSCH in a non-SBFD time-domain cell. In other words, the first power offset is applied when PRACH is in an SBFD time-domain cell and PUSCH is in a non-SBFD time-domain cell.

[0124] The second power offset corresponding to PRACH in a non-SBFD time domain and PUSCH in an SBFD time domain can be understood as follows: when PRACH is in a non-SBFD time domain and PUSCH is in an SBFD time domain, the second power offset is used to determine the transmission power of PUSCH, or to determine the transmission power of PUSCH in an SBFD time domain. In other words, the second power offset is applied when PRACH is in a non-SBFD time domain and PUSCH is in an SBFD time domain.

[0125] Among them, the time domain unit can be OFDM symbol (hereinafter referred to as symbol), time slot, micro-time slot, subframe, half frame, etc.

[0126] Taking time-domain units as symbols as an example, a symbol can be an uplink symbol, a downlink symbol, a flexible symbol, an SBFD symbol, or a non-SBFD symbol.

[0127] Uplink symbol (denoted as U symbol): The frequency domain resources on the uplink symbol can be used for uplink transmission, that is, downlink transmission cannot be performed on this symbol;

[0128] Downlink symbol (denoted as D symbol): The frequency domain resources on the downlink symbol can be used for downlink transmission, that is, uplink transmission cannot be performed on this symbol;

[0129] Flexible symbols (denoted as F symbols): The frequency domain resources on flexible symbols can be used for uplink or downlink transmission, and the transmission direction of flexible symbols can be determined based on control signaling.

[0130] SBFD Symbol: A symbol may be called an SBFD symbol if its frequency domain resources include frequency domain resources for uplink transmission (e.g., referred to as an uplink subband or uplink-available frequency domain resources) and frequency domain resources for downlink transmission (e.g., referred to as a downlink subband or downlink-available frequency domain resources). A guard band may also exist between the downlink and uplink subbands. The frequency domain resources on a symbol can be understood as the frequency domain resources across the entire BWP. This BWP can be a downlink BWP, such as an active downlink BWP. More specifically, for example, if an uplink subband is configured within the entire frequency domain resources of an active downlink BWP on a symbol, then the frequency domain resources on that symbol include both uplink and downlink subbands, and this symbol can be an SBFD symbol. It is understandable that when a network device configures frequency domain resources for uplink transmission on a downlink symbol or a flexible symbol, the symbol can be understood as an SBFD symbol, because at this time, the symbol contains both time-frequency resources for uplink transmission and time-frequency resources for downlink transmission, and uplink and downlink transmission can be performed simultaneously. For example, the network device can perform uplink and downlink transmission simultaneously.

[0131] Non-SBFD symbols: These can be understood as symbols that can only be used for uplink or downlink transmission, or symbols that only have time-frequency resources for uplink or downlink transmission. For example, uplink symbols, downlink symbols, and flexible symbols used only for downlink or uplink transmission can be collectively referred to as non-SBFD symbols.

[0132] It should be understood that the above examples are based on time-domain units. The same applies to time slots, subframes, half-frames, etc.

[0133] In the embodiments of this application, the network device may indicate (or configure) a corresponding first power offset for the PRACH of the SBFD time domain unit and the PUSCH of the non-SBFD time domain unit, and / or the network device may indicate (or configure) a corresponding second power offset for the PRACH of the non-SBFD time domain unit and the PUSCH of the SBFD time domain unit.

[0134] In one possible implementation, the first power offset can be the power difference between the PRACH in the SBFD time domain cell and the PUSCH in the non-SBFD time domain cell, and the second power offset can be the power difference between the PRACH in the non-SBFD time domain cell and the PUSCH in the SBFD time domain cell.

[0135] In addition, in the embodiments of this application, the network device may indicate a first power offset and / or a second power offset for 2-step random access and 4-step random access, respectively.

[0136] As an example: For a 2-step random access procedure, the first information can be used to indicate the first power offset for the PRACH in the SBFD time domain unit and the PUSCH in the non-SBFD time domain unit (e.g., msgA PUSCH in the 2-step random access procedure, hereinafter referred to as msgA PUSCH); for the PRACH in the non-SBFD time domain unit and the PUSCH in the SBFD time domain unit (e.g., msgA PUSCH), the first information can be used to indicate the second power offset.

[0137] For the 4-step random access, the first information can be used to indicate the first power offset for the PRACH in the SBFD time domain unit and the PUSCH in the non-SBFD time domain unit (such as the PUSCH in msg3, hereinafter referred to as msg3 PUSCH); the first information can be used to indicate the second power offset for the PRACH in the non-SBFD time domain unit and the PUSCH in the SBFD time domain unit (such as msg3PUSCH).

[0138] It is understood that if a first power offset and / or a second power offset are indicated for 2-step random access and 4-step random access respectively, the first power offset and / or the second power offset indicated for 2-step random access and 4-step random access respectively may be the same or different, and this application does not limit this.

[0139] In this embodiment of the application, the network device may also indicate the first power offset and / or the second power offset only for the 4-step random access.

[0140] In one possible implementation, the network device can also send other information to the terminal device, such as one or more of the following: PRACH configuration index (prach-ConfigurationIndex), subcarrier spacing, frequency domain start position, preambleReceivedTargetPower, msg3-DeltaPreamble, deltaPreamble, msgA-preambleReceivedTargetPower, msgA-DeltaPreamble, etc. The prach-ConfigurationIndex can be used to indicate the PRACH time-frequency resource configuration, the subcarrier spacing can be the PRACH subcarrier spacing, and the frequency domain start position can be used to indicate the PRACH frequency domain start position (or understood as the frequency domain start position of RACH occurrence, RO). The meanings of preambleReceivedTargetPower, msg3-DeltaPreamble, deltaPreamble, msgA-preambleReceivedTargetPower, and msgA-DeltaPreamble can be referred to the description of the PUSCH power control section above, and will not be repeated here.

[0141] Network devices can send initial information to terminal devices via broadcast, multicast, or other methods. For example, network devices can send initial information to terminal devices via system messages (such as system information block (SIB) 1) or via RRC messages.

[0142] In one possible implementation, if the terminal device has not established an RRC connection with the network device, after receiving SIB1, the terminal device can also send PRACH to the network device to initiate random access.

[0143] As an example: The terminal device can determine the PRACH time-frequency resources based on the PRACH time-frequency resource configuration indicated by prach-ConfigurationIndex, and transmit the PRACH on those resources. The network device receives the PRACH. It can be understood that the PRACH carries a random access preamble; transmitting the PRACH can also be called transmitting the random access preamble or simply receiving the preamble.

[0144] S502: The terminal device sends the first PUSCH, and the network device receives the first PUSCH accordingly.

[0145] The transmission power of the first PUSCH is determined based on the aforementioned first information.

[0146] Optionally, the first PUSCH can be a PUSCH in the random access procedure. For example, the first PUSCH can be the msgA PUSCH in a 2-step random access procedure, or it can be the msg3 PUSCH in a 4-step random access procedure, including the initial transmission or retransmission of the msg3 PUSCH. This random access procedure can be a contention-based random access procedure, or it can include a contention-based random access procedure. In this case, the PRACH is also the PRACH in the random access procedure.

[0147] In the random access procedure, the terminal device sends a PRACH, and then sends a PUSCH (i.e., the first PUSCH). If the PRACH is in an SBFD time domain cell and the first PUSCH is in a non-SBFD time domain cell, the transmission power of the first PUSCH is determined using a first power offset. If the PRACH is in a non-SBFD time domain cell and the first PUSCH is in an SBFD time domain cell, the transmission power of the first PUSCH is determined using a second power offset.

[0148] After receiving the first information, the terminal device can send the first PUSCH based on the first information. Taking the time domain unit as an example, refer to... Figure 6 The diagram showing the time slot distribution of PRACH and the first PUSCH is shown below. Figure 6 In (A), the PRACH is on the SBFD time slot (slot 1), and the first PUSCH is on a non-SBFD time slot (slot 4). The transmission power of the first PUSCH can be determined based on the first power offset. Figure 6 In (B), the PRACH is on a non-SBFD time slot (time slot 4), and the first PUSCH is on an SBFD time slot (time slot 7). The transmission power of the first PUSCH can be determined based on the second power offset.

[0149] For example: taking the first power offset as the power difference between the PRACH in the SBFD time domain unit and the PUSCH in the non-SBFD time domain unit, and the second power offset as the power difference between the PRACH in the non-SBFD time domain unit and the PUSCH in the SBFD time domain unit, and taking the first PUSCH as the msg3 PUSCH in msg3 of the 4-step random access procedure as an example, the terminal device can determine the transmission power of the first PUSCH according to the following formula.

[0150]

[0151] Where j = 0, P O_PUSCH,b,f,c (0)=PO_NOMINAL_PUSCH,f,c (0)+P O_UE_PUSCH,b,f,c (0), P PUSCH,b,f,c (i,j,q d ,l) represents the transmission power of the first PUSCH (i.e., msg3 PUSCH), P O_UE_PUSCH,b,f,c (0) = 0.

[0152] When PRACH is in the SBFD time domain, and the first PUSCH is in a non-SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Δ PREAMBLE,Msg3 This is configured in the first configuration information. If the first configuration information is not configured, the value configured in msg3-DeltaPreamble or deltaPreamble can be used. If neither msg3-DeltaPreamble nor deltaPreamble is configured, the default value is 0. In this case, Δ PREAMBLE,Msg3 This can be understood as the first power offset. Specifically, the first configuration information can be understood as configuring Δ for this scenario, where PRACH is in the SBFD time domain and the first PUSCH is in a non-SBFD time domain. PREAMBLE,Msg3 For example: the first configuration information can specifically be NonSBFDmsg3-DeltaSBFDPreamble.

[0153] When PRACH is in a non-SBFD time-domain cell, and the first PUSCH is in an SBFD time-domain cell, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Δ PREAMBLE,Msg3 This is configured in the second configuration information. If the second configuration information is not configured, the value configured in msg3-DeltaPreamble or deltaPreamble can be used. If neither msg3-DeltaPreamble nor deltaPreamble is configured, the default value is 0. In this case, Δ PREAMBLE,Msg3 This can be understood as the second power offset. Specifically, the second configuration information can be understood as configuring Δ for this scenario, where PRACH is in a non-SBFD time domain unit and the first PUSCH is in an SBFD time domain unit. PREAMBLE,Msg3 For example: the second configuration information can specifically be SBFDmsg3-DeltaNonSBFDPreamble.

[0154] When PRACH is in the SBFD time domain, the first PUSCH is in the SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 ΔPREAMBLE,Msg3 This is configured using the third configuration information. If the third configuration information is not configured, the value configured by msg3-DeltaPreamble or deltaPreamble can be used. If neither msg3-DeltaPreamble nor deltaPreamble is configured, the default value is 0. In this case, Δ PREAMBLE,Msg3 This can be understood as the third power offset. Specifically, the third configuration information can be understood as configuring Δ for this scenario, where PRACH is in the SBFD time domain and the first PUSCH is in the SBFD time domain. PREAMBLE,Msg3 Yes. Because the interference on the time domain cells of SBFD may be different from the interference on the time domain cells of non-SBFD.

[0155] When PRACH is in a non-SBFD time domain, and the first PUSCH is in a non-SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Δ PREAMBLE,Msg3 This is configured in the fourth configuration information. If the fourth configuration information is not configured, it defaults to 0. In this case, Δ PREAMBLE,Msg3 This can be understood as the fourth power offset. Specifically, the fourth configuration information can be understood as configuring Δ for this scenario, where PRACH is in a non-SBFD time domain unit and the first PUSCH is in a non-SBFD time domain unit. PREAMBLE,Msg3 The fourth configuration information can specifically be msg3-DeltaPreamble or deltaPreamble.

[0156] In one possible implementation, the first information may include one or more of the first configuration information, the second configuration information, the third configuration information, or the fourth configuration information. That is, the network device may indicate one or more of the first power offset, the second power offset, the third power offset, or the fourth power offset to the terminal device.

[0157] In one possible implementation, the third power offset can be equal to the fourth power offset, or the value of the third power offset can be equal to the value of the fourth power offset. In this case, it can be understood that the third configuration information and the fourth configuration information are the same, for example, both are msg3-DeltaPreamble or deltaPreamble.

[0158] In one possible implementation, the first power offset can be equal to the second power offset, or the value of the first power offset can be equal to the value of the second power offset. In this case, it can be understood that the first configuration information and the second configuration information are the same.

[0159] It should be understood that, alternatively, if the first configuration information is not configured, the value of the first power offset can be the value configured by the second configuration information. Alternatively, if the second configuration information is not configured, the value of the second power offset can be the value configured by the first configuration information.

[0160] Through the above design, when the time domain unit types of PRACH and the first PUSCH (such as msg3 PUSCH) are the same (e.g., both are SBFD time domain units or non-SBFD time domain units), considering that the channel environment experienced by PRACH and the first PUSCH is similar, the transmission power of the first PUSCH can be determined based on the power offset indicated by msg3-DeltaPreamble or deltaPreamble, i.e., the power difference between PRACH and PUSCH. When the time domain unit types of PRACH and the first PUSCH are different, the transmission power of the first PUSCH can be determined based on the first power offset or the second power offset indicated by the first information (e.g., the first configuration information or the second configuration information) (e.g., the first power offset indicated by NonSBFDmsg3-DeltaSBFDPreamble, or the second power offset indicated by SBFDmsg3-DeltaNonSBFDPreamble). This makes the determined transmission power of the first PUSCH more compatible with the channel environment of the first PUSCH transmission, which is beneficial to improving the performance of the first PUSCH. Because the power difference between PRACH on a non-SBFD time-domain unit and msg3 PUSCH on an SBFD time-domain unit, and the power difference between PRACH on an SBFD time-domain unit and msg3 PUSCH on a non-SBFD time-domain unit, these two power differences may be different. This is mainly because the antennas of the network devices on the SBFD time-domain unit and the non-SBFD time-domain unit may be different.

[0161] For China P PUSCH,b,f,c (i,j,q d The parameters in l) (such as α) b,f,c The meaning of (j) etc. can be found in the introduction of the power control section of PUSCH above, and will not be repeated here.

[0162] In yet another possible implementation, the above Δ PREAMBLE,Msg3 Existing methods can be used, such as the values ​​configured using msg3-DeltaPreamble or deltaPreamble. The first power offset can also be understood as the transmission power of the PUSCH in the case of PRACH in SBFD time domain units and PUSCH in non-SBFD time domain units, or as a parameter (such as Δ) used to determine the transmission power of the PUSCH. PREAMBLE,Msg3The correction value; the second power offset can also be understood as the power offset of the PUSCH transmission power or a parameter (such as Δ) used to determine the PUSCH transmission power when the PRACH is in a non-SBFD time domain unit and the PUSCH is in an SBFD time domain unit. PREAMBLE,Msg3 The correction value is [value]. The first power offset and the second power offset can be configured by the network device. When the PRACH is on an SBFD time domain unit and the first PUSCH is on a non-SBFD time domain unit, the terminal device can determine the transmission power of the first PUSCH based on the first power offset; when the PRACH is on a non-SBFD time domain unit and the first PUSCH is on an SBFD time domain unit, the terminal device can determine the transmission power of the first PUSCH based on the second power offset.

[0163] Taking the first PUSCH as an example in the 4-step random access procedure, the terminal device can determine the transmission power of the first PUSCH according to the following formula.

[0164]

[0165] Where j = 0, P O_PUSCH,b,f,c (0)=P O_NOMINAL_PUSCH,f,c (0)+P O_UE_PUSCH,b,f,c (0), P PUSCH,b,f,c (i,j,q d ,l) represents the transmit power of the first PUSCH, P O_UE_PUSCH,b,f,c (0) = 0.

[0166] When PRACH is in the SBFD time domain, and the first PUSCH is in a non-SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 +offset1. Where offset1 represents the first power offset, the value of which can be configured in the first configuration information. Δ PREAMBLE,Msg3 Please refer to the description of the power control section of the PUSCH above; further details are omitted here. At this point, the power offset between the PRACH and the first PUSCH can be understood as Δ. PREAMBLE,Msg3 +offset1.

[0167] When PRACH is in a non-SBFD time-domain cell, and the first PUSCH is in an SBFD time-domain cell, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 +offset2; where offset2 represents the second power offset, the value of which can be configured using the second configuration information. Δ PREAMBLE,Msg3Please refer to the description of the power control section of the PUSCH above; further details are omitted here. At this point, the power offset between the PRACH and the first PUSCH can be understood as Δ. PREAMBLE,Msg3 +offset2.

[0168] When the PRACH and the first PUSCH reside in the same time-domain cell type (e.g., both PRACH and the first PUSCH are in SBFD time-domain cells, or both PRACH and the first PUSCH are in non-SBFD time-domain cells), the channel environments experienced by PRACH and the first PUSCH are similar. Therefore, it can be assumed that there is no power offset or the power offset is 0, i.e., offset1 = 0, offset2 = 0. The meaning of each parameter in the above formula can be found in the introduction to the power control section of PUSCH above, and will not be repeated here.

[0169] It should be understood that when PRACH is in a non-SBFD time domain cell and the first PUSCH is in an SBFD time domain cell, or when PRACH is in an SBFD time domain cell and the first PUSCH is in a non-SBFD time domain cell, the aforementioned first power offset and second power offset can also be used to adjust P... O_UE_PUSCH,b,f,c (0) Make corrections.

[0170] As an example: when PRACH is in the SBFD time domain and PUSCH is in the non-SBFD time domain, P... O_UE_PUSCH,b,f,c (0) = offset1, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 ;

[0171] When PRACH is in a non-SBFD time domain cell and PUSCH is in an SBFD time domain cell, P O_UE_PUSCH,b,f,c (0) = offset2, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 .

[0172] When the PRACH is in a non-SBFD time domain unit and the first PUSCH is in an SBFD time domain unit, or when the PRACH is in an SBFD time domain unit and the first PUSCH is in a non-SBFD time domain unit, the transmit power P of the first PUSCH is... PUSCH,b,f,c (i,j,q d ,l), can be based on the modified P O_UE_PUSCH,b,f,c (0) OK.

[0173] In one possible implementation, the value of the second power offset can also be determined by the value of the first power offset, or the value of the first power offset can be determined by the value of the second power offset. The first information can indicate (or configure) only one of the power offsets (such as the first offset value or the second offset value) to save signaling overhead.

[0174] As an example: the value of the first power offset is X, and the value of the second power offset is -X, where X is an integer. That is, the values ​​of the first power offset and the second power offset are opposites. Network devices can indicate the first power offset or the second power offset through the first information to save signaling.

[0175] Taking the network device indicating a first power offset offset1 through first information (such as first configuration information) as an example, then the above P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 +offset2 can be replaced with P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 -offset1, the above P O_UE_PUSCH,b,f,c (0) = offset2 can be replaced with P O_UE_PUSCH,b,f,c (0) = -offset1, the network device can only indicate offset1 to the terminal device to save signaling overhead.

[0176] It is understandable that the aforementioned first power offset (e.g., offset1) and second power offset (e.g., offset2) can also be increased to P. PUSCH,b,f,c (i,j,q d Among the other items of ,l). For example, the above f b,f,c (i,l) can also be adjusted to f b,f,c (i,l)+offset, when PRACH is in the SBFD time domain cell and PUSCH is in the non-SBFD time domain cell, this offset is offset1 (i.e., the first power offset), when PRACH is in the non-SBFD time domain cell and PUSCH is in the SBFD time domain cell, this offset is offset2 (i.e., the second power offset), and in other cases the offset is 0.

[0177] The following examples illustrate 4-step random access and 2-step random access, respectively. Figure 7 and Figure 8 Specific embodiments, for the above Figure 5 The embodiments are described below.

[0178] Figure 7 This is the second schematic diagram of the communication method provided in the embodiments of this application. Figure 7Taking the first PUSCH as the msg3 PUSCH in the 4-step random access procedure, the first power offset being the power difference between the PRACH in the SBFD time domain unit and the PUSCH in the non-SBFD time domain unit, and the second power offset being the power difference between the PRACH in the non-SBFD time domain unit and the PUSCH in the SBFD time domain unit, the method includes:

[0179] S701: The network device sends the first information to the terminal device, and the terminal device receives the first information accordingly.

[0180] The first information may include a first configuration and a second configuration, wherein the first configuration information may be used to indicate a first power offset and the second configuration information may be used to indicate a second power offset.

[0181] In one possible implementation, the network device may also send other information to the terminal device, such as one or more of the following: prach-ConfigurationIndex, subcarrier spacing, preambleReceivedTargetPower, msg3-DeltaPreamble, deltaPreamble, etc.

[0182] S702: The terminal device sends a PRACH, and the network device receives the PRACH.

[0183] A terminal device can send a PRACH to a network device to initiate random access. As an example: the terminal device can determine the PRACH time-frequency resource based on the PRACH time-frequency resource configuration indicated by prach-ConfigurationIndex, send the PRACH on the PRACH time-frequency resource, and the network device receives the PRACH.

[0184] S703: The network device sends a random access response, and the terminal device receives the random access response accordingly.

[0185] The random access response may include information such as the random access preamble and uplink data timing advance, and may also include uplink grant (UL grant), which is the information of the PUSCH time-frequency resources (or the timing of PUSCH transmission) for the terminal device to send the first PUSCH.

[0186] It is understandable that random access responses can be carried in the physical downlink shared channel (PDSCH). The PDSCH can be scheduled by network devices through the physical downlink control channel (PDCCH), for example, by using the DCI carried in the PDCCH to indicate the time and frequency resources of the PDSCH carrying the random access response to the terminal device.

[0187] S704: The terminal device sends the first PUSCH to the network device, and the network device receives the first PUSCH accordingly.

[0188] The transmission power of the first PUSCH is determined based on the aforementioned first information.

[0189] As an example, the terminal device can determine the transmission power of the first PUSCH according to the following formula.

[0190]

[0191] Among them, P O_PUSCH,b,f,c (0)=P O_NOMINAL_PUSCH,f,c (0)+P O_UE_PUSCH,b,f,c (0), P PUSCH,b,f,c (i,j,q d ,l) represents the transmission power of the first PUSCH (i.e., msg3 PUSCH), P O_UE_PUSCH,b,f,c (0) = 0.

[0192] When PRACH is in the SBFD time domain, and the first PUSCH is in a non-SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Δ PREAMBLE,Msg3 It is the first power offset.

[0193] When PRACH is in a non-SBFD time-domain cell, and the first PUSCH is in an SBFD time-domain cell, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Δ PREAMBLE,Msg3 It is the second power offset.

[0194] When PRACH is in the SBFD time domain, the first PUSCH is in the SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Δ PREAMBLE,Msg3 It is the third power offset.

[0195] When PRACH is in a non-SBFD time domain, and the first PUSCH is in a non-SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 Δ PREAMBLE,Msg3 It is the fourth power offset.

[0196] It should be understood that the above-mentioned first power offset, second power offset, third power offset, and fourth power offset are referenced. Figure 5 The descriptions in the embodiments will not be repeated here.

[0197] S705: The network device sends a conflict resolution message to the terminal device, and the terminal device receives the conflict resolution message accordingly.

[0198] As an example: network devices will carry a unique identifier in the conflict resolution message to specify the terminal device that has successfully accessed the network, while other terminal devices that have not successfully accessed the network will re-initiate random access.

[0199] Figure 8 This is the third schematic diagram of the communication method provided in the embodiments of this application. Figure 8 Taking the first PUSCH as the msgA PUSCH in a two-step random access procedure, the first power offset being the power difference between the PRACH in the SBFD time domain unit and the PUSCH in the non-SBFD time domain unit, and the second power offset being the power difference between the PRACH in the non-SBFD time domain unit and the PUSCH in the SBFD time domain unit, the method includes:

[0200] S801: The network device sends the first information to the terminal device, and the terminal device receives the first information accordingly.

[0201] The first information may include a first configuration and a second configuration, wherein the first configuration information may be used to indicate a first power offset and the second configuration information may be used to indicate a second power offset.

[0202] In one possible implementation, the network device may also send other information to the terminal device, such as one or more of the following: prach-ConfigurationIndex, subcarrier spacing, preambleReceivedTargetPower, deltaPreamble, msgA-preambleReceivedTargetPower, msgA-DeltaPreamble, etc.

[0203] S802: The terminal device sends PRACH and the first PUSCH, and the network device receives PRACH and the first PUSCH.

[0204] After receiving the first information, the terminal device can send PRACH and the first PUSCH to the network device to initiate random access.

[0205] For example, the terminal device can determine the transmission power of the first PUSCH according to the following formula.

[0206]

[0207] Where j = 0, P O_PUSCH,b,f,c (0)=P O_NOMINAL_PUSCH,f,c (0)+P O_UE_PUSCH,b,f,c (0), P PUSCH,b,f,c (i,j,q d ,l) represents the transmission power of the first PUSCH (i.e., msgA PUSCH), P O_UE_PUSCH,b,f,c (0) = 0.

[0208] When PRACH is in the SBFD time domain, and the first PUSCH is in a non-SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH Δ MsgA_PUSCH This is the first power offset. It is configured by the first configuration information. If the first configuration information is not configured, then Δ MsgA_PUSCH =Δ PREAMBLE,Msg3 At this time, Δ PREAMBLE,Msg3 The PRACH is in the SBFD time domain, and the first PUSCH is in the non-SBFD time domain. PREAMBLE,Msg3 This can be understood as the Δ when PRACH is in the SBFD time domain and the first PUSCH is in a non-SBFD time domain in a 2-step RACH. MsgA_PUSCH In a 4-step RACH, the PRACH is performed in the SBFD time domain, and the first PUSCH is performed in the non-SBFD time domain. PREAMBLE,Msg3 .

[0209] When PRACH is in a non-SBFD time-domain cell, and the first PUSCH is in an SBFD time-domain cell, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH Δ MsgA_PUSCH This is the second power offset. It is configured by the second configuration information. If the second configuration information is not configured, then Δ MsgA_PUSCH =Δ PREAMBLE,Msg3 At this time, Δ PREAMBLE,Msg3 The PRACH is in a non-SBFD time domain cell, and the first PUSCH is in an SBFD time domain cell. PREAMBLE,Msg3This can be understood as the Δ when PRACH is in a non-SBFD time domain and the first PUSCH is in an SBFD time domain in a 2-step RACH. MsgA_PUSCH In the 4-step RACH, the PRACH is in a non-SBFD time domain cell, and the first PUSCH is in an SBFD time domain cell. Δ PREAMBLE,Msg3 .

[0210] When PRACH is in the SBFD time domain, the first PUSCH is in the SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH Δ MsgA_PUSCH This is the third power offset. It is configured by the third configuration information. If it is not configured, then Δ MsgA_PUSCH =Δ PREAMBLE,Msg3 At this time, Δ PREAMBLE,Msg3 It is the PRACH in the SBFD time-domain cell, and the first PUSCH in the SBFD time-domain cell Δ. PREAMBLE,Msg3 This can be understood as the Δ when PRACH is in the SBFD time domain and the first PUSCH is in the SBFD time domain in a 2-step RACH. MsgA_PUSCH In the 4-step RACH, the PRACH is in the SBFD time domain, and the first PUSCH is in the SBFD time domain, Δ PREAMBLE,Msg3 .

[0211] When PRACH is in a non-SBFD time domain, and the first PUSCH is in a non-SBFD time domain, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH Δ MsgA_PUSCH This is the fourth power offset. The fourth power offset is indicated or configured by msgA-DeltaPreamble or deltaPreamble; if not configured, then Δ MsgA_PUSCH =Δ PREAMBLE,Msg3 At this time, Δ PREAMBLE,Msg3 The PRACH is in a non-SBFD time domain, and the first PUSCH is in a non-SBFD time domain with Δ. PREAMBLE,Msg3 This can be understood as the Δ when PRACH is in a non-SBFD time domain cell and the first PUSCH is in a non-SBFD time domain cell. MsgA_PUSCH In the 4-step RACH, the PRACH is in a non-SBFD time domain, and the first PUSCH is in a non-SBFD time domain, Δ PREAMBLE,Msg3 msgA-DeltaPreamble or deltaPreamble can be understood as the fourth configuration information.

[0212] It should be understood that the first power offset, second power offset, third power offset, fourth power offset, first configuration information, second configuration information, third configuration information, and fourth configuration information can also be referenced. Figure 5 The specific implementation examples will not be described in detail here.

[0213] S803: The network device sends conflict resolution information (i.e., msg B), and the terminal device receives the conflict resolution information accordingly.

[0214] As an example: the conflict resolution message can carry a unique identifier to specify the terminal device that successfully accessed the network, while other terminal devices that failed to access the network will re-initiate random access.

[0215] In some implementations, network devices can also support individual power control of PUSCH in different time domains by indicating the target receive power (i.e., the first PRACH target receive power) of PRACH in the SBFD time domain unit and / or the target receive power (i.e., the second target receive power) of PRACH in non-SBFD time domain units through the second information.

[0216] Taking the first PUSCH as an example of a 4-step random access procedure or a 2-step random access procedure, the network device can indicate the target receive power of the first PRACH (i.e., the target receive power of the PRACH in the SBFD time domain unit) and can also indicate the target receive power of the second PRACH (i.e., the target receive power of the PRACH in the non-SBFD time domain unit).

[0217] Where j = 0, the expected received power P corresponds to the first PUSCH. O_PUSCH,b,f,c (0)=P O_NOMINAL_PUSCH,f,c (0)+P O_UE_PUSCH,b,f,c (0), P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ PREAMBLE,Msg3 (Corresponding to a 4-step random access process), or, P O_NOMINAL,PUSCH,f,c (0)=P O_PRE +Δ MsgA_PUSCH (Corresponds to a 2-step random access process). Δ PREAMBLE,Msg3 Δ MsgA_PUSCH The configuration can be found in the description of the power control section of PUSCH, and will not be repeated here.

[0218] For the target received power P of PRACH O_PRE When PRACH is in the SBFD time domain, regardless of whether the first PUSCH is in the SBFD time domain, P O_PRE This is the first PRACH target received power.

[0219] When PRACH is in a non-SBFD time domain cell, regardless of whether the first PUSCH is in an SBFD time domain cell, P O_PRE This is the target received power for the second PRACH.

[0220] It can be understood as P O_PRE It is related to the time domain unit where PRACH is located, but not to the time domain unit where the first PUSCH is located.

[0221] It should be understood that, in the embodiments of this application, the aforementioned first power offset and / or second power offset, and the first PRACH target receive power and / or second PRACH target receive power, can be applied in combination or individually. That is, the network device may only indicate the first power offset and / or second power offset without indicating the first PRACH target receive power and / or second PRACH target receive power; it may also only indicate the first PRACH target receive power and / or second PRACH target receive power without indicating the first power offset and / or second power offset; or it may indicate both the first PRACH target receive power and / or second PRACH target receive power and indicate the first power offset and / or second power offset.

[0222] Additionally, it is understood that, in the embodiments of this application, the network device may also indicate the path loss compensation factor α for PUSCH in the SBFD time domain unit and in the non-SBFD time domain unit, respectively. b,f,c (j) Power control adjustment status f b,f,c (i,l) and other methods are used to perform independent power control on PUSCH in SBFD time-domain units and in non-SBFD time-domain units. For example, the first α is used to indicate the PUSCH in the SBFD time-domain unit. b,f,c (j) PUSCH indication of the second α for the SBFD time domain unit b,f,c (j) etc.

[0223] After establishing an RRC connection with the network device during random access, the terminal device can also transmit a second PUSCH, which can be a CG PUSCH or a DG PUSCH. Considering that the first PUSCH in the random access procedure may be in a non-SBFD time domain unit or in an SBFD time domain unit, and the target received power of the first PUSCH in a non-SBFD time domain unit and in an SBFD time domain unit may be different, in one possible implementation, the transmission power of the second PUSCH can be determined based on the target received power of the PUSCH in the random access procedure that is closest to the second PUSCH in the time domain.

[0224] As an example, the terminal device can determine the target receive power of the second PUSCH based on the target receive power of the PUSCH (e.g., the first PUSCH) in the random access procedure that is closest to the second PUSCH in the time domain, and then determine the transmit power of the second PUSCH.

[0225] The second PUSCH can be understood as either the CG PUSCH or DG PUSCH following the random access procedure, or the CG PUSCH or DG PUSCH following the end of the random access procedure. Alternatively, it can be understood as the first PUSCH being a PUSCH within the random access procedure, while the second PUSCH is not.

[0226] Taking the first PUSCH as an example in the random access procedure that is closest to the second PUSCH in the time domain, it can be understood that, in the time domain, the first PUSCH is before the second PUSCH, and the first PUSCH is closest to the second PUSCH. For example, the slot where the first PUSCH is located is before the slot where the second PUSCH is located, and the first PUSCH is closest to the second PUSCH.

[0227] In this embodiment, the random access procedure closest to the second PUSCH can be a contention-based random access procedure or a non-contention-based random access procedure. Alternatively, the random access procedure can include both contention-based and non-contention-based random access procedures. The random access procedure can be a 4-step random access procedure or a 2-step random access procedure.

[0228] As an example, the transmit power of the second PUSCH can be determined based on the target receive power of the PUSCH in the most recent random access procedure in the time domain. For instance, in the time domain, if the most recent random access procedure before the second PUSCH is a 4-step random access procedure, then the transmit power of the second PUSCH can be determined based on the target receive power of the PUSCH in that 4-step random access procedure. Similarly, if the most recent random access procedure before the second PUSCH is a 2-step random access procedure, then the transmit power of the second PUSCH can be determined based on the target receive power of the PUSCH in that 2-step random access procedure. In the time domain, the most recent random access procedure before the second PUSCH can be understood as the period between the end of that random access procedure and the second PUSCH, during which no other random access procedures are performed. Alternatively, it can be understood that the transmit power of the second PUSCH after the end of a random access procedure can be determined based on the target receive power of the PUSCH in that random access procedure. Here, the PUSCH in the random access procedure can be understood as the first PUSCH.

[0229] It is understandable that the target received power of the second PUSCH may include the P power corresponding to the second PUSCH. O_NOMINAL_PUSCH,f,c (j) The target received power of the first PUSCH may include the P corresponding to the first PUSCH. O_NOMINAL_PUSCH,f,c (j). For example, if the second PUSCH is a CG PUSCH, j=1, the target received power of the second PUSCH may include P O_NOMINAL_PUSCH,f,c (1). The second PUSCH is a DG PUSCH, j>1, and the target received power of the second PUSCH may include P O_NOMINAL_PUSCH,f,c (j). When the first PUSCH is a PUSCH in the random access procedure, j=0, the target received power of the first PUSCH may include P O_NOMINAL_PUSCH,f,c (0). When the target receive power for the second PUSCH is not configured by the network, P... O_NOMINAL_PUSCH,f,c (j) can be equal to P O_NOMINAL,PUSCH,f,c (0), where j≥1, and j is an integer. For CGPUSCH, j=1, and for DG PUSCH, j>1.

[0230] In this case, the target received power of the second PUSCH is not configured by the network, which may be because the network device does not indicate the P to the terminal device. O_NOMINAL_PUSCH,f,c The value of (j), or the network device does not display an instruction P to the terminal device. O_NOMINAL_PUSCH,f,c The value of (j).

[0231] For CG PUSCH, the network device can explicitly configure P.O_NOMINAL_PUSCH,f,c (1) The value of P. For example, network devices can directly configure P through the signaling p0-NominalWithoutGrant. O_NOMINAL_PUSCH,f,c (1) takes a value, for example, p0-NominalWithoutGrant=-6, then P O_NOMINAL_PUSCH,f,c (1) = -6dBm. Network devices can also be configured without p0-NominalWithoutGrant, then P... O_NOMINAL_PUSCH,f,c (1) can be equal to P O_NOMINAL,PUSCH,f,c (0). For CGPUSCH, the target receive power of the second PUSCH is not configured by the network, which can be understood as p0-NominalWithoutGrant not being configured.

[0232] For DG PUSCH, the network device can display the P configuration. O_NOMINAL_PUSCH,f,c The value of (j), where j>1. For example, network devices can directly configure P through the signaling p0-NominalWithGrant. O_NOMINAL_PUSCH,f,c The value of (j), for example, p0-NominalWithGrant=-6, then P O_NOMINAL_PUSCH,f,c (j) = -6dBm. Network devices can also be configured without p0-NominalWithGrant, then P... O_NOMINAL_PUSCH,f,c (j) can be equal to P O_NOMINAL,PUSCH,f,c (0). For DG PUSCH, the target receive power of the second PUSCH is not configured by the network, which can be understood as p0-NominalWithGrant not being configured.

[0233] It is understandable that the target received power of the second PUSCH can also refer to the P power corresponding to the second PUSCH. O_PUSCH,b,f,c (j), (i.e., P) O_NOMINAL_PUSCH,f,c (j)+P O_UE_PUSCH,b,f,c (j)), the target received power of the first PUSCH can also refer to the P corresponding to the first PUSCH. O_PUSCH,b,f,c (j). For example, if the second PUSCH is a CG PUSCH, j=1, the target received power of the second PUSCH can be P. O_PUSCH,b,f,c (1) When the first PUSCH is a PUSCH in the random access procedure, j=0, the target received power of the first PUSCH can be P O_PUSCH,b,f,c (0), when the target receive power of the second PUSCH is not configured by the network, P O_PUSCH,b,f,c (1) can be equal to P O_PUSCH,b,f,c (0).

[0234] Figure 9The diagram illustrates the transmission of the second PUSCH in an embodiment of this application. After the terminal device establishes an RRC connection with the network device through a four-step random access procedure, the terminal device can send the second PUSCH to the network device. When the second PUSCH is a CGPUSCH, the network device does not configure p0-NominalWithoutGrant (for CG PUSCH); or when the second PUSCH is a DG PUSCH, the network device does not configure p0-NominalWithGrant (for DG PUSCH), the target received power of the second PUSCH can be determined using the PUSCH in the random access procedure that is closest to the second PUSCH in the time domain (e.g., the first PUSCH).

[0235] For example: if the first PUSCH (i.e., msg3 PUSCH) is in an SBFD time domain cell, then the target received power of the second PUSCH is the same as the target received power of the first PUSCH in the SBFD time domain cell. If the first PUSCH (i.e., msg3 PUSCH) is in a non-SBFD time domain cell, then the target received power of the second PUSCH is the same as the target received power of the first PUSCH in the non-SBFD time domain cell. The first PUSCH can be the initial transmission of msg3 PUSCH or a retransmission of msg3 PUSCH.

[0236] Reference Figure 10 The diagram illustrating the determination of the transmission power of the second PUSCH shows that the initial access of the terminal device uses a 2-step random access (i.e., 2-step RACH). After the 2-step random access, the transmission power of the second PUSCH sent by the terminal device can be determined based on the target receive power of the PUSCH (such as msgA PUSCH) in the 2-step random access. If the terminal device subsequently fails to transmit uplink due to reasons such as mobility, it can re-initiate a 4-step random access for uplink synchronization. After the 4-step random access, the transmission power of the second PUSCH sent by the terminal device can be determined based on the target receive power of the PUSCH (such as msg3 PUSCH) in the 4-step random access.

[0237] Alternatively, if the terminal device first performs a 4-step random access and then a 2-step random access, the transmission power of the second PUSCH sent by the terminal device after the 4-step random access can be determined based on the target receive power of the PUSCH (such as msg3 PUSCH) in the 4-step random access; after the 2-step random access, the transmission power of the second PUSCH sent by the terminal device can be determined based on the target receive power of the PUSCH (such as msgAPUSCH) in the 2-step random access. That is, the second PUSCH can be determined using the target receive power of the PUSCH (such as the first PUSCH) in the random access procedure that is closest to the second PUSCH in the time domain.

[0238] After a terminal device randomly accesses the network, it may fail to transmit uplink due to reasons such as movement, and re-initiate random access. If the terminal device re-initiates random access and still determines the transmit power of the second PUSCH based on the target receive power of the PUSCH in the previous random access procedure, the determined transmit power of the second PUSCH may not match the current channel environment, affecting the transmission performance of the second PUSCH.

[0239] In this application, through the above design, even if the network device does not configure the target receive power of the second PUSCH (such as DG PUSCH or CGPUSCH), the terminal device can determine the target receive power of the second PUSCH based on the target receive power of the PUSCH (such as the first PUSCH) in the random access procedure that is closest to the second PUSCH in the time domain. This allows the terminal device to determine the transmit power of the second PUSCH, making the determined transmit power of the second PUSCH more compatible with the current channel environment and improving the transmission performance of the second PUSCH.

[0240] In one possible implementation, the first PUSCH and the second PUSCH are in the same time domain unit type. That is, the transmit power of the second PUSCH can also be determined based on the target receive power of the PUSCH in the random access procedure (e.g., the first PUSCH) that is in the same time domain unit type as the second PUSCH and is closest to the second PUSCH in the time domain.

[0241] As an example: If a terminal device performs a 4-step random access, during which it sends a PUSCH (e.g., the initial transmission of msg 3PUSCH, denoted as PUSCH A) in the SBFD time domain and also sends a PUSCH (e.g., a retransmission of msg 3PUSCH, denoted as PUSCH B) in a non-SBFD time domain, then after the 4-step random access is completed, the terminal device sends a second PUSCH. If the second PUSCH is in the SBFD time domain, its transmission power can be determined based on the target receive power of PUSCH A (the first PUSCH). If the second PUSCH is in a non-SBFD time domain, its transmission power can be determined based on the target receive power of PUSCH B (the first PUSCH).

[0242] In some implementations, the PUSCH in the SBFD time domain and the PUSCH in the non-SBFD time domain may correspond to different target received powers, resulting in different power headrooms (PH). To align the understanding of the PH indicated by the PHR between terminal devices and network devices, and to facilitate PUSCH scheduling by network devices, one possible implementation is to set the PH indicated by the PHR to be determined by default based on the target received power of the PUSCH in the SBFD time domain, or the PH indicated by the PHR to be determined by default based on the target received power of the PUSCH in the non-SBFD time domain.

[0243] As an example: taking a virtual power headroom report (vPHR) of type 1 as an example, the type 1 virtual power headroom PH in this type 1 vPHR is... type1,b,f,c (i,j,q d ,l) can be determined using the following formula.

[0244]

[0245] Where b is the activated UL BWP, f is the carrier, c is the serving cell, i is the transmission occasion of PUSCH, j is the parameter set configuration index, and q is the parameter set configuration index. d Here, l is the reference signal index, and 1 is the power control adjustment status index. This represents the maximum transmit power (which can be understood as allowed maximum power reduction (MPR) = 0 dB, additional maximum power reduction (A-MPR) = 0 dB, power management maximum power reduction (P-MPR) = 0 dB, ΔT C Maximum transmit power at 0dB, ΔT C To allow operating band edge transmission power relaxation, α b,f,c (j) represents the road loss compensation factor, PL b,f,c (q d ) indicates downlink path loss, f b,f,c (i,l) represents the power control adjustment state, P O_PUSCH,b,f,c (j) represents the expected received power of PUSCH.

[0246] PO_PUSCH,b,f,c (j)=P O_NOMINAL_PUSCH,f,c (j)+P O_UE_PUSCH,b,f,c (j). Among them, P O_NOMINAL_PUSCH,f,c (j)=

[0247] P O_NOMINAL_PUSCH,f,c (0) can be understood as P O_NOMINAL_PUSCH,f,c In (j), the value of j is 0. P O_NOMINAL_PUSCH,f,c (0) represents the target receive power of PUSCH, or can be understood as the nominal target receive power of PUSCH.

[0248] Determining pH type1,b,f,c (i,j,q d When ,l), P O_NOMINAL_PUSCH,f,c (0) The default PUSCH in the SBFD time domain unit can be used. O_NOMINAL_PUSCH,f,c (0), or the default PUSCH in the non-SBFD time domain unit can be used. O_NOMINAL_PUSCH,f,c (0). Specifically, is the PUSCH in the SBFD time-domain unit used by default? O_NOMINAL_PUSCH,f,c (0), or by default, PUSCH in the non-SBFD time domain unit is used. O_NOMINAL_PUSCH,f,c (0) can be specified by protocols or instructed by network devices to terminal devices.

[0249] In another possible implementation, the determination of the PHR can also be related to the time-domain unit where the third PUSCH transmitting the PHR is located. For example, if the third PUSCH transmitting the PHR (which can be understood as carrying the PHR) is in a non-SBFD time-domain unit, the PH indicated by the PHR is based on the target received power (i.e., P) of the PUSCH in the non-SBFD time-domain unit. O_NOMINAL_PUSCH,f,c (0)) Determine; if the third PUSCH transmitting the PHR is in the SBFD time domain unit, the PH indicated by the PHR is based on the target received power (i.e., P) of the PUSCH in the SBFD time domain unit. O_NOMINAL_PUSCH,f,c (0)) Determined.

[0250] It is understood that the target receive power of PUSCH can refer to the target receive power of PUSCH during the random access procedure, or it can refer to the target receive power of PUSCH after the random access procedure, such as the target transmit power of CG / DGPUSCH. This application does not limit this.

[0251] In addition, the above method for determining the PH of the PHR indication can be applied to a single cell (such as one cell) or multiple cells (such as multiple cells).

[0252] As an example: Cell 1 is the primary cell (PCell), and Cell 2 is the secondary cell (SCell). When a terminal device transmits a PHR in the third PUSCH of the SBFD time-domain unit in Cell 1, the PH indicated by the PHR can be determined based on the target received power of the PUSCH in the SBFD time-domain unit in Cell 2. This can be understood as the type of the time-domain unit in which the PHR carries being located, and the P... O_NOMINAL_PUSCH,f,c (0) The corresponding time-domain cell types are the same. The type of time-domain cell can be understood as SBFD or Non-SBFD.

[0253] Figure 11 This is a schematic diagram of a PHR sending process provided in an embodiment of this application. The process includes:

[0254] S1101: The network device sends configuration information to the terminal device, and the terminal device receives the configuration information accordingly.

[0255] This configuration information can include parameters such as the PHR cycle.

[0256] S1102: The network device sends type 1vPHR on the third PUSCH, and the terminal device receives type 1vPHR accordingly.

[0257] Type 1vPHR is carried on the third PUSCH and can be signaling from a media access control (MAC) control element (MAC CE). The PH indicated by Type 1vPHR can be determined using the method described above and will not be repeated here.

[0258] The communication device provided in the embodiments of this application will now be described. Please refer to... Figure 12 , Figure 12 This is a schematic diagram of a communication device according to an embodiment of this application. The communication device may include units or modules corresponding to all or part of the steps in the above method embodiments, and can be used to execute the steps executed by the terminal device or network device in the above embodiments. Please refer to the relevant descriptions in the above method embodiments for details.

[0259] like Figure 12 As shown, the communication device 1200 includes a processing unit 1210 and an interface unit 1220, wherein the processing unit 1210 may be a processor or a processing circuit, and the interface unit 1220 may be a transceiver unit or an input / output interface. The communication device 1200 can be used to implement the steps performed by the terminal device or network device in the above embodiments.

[0260] When the communication device 1200 is used to implement the steps performed by the terminal device in the above embodiments:

[0261] Interface unit 1220 is configured to receive first information, the first information indicating a first power offset between PRACH in the SBFD time domain unit and PUSCH in a non-SBFD time domain unit, and / or a second power offset between PRACH in a non-SBFD time domain unit and PUSCH in the SBFD time domain unit; processing unit 1210 is configured to determine the transmission power of the first PUSCH based on the first information; interface unit 1220 is further configured to transmit the first PUSCH based on the transmission power of the first PUSCH.

[0262] In one possible design, the value of the first power offset is X, and the value of the second power offset is -X, where X is an integer.

[0263] In one possible design, the first information also indicates a fourth power offset, which is the power offset between PRACH in a non-SBFD time domain cell and PUSCH in a non-SBFD time domain cell.

[0264] In one possible design, interface unit 1220 is further configured to receive second information, which indicates a first PRACH target receive power and / or a second PRACH target receive power; wherein the first PRACH target receive power is the target receive power of the PRACH in the SBFD time domain unit, and the second target receive power is the target receive power of the PRACH in a non-SBFD time domain unit. The transmit power of the first PUSCH can also be determined based on the second information, or based on the first and second information.

[0265] In one possible design, the first PUSCH is the PUSCH in the random access procedure.

[0266] In one possible design, the interface unit 1220 is also used to transmit a second PUSCH, wherein the transmission power of the second PUSCH is determined based on the target reception power of the PUSCH in the random access procedure most recent to the second PUSCH in the time domain.

[0267] In one possible design, the PUSCH in the random access procedure that is closest to the second PUSCH in the time domain has the same time domain unit type as the second PUSCH.

[0268] In one possible design, the second PUSCH includes at least one of the following: CG PUSCH or DG PUSCH.

[0269] In one possible design, the target receive power of the second PUSCH is not configured by the network.

[0270] In one possible design, interface unit 1220 is also used to transmit a PHR, wherein the PHR indicates a target received power determination based on the PUSCH in the SBFD time domain unit, or a target received power determination based on the PUSCH in a non-SBFD time domain unit.

[0271] In one possible design, if the third PUSCH carrying the PHR is in a non-SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain cell; if the third PUSCH carrying the PHR is in an SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain cell.

[0272] In one possible design, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit during the random access procedure; the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit during the random access procedure.

[0273] When the communication device 1200 is used to implement the steps performed by the network device in the above embodiments:

[0274] Processing unit 1210 is configured to determine first information, the first information indicating a first power offset between PRACH in the SBFD time domain unit and PUSCH in the non-SBFD time domain unit, and / or a second power offset between PRACH in the non-SBFD time domain unit and PUSCH in the SBFD time domain unit; interface unit 1220 is configured to transmit the first information; and receive a first PUSCH, wherein the transmission power of the first PUSCH is determined according to the first information.

[0275] In one possible design, the value of the first power offset is X, the value of the second power offset is -X, and X is an integer.

[0276] In one possible design, the first information also indicates a fourth power offset, which is the power offset between PRACH in a non-SBFD time domain cell and PUSCH in a non-SBFD time domain cell.

[0277] In one possible design, interface unit 1220 is further configured to transmit second information, indicating a first PRACH target receive power and / or a second PRACH target receive power; wherein the first PRACH target receive power is the target receive power of the PRACH in the SBFD time domain unit, and the second target receive power is the target receive power of the PRACH in a non-SBFD time domain unit. The transmit power of the first PUSCH can also be determined based on the second information, or based on the first and second information.

[0278] In one possible design, the first PUSCH is the PUSCH in the random access procedure.

[0279] In one possible design, the interface unit 1220 is also used to receive a second PUSCH, wherein the transmit power of the second PUSCH is determined based on the target receive power of the PUSCH in the random access procedure most recent to the second PUSCH in the time domain.

[0280] In one possible design, the PUSCH in the random access procedure that is closest to the second PUSCH in the time domain has the same time domain unit type as the second PUSCH.

[0281] In one possible design, the second PUSCH includes at least one of the following: CG PUSCH or DG PUSCH.

[0282] In one possible design, the target receive power of the second PUSCH is not configured by the network.

[0283] In one possible design, interface unit 1220 is also used to receive PHR, wherein the power margin indicated by PHR is determined based on the target received power of PUSCH in the SBFD time domain unit, or based on the target received power of PUSCH in a non-SBFD time domain unit.

[0284] In one possible design, if the third PUSCH carrying the PHR is in a non-SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain cell; if the third PUSCH carrying the PHR is in an SBFD time domain cell, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain cell.

[0285] In one possible design, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in a non-SBFD time domain unit during the random access procedure; the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit, including: the power margin indicated by the PHR is determined based on the target received power of the PUSCH in an SBFD time domain unit during the random access procedure.

[0286] like Figure 13 As shown, this application also provides a communication device 1300, including a processor 1310 and potentially a communication interface 1320. The processor 1310 and the communication interface 1320 are coupled to each other. It is understood that the communication interface 1320 can be a transceiver, input / output interface, input interface, output interface, interface circuit, etc. Optionally, the communication device 1300 may further include a memory 1330 for storing instructions executed by the processor 1310, or storing input data required by the processor 1310 to execute instructions, or storing data generated after the processor 1310 executes instructions. The memory 1330 can be a physically independent unit, or it can be coupled to the processor 1310, or the processor 1310 may include the memory 1330.

[0287] When the communication device 1300 is used to implement the steps executed by the terminal device or network device in the above embodiments, the processor 1310 can be used to implement the function of the processing unit 1210, and the communication interface 1320 can be used to implement the function of the interface unit 1220.

[0288] When the communication device is the baseband chip of the terminal device Figure 14 This application provides an example block diagram of a terminal device-side baseband chip implementation. The terminal device-side baseband chip can be implemented using a processing system including one or more processors. The processing system can be implemented using a bus architecture, typically represented by a bus. The bus can include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus communicatively couples various circuits together, including one or more processors (typically represented by processors), memory, or computer-readable media (typically represented by computer-readable media). The bus can also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. The bus interface provides the interface between the bus and the transceiver, as well as between the bus and the interface.

[0289] A transceiver provides a communication interface or means for communicating with various other devices via a wireless transmission medium. The transceiver may be coupled to an antenna array, and the transceiver and antenna array may be used together for communication with a corresponding network type. At least one interface (e.g., a network interface and / or a user interface) provides a communication interface or means for communication via an internal bus or via an external transmission medium.

[0290] The processor is responsible for managing the bus and general processing, including executing software stored on a computer-readable medium (or memory). When the processor executes the software, the software causes the processing system to perform various functions described below for any particular device, such as implementing the communication methods suitable for terminal devices provided in the embodiments of this application.

[0291] The functions that the processor and memory (or computer-readable medium) can perform may include: encoding, decoding, rate matching, rate matching dematching, scrambling, descrambling, modulation, demodulation, layer mapping, fast Fourier transform (FFT), inverse discrete Fourier transform (IDFT), precoding, resource element (RE) mapping, channel equalization, RE demapping, digital beamforming (BF), adding cyclic prefix (CP), removing CP, etc.

[0292] In this application embodiment, the processor (e.g., processor 1310) can be one or more central processing units (CPUs). If the processor is a CPU, it can be a single-core CPU or a multi-core CPU. The processor can also be one or a combination of several of the following: CPU, general-purpose processor, application-specific integrated circuit (ASIC), digital signal processor (DSP), microprocessor unit (MPU), microcontroller unit (MCU), graphics processing unit (GPU), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, artificial intelligence processor (AI processor), or neural processing unit (NPU). The processor can implement or execute the methods, steps, and logic block diagrams disclosed in this application embodiment. The steps of the methods disclosed in this application embodiment can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0293] In this embodiment, the memory (e.g., memory 1330) may include, but is not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0294] It is understood that the method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can 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 disks, portable hard disks, CD-ROMs, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Additionally, the ASIC can reside in a network device or a terminal device. Alternatively, the processor and storage medium can exist as discrete components in the network device or terminal device.

[0295] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one network device, terminal, computer, server, or data center to another network device, terminal, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0296] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0297] Additionally, it should be understood that in the embodiments of this application, the term "exemplary" is used to indicate that it is an example, illustration, or description. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0298] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

Claims

1. A communication method, characterized in that, include: Receive first information, the first information indicating a first power offset between the physical random access channel PRACH in the sub-band full-duplex SBFD time domain unit and the physical uplink shared channel PUSCH in the non-SBFD time domain unit, and / or a second power offset between the PRACH in the non-SBFD time domain unit and the PUSCH in the SBFD time domain unit. A first PUSCH is transmitted, wherein the transmission power of the first PUSCH is determined based on the first information.

2. The method as described in claim 1, characterized in that, The value of the first power offset is X, and the value of the second power offset is -X, where X is an integer.

3. The method as described in claim 1 or 2, characterized in that, The first information also indicates a fourth power offset, which is a power offset between PRACH in a non-SBFD time domain unit and PUSCH in a non-SBFD time domain unit.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Receive second information, the second information indicating the first PRACH target receive power and / or the second PRACH target receive power; Wherein, the first PRACH target receive power is the target receive power of PRACH in the SBFD time domain unit, the second target receive power is the target receive power of PRACH in the non-SBFD time domain unit, and the transmit power of the first PUSCH is determined according to the first information and the second information.

5. The method according to any one of claims 1-4, characterized in that, The first PUSCH is the PUSCH in the random access procedure.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Send a second PUSCH, wherein the transmission power of the second PUSCH is determined based on the target receive power of the PUSCH in the random access procedure most recent to the second PUSCH in the time domain.

7. The method as described in claim 6, characterized in that, The PUSCH in the random access procedure is of the same time-domain unit type as the second PUSCH.

8. The method as described in claim 6 or 7, characterized in that, The second PUSCH includes at least one of the following: Configure and license CG PUSCH, or dynamically license DG PUSCH.

9. The method according to any one of claims 6-8, characterized in that, The target receive power of the second PUSCH is not configured by the network.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: Transmit a Power Headroom Report (PHR), wherein the power headroom indicated by the PHR is determined based on the target receive power of the PUSCH in the SBFD time domain unit, or based on the target receive power of the PUSCH in a non-SBFD time domain unit.

11. The method as described in claim 10, characterized in that, If the third PUSCH carrying the PHR is in a non-SBFD time domain unit, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain unit. If the third PUSCH carrying the PHR is in the SBFD time domain unit, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit.

12. The method as described in claim 10 or 11, characterized in that, The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain unit, including: The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain unit during the random access procedure. The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit, including: The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit during the random access procedure.

13. A communication method, characterized in that, include: Send a first message, the first message indicating a first power offset between the physical random access channel PRACH in the sub-band full-duplex SBFD time domain unit and the physical uplink shared channel PUSCH in the non-SBFD time domain unit, and / or a second power offset between the PRACH in the non-SBFD time domain unit and the PUSCH in the SBFD time domain unit. Receive a first PUSCH, wherein the transmission power of the first PUSCH is determined based on the first information.

14. The method as described in claim 13, characterized in that, The value of the first power offset is X, the value of the second power offset is -X, and X is an integer.

15. The method as described in claim 13 or 14, characterized in that, The first information also indicates a fourth power offset, which is a power offset between PRACH in a non-SBFD time domain unit and PUSCH in a non-SBFD time domain unit.

16. The method according to any one of claims 13-15, characterized in that, The method further includes: Send a second message, the second message indicating the first PRACH target receive power and / or the second PRACH target receive power; Wherein, the first PRACH target receive power is the target receive power of PRACH in the SBFD time domain unit, the second target receive power is the target receive power of PRACH in the non-SBFD time domain unit, and the transmit power of the first PUSCH is determined according to the first information and the second information.

17. The method according to any one of claims 13-16, characterized in that, The first PUSCH is the PUSCH in the random access procedure.

18. The method according to any one of claims 13-17, characterized in that, The method further includes: Receive a second PUSCH, wherein the transmit power of the second PUSCH is determined based on the target receive power of the PUSCH in the random access procedure most recent to the second PUSCH in the time domain.

19. The method as described in claim 18, characterized in that, The PUSCH in the random access procedure is of the same time-domain unit type as the second PUSCH.

20. The method as described in claim 18 or 19, characterized in that, The second PUSCH includes at least one of the following: Configure and license CG PUSCH, or dynamically license DG PUSCH.

21. The method according to any one of claims 18-20, characterized in that, The target receive power of the second PUSCH is not configured by the network.

22. The method according to any one of claims 13-21, characterized in that, The method further includes: A Receive Power Headroom Report (PHR) indicates a power headroom based on the target receive power of the PUSCH in the SBFD time domain unit, or based on the target receive power of the PUSCH in a non-SBFD time domain unit.

23. The method as described in claim 22, characterized in that, If the third PUSCH carrying the PHR is in a non-SBFD time domain unit, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain unit. If the third PUSCH carrying the PHR is in the SBFD time domain unit, the power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit.

24. The method as described in claim 22 or 23, characterized in that, The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain unit, including: The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the non-SBFD time domain unit during the random access procedure. The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit, including: The power margin indicated by the PHR is determined based on the target received power of the PUSCH in the SBFD time domain unit during the random access procedure.

25. A communication device, characterized in that, It includes modules or units for performing the method as described in any one of claims 1-12; or, it includes modules or units for performing the method as described in any one of claims 13-24.

26. A communication device, characterized in that, It includes a processor and an interface circuit, the interface circuit being used to input and / or output signals, and the processor being used to implement the method as described in any one of claims 1-12 through logic circuits or execution instructions; or, to implement the method as described in any one of claims 13-24.

27. A computer program product, characterized in that, It includes a computer program or instructions that, when executed by a processor, cause the method as described in any one of claims 1-12 to be implemented; or cause the method as described in any one of claims 13-24 to be implemented.

28. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a processor, cause the method as described in any one of claims 1-12 to be implemented; or cause the method as described in any one of claims 13-24 to be implemented.

Images