Wireless communication method, and devices and storage medium

Abstract

The embodiments of the present application provide a wireless communication method, and devices and a storage medium. The method comprises: a terminal device receiving a first parameter, wherein the first parameter is used for determining a first power parameter and a second power parameter, the first power parameter is a power parameter applied to a first-type time-domain unit, the second power parameter is a power parameter applied to a second-type time-domain unit, a carrier or a carrier group on the first-type time-domain unit comprises frequency-domain resources in different directions, and a carrier or a carrier group on the second-type time-domain unit only comprises frequency-domain resources in one direction.

Description

Method and device for wireless communication, and storage medium TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of mobile communication technology, and in particular to a method and device for wireless communication, and a storage medium. BACKGROUND

[0002] In related technologies, XDD technology is introduced, that is, data can be simultaneously transmitted and received on different subbands of the same subframe. This technology is mainly used at the base station side. The terminal side still maintains the current state, that is, only transmission or reception of data is supported in one subframe.

[0003] SUMMARY

[0004] Embodiments of the present application provide a method and device for wireless communication, and a storage medium.

[0005] The method for wireless communication provided by the embodiments of the present application comprises:

[0006] The terminal device receives a first parameter, the first parameter is used to determine a first power parameter and a second power parameter, the first power parameter is a power parameter applied to a first type of time domain unit, and the second power parameter is a power parameter applied to a second type of time domain unit, a carrier or a carrier group on the first type of time domain unit comprises frequency domain resources in different directions, and a carrier or a carrier group on the second type of time domain unit comprises frequency domain resources in only one direction.

[0007] The method for wireless communication provided by the embodiments of the present application comprises:

[0008] The network device sends a first parameter, the first parameter is used to determine a first power parameter and a second power parameter, the first power parameter is a power parameter applied to a first type of time domain unit, and the second power parameter is a power parameter applied to a second type of time domain unit, a carrier or a carrier group on the first type of time domain unit comprises frequency domain resources in different directions, and a carrier or a carrier group on the second type of time domain unit comprises frequency domain resources in only one direction.

[0009] The method for wireless communication provided by the embodiments of the present application comprises:

[0010] The terminal device receives a second parameter, the second parameter comprises one or two frequency domain resource allocation parameters, the second parameter is used to determine frequency domain transmission resources on a first type of time domain unit and frequency domain transmission resources on a second type of time domain unit, or the second parameter is used to determine frequency domain transmission resources on the first type of time domain unit, a carrier or a carrier group on the first type of time domain unit comprises frequency domain resources in different directions, and a carrier or a carrier group on the second type of time domain unit comprises frequency domain resources in only one direction.

[0011] The wireless communication method provided by the embodiments of the present application comprises:

[0012] The network device sends a second parameter, the second parameter comprising one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit and frequency domain transmission resources on the second type of time domain unit, or the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit; the carrier or carrier group on the first type of time domain unit comprising frequency domain resources of different directions, and the carrier or carrier group on the second type of time domain unit comprising frequency domain resources of only one direction.

[0013] The terminal device provided by the embodiments of the present application comprises:

[0014] The first communication unit is configured to receive a first parameter, the first parameter being used to determine a first power parameter and a second power parameter, the first power parameter being a power parameter applied to the first type of time domain unit, and the second power parameter being a power parameter applied to the second type of time domain unit, the carrier or carrier group on the first type of time domain unit comprising frequency domain resources of different directions, and the carrier or carrier group on the second type of time domain unit comprising frequency domain resources of only one direction.

[0015] The network device provided by the embodiments of the present application comprises:

[0016] The second communication unit is configured to send a first parameter, the first parameter being used to determine a first power parameter and a second power parameter, the first power parameter being a power parameter applied to the first type of time domain unit, and the second power parameter being a power parameter applied to the second type of time domain unit, the carrier or carrier group on the first type of time domain unit comprising frequency domain resources of different directions, and the carrier or carrier group on the second type of time domain unit comprising frequency domain resources of only one direction.

[0017] The terminal device provided by the embodiments of the present application comprises:

[0018] The third communication unit is configured to receive a second parameter, the second parameter comprising one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit and frequency domain transmission resources on the second type of time domain unit, or the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit; the carrier or carrier group on the first type of time domain unit comprising frequency domain resources of different directions, and the carrier or carrier group on the second type of time domain unit comprising frequency domain resources of only one direction.

[0019] The network device provided by the embodiments of the present application comprises:

[0020] a fourth communication unit, configured to send a second parameter, the second parameter comprising one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on a first type of time domain unit and frequency domain transmission resources on a second type of time domain unit, or the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit; a carrier or a carrier group on the first type of time domain unit comprising frequency domain resources in different directions, and a carrier or a carrier group on the second type of time domain unit comprising frequency domain resources in only one direction.

[0021] The communication device provided by the embodiments of the present application comprises a transceiver, a processor and a memory. The memory is used to store a computer program, and the processor is used to invoke and run the computer program stored in the memory to cooperate with the transceiver to execute the wireless communication method described above.

[0022] The chip provided by the embodiments of the present application comprises a processor, which is used to invoke and run a computer program from a memory, so that a device installed with the chip executes the wireless communication method described above.

[0023] The computer readable storage medium provided by the embodiments of the present application is used to store a computer program, and the computer program enables a computer to execute the wireless communication method described above.

[0024] The computer program product provided by the embodiments of the present application comprises computer program instructions, and the computer program instructions enable a computer to execute the wireless communication method described above.

[0025] The computer program provided by the embodiments of the present application enables a computer to execute the wireless communication method described above when the computer program runs on the computer.

[0026] Through the above technical solution, the carrier or carrier group comprises the first type of time domain unit in different directions, and the carrier or carrier group comprises the second type of time domain unit in one direction, which are respectively configured with different power parameters, so that different types of time domain units adopt different transmission powers, thereby adapting to different configurations of antennas on different types of time domain units, supplementing the reception signal-to-noise ratio (SNR) difference caused by the difference in antenna configuration, and ensuring the continuity of the transmission channel or signal. BRIEF DESCRIPTION OF DRAWINGS

[0027] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of the present application, and the illustrative embodiments of the present application and their description serve to explain the present application, and do not constitute improper limitations on the present application. In the drawings:

[0028] FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0029] FIG. 2 is an optional schematic diagram of a subband full duplex (SBFD) according to an embodiment of the present application;

[0030] FIG. 3 is an optional flow diagram of a wireless communication method according to an embodiment of the present application;

[0031] FIG. 4 is an optional flow diagram of a wireless communication method according to an embodiment of the present application;

[0032] FIG. 5 is an optional flow diagram of a wireless communication method according to an embodiment of the present application;

[0033] FIG. 6 is an optional flow diagram of a wireless communication method according to an embodiment of the present application;

[0034] FIG. 7 is an optional flow diagram of a wireless communication method according to an embodiment of the present application;

[0035] FIG. 8 is an optional flow diagram of a wireless communication method according to an embodiment of the present application;

[0036] FIG. 9 is an optional flow diagram of a time domain unit according to an embodiment of the present application;

[0037] FIG. 10 is an optional flow diagram of a time domain unit according to an embodiment of the present application;

[0038] FIG. 11 is an optional structural diagram of a terminal device according to an embodiment of the present application;

[0039] FIG. 12 is an optional structural diagram of a network device according to an embodiment of the present application;

[0040] FIG. 13 is an optional structural diagram of a terminal device according to an embodiment of the present application;

[0041] FIG. 14 is an optional structural diagram of a network device according to an embodiment of the present application;

[0042] FIG. 15 is an optional structural diagram of a communication device according to an embodiment of the present application;

[0043] FIG. 16 is an optional structural diagram of a chip according to an embodiment of the present application;

[0044] FIG. 17 is an optional structural diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative labor fall within the scope of the present application.

[0046] FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0047] As shown in FIG. 1, the communication system 100 can include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 through an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0048] It should be understood that the embodiments of the present application are only exemplarily described with the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: a Long Term Evolution (LTE) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunication System (UMTS), an Internet of Things (IoT) system, a Narrow Band Internet of Things (NB-IoT) system, an enhanced Machine-Type Communications (eMTC) system, a 5G communication system (also referred to as a New Radio (NR) communication system), or a future communication system, etc.

[0049] In the communication system 100 shown in FIG. 1, the network device 120 can be an access network device that communicates with the terminal device 110. The access network device can provide communication coverage for a specific geographic area, and can communicate with the terminal device 110 (for example, a UE) located in the coverage area.

[0050] The network device 120 can be an evolved node B (eNB or eNodeB) in a long term evolution (LTE) system, or a next generation radio access network (NG RAN) device, or a base station (gNB) in an NR system, or a radio controller in a cloud radio access network (CRAN), or a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved public land mobile network (PLMN), etc.

[0051] The terminal device 110 can be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wireless connection.

[0052] The terminal device 110 can be used for device to device (D2D) communication.

[0053] The wireless communication system 100 can further include a core network device 130 in communication with the base station.

[0054] The various functional units in the communication system 100 can also establish a connection through a next generation (NG) interface to communicate.

[0055] FIG. 1 exemplarily shows one base station, one core network device and two terminal devices. Optionally, the wireless communication system 100 can include multiple base station devices and each base station can include other numbers of terminal devices within its coverage, which are not limited in the embodiments of the present application.

[0056] It should be noted that FIG. 1 only schematically shows a system to which the embodiments of the present application are applied in an exemplary manner. Of course, the method shown in the embodiments of the present application can also be applied to other systems. In addition, the terms "system" and "network" are often used interchangeably in the present application. The term "and / or" in the present application is only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in the present application generally represents an "or" relationship between the front and rear associated objects. It should also be understood that the "indication" mentioned in the embodiments of the present application can be direct indication or indirect indication, and can also mean an associated relationship. For example, A indicates B, which can mean that B can be obtained through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship. It should also be understood that the "corresponding" mentioned in the embodiments of the present application can mean a direct correspondence or an indirect correspondence between the two, or can mean an associated relationship between the two, or can mean an indication and being indicated, a configuration and being configured, and the like. It should also be understood that the "predefined" or "predefined rule" mentioned in the embodiments of the present application can be realized by pre-saving corresponding codes, tables or other means for indicating related information in devices (for example, including terminal devices and network devices), and the specific implementation manner of the present application is not limited. For example, the predefinition can mean the definition in the protocol. It should also be understood that the "protocol" in the embodiments of the present application can mean a standard protocol in the communication field, which can include the LTE protocol, the NR protocol and the related protocol applied to the future communication system, and the present application is not limited thereto.

[0057] In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described as follows. The related technologies can be combined with the technical solutions of the embodiments of the present application in any manner, and all of them belong to the protection scope of the embodiments of the present application.

[0058] In the related technologies, the XDD technology is introduced, that is, data can be simultaneously transmitted and received on different subbands of the same subframe. This technology is mainly used at the base station side. The terminal side still maintains the current state, that is, only transmission or reception of data is supported within one subframe. As shown in FIG. 2, the middle subband of one downlink symbol is configured as an uplink subband, which is denoted as a subband full duplex (SBFD) symbol, and only one direction transmission is supported. The symbol is denoted as a non-SBFD symbol, and the frequency domain resource of the PDSCH on the symbol does not include the uplink subband part.

[0059] When a terminal is configured / instructed to receive data in a downlink time slot, for example, a physical downlink shared channel (PDSCH). Among them, for the part of the PDSCH overlapping with the uplink subband (UL subband), since the base station side is in the receiving state, it cannot send the data in this uplink subband, that is, the base station will only send the PDSCH on the downlink resources on both sides of the uplink subband.

[0060] When a terminal is configured / instructed to send data in a downlink time slot, for example, a physical uplink shared channel (PUSCH). Among them, the PUSCH can only be sent in the UL subband.

[0061] In addition, one implementation of the sub-band duplex technology is to use part of the multiple transmitting antennas as transmitting antennas and part of the multiple transmitting antennas as receiving antennas. For example, in a communication system with four transmitting antennas, when sub-band duplex is performed, two antennas are used as receiving antennas and two antennas are used as transmitting antennas.

[0062] Because the antenna configuration or frequency domain resource configuration on the SBFD symbol and the non-SBFD symbol are different, the transmission scheme on these symbols, such as the transmitting power and the frequency domain resource, is different from that on the non-SBFD symbol.

[0063] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, which all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0064] An optional processing procedure of the wireless communication method provided by the embodiments of the present application is applied to a terminal device, as shown in FIG. 3, and includes the following steps:

[0065] S301, the terminal device receives a first parameter, the first parameter is used to determine a first power parameter and a second power parameter, the first power parameter is a power parameter applied to a first type of time domain unit, and the second power parameter is a power parameter applied to a second type of time domain unit, a carrier or carrier group on the first type of time domain unit includes frequency domain resources in different directions, and a carrier or carrier group on the second type of time domain unit only includes frequency domain resources in one direction.

[0066] An optional processing procedure of the wireless communication method provided by the embodiments of the present application is applied to a network device, as shown in FIG. 4, and includes the following steps:

[0067] S401, the network device sends a first parameter, the first parameter is used to determine a first power parameter and a second power parameter, the first power parameter is a power parameter applied to a first type of time domain unit, the second power parameter is a power parameter applied to a second type of time domain unit, a carrier or carrier group on the first type of time domain unit includes frequency domain resources of different directions, and the carrier or carrier group on the second type of time domain unit only includes frequency domain resources of one direction.

[0068] An optional processing flow of the wireless communication method provided in the embodiments of the present application is applied to a wireless communication system including a network device and a terminal device, as shown in FIG. 5, and includes the following steps:

[0069] S501, the network device sends a first parameter to the terminal device, the first parameter is used to determine a first power parameter and a second power parameter, the first power parameter is a power parameter applied to a first type of time domain unit, the second power parameter is a power parameter applied to a second type of time domain unit, a carrier or carrier group on the first type of time domain unit includes frequency domain resources of different directions, and the carrier or carrier group on the second type of time domain unit only includes frequency domain resources of one direction.

[0070] In the following, the wireless communication method shown in FIG. 3, FIG. 4 or FIG. 5 is further described.

[0071] The first type of time domain unit can be understood as an SBFD time domain unit, and any one or more carriers in the carrier or carrier group on the type of time domain unit includes frequency domain resources of different directions. In an example, the carrier or carrier group on the first type of time domain unit includes an uplink transmission part, i.e., an uplink subband (UL subband), and a downlink transmission part, i.e., a downlink subband (DL subband).

[0072] The second type of time domain unit can be understood as a non-SBFD time domain unit, and all carriers in the carrier or carrier group on the type of time domain unit only include frequency domain resources of one direction. In an example, the carrier or carrier group on the second type of time domain unit is only used for uplink transmission or downlink transmission.

[0073] It can be understood that the carrier group is one or more carriers sharing a radio frequency channel, and usually one or more carriers in one band (Band) belong to the same carrier group, or one or more carriers in adjacent Bands belong to the same carrier group.

[0074] In the embodiments of the present application, the time domain unit can be understood as a resource unit in time domain, such as a symbol, a subframe, a frame, a time slot, etc. For convenience of description, in the examples, the first type of time domain unit or the second type of time domain unit is described by taking a symbol as an example.

[0075] The first parameter configured by the network device is used to determine the first power parameter and the second power parameter. The first power parameter is applied to the first type of time domain unit, and is used to determine the transmission power of the channel on the first type of time domain unit. The second power parameter is applied to the second type of time domain unit, and is used to determine the transmission power of the channel on the second type of time domain unit.

[0076] In the embodiments of the present application, one time domain unit can be used to transmit one or more channels, and the power parameters of different channels are different.

[0077] It can be understood that the channel transmitted by the time domain unit can also be replaced by a signal.

[0078] In the embodiments of the present application, the carrier or the carrier group includes the first type of time domain unit in different directions, and the carrier or the carrier group includes the second type of time domain unit in one direction, which are respectively configured with different power parameters, so that different types of time domain units can adopt different transmission powers, thereby adapting to different configurations of antennas on different types of time domain units, compensating for the differences in received SNR caused by the differences in antenna configurations, and ensuring the continuity of the transmitted channels or signals.

[0079] In the embodiments of the present application, the first parameter can be cell-specific or user-specific.

[0080] The wireless communication method provided by the embodiments of the present application is based on whether an uplink subband and a downlink subband are configured on one carrier, so that the radio frequency can be shared between different BWPs working in one carrier, thereby reducing the development cost and power consumption. Further, the power parameter is based on whether an uplink subband and a downlink subband are configured on one carrier group, so that multiple carriers can share the radio frequency, thereby reducing the development cost and power consumption. Moreover, the current device is usually in the mode of sharing the radio frequency by multiple carriers, which has good backward compatibility. When SBFD is deployed, the current hardware can be directly reused, thereby reducing the product development cost.

[0081] In some embodiments, the same channel on the same type of different time domain units shares the same power parameter.

[0082] It can be understood that the same channel on the first type of time domain unit shares the same power parameter for the channel, and the same channel on the second type of time domain unit shares the same power parameter for the channel.

[0083] In some embodiments,

[0084] The first parameter includes the first power parameter and the second power parameter; or,

[0085] The first parameter comprises the first power parameter or the second power parameter, and a first deviation parameter, the first deviation parameter representing a deviation amount between the first power parameter and the second power parameter.

[0086] The first parameter comprises the first power parameter and the second power parameter, which can be considered as being independently configured.

[0087] The first parameter comprises the first power parameter or the second power parameter, and a first deviation parameter, which can be understood as that the network device configures a type of power parameter of a time domain unit, and the power parameter of the type of time domain unit is used as a reference value to determine the power parameter of another type of time domain unit in combination with the first deviation parameter.

[0088] It can be understood that the second power parameter can reuse an existing power parameter, which can be understood as a power parameter of a time domain unit in a protocol without distinguishing between the first type and the type.

[0089] In some embodiments, the power parameter is used to determine one or both of:

[0090] a reception power of an uplink channel;

[0091] a transmission power of a downlink channel.

[0092] It can be understood that the power parameter in the embodiments of the present application can comprise one or both of: an uplink power parameter and a downlink power parameter, wherein the uplink power parameter is a power parameter applied to an uplink channel, and is used to determine a reception power of the uplink channel, and the downlink power parameter is a power parameter applied to a downlink channel, and is used to determine a transmission power of the downlink channel.

[0093] In the embodiments of the present application, the uplink power parameter comprises a reception power parameter of an uplink channel, to determine a reception power of the uplink channel, wherein the reception power of the uplink channel is used by a terminal device to determine a transmission power of the uplink channel.

[0094] In the embodiments of the present application, the downlink power parameter comprises a transmission power parameter of a downlink channel, to determine a transmission power of the downlink channel, wherein the transmission power of the downlink channel is used by a terminal device to determine a path loss in combination with a reception power of the downlink channel.

[0095] In some embodiments, the uplink channel comprises one or more of:

[0096] a physical uplink shared channel (PUSCH);

[0097] a physical uplink control channel (PUCCH);

[0098] Sounding Reference Signal, SRS.

[0099] If the uplink channel comprises a PUSCH, the first parameter is used to determine a power parameter for the PUSCH on the time-domain units of the first type and a power parameter for the PUSCH on the time-domain units of the second type to determine a transmission power for the PUSCH on the time-domain units of the first type and a transmission power for the PUSCH on the time-domain units of the second type, respectively.

[0100] PUSCH can be understood as a physical uplink shared channel.

[0101] If the uplink channel comprises a PUCCH, the first parameter is used to determine a power parameter for the PUCCH on the time-domain units of the first type and a power parameter for the PUCCH on the time-domain units of the second type to determine a transmission power for the PUCCH on the time-domain units of the first type and a transmission power for the PUCCH on the time-domain units of the second type, respectively.

[0102] PUCCH can be understood as a physical uplink control channel.

[0103] If the uplink channel comprises a SRS, the first parameter is used to determine a power parameter for the SRS on the time-domain units of the first type and a power parameter for the SRS on the time-domain units of the second type to determine a transmission power for the SRS on the time-domain units of the first type and a transmission power for the SRS on the time-domain units of the second type, respectively.

[0104] SRS can be understood as a sounding reference signal.

[0105] In some embodiments, the downlink channel comprises one or more of:

[0106] a Synchronization Signal, SS;

[0107] a Physical Broadcast Channel, PBCH;

[0108] a Channel Status Indicator Reference Signal, CSI-RS.

[0109] If the downlink channel comprises a SS, the first parameter is used to determine a power parameter for the SS on the time-domain units of the first type and a power parameter for the SS on the time-domain units of the second type to determine a transmission power for the SS on the time-domain units of the first type and a transmission power for the SS on the time-domain units of the second type, respectively.

[0110] If the downlink channel comprises PBCH, the first parameter is used to determine: a power parameter of the PBCH on the time-domain unit of the first type, and, a power parameter of the PBCH on the time-domain unit of the second type, to determine a transmission power of the PBCH on the time-domain unit of the first type and a transmission power of the PBCH on the time-domain unit of the second type, respectively.

[0111] PBCH can be understood as a broadcast channel.

[0112] If the downlink channel comprises CSI-RS, the first parameter is used to determine: a power parameter of the CSI-RS on the time-domain unit of the first type, and, a power parameter of the CSI-RS on the time-domain unit of the second type, to determine a transmission power of the CSI-RS on the time-domain unit of the first type and a transmission power of the CSI-RS on the time-domain unit of the second type, respectively.

[0113] CSI-RS can be understood as a downlink measurement reference signal.

[0114] In some embodiments, the power parameter comprises one or more of:

[0115] Information 1, a target received power parameter of a configured scheduling PUSCH;

[0116] Information 2, a target received power parameter of a dynamically scheduled PUSCH;

[0117] Information 3, a target received power parameter of a PUCCH;

[0118] Information 4, a target received power parameter of a SRS set;

[0119] Information 5, an Energy per Resource Element (EPRE) of an SSB;

[0120] Information 6, a power offset of a CSI-RS.

[0121] Information 1 is used to determine a transmission power of a configured scheduling PUSCH.

[0122] For a configured scheduling PUSCH, the first parameter is used to determine a target received power parameter P0 of the configured scheduling PUSCH on the time-domain unit of the first type, and P0 of the configured scheduling PUSCH on the time-domain unit of the second type.

[0123] Optionally, the first parameter can comprise a first target received power parameter applied to the configured scheduled PUSCH, and the first target received power parameter comprises: a first power parameter for the configured scheduled PUSCH on the first type of time domain unit, and a second power parameter for the configured scheduled PUSCH on the second type of time domain unit.

[0124] The information 2 is used to determine the transmission power of the dynamically scheduled PUSCH.

[0125] For the dynamically scheduled PUSCH, the first parameter is used to determine a target received power parameter P0 of the dynamically scheduled PUSCH on the first type of time domain unit, and P0 of the dynamically scheduled PUSCH on the second type of time domain unit.

[0126] Optionally, the first parameter can comprise a second target received power parameter applied to the dynamically scheduled PUSCH, and the second target received power parameter comprises: a third power parameter for the dynamically scheduled PUSCH on the first type of time domain unit, and a fourth power parameter for the dynamically scheduled PUSCH on the second type of time domain unit.

[0127] In an example, if the terminal device transmits a PUSCH using the parameter set with index j and the PUSCH power control adjustment state with index l on the active UL BWP b of the carrier f of the serving cell c, the UE determines the PUSCH transmission power P PUSCH,b,f,c (i,j,q d ,l) as:

[0128] wherein P CMAX,f,c (i) is the maximum output power of the UE configured for the carrier f of the serving cell c on the PUSCH transmission occasion i;

[0129] The target received power parameter P O_PUSCH,b,f,c (j) of the PUSCH is determined as: O_NOMINAL,PUSCH,f,c (j) is determined as: O_UE_PUSCH,b,f,c (j) is determined as: O_PUSCH,b,f,c (j) is the target received power parameter of the configured scheduled PUSCH, i has a value of 2 to J-1, and the PUSCH is the dynamically scheduled PUSCH, then P O_PUSCH,b,f,c (j) is the target received power parameter of the dynamically scheduled PUSCH.

[0130] is the number of PRBs of the PUSCH; andb,f,c (q d ) is the downlink path loss estimate, q d is the downlink reference signal index; Δ TFb,f,c (i) is the power adjustment amount for PUCCH equivalent code rate; f b,f,c (i,l) is the closed loop adjustment amount for PUSCH.

[0131] For configured scheduling PUSCH transmission or retransmission, j = 1:

[0132] P O_NOMINAL,PUSCH,f,c (1) is provided by the first target received power parameter P O_NOMINAL,PUSCH,f,c (1) = P O_NOMINAL,PUSCH,f,c (0).

[0133] If the first power parameter is denoted by p0-NominalWithoutGrant-r19, where the first power parameter comprised by the first target received power parameter can be denoted by p0-NominalWithoutGrant-SBFD, and the second power parameter comprised by the first target received power parameter can be denoted by p0-NominalWithoutGrant-nonSBFD.

[0134] For configured scheduling PUSCH transmission or retransmission on SBFD symbols, j = 1, then P O_NOMINAL,PUSCH,f,c (1) is provided by p0-NominalWithoutGrant-SBFD of p0-NominalWithoutGrant-r19, or if p0-NominalWithoutGrant-SBFD is not provided, then P O_NOMINAL,PUSCH,f,c (1) = P O_NOMINAL,PUSCH,f,c (0).

[0135] For configured scheduling PUSCH transmission or retransmission on nonSBFD symbols, j = 1, then P O_NOMINAL,PUSCH,f,c (1) is provided by p0-NominalWithoutGrant-nonSBFD of p0-NominalWithoutGrant-r19, or if p0-NominalWithoutGrant-nonSBFD is not provided, then P O_NOMINAL,PUSCH,f,c (1) = P O_NOMINAL,PUSCH,f,c (0).

[0136] For j ∈ {2,..., J-1} = S J , P O_NOMINAL,PUSCH,f,c(j) is determined by a second target received power parameter, wherein the second target received power parameter can be denoted as p0-NominalWithGrant-r19, wherein a third power parameter comprised by the second target received power parameter can be denoted as p0-NominalWithGrant-SBFD, and a fourth power parameter comprised by the second target received power parameter can be denoted as p0-NominalWithGrant-nonSBFD.

[0137] wherein P O_NOMINAL,PUSCH,f,c (j) is provided by p0-NominalWithGrant-r19, or p0-NominalWithGrant-r19 is not provided, then P O_NOMINAL,PUSCH,f,c (j) = P O_NOMINAL,PUSCH,f,c (j) = P

[0138] If the PUSCH includes SBFD symbols, P O_NOMINAL,PUSCH,f,c (j) is determined by p0-NominalWithGrant-SBFD of p0-NominalWithGrant-r19;

[0139] If the PUSCH includes nonSBFD symbols, P O_NOMINAL,PUSCH,f,c (j) is determined by p0-NominalWithGrant-nonSBFD of p0-NominalWithGrant-r19.

[0140] It can be understood that the first parameter can include: a first power parameter and a second power parameter, the first power parameter is used to determine the target received power parameter of the configured scheduling PUSCH on the time domain unit of the first type, and the second power parameter is used to determine the target received power parameter of the configured scheduling PUSCH on the time domain unit of the second type. At this time, there is no concept of the first target received power parameter.

[0141] It can be understood that the first parameter can include: a third power parameter and a fourth power parameter, the third power parameter is used to determine the target received power parameter of the dynamically scheduled PUSCH on the time domain unit of the first type, and the fourth power parameter is used to determine the target received power parameter of the dynamically scheduled PUSCH on the time domain unit of the second type. At this time, there is no concept of the second target received power parameter.

[0142] In the embodiments of the present application, the configured scheduling PUSCH on different types adopts different target received powers, which can adapt to different antenna configurations on different symbols, supplement the receiving SNR difference caused by the difference of antenna configurations, and ensure the continuity of user experience.

[0143] The information 3 is used to determine the transmission power of the PUCCH.

[0144] For PUCCH, the first parameter is used to determine a target received power parameter P0 of PUCCH on the first type of time domain unit, and P0 of PUCCH on the second type of time domain unit.

[0145] Optionally, the first parameter can comprise a third target received power parameter applied to PUCCH, and the third target received power parameter comprises: a fifth power parameter for PUCCH on the first type of time domain unit, and a sixth power parameter for PUCCH on the second type of time domain unit.

[0146] In an example, if the UE transmits a PUCCH using the PUCCH power control adjustment state with index l on an active UL BWP b of a carrier f of a primary cell c, the UE determines the PUCCH transmission power P PUCCH,b,f,c (i,qu,qd,l) is:

[0147] wherein P CMAX,f,c (i) is the maximum output power of the UE configured for a carrier f of a primary cell c on a PUCCH transmission occasion i, P O_PUCCH,b,f,c (q u ) is a target received power parameter of PUCCH, q u is an uplink reference signal target received power index; is the number of PRBs of the uplink control channel; PL b,f,c (q d ) is a downlink path loss estimate, q d is a downlink reference signal index; Δ F_PUCCH (F) is an offset for different PUCCH formats, F is the format of the uplink control channel; Δ TFb,f,c (i) is a power adjustment for PUCCH equivalent code rate; g b,f,c (i,l) is a closed loop adjustment of the uplink control channel, l is a power control adjustment index; f is the carrier where the uplink control channel is located, c is the primary cell where the uplink control channel is located, b is the BWP where the uplink control channel is located, i is the PUCCH transmission occasion index.

[0148] The target received power parameter P O_PUCCH,b,f,c (q u ) of PUCCH is composed of a component P O_NOMINAL,PUCCH,f,c (q u ) and a component P O_UE_PUCCH,b,f,c (q u ). P O_NOMINAL,PUCCH,f,c (q uThe second target received power parameter is provided, or if the second target received power parameter is not provided, then P O_NOMINAL,PUCCH,f,c (q u ) = 0. P O_UE_PUCCH,b,f,c (q u The p0-PUCCH-Value is provided by the p0-PUCCH of the activated UL BWP B on carrier f of the primary cell c.

[0149] Where 0≤q u <Q u Q u It is the P provided by the set maxNrofPUCCH-P0-PerSet O_UE_PUCCH The size of the set of values.

[0150] Optionally, the third target received power parameter can be labeled as p0-Nominal-SBFD-r19, the fifth power parameter included in the third target received power parameter can be labeled as p0-Nominal-SBFD, and the sixth power parameter included in the third target received power parameter can be labeled as p0-Nominal-nonSBFD.

[0151] If PUCCH includes the SBFD symbol, P O_NOMINAL,PUCCH,f,c (q u The value of ) is provided by p0-Nominal-SBFD of p0-Nominal-SBFD-r19; or, if p0-Nominal is not provided by carrier f of cell c, then P O_NOMINAL,PUCCH,f,c (q u ) = 0.

[0152] If PUCCH includes the nonSBFD symbol, P O_NOMINAL,PUCCH,f,c (q u The value of ) is provided by p0-Nominal-nonSBFD of p0-Nominal--SBFD-r19; or, if p0-Nominal is not provided by carrier f of cell c, then P O_NOMINAL,PUCCH,f,c (q u ) = 0.

[0153] Understandably, the first parameter may include a fifth power parameter and a sixth power parameter. The fifth power parameter is used to determine the target received power parameter of the PUCCH on the first type of time-domain unit, and the sixth power parameter is used to determine the target received power parameter of the PUCCH on the second type of time-domain unit. In this case, the concept of a third target received power parameter does not exist.

[0154] For PUCCH, different target received powers are used for different types of time domain units, which can adapt to different antenna configurations on different time domain units, supplement the received SNR difference caused by the difference of antenna configurations, and ensure the reliability of PUCCH.

[0155] Information 4 is used to determine the transmission power of SRS.

[0156] For SRS, the first parameter is used to determine the target received power parameter P0 of SRS on the first type of time domain unit, and the P0 of SRS on the second type of time domain unit.

[0157] Optionally, the first parameter can include a fourth target received power parameter applied to SRS, and the fourth target received power parameter includes: a seventh power parameter for SRS on the first type of time domain unit, and an eighth power parameter for SRS on the second type of time domain unit.

[0158] In an example, if the UE transmits an SRS on an active UL BWP b of a carrier f of a serving cell c using an SRS power control adjustment state with index l based on the SRS-ResourceSet configuration, the UE determines the SRS transmission power P SRS,b,f,c (i, q s , l) is formula (3);

[0159] Wherein, P CMAX,f,c (i) is the maximum output power of the UE configured carrier f of the serving cell c on the SRS transmission opportunity i;

[0160] The target received power parameter P O_SRS,b,f,c (q s ) of SRS is determined by the fourth target received power parameter. The SRS resource set q s Is provided by SRS-ResourceSet and SRS-ResourceSetId.

[0161] It can be understood that P O_SRS,b,f,c (q s ) is provided by the fourth target received power parameter of the active UL BWP b on the carrier f of the serving cell c.

[0162] Optionally, the fourth target received power parameter can be marked as p0-r19, the seventh power parameter in the fourth target received power parameter can be marked as: p0-SBFD, and the eighth power parameter in the fourth target received power parameter can be marked as: p0-nonSBFD.

[0163] The P O_SRS,b,f,c (qs ) provided by p0-nonSBFD within p0-r19 of the active UL BWP b on the carrier f of the serving cell c, SRS resource set q s provided by SRS-ResourceSet and SRS-ResourceSetId.

[0164] P of nonSBFD symbol O_SRS,b,f,c (q s ) provided by p0-nonSBFD within p0-r19 of the active UL BWP b on the carrier f of the serving cell c, SRS resource set q s provided by SRS-ResourceSet and SRS-ResourceSetId.

[0165] It can be understood that the first parameter can include a seventh power parameter and an eighth power parameter, the seventh power parameter is used to determine the target received power parameter of the SRS on the time domain unit of the first type, and the eighth power parameter is used to determine the target received power parameter of the SRS on the time domain unit of the second type. At this time, there is no concept of the fourth target received power parameter.

[0166] It can be understood that the SRS in the SRS resource set can be transmitted on different types of time domain units, so that the transmission of the SRS in the SRS resource set is not restricted, and the SRS transmission opportunity is increased.

[0167] The information 5 is used to determine the transmission power of the SSB.

[0168] For the SSB, the first parameter is used to determine the EPRE of the SS or PBCH in the SSB on the time domain unit of the first type, and the EPRE of the SS or PBCH in the SSB on the time domain unit of the second type.

[0169] It can be understood that the EPRE is the energy of one resource element, and the EPRE can be used to determine the energy of one time domain unit, that is, the transmission power.

[0170] Optionally, the first parameter can include a first transmission power parameter applied to the SSB, the first transmission power parameter is used to determine the transmission power of the SSB, and the first transmission power parameter includes a ninth power parameter and a tenth power parameter, the ninth power parameter is used for the SSB on the time domain unit of the first type, and the tenth power parameter is used for the SSB on the time domain unit of the second type. The ninth power parameter is used to determine the transmission power of the SSB on the time domain unit of the first type, and the tenth power parameter is used to determine the transmission power of the SSB on the time domain unit of the second type.

[0171] In an example, the ninth power parameter is used to define or give the transmission power of SSBs on the first type of time domain unit, and the tenth power parameter is used to define or give the transmission power of SSBs on the second type of time domain unit.

[0172] At this time, the first transmission power parameter is marked as ss-PBCH-BlockPower-r19, the ninth power parameter included in the first transmission power parameter can be marked as ss-PBCH-BlockPower-SBFD, and the tenth power parameter included in the first transmission power parameter can be marked as ss-PBCH-BlockPower-nonSBFD. Wherein, ss-PBCH-BlockPower-SBFD is used to determine the transmission power of SSBs on the first type of time domain unit, and ss-PBCH-BlockPower-nonSBFD is used to determine the transmission power of SSBs on the first type of time domain unit.

[0173] The EPRE of SSS in downlink SSBs within SBFD symbols can be derived from the SSB downlink transmission power given by ss-PBCH-BlockPower-SBFD within the parameter ss-PBCH-BlockPower-r19.

[0174] The EPRE of SSS in downlink SSBs within SBFD symbols can be derived from the SSB downlink transmission power given by ss-PBCH-BlockPower-SBFD within the parameter ss-PBCH-BlockPower-r19.

[0175] The EPRE of SSS in downlink SSBs within nonSBFD symbols can be derived from the SSB downlink transmission power given by ss-PBCH-BlockPower-nonSBFD within the parameter ss-PBCH-BlockPower-r19.

[0176] In an example, the ninth power parameter is used to define or give the transmission power of SSBs on the first type of time domain unit, and the tenth power parameter is used to define or give the transmission power of SSBs on the second type of time domain unit with a power offset of SSBs on the first type of time domain unit.

[0177] Optionally, the ninth power parameter is marked as ss-PBCH-BlockPower, and the tenth power parameter can be marked as ss-PBCH-BlockPoweroffset-r19.

[0178] The EPRE of SSS in a downlink SSB can be derived from the SSB downlink transmission power given by the parameters ss-PBCH-BlockPower and ss-PBCH-BlockPoweroffset-r19 provided by higher layers. The downlink SSS transmission power is defined as the linear average of the power contributions (in [W]) of all REs carrying SSS within the operating system bandwidth.

[0179] The EPRE of SSS in a downlink SSB within an SBFD symbol can be derived from the SSB downlink transmission power given by the parameter ss-PBCH-BlockPower.

[0180] The EPRE of SSS in a downlink SSB within a non-SBFD symbol can be derived from the SSB downlink transmission power given by the parameters ss-PBCH-BlockPower and ss-PBCH-BlockPoweroffset-r19.

[0181] Here, the method of offset is adopted, and the possible values of the offset are less, and the signaling overhead can be less.

[0182] In the embodiments of the present application, considering that the equivalent power after beamforming is different under different antenna configurations. In order to achieve the same coverage, therefore, different transmission powers can be used for PBCH on different symbol types. Moreover, the interference conditions on different symbol types are different, and PBCH sets different transmission powers, which can guarantee stable reception quality.

[0183] Information 6 is used to determine the transmission power of CSI-RS.

[0184] For CSI-RS, the first parameter can include an offset parameter applied to the CSI-RS and a second transmission power parameter, wherein the offset parameter is used to determine the power offset of the CSI-RS on the first type of time domain unit and the power offset of the CSI-RS on the second type of time domain unit, and the first transmission power parameter is used to determine the transmission power of the SSB on the first type of time domain unit and the transmission power of the SSB on the second type of time domain unit, or used to determine the transmission power of the SSB on the second type of time domain unit.

[0185] In some embodiments, the transmission power of the CSI-RS on the time domain unit of the first type is determined based on a first EPRE and a first offset, the first EPRE being an EPRE applied to the SSB on the time domain unit of the first type, the first offset being a power offset applied to the CSI-RS on the time domain unit of the first type and the time domain unit of the second type; the transmission power of the CSI-RS on the time domain unit of the second type is determined based on a second EPRE and the first offset, the second EPRE being an EPRE applied to the SSB on the time domain unit of the second type.

[0186] The first offset is an offset of the EPRE of the SSB and the EPRE of the CSI-RS on the time domain unit of the first type and the time domain unit of the second type. It can be understood that the offset parameter is used to determine the first offset, and the power offset of the CSI-RS on the time domain unit of the first type and the power offset of the CSI-RS on the time domain unit of the second type are the same as the first offset.

[0187] In an example, the offset parameter is denoted as powerControlOffsetSS. The second transmission power parameter is denoted as ss-PBCH-BlockPower-r19, and the second transmission power parameter includes ss-PBCH-BlockPower-SBFD for determining the first EPRE and ss-PBCH-BlockPower-nonSBFD for determining the second EPRE.

[0188] The EPRE of the downlink CSI-RS can be derived from the SSB downlink transmission power given by the parameter ss-PBCH-BlockPower-r19 provided by the higher layer and the CSI-RS offset given by the parameter powerControlOffsetSS provided by the higher layer.

[0189] The EPRE of the downlink CSI-RS within the SBFD symbol can be derived from the SSB downlink transmission power given by ss-PBCH-BlockPower-SBFD within the parameter ss-PBCH-BlockPower-r19 provided by the higher layer and the first offset given by the parameter powerControlOffsetSS provided by the higher layer.

[0190] The EPRE of the downlink CSI-RS within the nonSBFD symbol can be derived from the SSB downlink transmission power given by ss-PBCH-BlockPower-nonSBFD within the parameter ss-PBCH-BlockPower-r19 provided by the higher layer and the first offset given by the parameter powerControlOffsetSS provided by the higher layer.

[0191] In the embodiments of the present application, it is considered that the equivalent power after beamforming is different under different antenna configurations. In order to achieve the same coverage, different transmission powers can be used for CSI-RS on different symbol types. Meanwhile, it is considered in the prior art that the CSI-RS power is related to PBCH, so the transmission power of CSI-RS on different symbol types can be determined by referring to the PBCH power parameter on the corresponding symbol type.

[0192] In some embodiments, the transmission power of the CSI-RS on the time domain unit of the first type is based on the EPRE of the SSB and a second offset, the second offset being a power offset applied to the CSI-RS on the time domain unit of the first type;

[0193] The transmission power of the CSI-RS on the time domain unit of the second type is based on the EPRE of the SSB and the third offset, the third offset being a power offset applied to the CSI-RS on the time domain unit of the second type.

[0194] Here, the second offset is the offset of the EPRE of the SSB and the EPRE of the CSI-RS on the time domain unit of the first type, and the third offset is the offset of the EPRE of the SSB and the EPRE of the CSI-RS on the time domain unit of the first type.

[0195] It can be understood that the EPRE of the SSB here is the EPRE of the SSB under the condition that the time domain unit is not distinguished between the first type and the second type.

[0196] In an example, the offset parameter includes a first offset parameter indicating the second offset and a second offset parameter indicating the third offset, wherein the first offset parameter is marked as powerControlOffsetSS-SBFD, the second offset parameter is marked as powerControlOffsetSS-nonSBFD, and the second transmission power parameter is marked as ss-PBCH-BlockPower, which is used for a given EPRE of SSB.

[0197] At this time, the transmission power of the CSI-RS on the time domain unit of different types can be determined by the EPRE of the same SSB and different offsets.

[0198] The EPRE of the downlink CSI-RS can be derived by the parameter ss-PBCH-BlockPower provided by the higher layer, the given SSB downlink transmission power, and the parameters powerControlOffsetSS and powerControlOffsetSS-r19 provided by the higher layer, which are given CSI-RS offsets.

[0199] The EPRE of the downlink CSI-RS in the SBFD symbol can be derived by the parameter ss-PBCH-BlockPower provided by the higher layer, the downlink transmission power of the given SSB, and the CSI-RS offset given by the parameter powerControlOffsetSS-SBFD provided by the higher layer.

[0200] The EPRE of the downlink CSI-RS in the nonSBFD symbol can be derived by the parameter ss-PBCH-BlockPower provided by the higher layer, the downlink transmission power of the given SSB, and the CSI-RS offset given by the parameter powerControlOffsetSS-nonSBFD provided by the higher layer.

[0201] In the embodiments of the present application, considering that the equivalent power after beamforming is different under different antenna configurations. In order to achieve the same coverage. Therefore, different transmission powers can be used for CSI-RS on different symbol types. At the same time, considering that the CSI-RS power in the prior art is related to the PBCH, therefore, the CSI-RS on different symbol types can obtain the power on the other symbol type by introducing an offset while referring to the same PBCH power parameter.

[0202] In some embodiments, the transmission of the channel can have the following constraints:

[0203] Constraint 1, the ratio of the EPRE of the physical downlink control channel (PDCCH) and the EPRE of the CSI-RS in the same type of time domain unit is 0 decibel; and / or;

[0204] Constraint 2, the SRS in the same SRS resource set is configured on the same type of time domain unit; and / or,

[0205] Constraint 3, the EPRE of the synchronization signal (SS) in different SSBs on the same type of time domain unit is the same, and / or, the EPRE of the physical broadcast channel (PBCH) in different SSBs on the same type of time domain unit is the same.

[0206] For constraint 1, the ratio of the EPRE of the PDCCH and the EPRE of the CSI-RS on the first type of time domain unit is assumed to be 0 dB; the ratio of the EPRE of the PDCCH and the EPRE of the CSI-RS on the first type of time domain unit is assumed to be 0 dB.

[0207] In an example, for link recovery, the ratio of the EPRE of the PDCCH and the EPRE of the NZP CSI-RS in the SBFD symbol or the nonSBFD symbol is assumed to be 0 dB.

[0208] For constraint 2, SRS in the same SRS resource set is only transmitted in one type of time domain unit.

[0209] It can be understood that the SRS in the same SRS resource set is transmitted in the first type of time domain unit or the second type of time domain unit.

[0210] In an example, the SRS in the same SRS resource set is transmitted in SBFD symbols or nonSBFD symbols.

[0211] In the embodiment of the application, only the SRS in the SRS resource set is constrained on one type of time domain unit, without power enhancement, and can be upgraded by scheduling, with low upgrade complexity.

[0212] For constraint 3, the EPRE of SS in different SSBs on the same type of time domain unit is the same, and / or the EPRE of physical broadcast channel PBCH in different SSBs on the same type of time domain unit is the same.

[0213] It can be understood that the EPRE of SSS or PBCH in different SSBs belonging to different types of time domain units is different.

[0214] Here, the SSB can be used for measurement, and when the terminal measures based on the SSB, the EPRE of SS in different SSBs on the same type of time domain unit is the same, and / or the EPRE of physical broadcast channel PBCH in different SSBs on the same type of time domain unit is the same.

[0215] Optionally, the SSB measurement includes but is not limited to SS-RSRP, SS-RSRQ and SS-SINR.

[0216] In the embodiment of the application, for the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurement, the UE can assume that the downlink EPRE is constant for different bandwidths. For the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurement, the UE can assume that the downlink EPRE of SSS carried on the SSB within SBFD or nonSBFD is constant. For the purpose of SS-RSRP, SS-RSRQ and SS-SINR measurement, the UE can assume that the ratio of SSS EPRE to DM-RS EPRE is 0dB within SBFD or nonSBFD.

[0217] Considering that the equivalent power after beamforming is different under different antenna configurations. And in order to be able to use the power of the network device to the maximum, that is, to send at full power, to achieve the optimal coverage. Therefore, the received power of SS or PBCH on different symbol types can be independently assumed, so that the power of each symbol type is optimal.

[0218] An optional processing procedure of the wireless communication method provided by the embodiments of the present application is applied to a terminal device, as shown in FIG. 6, and includes the following steps:

[0219] S601, the terminal device receives a second parameter, the second parameter including one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on a first type of time domain unit and frequency domain transmission resources on a second type of time domain unit, or the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit; a carrier or a carrier group on the first type of time domain unit including frequency domain resources of different directions, and a carrier or a carrier group on the second type of time domain unit including frequency domain resources of only one direction.

[0220] An optional processing procedure of the wireless communication method provided by the embodiments of the present application is applied to a network device, as shown in FIG. 7, and includes the following steps:

[0221] S701, the network device sends a second parameter, the second parameter including one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on a first type of time domain unit and frequency domain transmission resources on a second type of time domain unit, or the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit; a carrier or a carrier group on the first type of time domain unit including frequency domain resources of different directions, and a carrier or a carrier group on the second type of time domain unit including frequency domain resources of only one direction.

[0222] An optional processing procedure of the wireless communication method provided by the embodiments of the present application is applied to a wireless communication system including a network device and a terminal device, as shown in FIG. 8, and includes the following steps:

[0223] S801, the network device sends a second parameter to the terminal device, the second parameter including one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on a first type of time domain unit and frequency domain transmission resources on a second type of time domain unit, or the second parameter being used to determine frequency domain transmission resources on the first type of time domain unit; a carrier or a carrier group on the first type of time domain unit including frequency domain resources of different directions, and a carrier or a carrier group on the second type of time domain unit including frequency domain resources of only one direction.

[0224] In the following, the wireless communication method shown in FIG. 6, FIG. 7 and FIG. 8 is further described.

[0225] The first type of time domain unit can be understood as an SBFD time domain unit, and the carrier or carrier group on the time domain unit of this type includes frequency domain resources of different directions in any one or more carriers. In an example, the carrier or carrier group on the time domain unit of the first type includes an uplink transmission part, i.e., an uplink subband (UL subband), and a downlink transmission part, i.e., a downlink subband (DL subband).

[0226] It can be understood that in the first type of time domain unit, the activated BWP contains frequency domain resources of different directions.

[0227] The second type of time domain unit can be understood as a nonSBFD time domain unit, and all carriers in the carrier or carrier group on the time domain unit of this type include frequency domain resources of only one direction. In an example, the carrier or carrier group on the time domain unit of the second type is used only for uplink transmission or downlink transmission.

[0228] It can be understood that in the second type of time domain unit, the activated BWP contains frequency domain resources of only one direction.

[0229] In the embodiments of the present application, the frequency domain transmission resource can be understood as a frequency domain resource used for channel or signal transmission on a time domain unit, wherein the channel or signal transmitted on the time domain unit can include PUSCH, PUCCH, SRS, PDSCH, etc.

[0230] In the wireless communication method shown in FIGS. 6, 7, and 8, the first type of symbol can be referred to as a symbol with an uplink subband (Symbol with UL subband), and the second type of symbol can be referred to as a normal symbol (Normal symbol).

[0231] In the embodiments of the present application, if the second parameter includes one frequency domain resource allocation parameter, it can be considered that the base station defaults that the activated BWP on the time domain unit includes only one direction of transmission. If the second parameter includes two frequency domain resource allocation parameters, the activated BWP on the time domain unit can include only one direction of transmission, or can include two directions of transmission.

[0232] It can be understood that the carrier group is one or more carriers sharing a radio frequency channel, and usually one or more carriers in one band belong to the same carrier group, or one or more carriers in adjacent bands belong to the same carrier group.

[0233] The second parameter configured by the network device is used to determine the frequency domain transmission resource on the first type of time domain unit and the second type of time domain unit, or is used to determine only the frequency domain transmission resource on the first type of time domain unit.

[0234] In the embodiments of the present application, one time domain unit can be used to transmit one or more channels, and the frequency domain transmission resources of different channels can be different.

[0235] In the embodiments of the present application, the second parameter can include one frequency domain resource allocation parameter or two frequency domain resource allocation parameters. When the active BWP in the SBFD symbol contains only one transmission direction, the available transmission resources in the active BWP in the SBFD symbol and the non-SBFD symbol are consistent, a unified frequency domain resource allocation scheme is adopted, for example, a set of frequency domain resource parameters are used, which can reduce the complexity of the terminal and the network. In addition, configuring one frequency domain resource parameter can meet the transmission requirements of the SBFD symbol and the non-SBFD symbol, and can also reduce unnecessary signaling overhead. When the active BWP in the SBFD symbol contains one transmission direction and other (other can be a guard interval, that is, unavailable resources, or other transmission directions), the available transmission resources in the active BWP in the SBFD symbol and the non-SBFD symbol are inconsistent, and two frequency domain resource parameters are configured, which can meet the frequency domain resource configuration requirements of the two types of time domain units, can optimize the frequency domain resource allocation on various time domain units, and avoid unnecessary invalid allocation. Therefore, through the scheme of multiple parameter numbers, the diversity of the transmission direction configuration in the active BWP can be adapted.

[0236] In the embodiments of the present application, if the second parameter includes one frequency domain resource allocation parameter, the one frequency domain resource allocation parameter is applicable to all symbol / slot types, and the symbol / slot type at least contains the first symbol / slot type, and any one or more carriers in the carrier or carrier group on the symbol / slot type contains an uplink transmission part (UL subband) and a downlink transmission part (DL subband). Further, it is considered that the active BWP contains only the uplink transmission part (UL subband) or the downlink transmission part (DL subband). Or, the active BWP contains only the uplink transmission part (UL subband) or the downlink transmission part (DL subband) is expected to be configured with only one set of frequency domain resource allocation parameters, that is, it is not expected to be configured with two sets of frequency domain resource allocation parameters. If the terminal receives one frequency domain resource allocation parameter, unnecessary signaling overhead can be reduced, and to some extent, it is also a recheck of the UL subband configuration.

[0237] In the embodiments of the present application, the wireless communication method shown in FIG. 3, FIG. 4 and FIG. 5 can be combined with the wireless communication method shown in FIG. 6, FIG. 7 and FIG. 8 without conflict, or can be implemented alone.

[0238] In some embodiments, if the second parameter only includes one frequency domain resource allocation parameter, the one frequency domain resource allocation parameter is used to determine the frequency domain transmission resources on the time domain units of the first type and the time domain units of the second type.

[0239] Here, the one frequency domain resource allocation parameter included in the second parameter is used for all types of time domain units. It can be understood that the second parameter here is used to determine the frequency domain transmission resources on the time domain units of the first type and the time domain units of the second type.

[0240] In the embodiments of the present application, the one frequency domain resource allocation parameter included in the second parameter can be a frequency domain resource allocation parameter for the time domain units of the first type already defined in the protocol, or a newly defined frequency domain resource allocation parameter.

[0241] In the embodiments of the present application, the one frequency domain resource allocation parameter included in the second parameter is applicable to all types. Further, it can be considered that the active BWP only includes an uplink transmission part (UL subband) or a downlink transmission part (DL subband). Or, the active BWP only includes an uplink transmission part (UL subband) or a downlink transmission part (DL subband) is only expected to be configured with one frequency domain resource allocation parameter, i.e., not expected to be configured with two frequency domain resource allocation parameters.

[0242] In some embodiments, if the second parameter only includes one frequency domain resource allocation parameter, the one frequency domain resource allocation parameter is used to enable frequency domain transmission resource allocation enhancement on the time domain units of the first type.

[0243] The frequency domain transmission resource allocation enhancement on the time domain units of the first type in the embodiments of the present application can be understood as enabling the allocated frequency domain transmission resources to be within the effective frequency domain resources on the time domain units of the first type by the one frequency domain resource allocation parameter included in the second parameter. The effective frequency domain resources can be understood as the available frequency domain resources belonging to one transmission direction.

[0244] Further, if the terminal device does not receive the second parameter or the second parameter is configured as “not enabled”, the same frequency domain resource allocation manner is adopted for all types of time domain units.

[0245] Further, the second parameter can be for one frequency domain resource allocation manner, for example, frequency hopping, or for multiple frequency domain resource allocation manners, for example, frequency hopping and RB numbering, or both. Here, the second parameter is only used to determine the frequency domain transmission resources on the time domain units of the first type.

[0246] As shown in 901 of FIG. 9, the downlink resource is divided into two parts by the UL subband. In order to avoid the overlap between the downlink continuous scheduling resource and the UL subband, the RBs of the downlink resource can be renumbered, as shown in 902 of FIG. 9, so that the continuous scheduling resource can avoid the UL subband. However, for the case where the UL subband is not contained in the active BWP, such as the DL BWP 2 in FIG. 9, the RB renumbering is unnecessary. Therefore, whether the terminal enables the RB renumbering operation on the SBFD symbol can be configured by RRC signaling. When the DL BWP does not contain the UL subband, the network side does not configure the second parameter or configures the second parameter as “not enabled”. When the DL BWP contains the UL subband, the network side configures the second parameter as “enabled”.

[0247] As shown in FIG. 10, when the UL BWP contains resources other than the UL subband, the frequency hopping range of the terminal device on the SBFD symbol and the non-SBFD symbol is different. For the SBFD symbol, the frequency hopping boundary is the upper and lower boundaries of the intersection of the UL subband and the resources of the UL BWP. For the non-SBFD symbol, the frequency hopping boundary is the UL BWP. When the UL BWP contains only the UL subband, the frequency hopping range of the terminal on the SBFD symbol and the non-SBFD symbol is the same, both of which are the UL BWP. Therefore, whether the terminal enables the frequency hopping boundary determination according to the boundary of the intersection of the UL subband and the resources of the UL BWP on the SBFD symbol can be configured by RRC signaling. When the UL BWP contains only the UL subband, the network side does not configure the second parameter or configures the second parameter as “not enabled”. When the UL BWP contains resources other than the UL subband, the network side configures the second parameter as “enabled”.

[0248] In the embodiments of the present application, if it is considered that the active BWP contains only the uplink transmission part (UL subband) or the downlink transmission part (DL subband), only one frequency domain resource allocation parameter can be effective, which can be the frequency domain resource configuration for the second type of time domain unit. Generally, the frequency domain resource allocation parameter can be an existing parameter in the protocol, or a defined parameter with the same meaning as the existing parameter.

[0249] In some embodiments, if the second parameter contains two frequency domain resource allocation parameters, the two frequency domain resource allocation parameters are respectively used to determine the frequency domain transmission resource on the first type of time domain unit and the frequency domain transmission resource on the second type of time domain unit.

[0250] In the embodiments of the present application, if the second parameter includes two frequency domain resource allocation parameters, the two frequency domain resource allocation parameters can be identified as a first frequency domain resource allocation parameter and a second frequency domain resource allocation parameter. The first frequency domain resource allocation parameter is used to determine the frequency domain transmission resource on the time domain unit of the first type, and the second frequency domain resource allocation parameter is used to determine the frequency domain transmission resource on the time domain unit of the second type.

[0251] In the embodiments of the present application, if the second parameter includes two frequency domain resource allocation parameters, the first type of time domain unit corresponding to the first frequency domain resource allocation parameter is activated by default on the BWP including different direction transmission or including impossible to use resources, for example, a guard band, and the second type of time domain unit corresponding to the second frequency domain resource allocation parameter is activated by default on the BWP including only one direction transmission.

[0252] In the embodiments of the present application, the activated BWP includes an uplink transmission part (UL subband) and a downlink transmission part (DL subband), or includes impossible to use resources, for example, a guard band, and expects to be configured with two frequency domain resource allocation parameters, that is, does not expect to be configured with one frequency domain resource allocation parameter.

[0253] The second parameter includes the first frequency domain resource allocation parameter or the second frequency domain resource allocation parameter, and a second offset parameter, wherein the second offset parameter represents an offset amount between the first frequency domain resource allocation parameter and the second frequency domain resource allocation parameter.

[0254] In the embodiments of the present application, the frequency domain transmission resources on the time domain units of different types can be independently configured, or can be determined by a configured reference value and a second offset value, wherein the reference value is used to determine the frequency domain transmission resources on the time domain units of the first type or the second type, and the second offset value is used to determine the offset amount between the frequency domain transmission resources on the time domain units of the first type and the frequency domain transmission resources on the time domain units of the second type.

[0255] In some embodiments, the same type of different time domain units share the same frequency domain resource allocation parameter.

[0256] In some embodiments, the frequency domain resource allocation parameter includes one or more of the following:

[0257] Parameter 1, frequency domain resource indication (FDRA) parameter;

[0258] Parameter 2, frequency hopping parameter;

[0259] Parameter 3, PUCCH resource parameter or PUCCH resource set parameter;

[0260] Parameter 4, SRS resource set parameter;

[0261] Parameter 5, a semi-static scheduling (SPS) parameter;

[0262] Parameter 6, a configured scheduling configuration parameter.

[0263] If the second parameter includes two frequency domain resource allocation parameters, one of the frequency domain resource allocation parameters includes two values, respectively corresponding to the first type of time domain unit and the second type of time domain unit.

[0264] In some embodiments, the frequency hopping parameter includes a frequency hopping range.

[0265] In some embodiments, the SRS resource set parameter includes, but is not limited to, one or more of the following parameters: freqDomainPosition, reqDomainShiftf, freqHopping.

[0266] In some embodiments, the PUCCH resource parameter includes:

[0267] First offset information, the first offset information indicating a relative offset of a starting resource block (RB) of the PUCCH in an uplink resource;

[0268] First bandwidth information, the first bandwidth information indicating a bandwidth of the uplink resource on a downlink time domain unit.

[0269] Here, the uplink resource can be understood as an uplink BWP or an uplink subband.

[0270] In the embodiments of the present application, if the second parameter includes only one frequency domain resource allocation parameter, the first offset information indicates a relative offset of a starting resource block (RB) of the PUCCH in an uplink BWP, and the first bandwidth information indicates a bandwidth of the uplink BWP.

[0271] In the embodiments of the present application, if the second parameter includes only one frequency domain resource allocation parameter, the first offset information indicates a relative offset of a starting resource block (RB) of the PUCCH in an uplink BWP, and the first bandwidth information indicates a bandwidth of the uplink BWP.

[0272] For the first type of time domain unit, the first offset information indicates a relative offset of a starting resource block (RB) of the PUCCH in an uplink subband, and the first bandwidth information indicates a bandwidth of the uplink subband.

[0273] For the second type of time domain unit, the first offset information indicates a relative offset of a starting resource block (RB) of the PUCCH in an uplink BWP, and the first bandwidth information indicates a bandwidth of the uplink BWP.

[0274] In an example, the PUCCH starting frequency domain resource and the frequency hopping parameter - two PUCCH frequency domain resource parameters are defined with reference to UL-subband / UL BWP configuration.

[0275] If and the UE is provided PUCCH resources by pucch-ResourceCommon and useInterlacePUCCH-PUSCH is not provided in BWP-UplinkCommon. Then:

[0276] The lowest index of PUCCH transmission determined by the UE within the first hop is and the lowest index of PUCCH transmission determined by the UE within the second hop is where N CS is the total number of initial cyclic shift indices in the initial cyclic shift index set, and in the second type of time domain unit, denotes the relative offset of the starting RB of the PUCCH configuration within the UL BWP, denotes the bandwidth of the UL BWP. In the second type of time domain unit, denotes the relative offset of the starting RB of the PUCCH configuration within the UL-subband, denotes the bandwidth of the UL subband.

[0277] The UE determines the initial cyclic shift index in the initial cyclic shift index set as PUCCH (r CS / 8) mod N

[0278] In some embodiments, the first hop and the second hop of the PUCCH transmission are located within the same type of time domain unit.

[0279] It can be understood that the first hop PUCCH transmission and the second hop PUCCH transmission are located on the symbol with UL subband or the normal symbol.

[0280] In the embodiments of the present application, further, the two hops of the PUCCH are on the same symbol / slot type. This constraint can avoid the complex processing and loss of combining gain caused by the difference in transmission effect of different types of symbols, and can ensure that the PUCCH is within the effective uplink resource.

[0281] In some embodiments, the SRSs in the SRS resource set are transmitted within the same type of time domain unit.

[0282] The SRSs of each SRS resource set can only be transmitted on one type of time domain unit, and the type can be indicated by RRC signaling.

[0283] In some embodiments, for different SRS resource sets, transmission can be performed on different types of time domain units.

[0284] In some embodiments, the repeated transmission of the SRS is transmitted within one type of time domain unit.

[0285] For SRS with multiple repetitions, only the transmission on one type of time domain unit is required.

[0286] In some embodiments, in case the repeated transmission of the SRS is transmitted within one type of time domain unit, the SRS on other types of time domain units is dropped.

[0287] In one example, if the repeated transmission of the SRS is transmitted on the first type of time domain unit, the repeated transmission of the SRS on the second type of time domain unit is dropped.

[0288] In one example, if the repeated transmission of the SRS is transmitted on the second type of time domain unit, the repeated transmission of the SRS on the first type of time domain unit is dropped.

[0289] In the embodiments of the present application, the number of repetitions of the SRS can be less than the configured number of repetitions.

[0290] In some embodiments,

[0291] For SPS / Type 2 configured scheduling, only PDSCH or PUSCH is transmitted on the third type of time domain unit, the third type being the first type or the second type, the third type being determined by protocol convention, RRC signaling configuration, or the type of time domain unit where the first periodic PDSCH or PUSCH is indicated by downlink scheduling or uplink scheduling.

[0292] It can be understood that, for SPS, only PDSCH is transmitted on one type of time domain unit. The type is determined by protocol convention, RRC signaling configuration, or the type of time domain unit where the first periodic PDSCH is indicated by downlink scheduling (DL grant). Alternatively, the type is the type of time domain unit where the first PDSCH is indicated by the DL grant. This scheme is simple and easy to operate.

[0293] It can be understood that, for Type 2 configured scheduling (Configure Grant), only PUSCH is transmitted on one type of time domain unit. The type is determined by protocol convention, RRC signaling configuration, or the type of symbol where the first PUSCH is indicated by uplink scheduling (UL grant).

[0294] Alternatively, the type is the type of time domain unit where the first PUSCH is indicated by the UL grant.

[0295] In some embodiments, for SPS or Type 2 configured scheduling:

[0296] The frequency domain resource of the PDSCH or PUSCH in the first period is determined according to the frequency domain resource indicated by the downlink scheduling or uplink scheduling;

[0297] The frequency domain resource of the first PDSCH or PUSCH is determined according to the frequency domain resource indicated by the downlink scheduling or uplink scheduling, and the first PDSCH or PUSCH is the PDSCH or PUSCH in other periods whose type of time domain unit is the same as that of the PDSCH or PUSCH in the first period;

[0298] The frequency domain resource of the second PDSCH or PUSCH is determined according to the RRC or the frequency domain resource indicated by the downlink scheduling or uplink scheduling, and the second PDSCH or PUSCH is the PDSCH or PUSCH in other periods whose type of time domain unit is different from that of the PDSCH or PUSCH in the first period.

[0299] It can be understood that for SPS, the PDSCH in different periods can be transmitted on different types of time domain units. For the frequency domain resource of the PDSCH in the first period, i.e. the first PDSCH transmission opportunity, the frequency domain resource indicated by the DL grant is determined. For the PDSCH occurring in other periods, if the type of the time domain unit where the PDSCH is located is the same as that of the PDSCH in the first period, the frequency domain resource of the PDSCH is determined according to the frequency domain resource indicated by the DL grant, and if the type of the time domain unit where the PDSCH is located is different from that of the PDSCH in the first period, the PDSCH is determined according to the frequency domain resource configured by the RRC signaling, such as SPS-Config. The RRC signaling can directly configure the frequency domain resource of the PDSCH occurring in the other periods, or can configure the frequency domain resource offset of the PDSCH on the two types of symbols.

[0300] It can be understood that, for Type 2 Configure Grant, PUSCHs in different periods can be transmitted on different types of time domain units. For the frequency domain resource of the PUSCH in the first period, i.e., the first PUSCH transmission opportunity, the frequency domain resource indicated by the UL grant is determined. For the PUSCHs occurring in other periods, if the type of the time domain unit in which the PUSCH is located is the same as the type of the time domain unit in which the PUSCH in the first period is located, the frequency domain resource of the PUSCH is determined according to the frequency domain resource indicated by the UL grant; if the type of the time domain unit in which the PUSCH is located is different from the type of the time domain unit in which the PUSCH in the first period is located, the frequency domain resource of the PUSCH is determined according to the frequency domain resource configured by RRC signaling, for example, configuredGrantConfig. The RRC signaling can directly configure the frequency domain resource of the PUSCH occurring in the other periods, or can configure the frequency domain resource offset of the PUSCH on two types of symbols.

[0301] In the embodiments of the application, the resource allocation is more flexible. The frequency domain resource of the first period is determined according to the UL grant or the DL grant, which is easy for base station scheduling, because the time domain resource in the first period is determined by the UL grant or the DL grant, the base station can determine the symbol type in advance and give the corresponding frequency domain resource indication. Other symbol types in other periods can be configured by RRC, which reduces the influence on the design of DCI. Configuring resources by two types of signaling also enhances the flexibility of resource allocation.

[0302] It should be noted that, in the embodiments of the application, for SPS, the transmission of PDSCH includes but is not limited to one or more of the following three ways:

[0303] A1, for SPS, only PDSCH is transmitted on one type of symbol. The symbol type is determined by the protocol, RRC signaling configuration, or the symbol type in which the first PDSCH indicated by the DL grant is located, i.e., the symbol type in which the first PDSCH indicated by the DL grant is located is the symbol type.

[0304] For SPS, PDSCH in different periods can be transmitted on different types of symbols. For the frequency domain resource of PDSCH in the first period, i.e. the first PDSCH transmission opportunity, the frequency domain resource indicated by the DL grant is determined. For the PDSCH in the symbol type of the other period, the frequency domain resource is determined according to the frequency domain resource indicated by the DL grant. For the case where the symbol type of the PDSCH in the other period is different from the symbol type of the PDSCH in the first period, the frequency domain resource of the PDSCH in the other period is determined according to the RRC signaling, such as SPS-Config. The RRC signaling can directly configure the frequency domain resource of the PDSCH in the other period, or can configure the frequency domain resource offset of the PDSCH on two types of symbols.

[0305] For SPS, PDSCH in different periods can be transmitted on different types of symbols. The DL grant indicates the frequency domain resource of PDSCH on two types of symbols. Among them, two frequency domain resource information fields, such as frequencyDomainAllocation, can be used, or one frequency domain information field can be used to obtain two frequency domain resources through two interpretation methods. For example, the frequency domain resource of PDSCH on the first type of symbol is directly obtained from the DL grant frequencyDomainAllocation. On this basis, the frequency domain resource of PUSCH on the second type of symbol is obtained by frequency domain offset. Whether the first type of symbol is a normal symbol or a symbol with UL subband is configured by RRC signaling. The same is true for the second type of symbol. Alternatively, the first type of symbol is the symbol in which the PDSCH in the first period is located.

[0306] It should be noted that in the embodiments of the present application, for type 2 configured scheduling, the transmission of PUSCH includes but is not limited to one or more of the following three ways:

[0307] For Type 2 Configure Grant, PUSCH is only transmitted on one type of symbol. The symbol type is determined by the protocol agreement, RRC signaling configuration, or the symbol type in which the first PUSCH is located indicated by the UL grant, i.e. the symbol type in which the first PUSCH is located indicated by the UL grant is the symbol type.

[0308] For Type 2 Configure Grant, PUSCH in different periods can be transmitted on different types of symbols. For the frequency domain resource of PUSCH in the first period, i.e. the first PUSCH transmission opportunity, it is determined according to the frequency domain resource indicated by the UL grant. For the symbol type of PUSCH in other periods, it is the same as that of PUSCH in the first period, and the frequency domain resource is determined according to the frequency domain resource indicated by the UL grant. For the case where the symbol type of PUSCH in other periods is different from that of PUSCH in the first period, the frequency domain resource of PUSCH in other periods is determined according to the RRC signaling, such as configuredGrantConfig. The RRC signaling can directly configure the frequency domain resource of PUSCH in other periods, or can configure the frequency domain resource offset of PUSCH on two types of symbols.

[0309] For Type 2 Configure Grant, PUSCH in different periods can be transmitted on different types of symbols. The UL grant indicates the frequency domain resource of PUSCH on two types of symbols. Specifically, two frequency domain resource information fields, such as frequencyDomainAllocation, can be used, or one frequency domain information field can be used to obtain two frequency domain resources through two interpretation methods. For example, the frequency domain resource of PUSCH on the first type of symbol is directly obtained from the UL grant frequencyDomainAllocation. On this basis, the frequency domain resource of PUSCH on the second type of symbol is obtained by frequency domain offset. Whether the first type of symbol is a normal symbol or a symbol with UL subband is configured by RRC signaling. The same applies to the second type of symbol. Alternatively, the first type of symbol is the symbol in which PUSCH in the first period is located.

[0310] For Type 2 Configure Grant, the UL grant has limited variables (to avoid increasing blind detection). The benefits of the three methods are similar to SPS.

[0311] It can be understood that if the configured scheduling is type 1 configured scheduling (ype 1 Configure Grant), the configured grant transmission resource configuration information configuredGrantConfig contains 2 frequency domain resource information. Among them, it can be 2 independent frequency domain resource information, for example, 2 frequencyDomainAllocation are respectively used for PUSCH transmission on Normal symbol and symbol with UL subband. It can also be configured to have one frequencyDomainAllocation and one offset value, which are respectively used for PUSCH transmission on Normal symbol and symbol with UL subband. Among them, the offset value can be directly configured, or it can be determined through the UL subband configuration. For example, according to the starting point deviation of the UL subband and the UL BWP.

[0312] Further, the configured grant transmission resource configuration information configuredGrantConfig contains 2 frequency hopping information. Specifically, it can be 2 independent frequency hopping information, for example, 2 frequencyHoppingOffset are respectively used for PUSCH transmission on Normal symbol and symbol with UL subband.

[0313] Further, the configured grant transmission resource configuration information configuredGrantConfig contains 2 time domain resource information. Specifically, it can be 2 independent time domain resource information, for example, 2 timeDomainAllocation are respectively used for PUSCH transmission on Normal symbol and symbol with UL subband.

[0314] For Type1CG, the signaling overhead is not sensitive, and more flexible scheduling can be supported by increasing signaling.

[0315] In the above description, the transmission of different channels or signals is described by taking a symbol as an example, and the symbol herein can be replaced by a slot or other time domain unit.

[0316] It should be noted that the first parameter and / or the second parameter exchanged in the wireless communication method provided by the embodiments of the present application can be applied to a communication system comprising a first node and a second node, the first node can be a terminal or a base station, and the second node can be a base station or a terminal. Therefore, the method is applicable to any link between a base station and a terminal, a terminal and a base station, and terminals.

[0317] The wireless transmission method provided by the embodiments of the present application involves the following two parameter configuration schemes:

[0318] Parameter configuration scheme 1: at least one of the parameters in the transmission power is related to whether the uplink sub-band is configured on the carrier / carrier group.

[0319] Parameter configuration scheme 2: at least one of the parameters in the frequency domain resource allocation and frequency hopping parameters is related to whether the uplink sub-band is included.

[0320] The power parameters and the resource allocation parameters use different decision methods. The power parameters not only include the uplink power control parameter determination method, but also include the downlink power parameter determination method and the power relationship constraint between multiple downlink signals. The resource allocation parameters include a method of configuring a set of resource allocation parameters and a method of configuring two sets of resource allocation parameters, so that the system resources can be used more efficiently.

[0321] The preferred embodiments of the present application are described in detail above with reference to the accompanying drawings, but the present application is not limited to the specific details in the above-described embodiments. Within the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application, and these simple modifications all belong to the protection scope of the present application. For example, in the above-described specific embodiments, various specific technical features described in the embodiments can be combined in any appropriate manner without contradiction. In order to avoid unnecessary repetition, the present application does not further describe various possible combination manners. For another example, various different embodiments of the present application can also be combined in any manner, as long as it does not deviate from the idea of the present application, and it should also be considered as disclosed by the present application. For another example, under the premise of no conflict, each embodiment described in the present application and / or the technical features in each embodiment can be combined with any prior art, and the technical solutions obtained after combination should also fall within the protection scope of the present application.

[0322] It should also be understood that the size of the sequence number of the above-mentioned processes does not mean the order of execution in various method embodiments of the present application, and the execution order of the processes should be determined according to its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink", "uplink" and "sidelink" are used to represent the transmission direction of signals or data, wherein "downlink" is used to represent the first direction of the transmission direction of signals or data from the station to the user equipment of the cell, "uplink" is used to represent the second direction of the transmission direction of signals or data from the user equipment of the cell to the station, and "sidelink" is used to represent the third direction of the transmission direction of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" represents that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is only used to describe the association relationship of the associated objects, and indicates that there can be three relationships. Specifically, A and / or B can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are in an "or" relationship.

[0323] FIG. 11 is a schematic diagram of an optional structure of a terminal device according to an embodiment of the present application. As shown in FIG. 11, the terminal device 1100 includes:

[0324] The first communication unit 1101 is configured to receive a first parameter, wherein the first parameter is used to determine a first power parameter and a second power parameter, the first power parameter is a power parameter applied to a first type of time domain unit, and the second power parameter is a power parameter applied to a second type of time domain unit, wherein a carrier or a carrier group on the first type of time domain unit includes frequency domain resources in different directions, and a carrier or a carrier group on the second type of time domain unit includes frequency domain resources in only one direction.

[0325] In some embodiments, the same signal or channel on different time domain units of the same type shares the same power parameter.

[0326] In some embodiments,

[0327] The first parameter includes: the first power parameter and the second power parameter; or,

[0328] The first parameter includes: the first power parameter or the second power parameter, and a first offset parameter, wherein the first offset parameter represents an offset amount between the first power parameter and the second power parameter.

[0329] In some embodiments, the power parameter is used to determine one or both of: the received power of an uplink channel; and the transmitted power of a downlink channel.

[0330] In some embodiments, the uplink channel comprises one or more of: a physical uplink shared channel (PUSCH); a physical uplink control channel (PUCCH); a sounding reference signal (SRS).

[0331] In some embodiments, the downlink channel comprises one or more of: a synchronization signal (SS); a physical broadcast channel (PBCH); a channel state information reference signal (CSI-RS).

[0332] In some embodiments, the power parameter comprises one or more of: a target received power parameter of a configured scheduled PUSCH; a target received power parameter of a dynamically scheduled PUSCH; a target received power parameter of a PUCCH; a target received power parameter of a SRS set; an energy per resource element (EPRE) of an SSB; a power offset of a CSI-RS.

[0333] In some embodiments,

[0334] a transmission power of the CSI-RS on the time-domain unit of the first type is determined based on a first EPRE and a first offset, the first EPRE being an EPRE applied to an SSB on the time-domain unit of the first type, the first offset being a power offset applied to the CSI-RS on the time-domain unit of the first type and the time-domain unit of the second type; and a transmission power of the CSI-RS on the time-domain unit of the second type is determined based on a second EPRE and the first offset, the second EPRE being an EPRE applied to an SSB on the time-domain unit of the second type.

[0335] In some embodiments,

[0336] a transmission power of the CSI-RS on the time-domain unit of the first type is determined based on an EPRE of an SSB and a second offset, the second offset being a power offset applied to the CSI-RS on the time-domain unit of the first type;

[0337] a transmission power of the CSI-RS on the time-domain unit of the second type is determined based on the EPRE of the SSB and a third offset, the third offset being a power offset applied to the CSI-RS on the time-domain unit of the second type.

[0338] In some embodiments,

[0339] a ratio of an EPRE of a physical downlink control channel (PDCCH) to an EPRE of the CSI-RS is 0 decibel within the time-domain unit of the same type; and / or;

[0340] SRSs in a same SRS resource set are configured on the time-domain unit of the same type; and / or,

[0341] The EPRE of a synchronization signal SS in different SSBs on the same type of time domain unit is the same, and / or the EPRE of a physical broadcast channel PBCH in different SSBs on the same type of time domain unit is the same.

[0342] Optionally, the terminal device 1100 further includes a first parsing unit, configured to parse the first parameter.

[0343] FIG. 12 is a schematic diagram of an optional structure of a network device according to an embodiment of the present application. As shown in FIG. 12, the network device 1200 includes:

[0344] The second communication unit 1201 is configured to send a first parameter, the first parameter being used to determine a first power parameter and a second power parameter, the first power parameter being a power parameter applied to a first type of time domain unit, the second power parameter being a power parameter applied to a second type of time domain unit, a carrier or a carrier group on the first type of time domain unit including frequency domain resources in different directions, and a carrier or a carrier group on the second type of time domain unit including frequency domain resources in only one direction.

[0345] In some embodiments, the same signal or channel on the same type of different time domain units shares the same power parameter.

[0346] In some embodiments,

[0347] The first parameter includes the first power parameter and the second power parameter, or

[0348] The first parameter includes the first power parameter or the second power parameter, and a first offset parameter, the first offset parameter representing an offset amount between the first power parameter and the second power parameter.

[0349] In some embodiments, the power parameter is used to determine one or both of the following:

[0350] The received power of an uplink channel;

[0351] The transmitted power of a downlink channel.

[0352] In some embodiments, the uplink channel includes one or more of the following: a physical uplink shared channel (PUSCH); a physical uplink control channel (PUCCH); a sounding reference signal (SRS).

[0353] In some embodiments, the downlink channel includes one or more of the following: a synchronization signal (SS); a physical broadcast channel (PBCH); a channel state information reference signal (CSI-RS).

[0354] In some embodiments, the power parameter comprises one or more of: a target received power parameter of a configured scheduled PUSCH; a target received power parameter of a dynamically scheduled PUSCH; a target received power parameter of a PUCCH; a target received power parameter of a SRS set; an energy per resource element of an SSB, EPRE; a power offset of a CSI-RS.

[0355] In some embodiments,

[0356] The transmission power of the CSI-RS on the time domain unit of the first type is determined based on a first EPRE and a first offset, the first EPRE being an EPRE applied to an SSB on the time domain unit of the first type, the first offset being a power offset applied to the CSI-RS on the time domain unit of the first type and the time domain unit of the second type; the transmission power of the CSI-RS on the time domain unit of the second type is determined based on a second EPRE and the first offset, the second EPRE being an EPRE applied to an SSB on the time domain unit of the second type.

[0357] In some embodiments,

[0358] The transmission power of the CSI-RS on the time domain unit of the first type is determined based on an EPRE of an SSB and a second offset, the second offset being a power offset applied to the CSI-RS on the time domain unit of the first type;

[0359] The transmission power of the CSI-RS on the time domain unit of the second type is determined based on the EPRE of the SSB and a third offset, the third offset being a power offset applied to the CSI-RS on the time domain unit of the second type.

[0360] In some embodiments,

[0361] Within the same type of time domain unit, a ratio of an EPRE of a physical downlink control channel, PDCCH, to an EPRE of the CSI-RS is 0 decibel; and / or;

[0362] SRSs in a same SRS resource set are configured on a same type of time domain unit; and / or;

[0363] EPREs of synchronization signals, SSs, in different SSBs on a same type of time domain unit are the same, and / or EPREs of physical broadcast channels, PBCHs, in different SSBs on a same type of time domain unit are the same.

[0364] Optionally, the network device 1200 further comprises a first determining unit, configured to determine the first parameter.

[0365] Fig. 13 is a schematic diagram of an optional structural composition of a terminal device according to an embodiment of the present application. As shown in Fig. 13, the terminal device 1300 includes:

[0366] a third communication unit 1301 configured to receive a second parameter, the second parameter including one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on time domain units of a first type and frequency domain transmission resources on time domain units of a second type, or the second parameter being used to determine frequency domain transmission resources on the time domain units of the first type; a carrier or a carrier group on the time domain units of the first type including frequency domain resources of different directions, and a carrier or a carrier group on the time domain units of the second type including only frequency domain resources of one direction.

[0367] In some embodiments, if the second parameter includes only one frequency domain resource allocation parameter, the one frequency domain resource allocation parameter is used to determine the frequency domain transmission resources on the time domain units of the first type and the frequency domain transmission resources on the time domain units of the second type.

[0368] In some embodiments, if the second parameter includes only one frequency domain resource allocation parameter, the one frequency domain resource allocation parameter is used to enable frequency domain transmission resource allocation enhancement on the time domain units of the first type.

[0369] In some embodiments, if the second parameter includes two frequency domain resource allocation parameters, the two frequency domain resource allocation parameters are respectively used to determine the frequency domain transmission resources on the time domain units of the first type and the frequency domain transmission resources on the time domain units of the second type.

[0370] In some embodiments, different time domain units of the same type share the same frequency domain resource allocation parameter.

[0371] In some embodiments, the frequency domain resource allocation parameter includes one or more of the following: a frequency domain resource indication (FDRA) parameter; a frequency hopping parameter; a PUCCH resource parameter or a PUCCH resource set parameter; an SRS resource set parameter; a semi-persistent scheduling (SPS) parameter; and a configured scheduling configuration parameter.

[0372] In some embodiments, the frequency hopping parameter includes a frequency hopping range.

[0373] In some embodiments, the PUCCH resource parameter includes:

[0374] first offset information, the first offset information indicating a relative offset of a starting resource block (RB) of a PUCCH in an uplink resource;

[0375] first bandwidth information, the first bandwidth information indicating a bandwidth of the uplink resource on a downlink time domain unit.

[0376] In some embodiments, the first hop and the second hop of the PUCCH transmission are located within the same type of time domain unit.

[0377] In some embodiments, the SRSs in the SRS resource set are transmitted within the same type of time domain unit.

[0378] In some embodiments, the repeated transmissions of the SRS are transmitted within one type of time domain unit.

[0379] In some embodiments, the SRSs on other types of time domain units are dropped.

[0380] In some embodiments, for SPS or type 2 configured scheduling, only PDSCH or PUSCH is transmitted on the third type of time domain unit, the third type being the first type or the second type, the third type being determined by protocol convention, RRC signaling configuration, or the type of time domain unit where the first periodic PDSCH or PUSCH indicated by downlink scheduling or uplink scheduling is located.

[0381] In some embodiments, for SPS or type 2 configured scheduling:

[0382] The frequency domain resources of the first periodic PDSCH or PUSCH are determined according to the frequency domain resources indicated by downlink scheduling or uplink scheduling;

[0383] The frequency domain resources of the first PDSCH or PUSCH are determined according to the frequency domain resources indicated by downlink scheduling or uplink scheduling, the first PDSCH or PUSCH being the PDSCH or PUSCH of other periods whose type of time domain unit is the same as that of the first periodic PDSCH or PUSCH;

[0384] The frequency domain resources of the second PDSCH or PUSCH are determined according to RRC or according to the frequency domain resources indicated by downlink scheduling or uplink scheduling, the second PDSCH or PUSCH being the PDSCH or PUSCH of other periods whose type of time domain unit is different from that of the first periodic PDSCH or PUSCH.

[0385] Optionally, the terminal device 1200 further includes a second parsing unit, configured to parse the second parameter.

[0386] FIG. 14 is a schematic diagram of an optional structural composition of a network device according to an embodiment of the present application. As shown in FIG. 14, the network device 1400 includes:

[0387] The fourth communication unit 1401 is configured to send a second parameter, the second parameter comprising one or two frequency domain resource allocation parameters, the second parameter being used to determine frequency domain transmission resources on time domain units of a first type and frequency domain transmission resources on time domain units of a second type, or the second parameter being used to determine frequency domain transmission resources on the time domain units of the first type; a carrier or a carrier group on the time domain units of the first type comprising frequency domain resources of different directions, and a carrier or a carrier group on the time domain units of the second type comprising frequency domain resources of only one direction.

[0388] In some embodiments, if the second parameter comprises only one frequency domain resource allocation parameter, the one frequency domain resource allocation parameter is used to determine the frequency domain transmission resources on the time domain units of the first type and the frequency domain transmission resources on the time domain units of the second type.

[0389] In some embodiments, if the second parameter comprises only one frequency domain resource allocation parameter, the one frequency domain resource allocation parameter is used to enable frequency domain transmission resource allocation enhancement on the time domain units of the first type.

[0390] In some embodiments, if the second parameter comprises two frequency domain resource allocation parameters, the two frequency domain resource allocation parameters are respectively used to determine the frequency domain transmission resources on the time domain units of the first type and the frequency domain transmission resources on the time domain units of the second type.

[0391] In some embodiments, different time domain units of the same type share the same frequency domain resource allocation parameter.

[0392] In some embodiments, the frequency domain resource allocation parameter comprises one or more of the following: a frequency domain resource indication (FDRA) parameter;

[0393] a frequency hopping parameter; a PUCCH resource parameter or a PUCCH resource set parameter; an SRS resource set parameter; a semi-persistent scheduling (SPS) parameter; a configured scheduling configuration parameter.

[0394] In some embodiments, the frequency hopping parameter comprises: a frequency hopping range.

[0395] In some embodiments, the PUCCH resource parameter comprises:

[0396] first offset information, the first offset information indicating a relative offset of a starting resource block (RB) of a PUCCH in an uplink resource;

[0397] first bandwidth information, the first bandwidth information indicating a bandwidth of an uplink resource on a downlink time domain unit.

[0398] In some embodiments, a first hop and a second hop of a PUCCH transmission are located in time domain units of the same type.

[0399] In some embodiments, the SRS in the SRS resource set is transmitted within the same type of time domain unit.

[0400] In some embodiments, the repeated transmission of the SRS is transmitted within one type of time domain unit.

[0401] In some embodiments, the SRS on the other type of time domain unit is dropped.

[0402] In some embodiments, for SPS or type 2 configured scheduling, only PDSCH or PUSCH is transmitted on the third type of time domain unit, the third type being the first type or the second type, the third type being determined by protocol convention, RRC signaling configuration, or the type of time domain unit where the first period of PDSCH or PUSCH indicated by downlink scheduling or uplink scheduling is located.

[0403] In some embodiments, for SPS or type 2 configured scheduling:

[0404] The frequency domain resource of the first period of PDSCH or PUSCH is determined according to the frequency domain resource indicated by downlink scheduling or uplink scheduling;

[0405] The frequency domain resource of the first PDSCH or PUSCH is determined according to the frequency domain resource indicated by downlink scheduling or uplink scheduling, the first PDSCH or PUSCH being the PDSCH or PUSCH of other periods whose type of time domain unit is the same as that of the first period of PDSCH or PUSCH;

[0406] The frequency domain resource of the second PDSCH or PUSCH is determined according to RRC or according to the frequency domain resource indicated by downlink scheduling or uplink scheduling, the second PDSCH or PUSCH being the PDSCH or PUSCH of other periods whose type of time domain unit is different from that of the first period of PDSCH or PUSCH.

[0407] Optionally, the network device 1400 further includes a second determining unit, configured to determine the second parameter.

[0408] Those skilled in the art should understand that the above description of the devices of the embodiments of the present application can be understood with reference to the description of the wireless communication method of the embodiments of the present application.

[0409] FIG. 15 is a schematic structural diagram of a communication device 1500 provided in an embodiment of the present application. The communication device can be a terminal device or a network device. The communication device 1500 shown in FIG. 15 includes a processor 1510, which can invoke and run a computer program from a memory to implement the method in the embodiments of the present application.

[0410] Optionally, as shown in FIG. 15, the communication device 1500 can further include a memory 1520. The processor 1510 can invoke and run a computer program from the memory 1520 to implement the method in the embodiments of the present application.

[0411] The memory 1520 can be a separate device independent of the processor 1510, or can be integrated in the processor 1510.

[0412] Optionally, as shown in FIG. 15, the communication device 1500 can further include a transceiver 1530, which can be controlled by the processor 1510 to communicate with other devices, specifically, to send information or data to other devices or receive information or data sent by other devices.

[0413] The transceiver 1530 can include a transmitter and a receiver. The transceiver 1530 can further include an antenna, and the number of antennas can be one or more.

[0414] Optionally, the communication device 1500 can be a network device in the embodiments of the present application, and the communication device 1500 can implement the corresponding processes in the various methods of the embodiments of the present application implemented by the network device. For brevity, details are not described herein.

[0415] Optionally, the communication device 1500 can be a mobile terminal / terminal device in the embodiments of the present application, and the communication device 1500 can implement the corresponding processes in the various methods of the embodiments of the present application implemented by the mobile terminal / terminal device. For brevity, details are not described herein.

[0416] FIG. 16 is a schematic structural diagram of a chip in the embodiments of the present application. The chip 1600 shown in FIG. 16 includes a processor 1610, which can invoke and run a computer program from a memory to implement the method in the embodiments of the present application.

[0417] Optionally, as shown in FIG. 16, the chip 1600 can further include a memory 1620. The processor 1610 can invoke and run a computer program from the memory 1620 to implement the method in the embodiments of the present application.

[0418] The memory 1620 can be a separate device independent of the processor 1610, or can be integrated in the processor 1610.

[0419] Optionally, the chip 1600 further includes an input interface 1630. The processor 1610 can control the input interface 1630 to communicate with other devices or chips, and specifically, can acquire information or data sent by other devices or chips.

[0420] Optionally, the chip 1600 further includes an output interface 1640. The processor 1610 can control the output interface 1640 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.

[0421] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes realized by the network device in the methods of the embodiments of the present application. For brevity, details are not described herein.

[0422] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of the present application, and the chip can implement the corresponding processes realized by the mobile terminal / terminal device in the methods of the embodiments of the present application. For brevity, details are not described herein.

[0423] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.

[0424] FIG. 17 is a schematic block diagram of a communication system 1700 provided by the embodiments of the present application. As shown in FIG. 17, the communication system 1700 includes a terminal device 1710 and a network device 1720.

[0425] The terminal device 1710 can be used to implement the corresponding functions realized by the terminal device in the above methods, and the network device 1720 can be used to implement the corresponding functions realized by the network device in the above methods. For brevity, details are not described herein.

[0426] It should be understood that the processor of the embodiments of the present application can be an integrated circuit chip with a processing capability of signals. In the implementation process, each step of the method embodiments described above can be completed by the integrated logic circuit of hardware in the processor or the instructions in the form of software. The processor described above can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, a discrete gate or transistor logic device, a discrete hardware component. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware code processor for execution, or can be executed by a combination of hardware and software modules in the code processor. The software module can be located in a random memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register or other mature storage medium in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and combines the hardware to complete the steps of the above method.

[0427] It is to be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (Random Access Memory, RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the system and method described herein is intended to include, but not limited to, these and any other suitable types of memory.

[0428] It should be understood that the above-mentioned memory is exemplary but not limiting, for example, the memory in the embodiments of the present application can also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and the like. That is, the memory in the embodiments of the present application is intended to include, but not limited to, these and any other suitable types of memory.

[0429] The embodiment of the present application further provides a computer readable storage medium for storing the computer program.

[0430] Optionally, the computer readable storage medium can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program makes the computer execute the corresponding process realized by the mobile terminal / terminal device in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0431] Optionally, the computer readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program makes the computer execute the corresponding process realized by the mobile terminal / terminal device in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0432] The embodiment of the present application further provides a computer program product comprising computer program instructions.

[0433] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding process realized by the mobile terminal / terminal device in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0434] Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding process realized by the mobile terminal / terminal device in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0435] The embodiment of the present application further provides a computer program.

[0436] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiment of the present application, and when the computer program runs on the computer, makes the computer execute the corresponding process realized by the mobile terminal / terminal device in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0437] Optionally, the computer program can be applied to the network device in the embodiment of the present application, and when the computer program runs on the computer, makes the computer execute the corresponding process realized by the mobile terminal / terminal device in the various methods of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0438] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0439] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0440] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0441] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0442] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.

[0443] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0444] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A wireless communication method, the method comprising: The terminal device receives a first parameter, which is used to determine a first power parameter and a second power parameter. The first power parameter is a power parameter applied to a first type of time domain unit, and the second power parameter is a power parameter applied to a second type of time domain unit. The carrier or carrier group on the first type of time domain unit includes frequency domain resources in different directions, and the carrier or carrier group on the second type of time domain unit includes frequency domain resources in only one direction.

2. The method according to claim 1, wherein, The same signal or channel on different time-domain units of the same type share the same power parameters.

3. The method according to claim 1 or 2, wherein, The first parameter includes: the first power parameter and the second power parameter; or, The first parameter includes either the first power parameter or the second power parameter, and a first deviation parameter, wherein the first deviation parameter characterizes the deviation between the first power parameter and the second power parameter.

4. The method according to any one of claims 1 to 3, wherein, The power parameters are used to determine one or both of the following: Uplink channel received power; Downlink channel transmit power.

5. The method according to claim 4, wherein, The uplink channel includes one or more of the following: Physical Uplink Shared Channel (PUSCH); Physical uplink control channel (PUCCH); Detection reference signal SRS.

6. The method according to claim 4, wherein, The downlink channel includes one or more of the following: Synchronization signal SS; Physical Broadcast Channel (PBCH); Channel State Information Reference Signal (CSI-RS) 7. The method according to any one of claims 1 to 6, wherein, The power parameters include one or more of the following: Configure the target receive power parameter for the scheduled PUSCH; Target receive power parameter for dynamically scheduled PUSCH; Target receive power parameters for PUCCH; Target received power parameter of SRS set; Energy per resource element (EPRE) of SSB; CSI-RS power offset.

8. The method according to claim 7, wherein, The transmit power of CSI-RS on the first type of time domain unit is determined based on a first EPRE and a first offset, wherein the first EPRE is the EPRE applied to the SSB on the first type of time domain unit, and the first offset is the power offset applied to the CSI-RS on the first and second types of time domain units; the transmit power of CSI-RS on the second type of time domain unit is determined based on a second EPRE and the first offset, wherein the second EPRE is the EPRE applied to the SSB on the second type of time domain unit.

9. The method according to claim 7, wherein, The transmit power of CSI-RS on the first type of time domain unit is based on the EPRE of SSB and a second offset, the second offset being a power offset applied to the CSI-RS on the first type of time domain unit; The transmit power of CSI-RS on the second type of time domain unit is based on the EPRE of the SSB and a third offset, the third offset being a power offset applied to the CSI-RS on the second type of time domain unit.

10. The method according to any one of claims 1 to 9, wherein, Within the same type of time-domain unit, the ratio of the EPRE of the Physical Downlink Control Channel (PDCCH) to the EPRE of the CSI-RS is 0 dB; and / or, SRSs in the same SRS resource set are configured on the same type of time-domain unit; and / or, The synchronization signals SS in different SSBs of the same type of time domain unit have the same EPRE, and / or the physical broadcast channels PBCH in different SSBs of the same type of time domain unit have the same EPRE.

11. A wireless communication method, the method comprising: The terminal device receives a second parameter, which includes one or two frequency domain resource allocation parameters. The second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit and the second type of time domain unit, or the second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit. The carrier or carrier group on the first type of time domain unit includes frequency domain resources in different directions, and the carrier or carrier group on the second type of time domain unit includes frequency domain resources in only one direction.

12. The method according to claim 11, wherein, If the second parameter contains only one frequency domain resource allocation parameter, the frequency domain resource allocation parameter is used to determine the frequency domain transmission resources on the time domain unit of the first type and the frequency domain transmission resources on the time domain unit of the second type.

13. The method according to claim 11, wherein, If the second parameter contains only one frequency domain resource allocation parameter, the frequency domain resource allocation parameter is used to enable frequency domain transmission resource allocation enhancement for the time domain unit of the first type.

14. The method according to claim 11, wherein, If the second parameter includes two frequency domain resource allocation parameters, the two frequency domain resource allocation parameters are used to determine the frequency domain transmission resources on the time domain unit of the first type and the frequency domain transmission resources on the time domain unit of the second type, respectively.

15. The method according to claim 14, wherein, Different time-domain units of the same type share the same frequency-domain resource allocation parameters.

16. The method according to any one of claims 11 to 15, wherein, The frequency domain resource allocation parameters include one or more of the following: Frequency Domain Resource Indicator (FDRA) parameters; Frequency hopping parameters; PUCCH resource parameters or PUCCH resource set parameters; SRS resource set parameters; Semi-static scheduling SPS parameters; Configure scheduling parameters.

17. The method according to claim 16, wherein, The frequency hopping parameters include: frequency hopping range.

18. The method according to claim 16, wherein, The PUCCH resource parameters include: First offset information, which indicates the relative offset of the starting resource block RB of PUCCH within the uplink resource; First bandwidth information, which indicates the bandwidth of uplink resources on the downlink time domain unit.

19. The method according to any one of claims 11 to 18, wherein, The first and second hops of the PUCCH transmission are located within the same type of time domain unit.

20. The method according to any one of claims 11 to 19, wherein, SRS in the SRS resource set are transmitted within the same type of time domain unit.

21. The method according to any one of claims 11 to 20, wherein, Repeated transmissions of SRS are transmitted within a time-domain unit of one type.

22. The method according to claim 21, wherein, SRS on other types of time-domain units are discarded.

23. The method according to any one of claims 11 to 22, wherein, For SPS or Type 2 configuration scheduling, PDSCH or PUSCH is transmitted only on the third type of time domain unit, which is either the first type or the second type. The third type is determined by the protocol agreement, RRC signaling configuration, or by the type of the time domain unit where the PDSCH or PUSCH of the first cycle is located, as indicated by the downlink or uplink scheduling.

24. The method according to any one of claims 11 to 23, wherein, For SPS or Type 2 configuration scheduling: The frequency domain resources of the PDSCH or PUSCH in the first cycle are determined according to the frequency domain resources indicated by the downlink scheduling or uplink scheduling. The frequency domain resources of the first PDSCH or PUSCH are determined according to the frequency domain resources indicated by the downlink scheduling or uplink scheduling. The first PDSCH or PUSCH is the PDSCH or PUSCH of other periods whose time domain unit type is the same as that of the PDSCH or PUSCH of the first period. The frequency domain resources of the second PDSCH or PUSCH are determined according to RRC or according to the frequency domain resources indicated by downlink scheduling or uplink scheduling. The second PDSCH or PUSCH is a PDSCH or PUSCH of another period whose time domain unit type is different from that of the first period's PDSCH or PUSCH.

25. A wireless communication method, comprising: The network device sends a first parameter, which is used to determine a first power parameter and a second power parameter. The first power parameter is a power parameter applied to a first type of time-domain unit, and the second power parameter is a power parameter applied to a second type of time-domain unit. The carrier or carrier group on the first type of time-domain unit includes frequency domain resources in different directions. The carrier or carrier group on the time-domain unit of this type includes frequency-domain resources in only one direction.

26. The method according to claim 25, wherein, The same signal or channel on different time-domain units of the same type share the same power parameters.

27. The method according to claim 25 or 26, wherein, The first parameter includes: the first power parameter and the second power parameter; or, The first parameter includes either the first power parameter or the second power parameter, and a first deviation parameter, wherein the first deviation parameter characterizes the deviation between the first power parameter and the second power parameter.

28. The method according to any one of claims 25 to 27, wherein, The power parameters are used to determine one or both of the following: Uplink channel received power; Downlink channel transmit power.

29. The method according to claim 28, wherein, The uplink channel includes one or more of the following: Physical Uplink Shared Channel (PUSCH); Physical uplink control channel (PUCCH); Detection reference signal SRS.

30. The method according to claim 28, wherein, The downlink channel includes one or more of the following: Synchronization signal SS; Physical Broadcast Channel (PBCH); Channel State Information Reference Signal (CSI-RS) 31. The method according to any one of claims 25 to 30, wherein, The power parameters include one or more of the following: Configure the target receive power parameter for the scheduled PUSCH; Target receive power parameter for dynamically scheduled PUSCH; Target receive power parameters for PUCCH; Target received power parameter of SRS set; Energy per resource element (EPRE) of SSB; CSI-RS power offset.

32. The method according to claim 31, wherein, The transmit power of CSI-RS on the first type of time domain unit is determined based on a first EPRE and a first offset, wherein the first EPRE is the EPRE applied to the SSB on the first type of time domain unit, and the first offset is the power offset applied to the CSI-RS on the first and second types of time domain units; the transmit power of CSI-RS on the second type of time domain unit is determined based on a second EPRE and the first offset, wherein the second EPRE is the EPRE applied to the SSB on the second type of time domain unit.

33. The method according to claim 31, wherein, The transmit power of CSI-RS on the first type of time domain unit is based on the EPRE of SSB and a second offset, the second offset being a power offset applied to the CSI-RS on the first type of time domain unit; The transmit power of CSI-RS on the second type of time domain unit is based on the EPRE of the SSB and the third offset, which is a power offset applied to the CSI-RS on the second type of time domain unit.

34. The method according to any one of claims 25 to 33, wherein, Within the same type of time-domain unit, the ratio of the EPRE of the Physical Downlink Control Channel (PDCCH) to the EPRE of the CSI-RS is 0 dB; and / or, SRSs in the same SRS resource set are configured on the same type of time-domain unit; and / or, The synchronization signals SS in different SSBs of the same type of time domain unit have the same EPRE, and / or the physical broadcast channels PBCH in different SSBs of the same type of time domain unit have the same EPRE.

35. A wireless communication method, the method comprising: The network device sends a second parameter, which includes one or two frequency domain resource allocation parameters. The second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit and the second type of time domain unit, or the second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit. The carrier or carrier group on the first type of time domain unit includes frequency domain resources in different directions, and the carrier or carrier group on the second type of time domain unit includes frequency domain resources in only one direction.

36. The method according to claim 35, wherein, If the second parameter contains only one frequency domain resource allocation parameter, the frequency domain resource allocation parameter is used to determine the frequency domain transmission resources on the time domain unit of the first type and the frequency domain transmission resources on the time domain unit of the second type.

37. The method according to claim 35 or 36, wherein, If the second parameter contains only one frequency domain resource allocation parameter, the frequency domain resource allocation parameter is used to enable frequency domain transmission resource allocation enhancement for the time domain unit of the first type.

38. The method according to claim 35, wherein, If the second parameter includes two frequency domain resource allocation parameters, the two frequency domain resource allocation parameters are used to determine the frequency domain transmission resources on the time domain unit of the first type and the frequency domain transmission resources on the time domain unit of the second type, respectively.

39. The method according to claim 38, wherein, Different time-domain units of the same type share the same frequency-domain resource allocation parameters.

40. The method according to any one of claims 35 to 39, wherein, The frequency domain resource allocation parameters include one or more of the following: Frequency Domain Resource Indicator (FDRA) parameters; Frequency hopping parameters; PUCCH resource parameters or PUCCH resource set parameters; SRS resource set parameters; Semi-static scheduling SPS parameters; Configure scheduling parameters.

41. The method according to claim 40, wherein, The frequency hopping parameters include: frequency hopping range.

42. The method according to claim 40, wherein, The PUCCH resource parameters include: First offset information, which indicates the relative offset of the starting resource block RB of PUCCH within the uplink resource; First bandwidth information, which indicates the bandwidth of uplink resources on the downlink time domain unit.

43. The method according to any one of claims 35 to 42, wherein, The first and second hops of the PUCCH transmission are located within the same type of time domain unit.

44. The method according to any one of claims 35 to 43, wherein, SRS in the SRS resource set are transmitted within the same type of time domain unit.

45. The method according to any one of claims 35 to 44, wherein, Repeated transmissions of SRS are transmitted within a time-domain unit of one type.

46. ​​The method according to claim 45, wherein, SRS on other types of time-domain units are discarded.

47. The method according to any one of claims 35 to 45, wherein, For SPS / Type 2 configuration scheduling, PDSCH or PUSCH is transmitted only on the third type of time domain unit, which is either the first type or the second type. The third type is determined by the protocol agreement, RRC signaling configuration, or by the type of the time domain unit where the PDSCH or PUSCH of the first cycle is located, as indicated by the downlink or uplink scheduling.

48. The method according to any one of claims 35 to 47, wherein, For SPS or Type 2 configuration scheduling: The frequency domain resources of the PDSCH or PUSCH in the first cycle are determined according to the frequency domain resources indicated by the downlink scheduling or uplink scheduling. The frequency domain resources of the first PDSCH or PUSCH are determined according to the frequency domain resources indicated by the downlink scheduling or uplink scheduling. The first PDSCH or PUSCH is the PDSCH or PUSCH of other periods whose time domain unit type is the same as that of the PDSCH or PUSCH of the first period. The frequency domain resources of the second PDSCH or PUSCH are determined according to RRC or according to the frequency domain resources indicated by downlink scheduling or uplink scheduling. The second PDSCH or PUSCH is a PDSCH or PUSCH of another period whose time domain unit type is different from that of the first period's PDSCH or PUSCH.

49. A terminal device, comprising: A first communication unit is configured to receive a first parameter, the first parameter being used to determine a first power parameter and a second power parameter. The first power parameter is a power parameter applied to a first type of time-domain unit, and the second power parameter is a power parameter applied to a second type of time-domain unit. The carrier or carrier group on the first type of time-domain unit includes frequency domain resources in different directions, while the carrier or carrier group on the second type of time-domain unit includes frequency domain resources in only one direction.

50. A network device, comprising: The second communication unit is configured to transmit a first parameter, which is used to determine a first power parameter and a second power parameter. The first power parameter is a power parameter applied to a first type of time domain unit, and the second power parameter is a power parameter applied to a second type of time domain unit. The carrier or carrier group on the first type of time domain unit includes frequency domain resources in different directions, and the carrier or carrier group on the second type of time domain unit includes frequency domain resources in only one direction.

51. A terminal device, comprising: The third communication unit is configured to receive a second parameter, which includes one or two frequency domain resource allocation parameters. The second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit and the second type of time domain unit, or the second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit. The carrier or carrier group on the first type of time domain unit includes frequency domain resources in different directions, and the carrier or carrier group on the second type of time domain unit includes frequency domain resources in only one direction.

52. A network device, comprising: The fourth communication unit is configured to transmit a second parameter, which includes one or two frequency domain resource allocation parameters. The second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit and the second type of time domain unit, or the second parameter is used to determine the frequency domain transmission resources on the first type of time domain unit. The carrier or carrier group on the first type of time domain unit includes frequency domain resources in different directions, and the carrier or carrier group on the second type of time domain unit includes frequency domain resources in only one direction.

53. A terminal device, comprising: A transceiver, a processor, and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to cooperate with the transceiver in performing the method as described in any one of claims 1 to 10, or to cooperate with the transceiver in performing the method as described in any one of claims 11 to 24.

54. A network device, comprising: A transceiver, a processor, and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to cooperate with the transceiver in performing the method as described in any one of claims 25 to 34, or to cooperate with the transceiver in performing the method as described in any one of claims 35 to 48.

55. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 24, or the method as claimed in any one of claims 25 to 34, or the method as claimed in any one of claims 35 to 48.

56. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 24, or the method as claimed in any one of claims 25 to 34, or the method as claimed in any one of claims 35 to 48.

57. A computer program product comprising computer program instructions that cause a computer to perform the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 24, or the method as claimed in any one of claims 25 to 34, or the method as claimed in any one of claims 35 to 48.

58. A computer program that causes a computer to perform the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 24, or the method as claimed in any one of claims 25 to 34, or the method as claimed in any one of claims 35 to 48.

Images