PUSCH scheduling transmission method, terminal and network side equipment

Abstract

The embodiment of the present application discloses a method, terminal and network-side device for scheduling transmission of PUSCH, which can solve the problem that PUSCH transmission cannot be realized in a multi-TRP scenario. The method comprises: the terminal receives scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; the terminal sends the PUSCH according to the SRS resource set and / or SRS resource.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a scheduling and transmission method, a terminal and a network-side device of a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH). Background Art

[0002] In mobile communication systems, uplink PUSCH only supports single transmission and reception point (TRP) transmission, and network-side devices can schedule PUSCH transmission through downlink control information (DCI). With the development of technology, it is necessary to support multiple TRP scenarios. In multiple TRP scenarios, it will become necessary to implement PUSCH transmission, for example, whether PUSCH is sent to one TRP or multiple TRPs, and no effective solution has been given in the relevant technology. Summary of the invention

[0003] The embodiments of the present application provide a PUSCH scheduling transmission method, terminal and network-side equipment, which can solve the problem that PUSCH transmission cannot be achieved in a multi-TRP scenario.

[0004] In a first aspect, a method for scheduling transmission of a PUSCH is provided, the method comprising: a terminal receives scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; the terminal sends the PUSCH according to the SRS resource set and / or SRS resource.

[0005] In a second aspect, a scheduling transmission method for PUSCH is provided, the method comprising: a network side device sends a scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used by a terminal to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; the network side device receives the PUSCH, and the PUSCH is sent by the terminal according to the SRS resource set and / or SRS resource.

[0006] In the third aspect, a terminal is provided, comprising: a receiving module for receiving scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; a sending module for sending the PUSCH according to the SRS resource set and / or SRS resource.

[0007] In a fourth aspect, a network side device is provided, including: a sending module for sending scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used by the terminal to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; a receiving module for receiving the PUSCH, and the PUSCH is sent by the terminal according to the SRS resource set and / or SRS resource.

[0008] In a fifth aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method described in the first aspect.

[0009] In a sixth aspect, a network side device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method described in the second aspect.

[0010] In a seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the method described in the first aspect is implemented, or the method described in the second aspect is implemented.

[0011] In an eighth aspect, a computer program product is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the method described in the first aspect is implemented, or the method described in the second aspect is implemented.

[0012] In the ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0013] In an embodiment of the present application, at least one SRS resource set and / or SRS resource associated with the PUSCH can be determined based on the scheduling signaling of the PUSCH, and each SRS resource set or SRS resource can correspond to a TRP. In this way, the embodiment of the present application can realize the transmission of PUSCH in a multi-TRP scenario, so that the terminal can send PUSCH to the TRP corresponding to the SRS resource set and / or SRS resource, thereby improving the transmission efficiency of PUSCH. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application;

[0015] Figure 2 is a schematic flowchart of a method for scheduling transmission of a PUSCH according to an embodiment of the present application;

[0016] Figure 3 is a schematic flowchart of a method for scheduling transmission of a PUSCH according to another embodiment of the present application;

[0017] Figure 4 is a schematic diagram of the structure of a terminal according to an embodiment of the present application;

[0018] Figure 5 is a schematic diagram of the structure of a network side device according to another embodiment of the present application;

[0019] Figure 6 is a schematic structural diagram of a communication device according to an embodiment of the present application;

[0020] Figure 7 is a schematic diagram of the structure of a terminal according to an embodiment of the present application;

[0021] Figure 8 It is a schematic diagram of the structure of a network side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0023] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0024] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0025] Figure 1A schematic diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a next generation node B (gNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0026] In conjunction with the accompanying drawings, the scheduling method, terminal and network-side device of the physical uplink shared channel (PUSCH) provided in the embodiments of the present application are described in detail through specific embodiments and their application scenarios.

[0027] like Figure 2 As shown, an embodiment of the present application provides a PUSCH scheduling transmission method 200, which can be executed by a terminal. In other words, the method can be executed by software or hardware installed in the terminal. The method includes the following steps.

[0028] S202: The terminal receives scheduling signaling, where the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH.

[0029] The scheduling signaling mentioned in each embodiment of this specification may be a radio resource control (Radio Resource Control, RRC) signaling or a downlink control information (Downlink Control Information, DCI) signaling.

[0030] The above scheduling signaling can be used to determine (such as explicit indication combined with implicit indication) at least one SRS resource associated with the PUSCH; or, the above scheduling signaling can be used to determine at least one SRS resource set associated with the PUSCH. Generally, an SRS resource set includes (or is associated with) one or more SRS resources. Therefore, when the above scheduling signaling determines at least one SRS resource set associated with the PUSCH, it is equivalent to simultaneously determining the SRS resources in the at least one SRS resource set.

[0031] Optionally, the embodiment of the present application can indicate at least one SRS resource set and / or SRS resource associated with PUSCH by combining direct indication (or explicit indication) with implicit indication. In this example, the direct indication method can adopt independent coding or at least partial joint coding.

[0032] Optionally, the embodiment of the present application may indicate at least one SRS resource set and / or SRS resource associated with the PUSCH by direct indication. This example may adopt an independent coding or at least a partial joint coding method.

[0033] S204: The terminal sends the PUSCH according to the SRS resource set and / or SRS resource.

[0034] The SRS resource set and / or SRS resources mentioned in this step may be consistent with the SRS resource set and / or SRS resources determined in S202. For example, the SRS resource set is determined in S202, and this step sends the PUSCH according to the determined SRS resource set; the SRS resources are determined in S202, and this step sends the PUSCH according to the determined SRS resources.

[0035] The step mentioned sending the PUSCH according to the SRS resource set and / or SRS resource, for example, sending the PUSCH using the same port number, beam information, etc. as the SRS resource set and / or SRS resource.

[0036] Optionally, for at least one SRS resource set associated with PUSCH, each SRS resource set can correspond to a transmission and reception point (TRP). In this way, the terminal can send PUSCH to the TRP corresponding to the at least one SRS resource set (respectively), and can realize PUSCH transmission in a multi-TRP scenario.

[0037] Optionally, for at least one SRS resource associated with PUSCH, each SRS resource can correspond to a TRP, so that the terminal can send PUSCH to the TRP corresponding to at least one SRS resource (respectively), and can realize PUSCH transmission in a multi-TRP scenario.

[0038] The PUSCH scheduling and transmission method provided in the embodiment of the present application can determine at least one SRS resource set and / or SRS resource associated with the PUSCH according to the scheduling signaling of the PUSCH, and each SRS resource set or SRS resource can correspond to a TRP. In this way, the embodiment of the present application can realize the transmission of PUSCH in a multi-TRP scenario, so that the terminal can send PUSCH to the TRP corresponding to the SRS resource set and / or SRS resource, so as to improve the transmission efficiency of PUSCH.

[0039] Optionally, the method of associating the PUSCH with the SRS resource set and / or SRS resource is implicit, that is, the association relationship between the PUSCH and the SRS resource set and / or SRS resource is implicitly indicated. In one example, the number of the SRS resource set and / or SRS resource associated with the PUSCH is the smallest or largest, and the smallest or largest mentioned here may be for all SRS resource sets and / or SRS resources configured for the terminal; in another example, the beam information of the receiving beam of the scheduling signaling or the beam information of the transmitting beam of the PUSCH is the same as at least one of the following: the path loss reference signal (PathLoss RS, PL RS) associated with the SRS resource set and / or SRS resource, and the beam information associated with the SRS resource set and / or SRS resource. The "same" beam information mentioned here may mean that the beam information is roughly the same or close, that is, a certain error range is allowed. It should be noted that the above two examples can be implemented separately or simultaneously.

[0040] Optionally, the scheduling signaling includes an indication field, and the indication field is used to indicate (i.e., explicitly indicate) the SRS resource set and / or the SRS resource. This example can directly indicate the SRS resource set and / or the SRS resource, for example, directly indicating the first SRS resource or the second SRS resource through the SRS Resource Indicator (SRI) field in the scheduling signaling, or indicating the first SRS resource and the second SRS resource at the same time.

[0041] In some embodiments of the present application, before S202, it also includes: the terminal receives an SRS configuration, the SRS configuration includes: at least one SRS resource set, each SRS resource set includes at least one SRS resource, wherein the number of SRS resources included in the target SRS resource set is greater than or equal to the number of SRS resources included in other SRS resource sets in at least one SRS resource set, and the target SRS resource set is the one with the smallest SRS resource set identifier in at least one SRS resource set.

[0042] Optionally, the scheduling signaling includes at least two independent coding fields, and the at least two independent coding fields are used to respectively indicate SRS resources in at least two SRS resource sets, and the order of the at least two independent coding fields may be predefined.

[0043] For example, the terminal receives an SRS configuration sent by a network-side device, and the SRS configuration includes two SRS resource sets for codebook or non-codebook transmission. The values ​​of the SRS resource set identifier (or SRS resource set index) are 1 and 2 (or numbered from 0, with indexes 0 and 1), respectively. The SRS resource set with a value of 1 is the first SRS resource set, and the SRS resource set with a value of 2 is the second SRS resource set; the first SRS resource set includes 4 SRS resources, and the second SRS resource set includes 2 SRS resources. Then, the two independent coding fields (such as the SRS resource indication field SRI field) in the scheduling signaling for scheduling PUSCH transmission use 2 bits of the first SRIfield and 1 bit of the second SRI field to indicate the SRS resources associated with the PUSCH transmission. Optionally, the scheduling signaling also includes a dynamic switching indication field, and the size of the dynamic switching indication field is 2 bits. The specific meanings are shown in Table 1:

[0044] Table 1

[0045]

[0046] in,

[0047] 00: indicates the SRS resources in the first SRS resource set indicated by the first SRI field in the DCI, and all repeated transmission opportunities of the PUSCH are only associated with the SRS resources.

[0048] 01: indicates the SRS resources in the second SRS resource set indicated by the first SRI field in the DCI, and all repeated transmission opportunities of the PUSCH are only associated with the SRS resources.

[0049] 10: Indicates that the first SRI field in the DCI indicates the SRS resources in the first SRS resource set, the second SRI field indicates the SRS resources in the second SRS resource set, and the PUSCH is repeatedly associated with the first SRS resource set and then the second SRS resource set;

[0050] 11: Indicates that the second SRI field in the DCI indicates the SRS resources in the second SRS resource set, the first SRI field indicates the SRS resources in the first SRS resource set, and is repeatedly associated with the PUSCH in the order of the second SRS resource set first and the first SRS resource set second.

[0051] Alternatively, the meanings of 10 and 11 in the above Table 1 may be interchanged, for example

[0052] 00: indicates the SRS resources in the first SRS resource set indicated by the first SRI field in the DCI, and all repeated transmission opportunities of the PUSCH are only associated with the SRS resources.

[0053] 01: indicates the SRS resources in the second SRS resource set indicated by the second SRI field in the DCI, and all repeated transmission opportunities of the PUSCH are only associated with the SRS resources.

[0054] 10: Indicates that the first SRI field in the DCI indicates the SRS resources in the first SRS resource set, the second SRI field indicates the SRS resources in the second SRS resource set, and the PUSCH is repeatedly associated with the second SRS resource set and then the first SRS resource set.

[0055] 11: Indicates that the second SRI field in the DCI indicates the SRS resources in the second SRS resource set, the first SRI field indicates the SRS resources in the first SRS resource set, and is repeatedly associated with the PUSCH in the order of the first SRS resource set first and the second SRS resource set.

[0056] In this example, it is assumed that PUSCH is associated with two SRS resource sets (hereinafter, SRS resource sets may be referred to as sets), that is, there are two independent coding domains. For SRS resource-level independent coding, the order indicated by the above two independent coding domains may be a default order agreed upon by the protocol, for example, the first independent coding domain corresponds to the first SRS resource set (referred to as the first set), and the second independent coding domain corresponds to the second SRS resource set (referred to as the second set); or according to the order of the indicated sets, when the indicated set order is the second set and the first set, the first independent coding domain corresponds to the second set, and the second independent coding domain corresponds to the first set.

[0057] Optionally, the PUSCH mentioned in the foregoing embodiments includes at least one transmission unit, and the transmission unit includes one of the following: a nominal PUSCH repetition transmission, an actual PUSCH repetition transmission, a PUSCH transmission within a time domain unit (such as a time slot), a PUSCH frequency hopping transmission, and a PUSCH transmission among multiple PUSCH repetition transmissions.

[0058] In an example, the scheduling signaling indicates an SRS resource set, and the transmission unit is associated with one of the SRS resource sets. For example, if the SRI field of the scheduling signaling indicates 1 set, the PUSCH transmission unit is associated with the set.

[0059] In another example, the scheduling signaling indicates a plurality of the SRS resource sets, the scheduling signaling is further used to indicate an order of the plurality of the SRS resource sets, and the transmission unit is associated with the order of the plurality of the SRS resource sets indicated by the scheduling signaling.

[0060] For example, if the SRI field of the scheduling signaling indicates multiple sets at the same time, and the SRI field can be used to indicate the set order, the PUSCH transmission unit is associated with the set order indicated by the SRI. For example, the scheduled PUSCH includes a first PUSCH transmission unit and a second PUSCH transmission unit, and the set indicated by the SRI includes a first set and a second set. Then, the first PUSCH transmission unit may correspond to the first set, such as sending the first PUSCH transmission unit to the TRP corresponding to the first set; and the second PUSCH transmission unit may correspond to the second set, such as sending the second PUSCH transmission unit to the TRP corresponding to the second set.

[0061] In one example, the scheduling signaling indicates multiple SRS resource sets, and the scheduling signaling does not indicate the order of the multiple SRS resource sets, and the transmission unit is associated with one of the following: the configuration order of the multiple SRS resource sets, such as the time order of configuration; the identification order of the multiple SRS resource sets (the order of identification size, and the same applies subsequently); the identification order of the SRS resources in the multiple SRS resource sets; the parity order of the time domain unit where the transmission unit is located, wherein the multiple SRS resource sets have a parity binding relationship with the time domain unit where the transmission unit is located.

[0062] In this example, if the SRI field of the scheduling signaling indicates multiple sets at the same time, but the SRI field is not used to indicate the order of multiple sets, the PUSCH transmission unit is associated with the following method, and the order of the configured SRS resource sets is associated: it can be the order of set configuration or the order of set ID; or the size order of SRS resource IDs in the SRS resource set; or the set is parity-bound with the slot where the PUSCH transmission unit is located, and the parity binding can be through a default rule, for example, the first set corresponds to odd slots, the second set corresponds to even slots, and vice versa.

[0063] Optionally, a code point in the scheduling signaling is used to indicate the at least one SRS resource set and / or SRS resource, wherein a correspondence between the code point and the SRS resource set and / or SRS resource satisfies one of the following:

[0064] 1) Predefined. For example, the protocol agreement method includes the pre-agreed correspondence between codepoint and set and / or resource, as well as the special processing method for invalid codepoints.

[0065] 2) Network-side device configuration. For example, when the number of resources configured in a set is less than the maximum number of supported code points, the network-side device configuration supports the above correspondence.

[0066] 3) The network side device updates the indication. For example, when the resource configured in a set is less than the maximum number of code points that can be supported, the network side device is supported to update the above correspondence.

[0067] It should be noted that the invalid code points mentioned in various embodiments of this specification include, for example: the set and / or resource indicated by the (invalid) code point is not configured; the terminal cannot determine the set and / or resource corresponding to the (invalid) code point, etc., for example, the relationship between the code point and the set and / or resource is not configured, not indicated or defined.

[0068] The above embodiment further includes the following step: determining a processing method corresponding to an invalid code point; wherein the processing method corresponding to the invalid code point includes at least one of the following:

[0069] 1) If only one SRS resource is configured in the SRS resource set corresponding to the target code point, the SRS resource corresponding to the target code point is the one SRS resource;

[0070] 2) If the target code point is an invalid code point, the SRS resource set and / or SRS resource corresponding to the code point before or after the target code point is used as the SRS resource set and / or SRS resource corresponding to the invalid code point;

[0071] 3) If the target code point is an invalid code point, the SRS resource set and / or SRS resource before or after the SRS resource set and / or SRS resource corresponding to the target code point is used as the SRS resource set and / or SRS resource corresponding to the invalid code point;

[0072] 4) The terminal does not expect that the SRS resource set corresponding to the code point is an SRS resource set that has not been configured;

[0073] 5) The terminal does not expect that the code point corresponding to the SRS resource is an unconfigured SRS resource.

[0074] Optionally, the PUSCH is associated with a first SRS resource and a second SRS resource, wherein the first SRS resource and the second SRS resource are associated with different SRS resource sets. In this embodiment, the first resource and the second resource are associated with different SRS resource set IDs.

[0075] Optionally, the PUSCH is associated with multiple SRS resource sets; wherein any two SRS resource sets among the multiple SRS resource sets satisfy at least one of the following: having different path loss RS, having different spatial beam configurations, having different associated RS, having the same time domain characteristics, being associated with the same SRS resource identification ID, having the same number of SRS resource ports, having the same period, having different periodic time slot offsets, being associated with different TRP indexes, being associated with different control resource set resource pool indexes, having different power control parameter indexes, and having different closed-loop power control index groups.

[0076] Optionally, the PUSCH is associated with a first SRS resource set and a second SRS resource set; wherein the first SRS resource set and the second SRS resource set satisfy at least one of the following:

[0077] 1) The first SRS resource set and the second SRS resource set are sorted from small to large or from large to small according to the SRS resource set identifier;

[0078] 2) The first SRS resource set and the second SRS resource set are arranged from front to back or from back to front according to the configuration order of the SRS resource sets (such as the configuration time sequence);

[0079] 3) The first SRS resource set and the second SRS resource set are configured in different sequences.

[0080] 4) The first SRS resource set and the second SRS resource set are configured with different power control parameter indexes, and the power control parameter index is used to distinguish the first SRS resource set from the second SRS resource set. Optionally, the power control parameter index can be configured within the SRS resource set.

[0081] Optionally, the PUSCH is associated with a first SRS resource and a second SRS resource; wherein, the first SRS resource and the second SRS resource are sorted from small to large or from large to small according to the SRS resource identifier; and / or the first SRS resource and the second SRS resource are sorted from front to back or from back to front according to the configuration order of the SRS resources.

[0082] In the above two embodiments, the first SRS resource set and the second SRS resource set are associated with SRS resources of the same specific purpose; or the first SRS resource and the second SRS resource are associated with SRS resources of the same specific purpose; wherein the specific purpose is:

[0083] 1) Predefined;

[0084] 2) Network-side equipment configuration; or

[0085] 3) Determined according to the transmission mode of the PUSCH. For example, if the PUSCH is configured with codebook transmission, the specific purpose is codebook; if the PUSCH is configured with noncodebook transmission, the specific purpose is noncodebook.

[0086] Optionally, the PUSCH is associated with multiple SRS resource sets, wherein any two of the multiple SRS resource sets are associated with different SRS resources. For example, the PUSCH is associated with a first set and a second set, and the first set and the second set need to be associated with different SRS resource IDs.

[0087] Optionally, the terminal supports full power mode 2; wherein the terminal does not expect the PUSCH to be associated with multiple SRS resource sets including codebook purposes. In this embodiment, when the terminal supports full power mode 2, PUSCH is not supported to be associated with multiple SRS resource sets including codebook purposes, for example, the terminal does not support the configuration of multiple SRS resource sets including codebook purposes.

[0088] The following is a brief introduction to full power mode 2: Since the network-side device can configure at most one SRS resource set for the terminal for acquisition based on the uplink transmission CSI, each SRS resource set contains at most two SRS resources, and the two SRS resources contain the same number of ports, which are 1, 2, and 4 ports, but in full power, rel-16 supports different numbers of ports, and the overhead is indicated according to the larger number: in full power mode 1, the ports are the same; but in full power mode 2, the ports can be the same or different, and the set supports at most 2 different spatial information configurations and a maximum of 4 resources, with a maximum of 2 bits of SRI indicating one resource.

[0089] Optionally, the overhead size of at least one of the following domain types in the scheduling signaling is related to the SRS resource set associated with the PUSCH: SRS Resource Indicator (SRS Resource Indicator, SRI) domain, Transmit Power Control (Transmit Power Control, TPC) domain, Transmitted Precoding Matrix Indicator (Transmitted Precoding Matrix Indicator, TPMI) domain, Redundancy version domain, SRS request domain (i.e., SRS request domain), Channel State Information (CSI) request domain (i.e., CSI request). For example, the scheduling signaling is DCI or RRC, the PUSCH is associated with a first set and a second set, and the overhead size of the above at least one domain type in the DCI or RRC is related to the configured first set and the second set.

[0090] At least one "domain class" mentioned in this embodiment may refer to a type of domain, and the domain class includes multiple implementations, such as extending the domain or adding an additional identical domain to indicate multiple sets, etc. For example, originally one TPC domain, 2 bits, the extended domain still corresponds to one TPC domain, but uses 4 bits, and adding an additional identical domain means that originally one TPC domain is now two independent domains, TPC 1 and TPC 2. The two domains can be encoded independently.

[0091] In this embodiment, optionally, only when the at least one domain class has a second set configuration, the domain class in the DCI or RRC needs to be extended accordingly, which may be to extend the domain or to add an identical domain.

[0092] In this embodiment, optionally, when the at least one domain class does not have a second set configuration, the domain class in the DCI or RRC also needs to be extended accordingly according to the situation where the second set configuration is present, but the terminal ignores the interpretation of the domain or code point indicated by the second set. For example, when the at least one SRS resource set includes a first SRS resource set but does not include a second SRS resource set, the at least one domain class includes an indication domain or code point related to the second SRS resource set, and the method further includes: the terminal ignores the indication domain or code point.

[0093] Optionally, the overhead size and / or interpretation method of at least one of the following domain categories in the scheduling signaling is related to the indication of the SRI domain in the scheduling signaling: transmission power control TPC domain, send precoding matrix indication TPMI domain, redundant version domain, SRS request domain, channel state information CSI request domain.

[0094] At least one "domain class" mentioned in this embodiment may refer to a type of domain, and the domain class includes multiple implementations, such as extending the domain or adding an additional identical domain to indicate multiple sets, etc. For example, originally one TPC domain, 2 bits, the extended domain still corresponds to one TPC domain, but uses 4 bits, and adding an additional identical domain means that originally one TPC domain is now two independent domains, TPC 1 and TPC 2. The two domains can be encoded independently.

[0095] Optionally, the overhead size of each TPMI domain in at least one TPMI domain is related to the number of ports of the SRS resource in the SRS resource set. The number of TPMI domains is equal to the number of SRS resource sets, that is, one TPMI domain corresponds to one SRS resource set, and this embodiment does not limit the corresponding order of TPMI domains and SRS resource sets.

[0096] Furthermore, the overhead size of the first TPMI domain in at least one TPMI domain is determined by the maximum number of ports of the SRS resource in at least one SRS resource set. For example, two SRS resources are configured in the first SRS resource set, both of which are two-port SRS resources, and a 4-port SRS resource and a 2-port SRS resource are configured in the second SRS resource set. Then, the DCI includes two TPMI domains, and the size of the first TPMI domain is determined by 4 ports.

[0097] For example, a 4-port SRS resource and a 2-port SRS resource are configured in the second SRS resource set, which is a typical configuration in full power mode 2.

[0098] Optionally, the above embodiment further includes one of the following:

[0099] 1) For the at least one domain class, when there are multiple SRS resource sets, the terminal interprets each domain class in the at least one domain class. For example, for the at least one domain class, when the SRI domain indicates that multiple SRS sets are associated, the needs of the domain class in the DCI or RRC are interpreted simultaneously.

[0100] 2) For the at least one domain class, when the at least one SRS resource set is one, the terminal only interprets one indication field in the domain class associated with the SRS resource set indicated by the SRI field. For example, for the at least one domain class, when the SRI field indicates that PUSCH is associated with one SRS set, the domain class in the DCI or RRC only interprets the PUSCH transmission associated with the SRS set indicated by the SRI.

[0101] With respect to the domains mentioned in the above embodiments, optionally, the method further includes: determining an interpretation order of the at least one domain class according to one of the following:

[0102] 1) Predefined order. For example, TPC1 corresponds to the first set and TPC2 corresponds to the second set.

[0103] 2) The order of the SRS resource sets indicated by the scheduling signaling. For example, if the order indicated by the scheduling signaling is the second set first and the first set second, then TPC1 corresponds to the second set and TPC2 corresponds to the first set. For another example, if the scheduling signaling indicates the second set, following the order indicated, TPC1 corresponds to the second set and TPC2 is not interpreted.

[0104] Optionally, the PUSCH is associated with a first SRS resource set and a second SRS resource set, and the method further includes: receiving configuration information; wherein the configuration information is used to configure two power control parameter sequences, and the two power control parameter sequences are used to indicate the power control parameters of the PUSCH transmission unit associated with the first SRS resource set and the second SRS resource set.

[0105] In this implementation example, the network side device configures two power control parameter sequences for the terminal, which are used to indicate the power control parameters of the PUSCH transmission units associated with the first set and the second set, and the power control parameters include at least one of the following: P0, alpha, pathloss RS ID, and closed loop power control index (closed loop index), and the power control parameter sequence includes at least one of the following: sri-PUSCH-MappingToAddModList, sri-PUSCH-MappingToReleaseList.

[0106] In one example, the two power control parameter sequences include different closed loop power control indexes. For example, the protocol stipulates that the first power control parameter sequence only includes close loop index i0, i1; and the second power control parameter sequence only includes close loop index i2, i3.

[0107] In one example, the first SRS resource set and the second SRS resource set are respectively associated with one of the power control parameter sequences. For example, the first set and the second set are respectively associated with one of the power control parameter sequences, and the first resource and the second resource are respectively associated with a close loop index in the power control parameter sequence, that is, when the set and resource associated with the PUSCH transmission are determined by the above SRI indication method, the power control parameter is also determined.

[0108] Optionally, the above embodiment also includes: determining the power control parameters associated with the PUSCH transmission according to the SRI field of the scheduling signaling. For example, for the first set and the second set, the first resource of the first set is associated with i0, the second resource of the first set is associated with i1, the first resource of the second set is associated with i2, and the second resource of the second set is associated with i3; for another example, if the SRI indicates the first resource of the first set, that is, the PUSCH transmission is associated with the first resource of the first set, then the closed-loop index of the PUSCH transmission is i0; for another example, if the SRI indicates the second resource of the first set and the first resource of the second set, that is, the PUSCH transmission is associated with the second resource of the first set and the first resource of the second set, then the closed-loop indexes of the PUSCH transmission are i1 and i2, and each PUSCH transmission unit corresponds to a closed-loop index.

[0109] In other examples, the first set and the second set associated with PUSCH may be associated with power control parameter sequences in an order agreed upon by the protocol. For example, the protocol agreement may be that the first set corresponds to the first power control parameter sequence, and the second set corresponds to the second power control parameter sequence.

[0110] Optionally, the scheduling signaling includes an SRI field, and an overhead of the SRI field satisfies one of the following:

[0111] Fixed expenses;

[0112] is related to the maximum number of SRS resources configurable by the SRS resource set supported by the terminal;

[0113] Related to the maximum number of configurable SRS resource sets supported by the terminal;

[0114] It is related to the number of the SRS resource sets.

[0115] It is related to the number of SRS resources configured in each of the SRS resource sets.

[0116] Related to the number of layers supported by the terminal;

[0117] It is related to the number of layers of PUSCH transmission associated with the target SRS resource set. For example, the target SRS resource set may be the first set determined by SRI.

[0118] It is related to the maximum number of layers supported by PUSCH transmission associated with the SRS resource set.

[0119] For detailed explanation, the following will be divided into cases one to three for explanation.

[0120] Case 1

[0121] The scheduling signaling is DCI, and the bit overhead of the SRI field in the DCI, in the case of a codebook, satisfies one of the following:

[0122] 1) Fixed bit correspondence.

[0123] For example, if two sets are configured and both are associated with only one resource, 2 bits are used; if two sets are configured and at least one set is associated with two resources, 3 bits or 4 bits are used; if two sets are configured and at least one set is associated with four resources, 5 bits are used.

[0124] 2) It is related to the maximum number of resources that can be supported in all sets. For example, the bit overhead of the SRI field can be calculated using the following formula:

[0125]

[0126] N SRS,max The maximum number of resources that can be supported.

[0127] 3) It is related to the maximum number of configurable sets and the maximum number of resources that can be supported in all sets. For example, the bit overhead of the SRI field can be calculated using the following formula:

[0128]

[0129] Where N SRS,i，max It indicates the maximum number of resources supported by the i-th SRS resource set, and k,max indicates the maximum number of configurable sets.

[0130] Alternatively, the bit overhead of the SRI field can be calculated using the following formula:

[0131]

[0132] Represents permutations and combinations.

[0133] 4) It is related to the number of sets and the maximum number of resources that can be supported in all sets. For example, the bit overhead of the SRI field can be calculated using the following formula:

[0134]

[0135] Where N SRS,i,maxIt indicates the maximum number of resources supported by the i-th SRS resource set, and k indicates the number of configured sets.

[0136] 5) It is related to the number of sets and the number of resources configured in each set. For example, the bit overhead of the SRI domain can be calculated using the following formula:

[0137]

[0138] Where N SRS,i represents the number of resources configured in the i-th SRS resource set, and k represents the number of configured sets.

[0139] Alternatively, the bit overhead of the SRI field can be calculated using the following formula:

[0140]

[0141] Where N SRS,i It represents the number of resources configured for the i-th SRS resource set, and k represents the number of configured sets.

[0142] 6) It is related to the number of sets and the number of resources configured in each set. For example, the bit overhead of the SRI domain can be calculated using the following formula:

[0143]

[0144] Among them, N SRS,i represents the number of resources configured in the i-th SRS resource set, and k represents the number of configured sets.

[0145] Case 2

[0146] The scheduling signaling is DCI, and the bit overhead of the SRI field in the DCI, in the case of non-codebook, satisfies one of the following:

[0147] 1) It is related to the number of layers supported by the terminal, the number of configuration sets, and the number of resources configured in each set. For example, the bit overhead of the SRI field can be calculated using the following formula:

[0148]

[0149] k represents the number of configured sets, L max,i Indicates the maximum number of layers supported by PUSCH transmission associated with the i-th resource set (obtained through signaling or protocol agreement), N SRS,iIndicates the number of resources configured in the i-th SRS resource set.

[0150] Alternatively, the bit overhead of the SRI field can be calculated using the following formula:

[0151]

[0152] k represents the number of configured sets, L max,i Indicates the maximum number of layers supported by PUSCH transmission associated with the i-th resource set (obtained through signaling or protocol agreement), N SRS,i Indicates the number of resources configured in the i-th SRS resource set.

[0153] Alternatively, the bit overhead of the SRI field can be calculated using the following formula:

[0154]

[0155] k represents the number of configured sets, L max,i Indicates the maximum number of layers supported by PUSCH transmission associated with the i-th resource set (obtained through signaling or protocol agreement), N SRS,i Indicates the number of resources configured in the i-th SRS resource set.

[0156] Optional, all sets share one L max , the bit overhead of the SRI domain can be calculated using the following formula:

[0157]

[0158] 2) It is related to the number of layers supported by the terminal, the number of configuration sets and the number of resources configured in each set, and the number of layers of PUSCH transmission associated with the first set (corresponding to the target SRS resource set in the previous text) determined by SRI. For example, the bit overhead of the SRI domain can be calculated using the following formula:

[0159]

[0160] Alternatively, the bit overhead of the SRI field can be calculated using the following formula:

[0161]

[0162] Alternatively, the bit overhead of the SRI field can be calculated using the following formula:

[0163]

[0164] k represents the number of configured sets, L max Indicates the maximum number of layers supported by the terminal, N SRS,i Indicates the number of resources configured in the i-th SRSresource set. L1 indicates the number of layers supported by the PUSCH transmission associated with the first set indicated by SRI.

[0165] Case 3

[0166] The scheduling signaling is RRC, and the bit overhead of the SRI domain in the configured grant parameter domain in the RRC signaling is related to the maximum number of layers supported by the PUSCH transmission associated with the set, the maximum number of sets that can be supported, and the maximum number of resources that can be supported in the set. For example, the bit overhead of the SRI domain can be calculated using the following formula:

[0167]

[0168] k,max indicates the maximum number of sets supported, L max Indicates the maximum number of layers supported by the PUSCH transmission associated with the set (obtained through signaling or protocol agreement), N SRS,max Indicates the maximum number of resources that can be supported in a set;

[0169] Alternatively, the bit overhead of the SRI field can be calculated using the following formula:

[0170]

[0171] It should be noted that each optional embodiment in the foregoing text of this specification is introduced separately. In fact, these optional embodiments can also be combined to form new embodiments. In order to avoid repetition, they will not be introduced one by one here.

[0172] To illustrate in detail the PUSCH scheduling transmission method provided in the embodiments of the present application, two specific embodiments will be described below.

[0173] Embodiment 1

[0174] In this embodiment, the DCI does not include an indication of the PUSCH transmission order.

[0175] Example 1: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by means of direct indication + implicit indication.

[0176] In this example, the set whose usage includes codebook only supports the configuration of one resource.

[0177] In this example, the SRI field in the scheduling signaling may occupy 1 bit to indicate that the PUSCH transmission is associated with an implicitly indicated resource or is associated with the first SRS resource and the second SRS resource at the same time.

[0178] For example, the SRI field is 0: indicating that the resource implicitly indicated by the association, the resource ID in the two sets is the smallest, or the two set IDs are the smallest.

[0179] For example, the SRI field is 1: indicating association between the first SRS resource and the second SRS resource.

[0180] Example 2: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by means of direct indication + implicit indication.

[0181] In this example, the usage includes a codebook set that supports configuring two resources (excluding the full power mode).

[0182] In this example, the SRI field in the scheduling signaling may occupy 2 bits, and is used to indicate that the PUSCH transmission is associated with an implicitly indicated set or an implicitly indicated resource or is associated with the first and second SRS resources at the same time.

[0183] 1) In case of joint coding indication, the first set is implicitly indicated.

[0184] 00, the first resource in the implicitly indicated set;

[0185] 01, the second resource in the implicitly indicated set;

[0186] 10, the first resource in the first set and the first resource in the second set;

[0187] 11. The second resource in the first set and the second resource in the second set.

[0188] If only one resource is configured in the implicit indication set, the terminal does not expect the network to indicate 01, or thinks that 01 also represents the first resource in the implicit indication set (the codepoint mentioned above corresponds to the special processing method).

[0189] 2) In case of at least partial independent coding indication, the first SRS resource is implicitly indicated.

[0190] In this example, the SRI field in the scheduling signaling can occupy 2 bits;

[0191] 1 bit is used to indicate the association with one or more resources, and the remaining 1 bit is used to indicate the resource.

[0192] 1) For example, 0 means to associate with a resource;

[0193] 1 bit remaining:

[0194] 0 indicates the resource implicitly indicated in the first set of the association, that is, the first resource;

[0195] 1 indicates the resource implicitly indicated in the associated second set, that is, the first resource;

[0196] 2) For example, 1 means associating two resources;

[0197] 1 bit remaining,

[0198] 0 indicates to associate the first resource in the first set with the first resource in the second set;

[0199] 1 indicates to associate the second resource in the first set with the second resource in the second set;

[0200] Example 3: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by means of direct indication + implicit indication.

[0201] In this example, the usage includes a codebook set that supports configuring two resources (excluding full power). The first set configures two resources, and the second set configures one resource.

[0202] In this example, the SRI field in the scheduling signaling may occupy 2 bits.

[0203] 1) Joint coding indication:

[0204] 00, the first resource of the first set;

[0205] 01, the second resource of the first set;

[0206] 10, the first resource of the second set;

[0207] 11, the first resource of the first set and the first resource of the second set.

[0208] 2) The corresponding relationship is updated through MAC CE or RRC configuration, and the updated relationship is as follows:

[0209] 00, the first resource of the first set;

[0210] 01, the first resource of the second set;

[0211] 10, the first resource of the first set and the first resource of the second set;

[0212] 11, the second resource of the first set and the first resource of the second set.

[0213] Example 4: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by direct indication.

[0214] In this example, the usage set containing codebook only supports the configuration of one resource.

[0215] In this example, the SRI field in the scheduling signaling may occupy 2 bits, and is used to indicate that the PUSCH transmission is associated with the first SRS resource, the second SRS resource, or both the first and second SRS resources.

[0216] 1) In case of joint coding indication:

[0217] 00, the first resource of the first set;

[0218] 01, the first resource of the second set;

[0219] 10 or 11 indicates the first resource that associates the first set with the second set.

[0220] 2) In the case of at least partially independent coding indications:

[0221] One bit is used to indicate whether multiple sets are associated. When indicating that multiple sets are associated, the remaining 1 bit is ignored and not interpreted. When only one set is associated, the remaining 1 bit is used to indicate the specific associated set.

[0222] 0 indicates that a set is associated, and the remaining 1 bit indicates;

[0223] 0 means the first resource associated with the first set;

[0224] 1 means the first resource associated with the second set;

[0225] 1 means associating all sets, and associating the first resource of the first set with the first resource of the second set;

[0226] At this time, the remaining 1 bit is ignored and not interpreted.

[0227] Example 5: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by direct indication.

[0228] In this example, usage includes codebook sets that are configured with two resources.

[0229] In this example, the SRI field in the scheduling signaling may occupy 3 bits, and is used to indicate that the PUSCH transmission is associated with the first SRS resource, the second SRS resource, or both the first and second SRS resources.

[0230] 1) In case of joint coding indication:

[0231] 000, indicating the first resource of the first set;

[0232] 001, indicating the second resource of the first set;

[0233] 010, indicating the first resource of the second set;

[0234] 011, indicating the second resource of the second set;

[0235] 100, indicating the first resource of the first set and the first resource of the second set;

[0236] 101, indicating the first resource of the first set and the second resource of the second set;

[0237] 110, indicating the second resource of the first set and indicating the first resource of the second set;

[0238] 111, indicating the second resource of the first set and indicating the second resource of the second set;

[0239] 2) In the case of at least partially independent coded indication, 1 bit is used to indicate whether multiple sets are associated. When multiple sets are associated, the remaining two bits are jointly coded for indication; when one set is associated, the remaining 2 bits are jointly coded or independently coded.

[0240] For example, 0 indicates that 1 set is associated; the remaining 2 bits are jointly encoded:

[0241] 00, indicating the first resource of the first set;

[0242] 01, indicating the second resource of the first set;

[0243] 10, indicating the first resource of the second set;

[0244] 11, indicating the second resource of the second set;

[0245] For example, 0 indicates that 1 set is associated; the remaining 2 bits are independently encoded:

[0246] 1 bit is used to indicate the set: 0 indicates the first set; 1 indicates the second set.

[0247] 1 bit is used to indicate resource: 0 indicates the first resource; 1 indicates the second resource.

[0248] For another example, 1 indicates that two sets are associated; the remaining 2 bits are jointly encoded:

[0249] 00, indicating the first resource of the first set and the first resource of the second set;

[0250] 01, indicating the first resource of the first set and the second resource of the second set;

[0251] 10, indicating the second resource of the first set and the first resource of the second set;

[0252] 11, indicating the second resource of the first set and indicating the second resource of the second set;

[0253] In this example 5, the SRI field in the scheduling signaling may occupy 4 bits, indicating that the set and resource levels are independently coded and indicated in a default order.

[0254] The 2 bits are used to indicate the first set, the second set, the first set and the second set, 00, the first set, 01, the second set, 10, the first and second sets.

[0255] The remaining 2 bits are independently encoded. The first independent encoding field 1 bit is used to indicate the resource selected in the first set, and the second independent encoding field 1 bit is used to indicate the resource selected in the second set.

[0256] In this example 5, the SRI field in the scheduling signaling may occupy 4 bits, indicating that the set and resource levels are independently coded and indicated in the set order.

[0257] Two bits are used to indicate the first set, the second set, the first set and the second set: 00, the first set, 01, the second set, 10, the first set and the second set, 11, the second set and the first set.

[0258] The remaining 2 bits are independently encoded. If the second set and the first set are indicated, 1 bit of the first independent encoding field is used to indicate the resource selected in the second set, and 1 bit of the second independent encoding field is used to indicate the resource selected in the first set.

[0259] Example 6: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by direct indication.

[0260] In this example, the usage contains two resources configured in the first set of codebooks, and one resource configured in the second set.

[0261] In this example 5, the SRI field in the scheduling signaling may occupy 3 bits and adopt joint coding indication.

[0262] 1) The originally agreed correspondence is as follows:

[0263] 000, indicating the first resource of the first set;

[0264] 001, indicating the second resource of the first set;

[0265] 010, indicating the first resource of the second set;

[0266] 011, indicating the second resource of the second set;

[0267] 100, indicating the first resource of the first set and the first resource of the second set;

[0268] 101, indicating the first resource of the first set and the second resource of the second set;

[0269] 110, indicating the second resource of the first set and indicating the first resource of the second set;

[0270] 111 indicates the second resource of the first set and indicates the second resource of the second set.

[0271] 2) Combined with the special processing method corresponding to the invalid code point:

[0272] Optionally, the terminal does not expect to indicate that the set or resource corresponding to the codepoint is not configured, that is, the terminal should not indicate an invalid codepoint. The terminal should not be indicated as a codepoint of 011 because the second set only configures one resource.

[0273] Optionally, the closest resource, the closest being based on the code point distance forward. For example, when the terminal is indicated with a code point of 011 (the second resource of the second set), the terminal interprets it as 010 selected by the network.

[0274] Optionally, the closest resource, the closest is based on the code point distance backward. For example, when the terminal is indicated as the code point of 011 (the second resource of the second set), the terminal interprets it as 100 selected by the network.

[0275] Optionally, the closest resource may be based on the distance of resources in the set. For example, when the terminal is indicated with a codepoint of 011 (the second resource in the second set), the terminal interprets that the network has selected the first resource in the second set.

[0276] Example 7: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by direct indication.

[0277] In this example, to support full power mode 2, usage includes a codebook and each set supports configuration of up to 4 resources. The first set is configured with 3 resources, and the second set is configured with 1 resource.

[0278] In this example, the joint encoding indicates that the overhead is related to the number of sets and the number of resources in the set:

[0279] 000, indicating the first resource of the first set;

[0280] 001, indicating the second resource of the first set;

[0281] 010, indicating the third resource of the first set;

[0282] 011, indicating the first resource of the second set;

[0283] 100, indicating the first resource of the first set and the first resource of the second set;

[0284] 101, indicating the second resource of the first set and indicating the first resource of the second set;

[0285] 110, indicating the third resource of the first set and the first resource of the second set;

[0286] 111, not used.

[0287] Embodiment 2

[0288] In this embodiment, the scheduling signaling includes an indication of the PUSCH transmission order:

[0289] Example 1: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by direct indication.

[0290] In this example, usage includes codebook sets that are configured with two resources.

[0291] In this example, the SRI field in the scheduling signaling may occupy 4 bits to indicate whether PUSCH transmission is associated with the first SRS resource, the second SRS resource, or both the first and second SRS resources, and the order of association needs to be indicated.

[0292] 1) Joint coding indication:

[0293] 0000, indicating the first resource of the first set;

[0294] 0001, indicating the second resource of the first set;

[0295] 0010, indicating the first resource of the second set;

[0296] 0011, indicating the second resource of the second set;

[0297] 0100, indicating the first resource of the first set and the first resource of the second set;

[0298] 0101, indicating the first resource of the first set and the second resource of the second set;

[0299] 0110, indicating the second resource of the first set and the first resource of the second set;

[0300] 0111, indicating the second resource of the first set and indicating the second resource of the second set;

[0301] 1000, indicating the first resource of the second set and the first resource of the first set;

[0302] 1001, indicating the first resource of the second set and indicating the second resource of the first set;

[0303] 1010, indicating the second resource of the second set and indicating the first resource of the first set;

[0304] 1011, indicating the second resource of the second set and indicating the second resource of the first set;

[0305] 1100, invalid code point;

[0306] 1101, invalid code point;

[0307] 1110, invalid code point;

[0308] 1111, invalid code point.

[0309] 2) If the SRI indicates 0100, PUSCH is transmitted 4 times.

[0310] The first repetition transmission is associated with the first set, the second repetition transmission is associated with the second set, the third repetition transmission is associated with the first set, and the fourth repetition transmission is associated with the second set; or the first and second repetition transmissions are associated with the first set, and the third and fourth repetition transmissions are associated with the second set.

[0311] 3) If the SRI indicates 1000, PUSCH is transmitted 4 times.

[0312] The first repetition transmission is associated with the second set, the second repetition transmission is associated with the first set, the third repetition transmission is associated with the second set, and the fourth repetition transmission is associated with the first set. Or the first and second repetition transmissions are associated with the second set, and the third and fourth repetition transmissions are associated with the first set.

[0313] 4) If the SRI indicates 0100, PUSCH is transmitted by frequency hopping on two different symbols in one slot. The first frequency hopping is associated with the first set, and the second frequency hopping is associated with the second set.

[0314] Example 2: In this example, the scheduling signaling indicates at least one SRS resource set and / or SRS resource associated with the PUSCH by direct indication.

[0315] In this example, usage includes codebook sets that are configured with two resources.

[0316] In this example, the SRI field in the scheduling signaling may occupy 4 bits to indicate whether PUSCH transmission is associated with the first SRS resource, the second SRS resource, or both the first and second SRS resources, and the order of association needs to be indicated.

[0317] 1) At least partially independently coded indication:

[0318] 2 bits are used to indicate association with the first SRS resource set, association with the second SRS resource set, association with the first SRS resource set and the second SRS resource set, or association with the second SRS resource set and the first SRS resource set.

[0319] For example, 00 indicates the first set;

[0320] 01, indicating the second set;

[0321] 10, indicating the first set and the second set;

[0322] 11, indicating the second set and the first set.

[0323] The other 2 bits can be associated with the first set and the second set in sequence, or according to the set order indicated by the first 2 bits.

[0324] For example, independent coding is used to indicate resources in a set, 1 bit is used to indicate resources in the first set, and another 1 bit is used to indicate resources in the second set;

[0325] For example, joint encoding is used to indicate the resource in a set:

[0326] 00 first resource and first resource;

[0327] 01 first resource and second resource;

[0328] 10 second resource and first resource;

[0329] 11 second resource and second resource;

[0330] For example, the first set and the second set are associated in order, and 0110 refers to the first resource of the second set;

[0331] For example, according to the set order association indicated by the first 2 bits, 0110 refers to the second resource of the second set.

[0332] Combination of the above Figure 2 The PUSCH scheduling transmission method according to the embodiment of the present application is described in detail. Figure 3 A method for scheduling transmission of a PUSCH according to another embodiment of the present application is described in detail. It can be understood that the interaction between the network side device and the terminal described in the network side device is similar to Figure 2 The description of the terminal side in the method shown is the same, and to avoid repetition, the relevant description is appropriately omitted.

[0333] Figure 3 1 is a schematic diagram of a PUSCH scheduling transmission method implementation flow diagram of an embodiment of the present application, which can be applied to network side devices. Figure 3 As shown, the method 300 includes:

[0334] S302: The network side device sends a scheduling signaling, where the scheduling signaling is used to schedule PUSCH transmission. The scheduling signaling is also used by the terminal to determine at least one SRS resource set and / or SRS resource associated with the PUSCH.

[0335] S304: The network side device receives the PUSCH.

[0336] The PUSCH is sent by the terminal according to the SRS resource set and / or SRS resource.

[0337] In an embodiment of the present application, before S302 it also includes: sending SRS configuration, the SRS configuration includes: at least one SRS resource set, each of the SRS resource sets includes at least one SRS resource, wherein the number of SRS resources included in the target SRS resource set is greater than or equal to the number of SRS resources included in other SRS resource sets in the at least one SRS resource set, and the target SRS resource set is the one with the smallest SRS resource set identifier in the at least one SRS resource set.

[0338] In an embodiment of the present application, at least one SRS resource set and / or SRS resource associated with the PUSCH can be determined based on the scheduling signaling of the PUSCH, and each SRS resource set or SRS resource can correspond to a TRP. In this way, the embodiment of the present application can realize the transmission of PUSCH in a multi-TRP scenario, so that the terminal can send PUSCH to the TRP corresponding to the SRS resource set and / or SRS resource, thereby improving the transmission efficiency of PUSCH.

[0339] Figure 4 is a schematic diagram of the structure of a terminal according to an embodiment of the present application, such as Figure 4 As shown, the terminal 400 includes:

[0340] The receiving module 402 may be configured to receive a scheduling signaling, wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is further used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH;

[0341] The sending module 404 may be configured to send the PUSCH according to the SRS resource set and / or the SRS resource.

[0342] In an embodiment of the present application, at least one SRS resource set and / or SRS resource associated with the PUSCH can be determined based on the scheduling signaling of the PUSCH, and each SRS resource set or SRS resource can correspond to a TRP. In this way, the embodiment of the present application can realize the transmission of PUSCH in a multi-TRP scenario, so that the terminal can send PUSCH to the TRP corresponding to the SRS resource set and / or SRS resource, thereby improving the transmission efficiency of PUSCH.

[0343] Optionally, as an embodiment, the receiving module 402 can also be used to receive an SRS configuration, wherein the SRS configuration includes: at least one SRS resource set, each of the SRS resource sets including at least one SRS resource, wherein the number of SRS resources included in the target SRS resource set is greater than or equal to the number of SRS resources included in other SRS resource sets in the at least one SRS resource set, and the target SRS resource set is the one with the smallest SRS resource set identifier in the at least one SRS resource set.

[0344] Optionally, as an embodiment, the method of associating the PUSCH with the SRS resource set and / or the SRS resource is implicit;

[0345] The number of the SRS resource set and / or the SRS resource is the smallest or largest; and / or

[0346] The beam information of the receiving beam of the scheduling signaling or the beam information of the transmitting beam of the PUSCH is the same as at least one of the following: the beam information of the path loss reference signal RS associated with the SRS resource set and / or the SRS resource, and the beam information associated with the SRS resource set and / or the SRS resource.

[0347] Optionally, as an embodiment, the scheduling signaling includes an indication field, and the indication field is used to indicate the SRS resource set and / or SRS resource.

[0348] Optionally, as an embodiment, the scheduling signaling includes at least two independent coding fields, and the at least two independent coding fields are used to respectively indicate SRS resources in at least two of the SRS resource sets.

[0349] Optionally, as an embodiment, the PUSCH includes at least one transmission unit, and the transmission unit includes one of the following:

[0350] One nominal PUSCH repetition transmission, one actual PUSCH repetition transmission, one PUSCH transmission in a time domain unit, one PUSCH frequency hopping transmission, and one PUSCH transmission among multiple PUSCH repetition transmissions.

[0351] Optionally, as an embodiment,

[0352] The scheduling signaling indicates one of the SRS resource sets, and the transmission unit is associated with one of the SRS resource sets; or

[0353] The scheduling signaling indicates a plurality of the SRS resource sets, the scheduling signaling is further used to indicate an order of the plurality of the SRS resource sets, and the transmission unit is associated with the order of the plurality of the SRS resource sets indicated by the scheduling signaling; or

[0354] The scheduling signaling indicates multiple SRS resource sets, and the scheduling signaling does not indicate the order of the multiple SRS resource sets. The transmission unit is associated with one of the following: the configuration order of the multiple SRS resource sets; the identification order of the multiple SRS resource sets; the identification order of the SRS resources in the multiple SRS resource sets; the parity order of the time domain unit where the transmission unit is located, wherein the multiple SRS resource sets have a parity binding relationship with the time domain unit where the transmission unit is located.

[0355] Optionally, as an embodiment, the code point in the scheduling signaling is used to indicate the at least one SRS resource set and / or SRS resource, wherein the correspondence between the code point and the SRS resource set and / or SRS resource is:

[0356] predefined;

[0357] Network-side device configuration; or

[0358] Network-side device update indication.

[0359] Optionally, as an embodiment, the terminal 400 further includes a determination module, configured to determine a processing method corresponding to an invalid code point; wherein the processing method corresponding to the invalid code point includes at least one of the following:

[0360] If only one SRS resource is configured in the SRS resource set corresponding to the target code point, the SRS resource corresponding to the target code point is the one SRS resource;

[0361] If the target code point is an invalid code point, the SRS resource set and / or SRS resource corresponding to the code point before or after the target code point is used as the SRS resource set and / or SRS resource corresponding to the invalid code point;

[0362] If the target code point is an invalid code point, the SRS resource set and / or SRS resource before or after the SRS resource set and / or SRS resource corresponding to the target code point are used as the SRS resource set and / or SRS resource corresponding to the invalid code point;

[0363] The terminal does not expect that the SRS resource set corresponding to the code point is an SRS resource set that is not configured;

[0364] The SRS resource corresponding to the code point that the terminal does not expect is an SRS resource that is not configured.

[0365] Optionally, as an embodiment, the PUSCH is associated with a first SRS resource and a second SRS resource; wherein,

[0366] The first SRS resource and the second SRS resource are associated with different SRS resource sets.

[0367] Optionally, as an embodiment, the PUSCH is associated with multiple SRS resource sets; wherein any two SRS resource sets among the multiple SRS resource sets satisfy at least one of the following:

[0368] Having different path loss RS, different spatial beam configurations, different associated RS, the same time domain characteristics, associated with the same SRS resource identification ID, the same number of SRS resource ports, the same period, different period time slot offsets, associated with different TRP indexes, associated with different control resource set resource pool indexes, different power control parameter indexes, and different closed-loop power control index groups.

[0369] Optionally, as an embodiment, the PUSCH is associated with a first SRS resource set and a second SRS resource set; wherein the first SRS resource set and the second SRS resource set satisfy at least one of the following:

[0370] The first SRS resource set and the second SRS resource set are sorted in ascending order or descending order according to the SRS resource set identifier;

[0371] The first SRS resource set and the second SRS resource set are arranged from front to back or from back to front according to the configuration order of the SRS resource sets;

[0372] The first SRS resource set and the second SRS resource set are configured in different sequences;

[0373] The first SRS resource set and the second SRS resource set are configured with different power control parameter indexes, and the power control parameter index is used to distinguish the first SRS resource set and the second SRS resource set.

[0374] Optionally, as an embodiment, the PUSCH is associated with a first SRS resource and a second SRS resource; wherein,

[0375] The first SRS resource and the second SRS resource are sorted in ascending order or descending order according to the SRS resource identifier; and / or

[0376] The first SRS resource and the second SRS resource are arranged from front to back or from back to front according to the configuration order of the SRS resources.

[0377] Optionally, as an embodiment, the first SRS resource set and the second SRS resource set are associated with SRS resources of the same specific purpose; or the first SRS resource and the second SRS resource are associated with SRS resources of the same specific purpose; wherein the specific purpose is:

[0378] predefined;

[0379] Configuration of network-side equipment; or

[0380] Determined according to the transmission mode of the PUSCH.

[0381] Optionally, as an embodiment, the PUSCH is associated with multiple SRS resource sets; wherein, the SRS resources associated with any two SRS resource sets among the multiple SRS resource sets are different.

[0382] Optionally, as an embodiment, the terminal supports full power mode 2; wherein the terminal does not expect the PUSCH to be associated with multiple SRS resource sets containing codebook usage.

[0383] Optionally, as an embodiment, the overhead size of at least one of the following domain classes in the scheduling signaling is related to the SRS resource set:

[0384] SRS resource indication field, transmission power control TPC field, transmit precoding matrix indication TPMI field, redundant version field, SRS request field, channel state information CSI request field.

[0385] Optionally, as an embodiment, the overhead size of each TPMI domain in the at least one TPMI domain is related to the number of ports of the SRS resources in the SRS resource set.

[0386] Optionally, as an embodiment, the overhead size of the first TPMI domain in the at least one TPMI domain is determined by the maximum number of ports of the SRS resources in the at least one SRS resource set.

[0387] Optionally, as an embodiment, the at least one SRS resource set includes a first SRS resource set but does not include a second SRS resource set, the at least one domain class includes an indication domain or code point related to the second SRS resource set, and the method further includes:

[0388] The terminal ignores the indication field or code point.

[0389] Optionally, as an embodiment, the overhead size and / or interpretation method of at least one of the following domain types in the scheduling signaling is related to the indication of the SRI domain in the scheduling signaling:

[0390] Transmit power control TPC domain, transmit precoding matrix indication TPMI domain, redundant version domain, SRS request domain, channel state information CSI request domain.

[0391] Optionally, as an embodiment, the terminal 400 further includes a processing module, configured to:

[0392] For the at least one domain class, when there are multiple at least one SRS resource sets, interpret each domain class in the at least one domain class; or

[0393] For the at least one domain class, when the at least one SRS resource set is one, only one indication field in the domain class associated with the SRS resource set indicated by the SRI field is interpreted.

[0394] Optionally, as an embodiment, the terminal 400 further includes a determining module, configured to determine the interpretation order of the at least one domain class according to one of the following:

[0395] Predefined order;

[0396] The order of the SRS resource sets indicated by the scheduling signaling.

[0397] Optionally, as an embodiment, the PUSCH is associated with a first SRS resource set and a second SRS resource set, and the receiving module 402 may be configured to receive configuration information;

[0398] The configuration information is used to configure two power control parameter sequences, and the two power control parameter sequences are used to indicate power control parameters of a PUSCH transmission unit associated with the first SRS resource set and the second SRS resource set.

[0399] Optionally, as an embodiment,

[0400] The two power control parameter sequences contain different closed-loop power control indexes; and / or

[0401] The first SRS resource set and the second SRS resource set are respectively associated with one power control parameter sequence.

[0402] Optionally, as an embodiment, the terminal 400 further includes a determination module, configured to determine a power control parameter associated with the PUSCH transmission according to an SRI field of the scheduling signaling.

[0403] Optionally, as an embodiment, the scheduling signaling includes an SRI field, and the overhead of the SRI field satisfies one of the following:

[0404] Fixed expenses;

[0405] is related to the maximum number of SRS resources configurable by the SRS resource set supported by the terminal;

[0406] Related to the maximum configurable number of SRS resource sets supported by the terminal;

[0407] It is related to the number of the SRS resource sets.

[0408] It is related to the number of SRS resources configured in each of the SRS resource sets.

[0409] Related to the number of layers supported by the terminal;

[0410] Related to the number of layers of PUSCH transmission associated with the target SRS resource set;

[0411] It is related to the maximum number of layers supported by PUSCH transmission associated with the SRS resource set.

[0412] According to the terminal 400 of the embodiment of the present application, the process of the method 200 corresponding to the embodiment of the present application can be referred to, and the various units / modules in the terminal 400 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 200, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.

[0413] The terminal in the embodiment of the present application may be a device, or a component, integrated circuit, or chip in the terminal. The device may be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include but is not limited to the types of terminal 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0414] The terminal in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0415] The terminal provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0416] Figure 5 is a schematic diagram of the structure of a network side device according to an embodiment of the present application, such as Figure 5 As shown, the network side device 500 includes:

[0417] The sending module 502 may be used to send scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used by the terminal to determine at least one SRS resource set and / or SRS resource associated with the PUSCH;

[0418] The receiving module 504 may be configured to receive the PUSCH, where the PUSCH is sent by the terminal according to the SRS resource set and / or the SRS resource.

[0419] Optionally, the sending module 502 of an embodiment of the present application can also be used to: send an SRS configuration, the SRS configuration including: at least one SRS resource set, each of the SRS resource sets including at least one SRS resource, wherein the number of SRS resources included in the target SRS resource set is greater than or equal to the number of SRS resources included in other SRS resource sets in the at least one SRS resource set, and the target SRS resource set is the one with the smallest SRS resource set identifier in the at least one SRS resource set.

[0420] In an embodiment of the present application, at least one SRS resource set and / or SRS resource associated with the PUSCH can be determined based on the scheduling signaling of the PUSCH, and each SRS resource set or SRS resource can correspond to a TRP. In this way, the embodiment of the present application can realize the transmission of PUSCH in a multi-TRP scenario, so that the terminal can send PUSCH to the TRP corresponding to the SRS resource set and / or SRS resource, thereby improving the transmission efficiency of PUSCH.

[0421] According to the network side device 500 of the embodiment of the present application, the process of the method 300 corresponding to the embodiment of the present application can be referred to, and the various units / modules in the network side device 500 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 300, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.

[0422] Optional, such as Figure 6 As shown, the embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, and a program or instruction stored in the memory 602 and executable on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement the various processes of the above-mentioned PUSCH scheduling transmission method embodiment, and can achieve the same technical effect. When the communication device 600 is a network side device, the program or instruction is executed by the processor 601 to implement the various processes of the above-mentioned PUSCH scheduling transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0423] Figure 7 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0424] The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710.

[0425] Those skilled in the art will appreciate that the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0426] It should be understood that in the embodiment of the present application, the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0427] In the embodiment of the present application, the radio frequency unit 701 receives downlink data from the network side device and sends it to the processor 710 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 701 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0428] The memory 709 can be used to store software programs or instructions and various data. The memory 709 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 709 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile 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. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0429] The processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 710.

[0430] Among them, the radio frequency unit 701 is used to receive scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; and send the PUSCH according to the SRS resource set and / or SRS resource.

[0431] In an embodiment of the present application, at least one SRS resource set and / or SRS resource associated with the PUSCH can be determined according to the scheduling signaling of the PUSCH, and each SRS resource set or SRS resource can correspond to a TRP. In this way, the embodiment of the present application can realize the transmission of PUSCH in a multi-TRP scenario, so that the terminal can send PUSCH to the TRP corresponding to the SRS resource set and / or SRS resource, thereby improving the transmission efficiency of PUSCH.

[0432] The terminal 700 provided in the embodiment of the present application can also implement the various processes of the above-mentioned PUSCH scheduling transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0433] Specifically, the embodiment of the present application also provides a network side device. Figure 8As shown, the network side device 800 includes: an antenna 81, a radio frequency device 82, and a baseband device 83. The antenna 81 is connected to the radio frequency device 82. In the uplink direction, the radio frequency device 82 receives information through the antenna 81 and sends the received information to the baseband device 83 for processing. In the downlink direction, the baseband device 83 processes the information to be sent and sends it to the radio frequency device 82. The radio frequency device 82 processes the received information and sends it out through the antenna 81.

[0434] The frequency band processing device may be located in the baseband device 83 . The method executed by the network-side device in the above embodiment may be implemented in the baseband device 83 . The baseband device 83 includes a processor 84 and a memory 85 .

[0435] The baseband device 83 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 8 As shown, one of the chips is, for example, a processor 84, which is connected to a memory 85 to call a program in the memory 85 to execute the network-side device operations shown in the above method embodiment.

[0436] The baseband device 83 may further include a network interface 86 for exchanging information with the radio frequency device 82 , and the interface may be, for example, a common public radio interface (CPRI for short).

[0437] Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 85 and executable on the processor 84, and the processor 84 calls the instructions or programs in the memory 85 to execute Figure 5 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0438] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned PUSCH scheduling transmission method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0439] The processor may be a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0440] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the various processes of the above-mentioned PUSCH scheduling transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0441] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0442] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0443] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, computer, server, air conditioner, or network side device, etc.) to execute the methods described in each embodiment of the present application.

[0444] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for scheduling transmission of a physical uplink shared channel PUSCH, characterized in that: The method comprises: The terminal receives scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; The terminal sends the PUSCH according to the SRS resource set and / or the SRS resource; The PUSCH is associated with a first SRS resource and a second SRS resource; and the first SRS resource and the second SRS resource are associated with different SRS resource sets.

2. The method according to claim 1, characterized in that The method of associating the PUSCH with the SRS resource set and / or the SRS resource is implicit; The number of the SRS resource set and / or the SRS resource is the smallest or largest; and / or The beam information of the receiving beam of the scheduling signaling or the beam information of the transmitting beam of the PUSCH is the same as at least one of the following: the beam information of the path loss reference signal RS associated with the SRS resource set and / or the SRS resource, and the beam information associated with the SRS resource set and / or the SRS resource.

3. The method according to claim 1, characterized in that The scheduling signaling includes an indication field, and the indication field is used to indicate the SRS resource set and / or the SRS resource.

4. The method according to claim 1, characterized in that: The scheduling signaling includes at least two independent coding fields, and the at least two independent coding fields are used to respectively indicate SRS resources in at least two of the SRS resource sets.

5. The method according to any one of claims 1 to 4, characterized in that: The PUSCH includes at least one transmission unit, and the transmission unit includes one of the following: One nominal PUSCH repetition transmission, one actual PUSCH repetition transmission, one PUSCH transmission in a time domain unit, one PUSCH frequency hopping transmission, and one PUSCH transmission among multiple PUSCH repetition transmissions.

6. The method according to claim 5, characterized in that The scheduling signaling indicates one of the SRS resource sets, and the transmission unit is associated with one of the SRS resource sets; or The scheduling signaling indicates a plurality of the SRS resource sets, the scheduling signaling is further used to indicate an order of the plurality of the SRS resource sets, and the transmission unit is associated with the order of the plurality of the SRS resource sets indicated by the scheduling signaling; or The scheduling signaling indicates multiple SRS resource sets, and the scheduling signaling does not indicate the order of the multiple SRS resource sets. The transmission unit is associated with one of the following: the configuration order of the multiple SRS resource sets; the identification order of the multiple SRS resource sets; the identification order of the SRS resources in the multiple SRS resource sets; the parity order of the time domain unit where the transmission unit is located, wherein the multiple SRS resource sets have a parity binding relationship with the time domain unit where the transmission unit is located.

7. The method according to claim 1, characterized in that The code point in the scheduling signaling is used to indicate the at least one SRS resource set and / or SRS resource, wherein the correspondence between the code point and the SRS resource set and / or SRS resource is: predefined; Network-side device configuration; or Network-side device update indication.

8. The method according to claim 7, characterized in that The method further includes: determining a processing method corresponding to an invalid code point; wherein the processing method corresponding to the invalid code point includes at least one of the following: If only one SRS resource is configured in the SRS resource set corresponding to the target code point, the SRS resource corresponding to the target code point is the one SRS resource; If the target code point is an invalid code point, the SRS resource set and / or SRS resource corresponding to the code point before or after the target code point is used as the SRS resource set and / or SRS resource corresponding to the invalid code point; If the target code point is an invalid code point, the SRS resource set and / or SRS resource before or after the SRS resource set and / or SRS resource corresponding to the target code point are used as the SRS resource set and / or SRS resource corresponding to the invalid code point; The terminal does not expect that the SRS resource set corresponding to the code point is an SRS resource set that is not configured; The SRS resource corresponding to the code point that the terminal does not expect is an SRS resource that is not configured.

9. The method according to claim 1, characterized in that: The PUSCH is associated with multiple SRS resource sets; wherein any two SRS resource sets among the multiple SRS resource sets satisfy at least one of the following: Having different path loss RS, different spatial beam configurations, different associated RS, the same time domain characteristics, associated with the same SRS resource identification ID, the same number of SRS resource ports, the same period, different period time slot offsets, associated with different TRP indexes, associated with different control resource set resource pool indexes, different power control parameter indexes, and different closed-loop power control index groups.

10. The method according to claim 1, characterized in that The PUSCH is associated with a first SRS resource set and a second SRS resource set; wherein the first SRS resource set and the second SRS resource set satisfy at least one of the following: The first SRS resource set and the second SRS resource set are sorted in ascending order or descending order according to the SRS resource set identifier; The first SRS resource set and the second SRS resource set are arranged from front to back or from back to front according to the configuration order of the SRS resource sets; The first SRS resource set and the second SRS resource set are configured in different sequences; The first SRS resource set and the second SRS resource set are configured with different power control parameter indexes, and the power control parameter index is used to distinguish the first SRS resource set and the second SRS resource set.

11. The method according to claim 1, characterized in that: The first SRS resource and the second SRS resource are sorted in ascending order or descending order according to the SRS resource identifier; and / or The first SRS resource and the second SRS resource are arranged from front to back or from back to front according to the configuration order of the SRS resources.

12. The method according to claim 10, characterized in that The first SRS resource set and the second SRS resource set are associated with SRS resources of the same specific purpose; or the first SRS resource and the second SRS resource are associated with SRS resources of the same specific purpose; wherein the specific purpose is: predefined; Configuration of network-side equipment; or Determined according to the transmission mode of the PUSCH.

13. The method according to claim 1, characterized in that The PUSCH is associated with a plurality of SRS resource sets; wherein any two of the plurality of SRS resource sets are associated with different SRS resources.

14. The method according to claim 1, characterized in that The terminal supports full power mode 2; wherein the terminal does not expect the PUSCH to be associated with multiple SRS resource sets including codebook usage.

15. The method according to claim 1, characterized in that The overhead size of at least one of the following domain classes in the scheduling signaling is related to the SRS resource set: SRS resource indication field, transmission power control TPC field, transmit precoding matrix indication TPMI field, redundant version field, SRS request field, channel state information CSI request field.

16. The method according to claim 15, characterized in that The overhead size of each TPMI domain in the at least one TPMI domain is related to the number of ports of the SRS resources in the SRS resource set.

17. The method according to claim 16, characterized in that The overhead size of the first TPMI domain in the at least one TPMI domain is determined by the maximum number of ports of the SRS resources in the at least one SRS resource set.

18. The method according to claim 15, characterized in that The at least one SRS resource set includes a first SRS resource set but does not include a second SRS resource set, the at least one domain class includes an indication domain or code point related to the second SRS resource set, and the method further includes: The terminal ignores the indication field or code point.

19. The method according to claim 1, characterized in that The overhead size and / or interpretation method of at least one of the following domain types in the scheduling signaling is related to the indication of the SRI domain in the scheduling signaling: Transmit power control TPC domain, transmit precoding matrix indication TPMI domain, redundant version domain, SRS request domain, channel state information CSI request domain.

20. The method according to claim 19, characterized in that The method further comprises: For the at least one domain class, when there are multiple at least one SRS resource sets, the terminal interprets each domain class in the at least one domain class; or For the at least one domain class, when the at least one SRS resource set is one, the terminal only interprets one indication field in the domain class associated with the SRS resource set indicated by the SRI field.

21. The method according to claim 15 or 19, characterized in that The method further includes: determining the interpretation order of the at least one domain class according to one of the following: Predefined order; The order of the SRS resource sets indicated by the scheduling signaling.

22. The method according to claim 1, characterized in that The PUSCH is associated with a first SRS resource set and a second SRS resource set, and the method further includes: receiving configuration information; The configuration information is used to configure two power control parameter sequences, and the two power control parameter sequences are used to indicate power control parameters of a PUSCH transmission unit associated with the first SRS resource set and the second SRS resource set.

23. The method according to claim 22, characterized in that The two power control parameter sequences contain different closed-loop power control indexes; and / or The first SRS resource set and the second SRS resource set are respectively associated with one power control parameter sequence.

24. The method according to claim 22, characterized in that The method further comprises: The power control parameter associated with the PUSCH transmission is determined according to the SRI field of the scheduling signaling.

25. The method according to claim 1, characterized in that The scheduling signaling includes an SRI domain class, and the overhead of the SRI domain class satisfies one of the following: Fixed expenses; is related to the maximum number of SRS resources configurable by the SRS resource set supported by the terminal; Related to the maximum configurable number of SRS resource sets supported by the terminal; Related to the number of the SRS resource sets; is related to the number of SRS resources configured in each of the SRS resource sets; Related to the number of layers supported by the terminal; Related to the number of layers of PUSCH transmission associated with the target SRS resource set; It is related to the maximum number of layers supported by PUSCH transmission associated with the SRS resource set.

26. The method according to claim 1, characterized in that Before the terminal receives the scheduling signaling, it also includes: The terminal receives an SRS configuration, the SRS configuration comprising: at least one SRS resource set, each of the SRS resource sets comprising at least one SRS resource, wherein the number of SRS resources included in a target SRS resource set is greater than or equal to the number of SRS resources included in other SRS resource sets in the at least one SRS resource set, and the target SRS resource set is the one with the smallest SRS resource set identifier in the at least one SRS resource set.

27. A method for scheduling transmission of PUSCH, characterized in that: The method comprises: The network side device sends a scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used by the terminal to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; The network side device receives the PUSCH, where the PUSCH is sent by the terminal according to the SRS resource set and / or the SRS resource; The PUSCH is associated with a first SRS resource and a second SRS resource; and the first SRS resource and the second SRS resource are associated with different SRS resource sets.

28. The method according to claim 27, characterized in that Before the network side device sends the scheduling signaling, it also includes: The network side device sends an SRS configuration, and the SRS configuration includes: at least one SRS resource set, each of the SRS resource sets includes at least one SRS resource, wherein the number of SRS resources included in the target SRS resource set is greater than or equal to the number of SRS resources included in other SRS resource sets in the at least one SRS resource set, and the target SRS resource set is the one with the smallest SRS resource set identifier in the at least one SRS resource set.

29. A terminal, characterized in that: include: A receiving module, configured to receive a scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; A sending module, configured to send the PUSCH according to the SRS resource set and / or the SRS resource; The PUSCH is associated with a first SRS resource and a second SRS resource; and the first SRS resource and the second SRS resource are associated with different SRS resource sets.

30. A network side device, characterized in that: include: A sending module, configured to send a scheduling signaling; wherein the scheduling signaling is used to schedule PUSCH transmission, and the scheduling signaling is also used by the terminal to determine at least one SRS resource set and / or SRS resource associated with the PUSCH; A receiving module, configured to receive the PUSCH, where the PUSCH is sent by the terminal according to the SRS resource set and / or the SRS resource; The PUSCH is associated with a first SRS resource and a second SRS resource; and the first SRS resource and the second SRS resource are associated with different SRS resource sets.

31. A terminal, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the scheduling and transmission method of the PUSCH as described in any one of claims 1 to 26 is implemented.

32. A network side device, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein when the program or instruction is executed by the processor, the scheduling transmission method of the PUSCH as described in claim 27 or 28 is implemented.

33. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the scheduling transmission method of the PUSCH as described in any one of claims 1 to 26, or implements the scheduling transmission method of the PUSCH as described in claim 27 or 28.

Images