Communication method, terminal device, and network device

Abstract

The embodiments of the present disclosure relate to a method, an apparatus, and a computer-readable storage medium for communication. The method includes: receiving a DCI for scheduling a Physical Uplink Shared Channel (PUSCH) transmission from a network device in a terminal device, the DCI including a first field indicating a first number of layers for the PUSCH transmission and a second field indicating a second number of layers for the PUSCH transmission; determining a power for the PUSCH transmission based on the first number and the second number; and transmitting the PUSCH transmission to the network device based on the DCI, the total number of layers for the PUSCH transmission being determined based on the sum of the first number and the second number. Thus, the number of layers and the power for the PUSCH transmission can be determined.

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to communication methods, apparatus, and computer storage media. [Background technology]

[0002] Multiple input multiple output (MIMO) technology is widely used in conventional wireless communication systems in which a large number of antenna elements are used by network equipment to communicate with terminal devices. To improve the reliability and robustness of communications between network equipment and terminal devices, multi-transmit / receive point (multi-TRP) (and multi-panel reception) technology has recently been proposed and discussed. Generally speaking, downlink control information (DCI) can be used by network equipment to indicate scheduling information to terminal devices. Several proposals for DCI to enable multi-TRP and / or multi-panel reception have been discussed.

[0003] Recently, there has been discussion about strengthening support for the introduction of multi-TRP. For example, it has been proposed to use multi-TRP and / or multi-panel based on the Release 16 reliability characteristics to identify and specify characteristics that improve the reliability and robustness of physical channels other than the physical downlink shared channel (PDSH), such as the physical downlink control channel (PDCCH), the physical uplink shared channel (PUSCH), and / or the physical uplink control channel (PUCCH). To improve the reliability and robustness of the PUSCH, a single or identical DCI may be used to schedule PUSCH transmissions based on multi-TRP and / or multi-panel. It has been agreed that the maximum number of sounding reference signal (SRS) resource sets may be increased to two, and two SRS resource indicator fields corresponding to the two SRS resource sets may be introduced in the DCI for scheduling PUSCH transmissions. Furthermore, two transmit precoding matrix indicator (TPMI) fields may be introduced in the DCI for scheduling PUSCH transmissions. PUSCH transmission based on spatial domain multiplexing (SDM) or frequency domain multiplexing (FDM) in the case of multi-TRP transmission has also been proposed. Therefore, it is desired to propose a solution to support PUSCH transmission based on SDM or FDM in the case of multi-TRP. Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, the exemplary embodiments of the present disclosure provide a communication method, apparatus, and computer storage medium. [Means for solving the problem]

[0005] In a first aspect, a method of communication is provided, the method including: receiving, in a terminal device, DCI for scheduling a Physical Uplink Shared Channel (PUSCH) transmission from a network device, the DCI including a first field indicating a first number of layers for the PUSCH transmission and a second field indicating a second number of layers for the PUSCH transmission, determining power for the PUSCH transmission based on the first number and the second number, and transmitting the PUSCH transmission to the network device based on the DCI, wherein a total number of layers for the PUSCH transmission is determined based on a sum of the first number and the second number.

[0006] In a second aspect, a method of communication is provided, the method including: transmitting, in a network device, DCI for scheduling Physical Uplink Shared Channel (PUSCH) transmission to a terminal device, the DCI including a first field indicating a first number of layers for the PUSCH transmission and a second field indicating a second number of layers for the PUSCH transmission; and receiving, from the terminal device, the PUSCH transmission based on the DCI, wherein a total number of layers for the PUSCH transmission is determined based on a sum of the first number and the second number.

[0007] In a third aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the first aspect of the present disclosure.

[0008] In a fourth aspect, there is provided a network device, the network device comprising circuitry configured to perform a method according to the second aspect of the present disclosure.

[0009] In a fifth aspect, there is provided a terminal device, the terminal device comprising circuitry configured to perform the method according to the third aspect of the present disclosure.

[0010] In a sixth aspect, there is provided a network device, the network device comprising circuitry configured to perform a method according to the fourth aspect of the present disclosure.

[0011] In a seventh aspect, there is provided a computer program product comprising machine-executable instructions that, when executed, cause a machine to perform a method according to any one of the first to fourth aspects of the present disclosure.

[0012] In an eighth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed by at least one processor, cause the at least one processor to perform a method according to any one of the first to fourth aspects of the present disclosure.

[0013] It should be understood that this Summary of the Invention is not intended to identify key or essential features of the embodiments of the present disclosure, nor to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent from the following description. [Brief explanation of the drawings]

[0014] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description of several embodiments of the present disclosure in the accompanying drawings.

[0015] [Figure 1A] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented. [Figure 1B] FIG. 1 illustrates an exemplary communication network in which embodiments of the present disclosure may be implemented.

[0016] [Figure 2] FIG. 2 illustrates a signaling flow for communication in accordance with some exemplary embodiments of the present disclosure.

[0017] [Figure 3] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0018] [Figure 4] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0019] [Figure 5] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0020] [Figure 6A] FIG. 1 illustrates an example embodiment of the present disclosure. [Figure 6B] FIG. 1 illustrates an example embodiment of the present disclosure. [Figure 6C] FIG. 1 illustrates an example embodiment of the present disclosure.

[0021] [Figure 7] FIG. 1 illustrates an example of an embodiment of the present disclosure.

[0022] [Figure 8] 1 is a flowchart illustrating an exemplary method performed by a terminal device, according to some embodiments of the present disclosure.

[0023] [Figure 9] 4 is a flowchart illustrating an exemplary method performed by a network device, according to some embodiments of the present disclosure.

[0024] [Figure 10] 1 is a flowchart illustrating an exemplary method performed by a terminal device, according to some embodiments of the present disclosure.

[0025] [Figure 11] 4 is a flowchart illustrating an exemplary method performed by a network device, according to some embodiments of the present disclosure.

[0026] [Figure 12] FIG. 1 is a schematic block diagram of an apparatus suitable for implementing embodiments of the present disclosure.

[0027] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0028] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are provided for illustrative purposes only to aid those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various ways different from those described below.

[0029] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0030] The terminology used herein is used only for the purpose of describing particular embodiments and is not intended to limit example embodiments. As used herein, the singular forms "a," "an," and "said" include the plural forms unless the context clearly indicates otherwise. It should be further understood that, as used herein, the terms "comprise," "include," "have," "comprise," "comprises," and / or "have" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. The term "based on" should be understood as "based at least in part on."

[0031] While the terms "first," "second," and the like may be used herein to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be termed a second element, and similarly, a second element may be termed a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0032] As used herein, the term "determining" (and grammatical variations thereof) may include, but is not limited to, calculating, computing, processing, deriving, measuring, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, etc. "Determining" may also include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), obtaining, etc. Furthermore, "determining" may also include resolving, selecting, choosing, establishing, etc.

[0033] In some instances, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to illustrate that choices may be made from among many functional alternatives used, and that such choices are not necessarily better, smaller, higher, or otherwise more preferred than other choices.

[0034] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but do not necessarily mean that each embodiment includes that particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0035] As used herein, the term "circuitry" may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry and software / firmware. As yet another example, a circuit may be any portion of a hardware processor with software, including a digital signal processor, software, and one or more memories, that cooperate to cause a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or portion thereof, that requires software / firmware for operation, although the software may not be present if not necessary for operation. As used herein, the term "circuitry" also includes an implementation of a hardware circuit or one or more processors only, or a hardware circuit or portion of one or more processors and its / their accompanying software and / or firmware.

[0036] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT), etc. Furthermore, communications between terminal devices and network devices in a communication network may be implemented according to any suitable generation of communication protocols, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and / or any other protocols currently known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. Given the rapid development of communications, there will naturally be future types of communication technologies and systems in which the present disclosure can be embodied. This should not be considered to limit the scope of the present disclosure to only the aforementioned systems.

[0037] As used herein, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives service from it. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a femto, a pico, or other low-power node.

[0038] The term "terminal" refers to any end device that may be capable of wireless communication. By way of example and not limitation, a terminal may be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station (Portable Subscriber Station), mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, imaging terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronic devices, devices operating in commercial and / or industrial wireless networks, etc. In the following description, the terms “terminal device,” “communications device,” “terminal,” “user equipment,” and “UE” may be used interchangeably.

[0039] As used herein, the term "TRP" refers to an antenna array (having one or more antenna elements) available to network devices located at a particular geographic location. Although some embodiments of the present disclosure have been described with reference to multi-TRPs as examples, these embodiments are for illustrative purposes only and are intended to assist those skilled in the art in understanding and practicing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the contents of the present disclosure described herein can be implemented in various ways different from those described below.

[0040] Generally speaking, one TRP typically corresponds to one SRS resource set. As used herein, the term "single-TRP" means that a single SRS resource set is used to perform associated transmissions (e.g., PUSCH transmissions), and the term "multiple-TRP" means that multiple SRS resource sets are used to perform associated transmissions (e.g., PUSCH transmissions).

[0041] Hereinafter, the terms "PUSCH transmission," "uplink transmission," "PUSCH repetition," "PUSCH occasion," and "PUSCH reception" may be used interchangeably. The terms "DCI" and "DCI format" may be used interchangeably. The terms "transmission," "transmission occasion," and "repetition" may be used interchangeably. The terms "precoder," "precoding," "precoding matrix," "beam," "spatial relationship information," "spatial relationship info," "TPMI," "precoding information," "precoding information and layer number," "precoding matrix indicator (PMI)," "precoding matrix indicator," "transmit precoding matrix indication," "precoding matrix indication," "TCI state," "transmission configuration indicator," "quasi-co-location (QCL)," "quasi-co-location," "QCL parameters," and "spatial relationship" may be used interchangeably. The terms "antenna port," "port," and "DMRS port" may be used interchangeably.

[0042] As mentioned above, multi-TRP (and multi-panel reception) technology has recently been proposed and discussed to improve the reliability and robustness of communications between network devices and terminal devices. Specifically, to enhance support for multi-TRP deployments, Identifying and specifying features to improve the reliability and robustness of physical channels (e.g., PDCCH, PUSCH, and / or PUCCH other than PDSCH) using the multi-TRP and / or multi-panel with Release 16 reliability features as a baseline; and Identifying and specifying functionality to enable inter-cell multi-TRP operation; Several agreements were reached, including that simultaneous multi-TRP transmission with multi-panel reception should be evaluated and enhancements provided for as needed.

[0043] Therefore, channels other than the PDSCH can benefit from multi-TRP transmission (and multi-panel reception).

[0044] In conventional solutions, to improve the reliability and robustness of the PUSCH, PUSCH transmissions may be scheduled based on multiple TRPs and / or multiple panels using a single or identical DCI.

[0045] Furthermore, as mentioned above, it has recently been proposed that dynamic switching between multi-TRP and / or multi-panel and single-TRP should be supported. It is therefore desirable to propose a solution for supporting dynamic switching between single-TRP and multi-TRP transmissions without introducing significant overhead.

[0046] According to some example embodiments of the present disclosure, a communication solution is provided. In the solution, a terminal device receives DCI for scheduling at least one PUSCH transmission from a network device. The DCI includes a first field indicating that the at least one PUSCH transmission is transmitted based on an SRS resource set from a plurality of SRS resource sets or based on the plurality of SRS resource sets, and a second field indicating an index of a single SRS resource set for transmitting the at least one PUSCH transmission. Furthermore, the terminal device transmits the at least one PUSCH transmission to the network device based on the DCI. In this way, when supporting dynamic switching between single-TRP transmission and multi-TRP transmission, newly introduced overhead can be minimized.

[0047] 1A illustrates an exemplary communication network 100 in which embodiments of the present disclosure can be implemented. Communication network 100 includes a network device 110 and a terminal device 120 served by network device 110. Furthermore, the service area provided by network device 110 is referred to as a serving cell 102. Network 100 may provide one or more serving cells 102 for serving terminal device 120. Terminal device 120 can communicate with network device 110 via one or more physical communication channels or links.

[0048] In communication network 100, the link from terminal device 120 to network device 110 is referred to as the uplink (UL), and the link from network device 110 to terminal device 120 is referred to as the downlink (DL). In the UL, terminal device 120 is the TX device (or transmitter) and network device 110 is the RX device (or receiver). In the DL, network device 110 is the transmit (TX) device (or transmitter) and terminal device 120 is the receive (RX) device (or receiver).

[0049] 1A, the network device 110 may schedule an UL transmission (e.g., a PUSCH transmission) as a DCI. Exemplary messages used to schedule a PUSCH transmission are discussed below along with the DCI. It should be understood that radio resource control (RRC) messages / signaling and medium access control (MAC) control element (CE) messages / signaling may also be used to schedule a PUSCH transmission.

[0050] Communications in communication network 100 may conform to any suitable standard, including, but not limited to, Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM). Furthermore, communications may be performed in accordance with any currently known or future-developed generation of communication protocols. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, and fifth-generation (5G) communication protocols.

[0051] It should be understood that the number of network devices, terminal devices, and / or serving cells is for illustrative purposes only and no limitation to the present disclosure is to be implied. Communications network 100 may include any appropriate number of network devices, terminal devices, and / or serving cells suitable for implementing embodiments of the present disclosure. It should also be understood that in some examples, communications network 100 may include only homogeneous network deployments or only heterogeneous network deployments.

[0052] Furthermore, to support multiple TRPs and / or multiple panels, the network device 110 may include one or more TRPs. For example, the network device 110 may be coupled to multiple TRPs in different geographic locations to achieve better coverage. One or more TRPs of the multiple TRPs may be included in the same serving cell or different serving cells. It should be understood that a TRP may be a panel, and a panel may refer to an antenna array (having one or more antenna elements).

[0053] In one embodiment, the terminal device 120 may be connected to a first network device (e.g., a network) and a second network device (not shown in FIG. 1A). One of the first network device and the second network device may be in a master node and the other may be in a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device may be an eNB, and the second RAT device may be a gNB. Information regarding different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device 120. In one embodiment, the first information may be transmitted from the first network device to the terminal device 120, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device 120. In one embodiment, information regarding the settings of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information regarding the resetting of the terminal device 120 set by the second network device may be transmitted from the second network device directly or via the first network device to the terminal device 120. This information may be transmitted via any one of RRC signaling, MAC CE, or DCI.

[0054] FIG. 1B shows an exemplary scenario of the communication network 100 shown in FIG. 1A. As shown in FIG. 1B, the network device 110 may communicate with the terminal device 120 via the TRPs 130-1 and 130-2 (collectively referred to as TRP 220). In the following text, the TRP 130-1 may be referred to as the first TRP, and the TRP 130-2 may be referred to as the second TRP. The first TRP 130-1 and the second TRP 130-2 may be included in the same serving cell provided by the network device 110 (e.g., the serving cell 102 shown in FIG. 1A) or different serving cells.

[0055] It should be understood that the number of network devices, terminal devices, and / or TRPs is for illustrative purposes only and no limitation to the present disclosure is to be implied. Communications network 100 may include any suitable number of network devices, terminal devices, and / or TRPs suitable for implementing embodiments of the present disclosure.

[0056] Although some embodiments of the present disclosure are described below with reference to two TRPs, a first TRP 130-1 and a second TRP 130-2, in the same serving cell provided by the network device 110, these embodiments are for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the contents of the present disclosure described herein can be implemented in various ways different from those described below.

[0057] In some exemplary embodiments, there may be M TRPs serving terminal device 120, where M is a positive integer. For example, 1≦M≦4. For another example, M=2. In some exemplary embodiments, for each of the M TRPs, terminal device 120 may be configured with at least one of a control resource set (CORESET), an SRS resource set, a set of spatial relationship information, a transmission configuration indicator (TCI) state, and a QCL parameter set. That is, terminal device 120 may be configured with M CORESETs, M SRS resource sets, M sets of spatial relationship information, M TCI states, and / or M QCL parameters, each associated with the M TRPs. One of the M TRPs may be represented by a corresponding one of the M CORESETs, M SRS resource sets, M sets of spatial relationship information, M TCI states, and / or M QCL parameter sets.

[0058] In some exemplary embodiments, the SRS resource set is configured for codebook-based uplink transmission. In some exemplary embodiments, the SRS resource set is configured for non-codebook-based uplink transmission. In the example shown in FIG. 1B , M=2. In this case, the first TRP 130-1 may be associated with a first CORESET, a first SRS resource set, first spatial relationship information, a first TCI state, and / or a first set of QCL parameters, and the second TRP 130-2 may be associated with a second CORESET, a second SRS resource set, second spatial relationship information, a second TCI state, and / or a second set of QCL parameters.

[0059] 1B, the first TRP 130-1 and the second TRP 130-2 correspond to different SRS resource sets. In the following text, the SRS resource set corresponding to the first TRP 130-1 may be referred to as the first SRS resource set, and the SRS resource set corresponding to the second TRP 130-2 may be referred to as the second SRS resource set.

[0060] Furthermore, the DCI for scheduling the PUSCH of the terminal device 120 may include multiple SRS resource indicator (SRI) fields corresponding to the multiple SRS resource sets. In the example of FIG. 1B, the DCI may include two SRI fields. In the following text, the SRI field corresponding to the first SRS resource set may be referred to as the first SRI field, and the SRI field corresponding to the second SRS resource set may be referred to as the second SRI field.

[0061] Furthermore, in the example of FIG. 1B , codebook-based PUSCH transmission and / or non-codebook-based PUSCH transmission is supported. For a multi-TRP PUSCH repetition scheme based on a single DCI, non-codebook-based PUSCH transmission may be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or semi-statically configured parameters, where the DCI or parameters may include first and second SRI fields corresponding to first and second SRS resource sets, respectively. For example, for non-codebook-based PUSCH transmission, the first SRI field may be based on a conventional structure (e.g., the structure specified in Release 15 / 16 of the 3rd Generation Partnership Project (3GPP)) and may be used to indicate the number of SRS resources, the number of transmission layers (also referred to as "transmission rank"), etc. The second SRI field may indicate only the number of SRS resources, and the number of transmission layers is assumed to be the same as the first SRI field. For another example, for a non-codebook-based PUSCH transmission, the first SRI field and the second SRI field may be based on a conventional structure (e.g., a structure specified in Release 15 / 16 of the 3rd Generation Partnership Project (3GPP)) and may be used to indicate the number of SRS resources, the number of transmission layers (also referred to as "transmission rank"), etc.

[0062] For example, for a non-codebook-based multi-TRP PUSCH transmission, the first SRI field is used to determine entries for the second SRI field that include only SRI combinations corresponding to the indicated rank (i.e., layer number) of the first SRI field. The number of bits N2 for the second SRI field is determined by the maximum number of codepoints per rank among all ranks associated with the first SRI field. For each rank x, the first Kx codepoints are mapped to the Kx SRIs of rank x associated with the first SRI field, and the remaining Kx codepoints are mapped to the Kx SRIs of rank x associated with the first SRI field. The JPEG0007827133000001.jpg14168 codepoint is reserved. For example, if one SRS resource is in an SRS resource set for non-codebook-based transmission, N2 may be 1 or 0. For example, the SRS resource set may be the second SRS resource set.

[0063] In some exemplary embodiments, when multiple SRS resources are configured, terminal device 120 may determine its PUSCH precoder and transmission rank based on the SRI, where the SRI is given by the SRS resource indicator in DCI format 0_1 ​​and DCI format 0_2, or the SRI is given by a higher layer parameter, such as srs-ResourceIndicator. The SRS-ResourceSet(s) applicable to PUSCHs scheduled by DCI format 0_1 ​​and DCI format 0_2 are defined by entries of the higher layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 in SRS-config, respectively. Terminal device 120 may use one or more SRS resources for SRS transmission, where the maximum number of SRS resources in an SRS resource set and the maximum number of SRS resources that can be configured in terminal device 120 for simultaneous transmission within the same symbol depend on the capabilities of terminal device 120. Simultaneously transmitted SRS resources occupy the same resource block (RB). For each SRS resource, only one SRS port is configurable. One or two SRS resource sets may be configured with the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook". The maximum number of SRS resources in an SRS resource set configurable for non-codebook-based uplink transmissions may be four. The SRI indicated in slot n may be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission precedes the PDCCH carrying the SRI.

[0064] For an M-TRP PUSCH repetition scheme based on a single DCI, codebook-based PUSCH transmission may be scheduled by DCI format 0_0, DCI format 0_1, DCI format 0_2, or semi-statically configured parameters. The DCI or parameters may include first and second SRI fields corresponding to the first and second SRS resource sets, respectively. Furthermore, the DCI may include two TPMI fields corresponding to the first TRP 130-1 and the second TRP 130-2, respectively. The TPMI applies to layers {0...v-1} and is used to indicate the precoder corresponding to the SRS resource selected by the SRI when multiple SRS resources are configured. Alternatively, when a single SRS resource is configured in one SRS resource set, the TPMI applies to layers {0...v-1} and is used to indicate the precoder corresponding to the SRS resource. In some exemplary embodiments, the first TPMI field may include a TPMI index and a layer number, and the second TPMI field may include only the second TPMI index. The same layer number indicated in the first TPMI field applies to the second TPMI field. In some exemplary embodiments, the first TPMI field may include a first TPMI index and a first layer number for the PUSCH transmission, and the second TPMI field includes a second TPMI index and a second layer number for the PUSCH transmission.

[0065] For example, for a codebook-based (CB) multi-TRP PUSCH transmission, the first TPMI field is used to determine the entries of the second TPMI field, and the second TPMI field includes only the TPMI corresponding to the indicated rank (layer number) of the first TPMI field. The bit width of the second TPMI field is determined by the maximum number of TPMIs per rank among all ranks associated with the first TPMI field. For each rank y, the first K TPMIs of the second TPMI field are used to determine the entries of the second TPMI field. yK code points of rank y are associated with the first TPMI field y are mapped to TPMIs in descending order of code point index, and the remaining JPEG0007827133000002.jpg14168 code points are reserved. For example, if the number of ports for SRS resources in an SRS resource set for codebook-based transmission is 1, M2 may be 1 or 0. For example, the SRS resource set may be the second SRS resource set.

[0066] In some exemplary embodiments, terminal device 120 may determine its PUSCH transmission precoder based on the SRI, TPMI, and transmission rank, where the SRI, TPMI, and transmission rank are given by the DCI fields, precoding information, and layer number of the SRS resource indicator in DCI formats 0_1 and 0_2, or by higher layer parameters, such as srs-ResourceIndicator and precodingAndNumberOfLayers. The SRS-ResourceSet(s) applicable to PUSCHs scheduled by DCI formats 0_1 and 0_2 are defined by entries of the higher layer parameters srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 in SRS-config, respectively. The TPMI applies to layers {0...v-1} and is used to indicate the precoder corresponding to the SRS resource selected by the SRI when multiple SRS resources are configured. Alternatively, if a single SRS resource is configured, TPMI is used to indicate the precoder that applies to layers {0...v-1} and corresponds to the SRS resource. The transmit precoder is selected from an uplink codebook with a number of antenna ports equal to the higher layer parameter nrofSRS-Ports in SRS-config. If terminal device 120 is configured with the higher layer parameter txConfig set to "codebook," terminal device 120 may be configured with at least one SRS resource. The SRI indicated in slot n may be associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource precedes the PDCCH carrying the SRI.

[0067] Furthermore, in some exemplary embodiments, the DCI may include multiple transmission power control (TPC) fields. In the particular example of FIG. 1B, these multiple TPC fields may include a first TPC field and a second TPC field.

[0068] In some embodiments, network device 110 may configure terminal device 120 with multiple SRS resource sets (e.g., for codebook-based uplink / PUSCH transmission, these multiple SRS resource sets may be one or two. For another example, for non-codebook-based uplink / PUSCH transmission, these multiple SRS resource sets may be one or two) (e.g., a first SRS resource set is applied for PUSCH transmission via the first TRP 130-1, and a second SRS resource set is applied for PUSCH transmission via the second TRP 130-2). In some exemplary embodiments, network device 110 may configure terminal device 120 with codebook-based uplink / PUSCH transmission, and network device 110 may configure terminal device 120 with one or two SRS resource sets. For example, the one or two SRS resource sets are applied for codebook-based uplink / PUSCH transmission. In some exemplary embodiments, network device 110 may configure terminal device 120 for non-codebook-based uplink / PUSCH transmission, and network device 110 may configure terminal device 120 with one or two SRS resource sets. For example, the one or two SRS resource sets are applied for non-codebook-based uplink / PUSCH transmission. In some exemplary embodiments, network device 110 may transmit a DCI to terminal device 120 to schedule at least one PUSCH transmission. In some exemplary embodiments, the DCI may include multiple SRI fields corresponding to multiple SRS resource sets. For example, the multiple SRI fields may include a first SRI field and a second SRI field. Additionally or additionally, the DCI may include multiple TPMI fields (e.g., a first TPMI field and a second TPMI field) for codebook uplink / PUSCH transmission. Additionally or additionally, the DCI may include multiple TPC fields (e.g., a first TPC field and a second TPC field).

[0069] Furthermore, multiple TRPs and / or dynamic switching between multiple panels and a single TRP may be supported. More specifically, if a single TRP transmission with a first TRP 130-1 is dynamically indicated by the DCI, a first SRS resource set may be applied for the PUSCH transmission. If a single TRP transmission with a second TRP 130-2 is dynamically indicated by the DCI, a second SRS resource set may be applied for the PUSCH transmission. Alternatively, if a multi-TRP transmission is dynamically indicated, both the first and second SRS resource sets may be applied for the PUSCH transmission.

[0070] Furthermore, this multi-TRP transmission may be associated with an order of the TRPs (i.e., an order of the multiple SRS resource sets applied for a PUSCH transmission). One example of this order is for terminal device 120 to apply a first SRS resource set for the first PUSCH transmission / at least one repetition of a PUSCH transmission. Another example of this order is for terminal device 120 to apply a second SRS resource set for the first PUSCH transmission / at least one repetition of a PUSCH transmission.

[0071] In some exemplary embodiments, terminal device 120 may be configured / indicated / scheduled to have a set of PUSCH transmissions or a total number of layers for PUSCH transmissions. For example, the set of PUSCH transmissions may include a first subset of PUSCH transmissions and a second subset of PUSCH transmissions. For another example, the total number of layers for PUSCH transmissions may include a first number of layers for PUSCH transmissions and a second number of layers for PUSCH transmissions. In some exemplary embodiments, a precoder for the first subset of PUSCH transmissions / repetitions or the total number of layers for PUSCH transmissions may be determined based on at least one of a first SRI indicated by a first SRI field, a first TPMI / PMI field, and a transmission rank. A precoder for the second subset of PUSCH transmissions / repetitions or a second number of layers for PUSCH transmissions may be determined based on at least one of a second SRI indicated by a second SRI field, a second TPMI / PMI field, and a transmission rank.

[0072] In some exemplary embodiments, terminal device 120 may be configured / indicated / scheduled to have a total number of layers for PUSCH transmission. The total number of layers for PUSCH transmission may include a first number of layers and a second number of layers. In some exemplary embodiments, a precoder for the first number of layers for PUSCH transmission may be determined based on at least one of a first SRI indicated by a first SRI field, a first TPMI / PMI field, and a transmission rank. A precoder for the second number of layers for PUSCH transmission may be determined based on at least one of a second SRI indicated by a second SRI field, a second TPMI / PMI field, and a transmission rank. For example, the total number of layers for PUSCH transmission is determined based on the sum of the first number and the second number.

[0073] In some exemplary embodiments, at least one SRS resource in a first SRS resource set may be applied to or associated with a first subset of PUSCH transmissions or a first layer number for PUSCH transmissions, and at least one SRS resource in a second SRS resource set may be applied to or associated with a second subset of PUSCH transmissions or a second layer number for PUSCH transmissions. In some exemplary embodiments, the precoder for the first subset of PUSCH transmissions or the first layer number for PUSCH transmissions or the first subset of PUSCH transmissions or the first layer number for PUSCH transmissions may be based on or corresponds to at least one SRS resource in the first SRS resource set, and the precoder for the second subset of PUSCH transmissions or the second layer number for PUSCH transmissions or the second subset of PUSCH transmissions or the second layer number for PUSCH transmissions may be based on or corresponds to at least one SRS resource in the second SRS resource set.

[0074] In some example embodiments, the first of the PUSCH transmissions or the first of the first subset of PUSCH transmissions may start and / or end earlier in the time domain than the first of the PUSCH transmissions or the first of the second subset of PUSCH transmissions.

[0075] In some exemplary embodiments, terminal device 120 may be configured / indicated with a configuration / indication regarding an association / application between an SRI field and a subset of PUSCH transmissions (or a precoder for the subset of PUSCH transmissions) or a subset of layers for PUSCH transmissions (or a precoder for the subset of layers for PUSCH transmissions). In some exemplary embodiments, terminal device 120 may be configured / indicated with a first configuration / indication that a precoder for a first subset of PUSCH transmissions / repetitions or a precoder for a first number of layers for PUSCH transmissions may be determined based on at least one of a first SRI indicated by a first SRI field, a first TPMI / PMI field, and a transmission rank, and a precoder for a second subset of PUSCH transmissions / repetitions or a precoder for a second number of layers for PUSCH transmissions may be determined based on at least one of a second SRI indicated by a second SRI field, a second TPMI / PMI field, and a transmission rank. The terminal device 120 may be configured / indicated to have a second configuration / instruction that a precoder for a second subset for PUSCH transmission / repetition or a precoder for a second number of layers for PUSCH transmission may be determined based on at least one of a first SRI indicated by a first SRI field, a first TPMI / PMI field, and a transmission rank, and that a precoder for a first subset for PUSCH transmission / repetition or a precoder for a first number of layers for PUSCH transmission may be determined based on at least one of a second SRI indicated by a second SRI field, a second TPMI / PMI field, and a transmission rank.

[0076] In some exemplary embodiments, terminal device 120 may be configured / indicated with a configuration / indication regarding the association / application between an SRS resource set and a subset of PUSCH transmissions (or a precoder for a subset of PUSCH transmissions) or a subset of layers for PUSCH transmissions. In some exemplary embodiments, terminal device 120 may be configured / indicated with a first configuration / indication that at least one SRS resource in a first SRS resource set may be applied to or associated with a first subset of PUSCH transmissions or a first layer number for PUSCH transmissions, and at least one SRS resource in a second SRS resource set may be applied to or associated with a second subset of PUSCH transmissions or a second layer number for PUSCH transmissions. The terminal device 120 may be configured / indicated to have a second configuration / indication that at least one SRS resource in the second SRS resource set may be applied to or associated with a first subset of PUSCH transmissions or a first layer number for PUSCH transmissions, and at least one SRS resource in the first SRS resource set may be applied to or associated with a second subset of PUSCH transmissions or a second layer number for PUSCH transmissions. In some exemplary embodiments, terminal device 120 may be configured / indicated to have a first configuration / indication that a precoder for a first subset of PUSCH transmissions or a precoder for a first number of layers for PUSCH transmissions may be based on or correspond to at least one SRS resource in a first SRS resource set, and a precoder for a second subset of PUSCH transmissions or a precoder for a second number of layers for PUSCH transmissions may be based on or correspond to at least one SRS resource in a second SRS resource set.The terminal device 120 may be configured / indicated to have a second configuration / indication that a first subset of PUSCH transmissions or a first number of layers for PUSCH transmissions or a precoder for the first subset of PUSCH transmissions or a precoder for the first number of layers for PUSCH transmissions may be based on or correspond to at least one SRS resource in a second SRS resource set, and that a second subset of PUSCH transmissions or a second number of layers for PUSCH transmissions or a precoder for the second subset of PUSCH transmissions or a precoder for the second number of layers for PUSCH transmissions may be based on or correspond to at least one SRS resource in the first SRS resource set.

[0077] In some exemplary embodiments, the configuration / indication may be explicitly or implicitly configured / indicated via at least one of RRC, MAC CE, and DCI. In some exemplary embodiments, the first configuration / indication may be different from the second configuration / indication. For example, the configuration / indication may be explicitly transmitted via at least one of RRC, MAC CE, and DCI. For another example, the configuration / indication may be implicitly indicated by some parameters. For example, the parameters may include, but are not limited to, at least one of the following: an SRI indicated by an SRI field in the DCI; precoding information and layer number indicated in the DCI; antenna port indicated in the DCI; a DMRS configuration; a DMRS port index; a first DMRS port index; and a code domain multiplexing (CDM) group index.

[0078] 2 is an example signaling diagram according to some embodiments of the present disclosure, in which a signaling flow 200 for communication according to some example embodiments of the present disclosure is shown.

[0079] Reference is now made to Figure 2. For illustrative purposes, a signaling flow 200 will be described with reference to Figures 1A and 1B. The signaling flow 200 may involve a network device 110, a terminal device 120, a first TRP 130-1, and a second TRP 130-2.

[0080] 2, network device 110 transmits 210 a DCI to terminal device 120 to schedule at least one PUSCH transmission. The DCI includes a first field and a second field indicating that the at least one PUSCH transmission is transmitted based on a single SRS resource set (e.g., a first SRS resource set or a second SRS resource set) or multiple SRS resource sets (e.g., both the first SRS resource set and the second SRS resource set). For example, in the following text, a PUSCH transmission transmitted based on a single SRS resource set is referred to as a single TRP, and a PUSCH transmission transmitted based on multiple SRS resource sets is referred to as a multi-TRP.

[0081] In some embodiments, the first field indicates a first number of layers for PUSCH transmission (e.g., based on a first SRS resource set), and the second field indicates a second number of layers for PUSCH transmission (e.g., based on a second SRS resource set). For example, the total number of layers for PUSCH transmission is determined based on the sum of the first number and the second number.

[0082] In some exemplary embodiments, network device 110 may configure terminal device 120 for codebook-based uplink / PUSCH transmission, and network device 110 may configure terminal device 120 with two SRS resource sets (e.g., a first SRS resource set and a second SRS resource set) for the codebook-based uplink / PUSCH transmission.

[0083] In some exemplary embodiments, network device 110 may configure terminal device 120 for non-codebook-based uplink / PUSCH transmission, and network device 110 may configure terminal device 120 with two SRS resource sets (e.g., a third SRS resource set and a fourth SRS resource set) for the non-codebook-based uplink / PUSCH transmission.

[0084] In some embodiments, the network device 110 may configure the terminal device 120 with a transmission scheme for uplink / PUSCH transmission, for example, the transmission scheme may be at least one of spatial domain multiplexing (SDM), time domain multiplexing (TDM), and frequency domain multiplexing (FDM).

[0085] In some embodiments, terminal device 120 may receive downlink control information (DCI) from network device 110, where the DCI may schedule a PUSCH transmission and the DCI may include a first field and a second field. For example, the first field may indicate a first number of layers for the PUSCH transmission, and the second field may indicate a second number of layers for the PUSCH transmission. In some embodiments, terminal device 120 may transmit a PUSCH transmission to network device 110 based on the DCI, and the total number of layers for the PUSCH transmission may be determined based on the sum of the first number and the second number.

[0086] FIG. 3 is a diagram illustrating an example of an embodiment of the present disclosure.

[0087] As shown in FIG. 3, the terminal device 120 may transmit a PUSCH transmission to the network device 110 (e.g., to a first TRP and a second TRP), where the PUSCH transmission includes a first layer number and a second layer number.

[0088] In some embodiments, the first field may include at least one of a first SRS resource indicator (SRI) field, a first precoding information and layer number field, a first transmit precoding matrix indicator (TPMI) field, and a first antenna port field. In some embodiments, the second field may include at least one of a second SRI field, a second precoding information and layer number field, a second TPMI field, a first antenna port field, and a third field. In some embodiments, the third field may indicate a value of the second layer number. For example, the third field may be 1 bit or 2 bits in the DCI. For example, the third field may indicate at least one of {1, 2}, {1, 2, 3, 4}, or {1, 2, 3, 4, 5, 6, 7, 8}.

[0089] In some embodiments, terminal device 120 may determine one or more parameters for a demodulation reference signal (DMRS) corresponding to a PUSCH transmission based on the first, second, and fourth fields in the DCI, where the one or more parameters include at least one of: a number of ports for the DMRS, a set of port indices for the DMRS, a first number of ports for the DMRS corresponding to the first layer number, a first number of ports for the DMRS associated with the first field, a first set of indices for the first number of ports for the DMRS corresponding to the first layer number, a first set of indices for the first number of ports for the DMRS associated with the first field, a second number of ports for the DMRS corresponding to the second layer number, a second number of ports for the DMRS associated with the second field, a second set of indices for the second number of ports for the DMRS corresponding to the second layer number, and a second set of indices for the second number of ports for the DMRS associated with the second field. For example, the fourth field may be an antenna port field.

[0090] In some embodiments, terminal device 120 may determine the total number of transmission schemes or layers for PUSCH transmission based on the value of the fourth field. In some embodiments, terminal device 120 may determine the transmission scheme to be spatial domain multiplexing (SDM) based on the first value of the fourth field. In some embodiments, terminal device 120 may determine the total number to be the sum of the first number and the second number based on the first value of the fourth field.

[0091] In some embodiments, terminal device 120 may determine that the transmission scheme is one of time domain multiplexing (TDM) and frequency domain multiplexing (FDM) based on the second value of the fourth field. For example, terminal device 120 may further determine that the transmission scheme is TDM or FDM based on a parameter from at least one of RRC, MAC CE, and DCI. For example, the parameter may indicate TDM and SDM, or FDM and SDM. In some embodiments, terminal device 120 may determine that the total number is one of a first number and a second number based on the second value of the fourth field. For example, the first number is equal to the second number. For another example, terminal device 120 may determine that the total number is the smaller or larger of the first number and the second number based on the second value of the fourth field.

[0092] In some embodiments, a first layer number for PUSCH transmission may be associated with a first SRS resource set, and a second layer number for PUSCH transmission may be associated with a second SRS resource set.

[0093] In some embodiments, based on a first value of the fourth field, a first layer number for PUSCH transmission may be associated with a first SRS resource set, and a second layer number for PUSCH transmission may be associated with a second SRS resource set. In some embodiments, based on a second value of the fourth field, a first layer number for PUSCH transmission may be associated with a second SRS resource set, and a second layer number for PUSCH transmission may be associated with the first SRS resource set. For example, the first value is different from the second value.

[0094] In some embodiments, terminal device 120 may determine power for a first number of layers for PUSCH transmission based on a first set of parameters and may determine power for a second number of layers for PUSCH transmission based on a second set of parameters. For example, the first set of parameters and / or the second set of parameters may be configured via at least one of RRC, MAC CE, and DCI from a network device.

[0095] In some embodiments, the terminal device 120 may determine the power for the first number of layers for PUSCH transmission based on a first coefficient and may determine the power for the second number of layers for PUSCH transmission based on a second coefficient. In some embodiments, the first coefficient may be determined based on at least one of the first number and the total number. For example, the first coefficient may be a ratio between the first number and the total number. For example, the first coefficient may be (first number) / (total number). In some embodiments, the second coefficient may be determined based on at least one of the second number and the total number. For example, the second coefficient may be a ratio between the second number and the total number. For example, the second coefficient may be (second number) / (total number).

[0096] In some embodiments, there may be two SRI and / or two TPMI fields in the DCI, and each of the two SRI and / or two TPMI fields indicates a rank value or number of layers for a PUSCH transmission, for example, in the case of SDM transmission.

[0097] In some embodiments, the values ​​of the first number and the second number may be restricted to at least one of {1,1}, {1,2}, {2,1}, {2,2}, {2,3}, {3,2}, {3,3}, {3,4}, {4,3}, and {4,4}. For example, the difference in value between the first number and the second number should be 1 or less. For example, |First number - Second number|≦1.

[0098] In some embodiments, the rank value is determined based on two SRS resource indicator fields when the upper layer parameter txConfig=nonCodebook, and is the sum of values ​​determined based on two precoding information and number of layers fields when the upper layer parameter txConfig=codebook and the PUSCH transmission scheme is configured as SDM (e.g., when the upper layer parameter PUSCH_scheme is configured as SDM); otherwise, the rank value is determined based on one of the two SRS resource indicator fields and one of the two precoding information and number of layers fields when the upper layer parameter txConfig=nonCodebook.

[0099] In some embodiments, the rank value for PUSCH transmission is determined based on two SRS resource indicator fields when the upper layer parameter txConfig=nonCodebook, and is the sum of values ​​determined based on two precoding information and number of layers fields when the upper layer parameter txConfig=codebook and the PUSCH transmission scheme is configured as SDM (e.g., when the upper layer parameter PUSCH_scheme is configured as SDM). In some embodiments, the rank value is determined based on one of the two SRS resource indicator fields when the upper layer parameter txConfig=nonCodebook, and based on one of the two precoding information and number of layers fields when the upper layer parameter txConfig=codebook and the PUSCH transmission scheme is not configured as SDM.

[0100] In some embodiments, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to a code domain multiplexing (CDM) group of a first antenna port indicated in the DCI (e.g., by the fourth field, or for another example, by an antenna port indication table), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to a code domain multiplexing (CDM) group of another CDM group indicated in the DCI (e.g., by the fourth field, or for another example, by an antenna port indication table). For example, a third field (e.g., a field indicating single-TRP or multi-TRP transmission) may be applied to indicate the association between the CDM group and / or DMRS port and the SRI field and / or TPMI field and / or SRS resource set.

[0101] In some embodiments, if the antenna ports or DMRS ports are denoted as {0,2}, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to the first CDM group (including antenna port 0 or DMRS port 0), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to the second CDM group (including antenna port 2 or DMRS port 2).

[0102] In some embodiments, if the antenna ports or DMRS ports are denoted as {1,3}, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to the first CDM group (including antenna port 1 or DMRS port 1), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to the second CDM group (including antenna port 3 or DMRS port 3).

[0103] In some embodiments, if antenna ports or DMRS ports are denoted as {0,1,2}, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to the first CDM group (including antenna port {0,1} or DMRS port {0,1}), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to the second CDM group (including antenna port 2 or DMRS port 2).

[0104] In some embodiments, if antenna ports or DMRS ports are indicated as {0,2,3}, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to the first CDM group (including antenna port {0} or DMRS port {0}), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to the second CDM group (including antenna port {2,3} or DMRS port {2,3}).

[0105] In some embodiments, if antenna ports or DMRS ports are indicated as {3,4,5}, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to the first CDM group (including antenna port {3} or DMRS port {3}), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to the second CDM group (including antenna port {4,5} or DMRS port {4,5}).

[0106] In some embodiments, when antenna ports or DMRS ports are indicated as {2,3,4} or {2,3,5}, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to the first CDM group (including antenna ports {2,3} or DMRS ports {2,3}), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to the second CDM group (including antenna ports {4} or {5}, or DMRS ports {4} or {5}).

[0107] In some embodiments, if antenna ports or DMRS ports are denoted as {0,1,2,3}, the first SRI field and / or the first TPMI field and / or the first SRS resource set may correspond to the first CDM group (including antenna port {0,1} or DMRS port {0,1}), and the second SRI field and / or the second TPMI field and / or the second SRS resource set may correspond to the second CDM group (including antenna port {2,3} or DMRS port {2,3}).

[0108] In some embodiments, the total number of layers may be indicated as 3, and a new antenna port indication table may be applied. For example, a first value of the antenna port field may indicate that the DMRS ports are {0, 1, 2}. For another example, a second value of the antenna port field may indicate that the DMRS ports are {0, 2, 3}. For another example, a first value of the antenna port field may indicate that the DMRS ports are {3, 4, 5}. For another example, a second value of the antenna port field may indicate that the DMRS ports are {2, 3, 4} or {2, 3, 5}. For example, the first number is set as 1 and the second number is set as 2. For another example, the first number is set as 2 and the second number is set as 1. Examples are shown in Table 1A and Table 1B. [Table 1A] [Table 1B]

[0109] In some embodiments, terminal device 120 may be configured with a transform precoder enabled, or may be configured with single carrier frequency division multiple access (SC-FDMA), or may be configured with discrete fourier transform spread orthogonal frequency division multiplexing (DFT-s-OFDM), and terminal device 120 may be configured with an SDM transmission scheme for PUSCH transmission. In some embodiments, the total number of layers or rank value for PUSCH transmission may be 2. For example, the first number of layers may be 1, and the second number of layers may be 1. In some embodiments, the index of the second DMRS port (or antenna port) for the second layer number, or associated with the second SRI field or the second TPMI field, or the second SRS resource set, may be determined based on the indicated index of the first DMRS port (or antenna port) for the first layer number, or associated with the first SRI field or the first TPMI field, or the first SRS resource set. For example, if the first DMRS port is indicated as 0, the second DMRS port may be 2. For another example, if the first DMRS port is indicated as 1, the second DMRS port may be 3. For another example, the index of the second DMRS port may be the same as the indicated index of the first DMRS port. For another example, if the first DMRS port is indicated as 0, the second DMRS port may be 0. For another example, if the first DMRS port is indicated as 1, the second DMRS port may be 1. For another example, if the first DMRS port is shown as 2, the second DMRS port may be 2. For another example, if the first DMRS port is shown as 3, the second DMRS port may be 3. An example is shown in Table 2. [Table 2]

[0110] In some embodiments, a new antenna port indication table may be applied. For example, a first value of the antenna port field may indicate that the DMRS port is {0,2}. For another example, a second value of the antenna port field may indicate that the DMRS port is {1,3}. An example is shown in Table 3. [Table 3]

[0111] In some embodiments, terminal device 120 may be configured to have an SDM transmission scheme for PUSCH transmission, and a new antenna port indication table may be applied. In some embodiments, the number of code points for the new antenna port indication table may be up to three (e.g., 1, 2, or 3), where no code point is defined as "reserved." In some embodiments, the number of bits for the new antenna port indication table may be up to two (e.g., 0, 1, or 2). In some embodiments, indication of antenna ports may not be required.

[0112] In some embodiments, the first number may be set as 1, the second number may be set as 1, and the DMRS / antenna ports for PUSCH transmission may be assumed as {0,2}. In some embodiments, the first number may be set as 1, the second number may be set as 2, and the DMRS / antenna ports for PUSCH transmission may be assumed as {0,1,2}. In some embodiments, the first number may be set as 2, the second number may be set as 1, and the DMRS / antenna ports for PUSCH transmission may be assumed as {0,1,2}. In some embodiments, the first number may be set as 2, the second number may be set as 2, and the DMRS / antenna ports for PUSCH transmission may be assumed as {0,1,2,3}. For example, a bit indicating the DMRS / antenna ports may not be required in the DCI.

[0113] In some embodiments, the first number and the second number may be set as {2,1} or {1,2}, respectively, and the DMRS / antenna port for PUSCH transmission may be set from at least one of {0,1,2} or {3,4,5}. An example of a DMRS / antenna port indication table is shown in Table 4. For example, the DMRS is set as Type 2. For example, the bit size of the antenna port indication table is 2. [Table 4]

[0114] In some embodiments, the first number may be set as 2, the second number may be set as 2, and the DMRS / antenna port for PUSCH transmission may be set from at least one of {0, 1, 2, 3}. Examples of the DMRS / antenna port indication table are shown in Table 5A and Table 5B. For example, the DMRS is set as Type 2. For example, the bit size of the antenna port indication table is 1. [Table 5A] [Table 5B]

[0115] In some embodiments, terminal device 120 may be configured to have an SDM transmission scheme for PUSCH transmission and may employ a new field (e.g., a third field) in the DCI to indicate the value of the second number or to indicate a rank value corresponding to the second SRI field and / or the second TPMI field and / or the second SRS resource set. In some embodiments, the number of bits for the new field may be 1 or 2. Examples are shown in Table 6A and Table 6B. [Table 6A] [Table 6B]

[0116] In some embodiments, the terminal device 120 may be configured to have an SDM transmission scheme for PUSCH transmission, and the value of the second number and the rank value corresponding to the second SRI field and / or the second TPMI field and / or the second SRS resource set may both be indicated together with the DMRS / antenna port.

[0117] In some embodiments, terminal device 120 may be configured to have two or more transmission schemes (e.g., SDM and TDM; for another example, SDM and FDM; for another example, SDM, TDM, and FDM). For example, via at least one of RRC and MAC CE. For example, the two or more transmission schemes may be based on multi-TRP transmission. In some embodiments, the first number and the second number may be set as 1 or 2. In some embodiments, dynamic switching between different transmission schemes may be based on an indicated value and / or an indicated codepoint in an antenna port field in the DCI. In some embodiments, the total number of layers for PUSCH transmission may be the sum of the first number and the second number (e.g., 2 or 4) based on at least one of: if a first value is indicated in the antenna port field; if the indicated DMRS port is {0, 2} or {0, 1, 2, 3}; and if the indicated value in the antenna port field belongs to a first subset. In some embodiments, the transmission scheme for the PUSCH transmission may be SDM based on at least one of the following: if a first value is indicated in the antenna port field, the indicated DMRS port is {0,2} or {0,1,2,3}, and the indicated value in the antenna port field belongs to a first subset. In some embodiments, the total number of layers for the PUSCH transmission may be the same as one of the first number and a second number (e.g., 1 or 2). For example, the first number is equal to the second number based on at least one of the following: if a second value is indicated in the antenna port field, the indicated DMRS port is not {0,2} or is not {0,1,2,3}, and the indicated value in the antenna port field belongs to a second subset. In some embodiments, the transmission scheme for the PUSCH transmission may be FDM or TDM based on at least one of the following: if a second value is indicated in the antenna port field, the indicated DMRS port is not {0,2} or is not {0,1,2,3}, and the indicated value in the antenna port field belongs to the second subset.

[0118] FIG. 4 is a diagram illustrating an example of an embodiment of the present disclosure.

[0119] 4, terminal device 120 may be configured to have a multi-TRP transmission scheme (e.g., at least one of SDM, FDM, and TDM), and terminal device 120 may be configured to have a first number (e.g., R1, where R1 is a positive integer. For example, R1 may be at least one of {1, 2, 3, 4}) and a second number (e.g., R2, where R2 is a positive integer. For example, R2 may be at least one of {1, 2, 3, 4}) for PUSCH transmission. For example, terminal device 120 may be configured to have a code point corresponding to a value indicated in an antenna port field in DCI. For example, if this code point corresponds to a first subset (e.g., if the code point corresponds to a DMRS port having R1+R2 ports and the DMRS port is in two CDM groups), terminal device 120 may determine that the transmission scheme for PUSCH transmission is SDM, or the rank value or the total number of layers for PUSCH transmission is determined as R1+R2; otherwise (e.g., if this code point corresponds to a code point of a second subset), terminal device 120 may determine that the transmission scheme for PUSCH transmission is FDM or TDM (not SDM), or the rank value or the total number of layers for PUSCH transmission is determined as R1 or R2 or min(R1,R2) or max(R1,R2). For example, R1=R2.

[0120] In some embodiments, terminal device 120 may be configured to have a first number and a second number. For example, if the value indicated in the antenna port field is 12, 13, 14, or 15, terminal device 120 may determine that the PUSCH transmission scheme is SDM, or that the rank value or total number of layers for PUSCH transmission is 2. For another example, if the value indicated in the antenna port field is any one of {0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11}, terminal device 120 may determine that the PUSCH transmission scheme is FDM or TDM (not SDM), or that the rank value or total number of layers for PUSCH transmission is 1. For example, whether the PUSCH transmission scheme is FDM or TDM may be based on RRC configuration. An example is shown in Table 7A. For example, terminal device 120 may be configured to have an enabled transform precoder. For another example, terminal device 120 may be configured to have DMRS type 2. For another example, terminal device 120 may be configured such that the maximum length or number of OFDM symbols for DMRS is one. [Table 7A]

[0121] In some embodiments, terminal device 120 may be configured to have a second number and a second number. For example, if the value indicated in the antenna port field is any one of {7, 8, 9, 10, 11, 12, 13, 14, 15}, terminal device 120 may determine that the PUSCH transmission scheme is SDM or that the rank value or total number of layers for PUSCH transmission is 4. For another example, if the value indicated in the antenna port field is any one of {0, 1, 2, 3, 4, 5, 6}, terminal device 120 may determine that the PUSCH transmission scheme is FDM or TDM (not SDM) or that the rank value or total number of layers for PUSCH transmission is 2. For example, whether the PUSCH transmission scheme is FDM or TDM may be based on RRC configuration. An example is shown in Table 7B. For example, terminal device 120 may be configured to have an enabled transform precoder. For another example, terminal device 120 may be configured to have DMRS type 2. For another example, terminal device 120 may be configured to have a maximum length or number of OFDM symbols for DMRS of two. [Table 7B]

[0122] In some embodiments, terminal device 120 may be configured such that the transmission scheme for PUSCH transmission is FDM, and the number of bandwidths or resource blocks (RBs) for PUSCH transmission may be configured as M (e.g., M is a positive integer, for another example, 1≦M≦276). For example, a first group of RBs (e.g., M1, where M1 is a positive integer, for example, 1≦M1≦M) from M RBs may be associated with a first SRI field and / or a first TPMI field and / or a first SRS resource set, and a second group of RBs (e.g., M2, where M2 is a positive integer, for example, 1≦M2≦M) from M RBs may be associated with a second SRI field and / or a second TPMI field and / or a second SRS resource set. For example, M1 may be floor(M / 2) or ceil(M / 2). For another example, M2=M−M1. In some embodiments, terminal device 120 may be configured with a transform precoder enabled, with the value of M being JPEG0007827133000014.jpg14168, where α1, α2, and α3 are non-negative integers. In some embodiments, the value of M1 is JPEG0007827133000015.jpg14168 should be satisfied, where α 11 , α 21 , α 31 is a non-negative integer, and the value of M2 is JPEG0007827133000016.jpg14168 should be satisfied, where α 12 , α 22 , α 32 are non-negative integers satisfying M1+M2≦M. For example, the value of M1 is rounded to ceil(M / 2) or floor(M / 2) or the nearest integer, JPEG0007827133000017.jpg14168, where α 11 , α 21 , α 31is a non-negative integer. For another example, the value of M1 is the largest integer less than or equal to ceil(M / 2) or floor(M / 2), JPEG0007827133000018.jpg16168, where α 11 , α 21 , α 31 is a non-negative integer. For another example, the value of M2 is rounded to ceil(M / 2) or floor(M / 2) or the nearest integer or M-M1, JPEG0007827133000019.jpg16168, where α 12 , α 22 , α 32 is a non-negative integer. For another example, the value of M2 is the largest integer less than or equal to ceil(M / 2) or floor(M / 2), or M-M1, JPEG0007827133000020.jpg15168, where α 12 , α 22 , α 32 is a non-negative integer. For example, terminal device 120 may be configured so that the bandwidth or the number of RBs for PUSCH transmission is M=15. Also, the RBs of the first group may be determined as M1=8 or 6, and the RBs of the second group may be determined as M2=6 or 8.

[0123] In some embodiments, terminal device 120 may not be configured to have a value of M for PUSCH transmission, where either ceil(M / 2) or floor(M / 2) is JPEG0007827133000021.jpg14168 or JPEG0007827133000022.jpg14168 is not satisfied, where α 11 , α 21 , α 31 , α 12 , α 22 , α 32is a non-negative integer. For example, terminal device 120 may not be expected to configure the bandwidth or number of RBs for PUSCH transmission to be M=15. For example, floor(M / 2)=7, which is JPEG0007827133000023.jpg15168 does not satisfy, where α 12 , α 22 , α 32 is a non-negative integer.

[0124] In some embodiments, terminal device 120 may be configured such that the transmission scheme for PUSCH transmission is SDM, and terminal device 120 may be configured such that a phase tracking reference signal (PTRS) is present, whereby the actual number of PTRS ports is two, with each PTRS port corresponding to one of the first and second SRI fields, and / or one of the first and second TPMI fields, and / or one of the first and second SRS resource sets. In some embodiments, a first set of DMRS ports for PUSCH transmission corresponding to an SRI in the first SRI field may be associated with a first PTRS port, and other DMRS ports for PUSCH transmission may be associated with a second PTRS port. For example, terminal device 120 may be configured to have non-codebook-based uplink transmission.

[0125] In some embodiments, the terminal device 120 may report an ability to support fully coherent uplink transmission, and if PTRS is configured, the terminal device 120 may assume that the number of PTRS ports is set as two if PTRS is configured, and if the terminal device 120 is configured with an SDM transmission scheme for PUSCH transmission, and if two SRI fields and / or two TPMI fields are used (or in the case of multi-TRP transmission), and otherwise, the terminal device 120 may assume that the number of PTRS ports is one.

[0126] In some embodiments, the terminal device 120 may be configured such that the transmission scheme for PUSCH transmission is SDM, and the PUSCH-to-PTRS power ratio for each resource element (RE) in each layer may be determined for each SRI field or each TPMI field, or may be determined based on the first or second number. Examples are shown in Table 8A and Table 8B. For example, Q p may be the number of PTRS ports. For example, Q p may be any one of {1,2}. [Table 8A] [Table 8B]

[0127] In some embodiments, the power ratio of PUSCH to PTRS for each RE in each layer may be less than or equal to 6. For example, the number of layers for PUSCH transmission is greater than 4.

[0128] In some embodiments, the terminal device 120 may be configured such that the transmission scheme for PUSCH transmission is FDM, and the density of the PTRS in the frequency domain may be determined based on the number of RBs in a first group, where the PTRS is transmitted within the frequency range of the RBs in this first group, and the density of the PTRS in the frequency domain may be determined based on the number of RBs in a second group, where the PTRS is transmitted within the frequency range of the RBs in this second group.

[0129] FIG. 5 is a diagram illustrating an example of an embodiment of the present disclosure.

[0130] As shown in FIG. 5, terminal device 120 may be scheduled to have a PUSCH transmission to network device 110, and terminal device 120 may determine a power for this PUSCH transmission. For example, terminal device 120 may calculate a first power (e.g., P0) based on a set of parameters. For another example, terminal device 120 may determine a second power (e.g., P1), where P1=min(Pcmax, P0), where Pcmax is the maximum power configured for the terminal device. This parameter set may also be configured via RRC signaling. For another example, the second power may be scaled using the parameters. For another example, the power is distributed evenly across the number of antenna ports or layers for the PUSCH transmission.

[0131] 6A-6C show an example embodiment of the present disclosure.

[0132] 6A, for example, terminal device 120 may be configured to have two layers for PUSCH transmission based on a single TRP (e.g., TRP1), the power for PUSCH transmission may be P1, and the power at each layer may be P1 / 2. For example, terminal device 120 may be configured to have one layer for PUSCH transmission based on a single TRP (e.g., TRP2), the power for PUSCH transmission may be P2, and the power at each layer may be P2. For example, terminal device 120 may be configured to have 2+1=3 layers for PUSCH transmission based on multiple TRPs (e.g., TRP1 and TRP2), and it is necessary to define how to determine the power P for each layer of PUSCH transmission.

[0133] 6B, for example, terminal device 120 may be configured to have two layers for PUSCH transmission based on a single TRP (e.g., TRP1), and the power for PUSCH transmission may be P1. For example, terminal device 120 may be configured to have one layer for PUSCH transmission based on a single TRP (e.g., TRP2), and the power for PUSCH transmission may be P2. For example, terminal device 120 may be configured to have 2+1=3 layers for PUSCH transmission based on multiple TRPs (e.g., TRP1 and TRP2), and it is necessary to define how to determine the power P for PUSCH transmission.

[0134] As shown in FIG. 6C , for example, terminal device 120 may be configured to have two layers for PUSCH transmission based on a single TRP (e.g., TRP1), where the power for PUSCH transmission may be P1 and the power at each layer may be P1 / 2. For example, terminal device 120 may be configured to have one layer for PUSCH transmission based on a single TRP (e.g., TRP2), where the power for PUSCH transmission may be P2 and the power at each layer may be P2. For another example, terminal device 120 may be configured to have three layers for PUSCH transmission based on a single TRP (e.g., TRP1), where the power at each layer for PUSCH transmission may be P1 / 3. For another example, terminal device 120 may be configured to have three layers for PUSCH transmission based on a single TRP (e.g., TRP2), where the power at each layer for PUSCH transmission may be P2 / 3. For example, the terminal device 120 may be configured to have 2+1=3 layers for PUSCH transmission based on multiple TRPs (e.g., TRP1 and TRP2), and the power at each layer of the PUSCH transmission may be (P1+P2) / 3. For example, the power at each layer is greater than that for single-TRP transmission. P2 / 3. For example, the terminal device 120 may be configured to have 2+1=3 layers for PUSCH transmission based on multiple TRPs (e.g., TRP1 and TRP2), and the power at each layer of the PUSCH transmission may be (2*P1 / 3+P2 / 3) / 3. For example, the power may be significantly different between single-TRP transmission and multi-TRP transmission. For another example, the terminal device 120 may be configured to have 2+1=3 layers for PUSCH transmission based on multiple TRPs (e.g., TRP1 and TRP2), where two layers are transmitted on panel 1 and one layer is transmitted on panel 2, and the power for each of the two layers on panel 1 may be P1 / 2 and the power for the one layer on panel 2 may be P2. For example, the power for different layers for PUSCH transmission may vary greatly.

[0135] In some embodiments, for a PUSCH with uplink shared channel (UL-SCH) data: JPEG0007827133000026.jpg16168, and for channel state information (CSI) transmission in PUSCH without UL-SCH data, JPEG0007827133000027.jpg14168, where - C is the number of code blocks to be transmitted, and K r is the size of the code block r, and N RE teeth is the number of resource elements determined as JPEG0007827133000028.jpg17168, where: JPEG0007827133000029.jpg12168 is the number of symbols for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c, JPEG0007827133000030.jpg14168 is the PUSCH symbol j is the number of subcarriers that do not include DM-RS subcarriers and phase tracking RS samples [4, TS 38.211] in [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 2 JPEG0007827133000031.jpg14168. - if the PUSCH contains UL-SCH data, JPEG0007827133000032.jpg15168 and PUSCH contains CSI but no UL-SCH data. JPEG0007827133000033.jpg14168. - Q m is the modulation order, and R is the code rate provided by the DCI format that schedules the PUSCH transmission containing CSI and no UL-SCH data.

[0136] In some embodiments, the PUSCH power control adjustment state f b,f,cFor (i, l), for the active UL BWP b of carrier f of serving cell c in PUSCH transmission occasion i, δ PUSCH,b,f,c (i,l) is the TPC command value included in the DCI format for scheduling PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c, or encoded together with other TPC commands in DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI.

[0137] In some embodiments, if terminal device 120 is configured to have twoPUSCH-PC-AdjustmentStates, then l∈{0,1}, and if terminal device 120 is not configured to have twoPUSCH-PC-AdjustmentStates or if PUSCH transmission is scheduled by a RAR UL grant, then l=0.

[0138] In some embodiments, for PUSCH (re)transmissions configured by ConfiguredGrantConfig, the value of l∈{0,1} is provided to terminal device 120 by powerControlLoopToUse.

[0139] In some embodiments, when SRI-PUSCH-PowerControl is provided to terminal device 120, terminal device 120 obtains a mapping between a set of values ​​of the SRI field in a DCI format that schedules PUSCH transmission and the l values ​​provided by sri-PUSCH-ClosedLoopIndex, and determines the l values ​​to be mapped to the SRI field values.

[0140] In some embodiments, if a PUSCH transmission is scheduled with a DCI format that does not include an SRI field, or if SRI-PUSCH-PowerControl is not provided to terminal device 120, then l=0.

[0141] In some embodiments, when terminal device 120 obtains TPC commands from DCI format 2_2 having a CRC scrambled by TPC-PUSCH-RNTI, the l values ​​are provided by a closed-loop indicator field in DCI format 2_2.

[0142] In some embodiments, JPEG0007827133000034.jpg17168 is the PUSCH power control adjustment state l for active UL BWP b and PUSCH transmission occasion i of carrier f of serving cell c when tpc-Accumulation is not provided to terminal device 120, where δ PUSCH,b,f,c The values ​​are given in Table 9.

[0143] In some embodiments, JPEG0007827133000035.jpg15168 shows the PUSCH transmission occasion i-i0 in the active UL BWP b of carrier f of serving cell c for PUSCH power control adjustment state l. PUSCH (i-i0)-1 symbols ago and K of PUSCH transmission occasion i PUSCH (i) The concentration C(D i ) a set of TPC command values ​​D i where i0>0 is the sum of the TPC command values ​​in K for PUSCH transmission occasion i-i0. PUSCH The (i-i0)th symbol before is K for PUSCH transmission occasion i. PUSCH (i) The smallest integer that is earlier than the symbol before.

[0144] In some embodiments, when PUSCH transmission is scheduled by a DCI format, K PUSCH (i) is the number of symbols for the active UL BWP b of carrier f of serving cell c after the last symbol of the corresponding PDCCH reception and before the first symbol of the PUSCH transmission.

[0145] In some embodiments, if PUSCH transmission is configured by ConfiguredGrantConfig, K PUSCH (i) is K, which is equal to the product of the number of symbols per slot and the minimum of the values ​​provided by k2 in PUSCH-ConfigCommon for the active UL BWP b of carrier f of serving cell c. PUSCH,min The number of symbols.

[0146] In some embodiments, terminal device 120 reaches maximum power for an active UL BWP b of carrier f of serving cell c at PUSCH transmission occasion i-i0, and If the file is JPEG0007827133000036.jpg17168, JPEG0007827133000037.jpg14168.

[0147] In some embodiments, terminal device 120 reaches a minimum power for an active UL BWP b of carrier f of serving cell c at PUSCH transmission occasion i-i0, and If the file is JPEG0007827133000038.jpg17168, JPEG0007827133000039.jpg13168.

[0148] In some embodiments, the corresponding P O_UE_PUSCH,b,f,c (j) If the value is set by a higher layer, and / or the corresponding If the configuration for the JPEG0007827133000040.jpg613 value is provided by a higher layer, the terminal device 120 calculates the accumulated PUSCH power control adjustment state for the active UL BWP b of the carrier f of the serving cell c by f b,f,c Reset (k,l)=0, k=0,1,...,i, where l is determined from the value of j as follows:

[0149] If j>1 and the UE is provided with a higher SRI-PUSCH-PowerControl, l is the sri-PUSCH-ClosedLoopIndex value configured in any SRI-PUSCH-PowerControl with the sri-P0-PUSCH-AlphaSetId value corresponding to j.

[0150] If j>1 and SRI-PUSCH-PowerControl is not provided to the terminal device 120, or j=0, then l=0.

[0151] If j=1, then l is given by the value of powerControlLoopToUse.

[0152] In some embodiments, f b,f,c (i,l)=δ PUSCHb,f,c (i,l) is the PUSCH power control adjustment state for the active UL BWP b of carrier f of serving cell c and PUSCH transmission occasion i when tpc-Accumulation is provided to terminal device 120, where δ PUSCH,b,f,c The absolute values ​​are given in Table 9. [Table 9]

[0153] In some embodiments, μ may be a subcarrier spacing setting. For example, μ=0 corresponds to 15 kHz subcarrier spacing. For another example, μ=1 corresponds to 30 kHz subcarrier spacing. For another example, μ=2 corresponds to 60 kHz subcarrier spacing. For another example, μ=3 corresponds to 120 kHz subcarrier spacing. For another example, μ=4 corresponds to 240 kHz subcarrier spacing. For example, μ=5 corresponds to 480 kHz subcarrier spacing. For another example, μ=6 corresponds to 960 kHz subcarrier spacing.

[0154] In some embodiments, terminal device 120 may be configured to have a first number (e.g., R1, where R1 may be any one of {1, 2, 3, 4}) and a second number (e.g., R2, where R2 may be any one of {1, 2, 3, 4}) for PUSCH transmission. For example, a transmission scheme for PUSCH transmission may be configured as SDM. In some embodiments, a power for the first number of layers and a power for the second number of layers may be calculated separately. In some embodiments, terminal device 120 may calculate a first power (e.g., P0_1) for the first number of layers for PUSCH transmission based on the first set of parameters.

[0155] In some embodiments, the first power is For example, i may be a PUSCH transmission occasion. O_PUSCH_1 may be a parameter in the first set of parameters, which is a parameter of the component P O_NOMINAL_PUSCH_1 and component P O_UE_PUSCH_1 For example, P O_NOMINAL_PUSCH_1 and P O_UE_PUSCH_1 and are in the first set of parameters and may be configured via at least one of RRC and MAC CE. For example, α1 is in the first set of parameters and may be configured via at least one of RRC and MAC CE. For example, JPEG0007827133000043.jpg14168 may be the bandwidth or the number of RBs set for PUSCH transmission. For example, PL1(q d_1 ) is the downlink path loss estimate in dB, and the RS index q d_1 For example, K s =1.25, JPEG0007827133000044.jpg17168. For another example, s If =0, Δ TF_1 (i)=0. For example, Ks is in the first set of parameters, e.g., configured by deltaMCS via RRC. For example, if the number of layers for PUSCH transmission is greater than 1, then Δ TF_1 (i)=0. For example, f1(i,l1) is the power control adjustment for the first layer number. For example, f1(i,l1) may be based on a first TPC command value indicated in the DCI. For example, the first set of parameters may be associated with a first SRS resource set.

[0156] In some embodiments, terminal device 120 may calculate a second power (e.g., P0_2) for a second number of layers for PUSCH transmission based on a second set of parameters, e.g., the second set of parameters may be associated with a second SRS resource set.

[0157] In some embodiments, the second power is For example, i may be a PUSCH transmission occasion. O_PUSCH_2 may be a parameter in the second set of parameters, which is a parameter of the component P O_NOMINAL_PUSCH_2 and component P O_UE_PUSCH_2 For example, P O_NOMINAL_PUSCH_2 and P O_UE_PUSCH_2 and α are in the second set of parameters and may be configured via at least one of RRC and MAC CE. For example, α2 is in the second set of parameters and may be configured via at least one of RRC and MAC CE. For example, JPEG0007827133000046.jpg14168 may be the bandwidth or the number of RBs set for PUSCH transmission. For example, PL2(q d_2 ) is the downlink path loss estimate in dB, and the RS index q d_2 For example, K s =1.25, JPEG0007827133000047.jpg18168. For another example, s If =0, Δ TF_2 (i)=0. For example, K s is in a second set of parameters, e.g., configured by deltaMCS via RRC. For example, if the number of layers for PUSCH transmission is greater than 1, then Δ TF_2 (i)=0. For example, f2(i,l2) is the power control adjustment for the second layer number. For example, f2(i,l2) may be based on a second TPC command value indicated in the DCI. For example, the second set of parameters may be associated with a second SRS resource set.

[0158] In some embodiments, the first power may be scaled using a first factor (e.g., γ). In some embodiments, the second power may be scaled using a second factor (e.g., δ). In some embodiments, γ=R1 / (R1+R2). In some embodiments, δ=R2 / (R1+R2). In some embodiments, γ=1 or ½ or ⅓ or 1 / (R1+R2). In some embodiments, δ=1 or ½ or ⅓ or 1 / (R1+R2). In some embodiments, γ=δ.

[0159] In some embodiments, the terminal device 120 may determine a third power (e.g., P1), where P1=min(Pcmax,(γ*P0_1+δ*P0_2)). In some embodiments, the terminal device may determine the fourth power and the fifth power based on the third power and one or more coefficients. For example, the third power may be divided into the fourth power and the fifth power according to the one or more coefficients. For example, the fourth power may be JPEG0007827133000048.jpg17168 or P0_4=P1*γ. For example, the fourth power may be related to the first layer number for PUSCH transmission. For example, the fifth power may be JPEG0007827133000049.jpg19168 or P0_5=P1*δ. For another example, the fifth power may be associated with a second number of layers for PUSCH transmission. For example, terminal device 120 may distribute the fourth power evenly to a first number of DMRS / antenna ports. For example, the first number of DMRS / antenna ports may correspond to a first number of layers for PUSCH transmission. For another example, terminal device 120 may distribute the fifth power evenly to a second number of DMRS / antenna ports. For example, the second number of DMRS / antenna ports may correspond to a second number of layers for PUSCH transmission.

[0160] FIG. 7 is a diagram illustrating an example of an embodiment of the present disclosure.

[0161] As shown in FIG. 7 , for example, the terminal device 120 may be configured to have a first number (e.g., R1, where R1 may be any one of {1, 2, 3, 4}) and a second number (e.g., R2, where R2 may be any one of {1, 2, 3, 4}) for PUSCH transmission. For example, the transmission scheme for PUSCH transmission may be configured as SDM. For example, the terminal device may calculate a first power (e.g., P0_1) and a second power (e.g., P0_2). For example, the first power may be scaled using a first factor γ. For another example, the second power may be scaled using a second factor δ. For example, the first power may be associated with a first layer number for PUSCH transmission. For another example, the second power may be associated with a second layer number for PUSCH transmission. For example, terminal device 120 may determine a third power (e.g., P1), where P1 = min(Pcmax,(γ*P0_1+δ*P0_2)). For example, the terminal device may determine a fourth power and a fifth power based on the third power and one or more coefficients. For example, the third power may be distributed to the fourth power and the fifth power according to the one or more coefficients. For example, the fourth power may be associated with a first number of layers for PUSCH transmission. For another example, the fifth power may be associated with a second number of layers for PUSCH transmission. For example, terminal device 120 may distribute the fourth power evenly to a first number of DMRS / antenna ports. For example, the first number of DMRS / antenna ports may correspond to a first number of layers for PUSCH transmission. For another example, terminal device 120 may distribute the fifth power evenly to a second number of DMRS / antenna ports. For example, the second number of DMRS / antenna ports may correspond to a second number of layers for PUSCH transmission.

[0162] In some embodiments, terminal device 120 may be configured such that the number of bandwidths or resource blocks (RBs) for PUSCH transmission is M (e.g., M is a positive integer, for another example, 1≦M≦276). In some embodiments, terminal device 120 may be configured such that the transmission scheme for PUSCH transmission is FDM. For example, a first group of RBs (e.g., M1, where M1 is a positive integer, for example, 1≦M1≦M) from M RBs may be associated with a first SRI field and / or a first TPMI field and / or a first SRS resource set, and a second group of RBs (e.g., M2, where M2 is a positive integer, for example, 1≦M2≦M) from M RBs may be associated with a second SRI field and / or a second TPMI field and / or a second SRS resource set. For example, M1 may be floor(M / 2) or ceil(M / 2). For another example, M2=M−M1. In some embodiments, the power for the first group of RBs and the power for the second group of RBs may be calculated separately. In some embodiments, terminal device 120 may calculate a first power (e.g., P0_1) for the first group of RBs for PUSCH transmission based on the first set of parameters.

[0163] In some embodiments, the first power is For example, i may be a PUSCH transmission occasion. O_PUSCH_1 may be a parameter in the first set of parameters, which is a parameter of the component P O_NOMINAL_PUSCH_1 and component P O_UE_PUSCH_1 For example, P O_NOMINAL_PUSCH_1 and P O_UE_PUSCH_1 and may be in the first set of parameters and may be configured via at least one of RRC and MAC CE. For example, α1 may be in the first set of parameters and may be configured via at least one of RRC and MAC CE. For example, PL1(qd_1 ) is the downlink path loss estimate in dB, and the RS index q d_1 For example, K s =1.25, JPEG0007827133000051.jpg16168. For another example, s If =0, Δ TF_1 (i)=0. For example, K s is in the first set of parameters, e.g., configured by deltaMCS via RRC. For example, if the number of layers for PUSCH transmission is greater than 1, then Δ TF_1 (i)=0. For example, f1(i,l1) is the power control adjustment for the first layer number. For example, f1(i,l1) may be based on a first TPC command value indicated in the DCI. For example, the first set of parameters may be associated with a first SRS resource set.

[0164] In some embodiments, terminal device 120 may calculate a second power (e.g., P0_2) for the second group of RBs for PUSCH transmission based on a second set of parameters, e.g., the second set of parameters may be associated with a second SRS resource set.

[0165] In some embodiments, the second power is For example, i may be a PUSCH transmission occasion. O_PUSCH_2 may be a parameter in the second set of parameters, which is a parameter of the component P O_NOMINAL_PUSCH_2 and component P O_UE_PUSCH_2 For example, P O_NOMINAL_PUSCH_2 and P O_UE_PUSCH_2 and α are in the second set of parameters and may be configured via at least one of RRC and MAC CE. For example, α2 is in the second set of parameters and may be configured via at least one of RRC and MAC CE. For example, JPEG0007827133000053.jpg14168 may be the bandwidth or the number of RBs set for PUSCH transmission. For example, PL2(q d_2 ) is the downlink path loss estimate in dB, and the RS index q d_2 For example, K s =1.25, JPEG0007827133000054.jpg17168. For another example, s If =0, Δ TF_2 (i)=0. For example, K s is in a second set of parameters, e.g., configured by deltaMCS via RRC. For example, if the number of layers for PUSCH transmission is greater than 1, then Δ TF_2 (i)=0. For example, f2(i,l2) is the power control adjustment for the second layer number. For example, f2(i,l2) may be based on a second TPC command value indicated in the DCI. For example, the second set of parameters may be associated with a second SRS resource set.

[0166] In some embodiments, the first power may be scaled using a first factor (e.g., γ). In some embodiments, the second power may be scaled using a second factor (e.g., δ). In some embodiments, γ=R1 / (R1+R2). In some embodiments, δ=R2 / (R1+R2). In some embodiments, γ=1 or ½ or ⅓ or 1 / (R1+R2). In some embodiments, δ=1 or ½ or ⅓ or 1 / (R1+R2). In some embodiments, γ=δ.

[0167] In some embodiments, the terminal device 120 may determine a third power (e.g., P1), where P1=min(Pcmax,(γ*P0_1+δ*P0_2)). In some embodiments, the terminal device may determine the fourth power and the fifth power based on the third power and one or more coefficients. For example, the third power may be divided into the fourth power and the fifth power according to the one or more coefficients. For example, the fourth power may be JPEG0007827133000055.jpg19168 or P0_4=P1*γ. For example, the fourth power may be related to the first layer number for PUSCH transmission. For example, the fifth power may be JPEG0007827133000056.jpg17168 or P0_5=P1*δ. For another example, the fifth power may be associated with the second layer number for PUSCH transmission. For example, terminal device 120 may evenly distribute the fourth power to multiple DMRS / antenna ports for PUSCH transmission in the first group of RBs. For another example, terminal device 120 may evenly distribute the fifth power to multiple DMRS / antenna ports for PUSCH transmission in the second group of RBs.

[0168] In some embodiments, terminal device 120 may determine a fourth power (e.g., P0_4) as P0_4=min(Pcmax_1,P0_1). For example, Pcmax_1 may be the maximum output power set in association with a first group of RBs or a first number of layers. In some embodiments, terminal device 120 may determine a fifth power (e.g., P0_5) as P0_5=min(Pcmax_2,P0_2). For example, Pcmax_2 may be the maximum output power set in association with a second group of RBs or a second number of layers. For example, terminal device 120 may evenly distribute the fourth power to a first number of DMRSs / antenna ports. For example, the first number of DMRSs / antenna ports may correspond to a first number of layers for PUSCH transmission. For another example, terminal device 120 may evenly distribute the fifth power to a second number of DMRSs / antenna ports. For example, the second number of DMRSs / antenna ports may correspond to a second number of layers for PUSCH transmission. For example, terminal device 120 may evenly distribute the fourth power to multiple DMRSs / antenna ports for PUSCH transmission in the first group of RBs. For another example, terminal device 120 may evenly distribute the fifth power to multiple DMRSs / antenna ports for PUSCH transmission in the second group of RBs.

[0169] In some embodiments, terminal device 120 may be configured to have multiple sets of power control parameters based on different transmission schemes. In some embodiments, terminal device 120 may be configured to have two sets of power control parameters (e.g., Set 1_1 and Set 1_2) associated with a first SRS resource set. For example, if the transmission scheme is configured as SDM, Set 1_1 is applied to calculate the power associated with the first SRS resource set. For another example, if the transmission scheme is not configured as SDM (or is configured as single TRP transmission, or as TDM or FDM), Set 1_2 is applied to calculate the power associated with the first SRS resource set. In some embodiments, terminal device 120 may be configured to have two sets of power control parameters (e.g., Set 2_1 and Set 1_2) associated with a second SRS resource set. For example, if the transmission scheme is configured as SDM, Set 2_1 is applied to calculate the power associated with the second SRS resource set. For another example, if the transmission scheme is not configured as SDM (or is configured as single TRP transmission, or TDM or FDM), set 2_2 is applied to calculate the power associated with the second SRS resource set.

[0170] In some embodiments, terminal device 120 may be configured such that the transmission scheme for PUSCH transmission is SDM and / or FDM, and two path loss RSs may be configured to calculate downlink path loss estimates. For example, the two path loss RSs may be assigned index q d_1 and q d_2 and

[0171] In some embodiments, terminal device 120 may calculate the power headroom based on the maximum output power and the third power. For example, the power headroom is calculated as PH=P CMAX -P1 may also be used.

[0172] In some embodiments, when the transmission scheme is set to SDM and / or FDM, the terminal device 120 may calculate two values ​​of power headroom, where a first power headroom may be calculated based on the maximum output power Pcmax_1 and the fourth power, and a second power headroom may be calculated based on the maximum output power Pcmax_2 and the fifth power. For example, the first power headroom is calculated as PH_1=P CMAX_1 For example, the second power headroom may be PH_2=P CMAX_2 -P0_5 is also acceptable.

[0173] In some embodiments, terminal device 120 may calculate the power headroom based on a reference PUSCH transmission. For example, JPEG0007827133000057.jpg32168.

[0174] 8-11 are flowcharts of exemplary methods performed by terminal device 120 or network device 110. FIG.

[0175] It should be understood that the correspondence between values ​​and descriptions shown in Figures 3-7 is provided for illustrative purposes and does not imply any limitations on the present disclosure. In other exemplary embodiments, this correspondence may be redefined.

[0176] Furthermore, it should be understood that this correspondence is known in advance to the network device 110 and the terminal device 120. Specifically, the network device 110 and the terminal device 120 may locally store / configure this correspondence. Furthermore, this correspondence may be realized by the terminal device 120 and the network device 110 as computer program code or configuration files in a storage device.

[0177] In some exemplary embodiments, this correspondence may be predefined / preconfigured / predefined by a wireless communication standard (e.g., a 3GPP standard), in which case no additional interaction is required between network device 110 and terminal device 120.

[0178] In some other exemplary embodiments, this correspondence may be predefined / preconfigured / predefined by a communications network operator or service provider, in which case terminal device 120 may obtain this correspondence from network device 110 via, for example, an RRC message, a MAC CE, or a physical layer message, and terminal device 120 may then store this correspondence in local storage.

[0179] 8 is a flowchart of an example method 800 according to some embodiments of the present disclosure. For example, the method 800 may be implemented in a terminal device 120 such as shown in FIGS. 1A and 1B.

[0180] In block 810, terminal device 120 may receive DCI for scheduling at least one PUSCH transmission from network device 110. The DCI includes a first field indicating that the at least one PUSCH transmission is transmitted based on an SRS resource set from multiple SRS resource sets or the multiple SRS resource sets, and a second field indicating an index of a single SRS resource set for transmitting the at least one PUSCH transmission.

[0181] At block 820, terminal device 120 may transmit a PUSCH transmission to network device 110 based on the DCI. For example, the PUSCH transmission may include a first layer number and a second layer number. For another example, the PUSCH transmission may include a first group of RBs and a second group of RBs. For example, the PUSCH transmission may be based on a power determined according to an embodiment of the present disclosure. Note that method 800 may include one or more of the steps and / or features described above.

[0182] 9 is a flowchart of an example method 900 according to some embodiments of the present disclosure. For example, the method 900 may be implemented in a network device 110 such as shown in FIGS. 1A and 1B.

[0183] At block 910, network device 110 may transmit DCI for scheduling PUSCH transmission to terminal device 120. According to an embodiment of the present disclosure, the DCI includes a first field and a second field.

[0184] At block 920, network device 110 may receive at least one PUSCH transmission sent based on the DCI from terminal device 120. Note that method 900 may include one or more of the steps and / or features described above.

[0185] 10 is a flowchart of an example method 1000 according to some embodiments of the present disclosure. For example, the method 1000 may be implemented in a terminal device 120 such as shown in FIGS. 1A and 1B.

[0186] At block 1010, terminal device 120 may receive DCI for scheduling PUSCH transmission from network device 110. According to an embodiment of the present disclosure, the DCI includes a first field and a second field.

[0187] In block 1020, terminal device 120 may send the at least one PUSCH transmission to network device 110 based on the DCI.

[0188] In some exemplary embodiments, the plurality of SRS resource sets includes a first SRS resource set and a second SRS resource set. Note that method 1000 may include one or more of the steps and / or features described above.

[0189] 11 is a flowchart of an example method 1100 according to some embodiments of the present disclosure. For example, the method 1100 may be implemented in a network device 110 such as shown in FIGS. 1A and 1B.

[0190] At block 1110, the network device 110 may transmit DCI for scheduling PUSCH transmission to the terminal device 120. According to an embodiment of the present disclosure, the DCI includes a first field and a second field.

[0191] At block 1120, network device 110 may receive at least one PUSCH transmission sent based on the DCI from terminal device 120. Note that method 1100 may include one or more of the steps and / or features described above.

[0192] In some embodiments, terminal device 120 may include circuitry configured to receive DCI for scheduling a PUSCH transmission from network device 110. According to an embodiment of the present disclosure, the DCI includes a first field and a second field. The circuitry is further configured to transmit the PUSCH transmission to network device 110 based on the DCI.

[0193] In some embodiments, network device 110 may include circuitry configured to transmit DCI for scheduling a PUSCH transmission to terminal device 120. According to an embodiment of the present disclosure, the DCI includes a first field and a second field. The circuitry is further configured to receive from terminal device 120 the PUSCH transmission sent based on the DCI.

[0194] 12 is a schematic block diagram of an apparatus 1200 suitable for implementing embodiments of the present disclosure. The apparatus 1200 may be considered as another exemplary implementation of the network apparatus 110 and / or the terminal apparatus 120 shown in FIGS. 1A and 1B. Accordingly, the apparatus 1200 may be implemented in, or as at least a part of, the network apparatus 110 and / or the terminal apparatus 120 shown in FIGS. 1A and 1B.

[0195] As shown, the apparatus 1200 includes a processor 1210, a memory 1220 coupled to the processor 1210, a suitable transmitter (TX) and receiver (RX) 1240 coupled to the processor 1210, and a communication interface coupled to the TX / RX 1240. The memory 1210 stores at least a portion of a program 1230. The TX / RX 1240 is used for bidirectional communication. The TX / RX 1240 has at least one antenna to facilitate communication, although the access nodes referred to herein may actually have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, an Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device 120.

[0196] The program 1230 is assumed to include program instructions that, when executed by the associated processor 1210, enable the device 1200 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 2-11. The embodiments herein may be implemented by computer software executable by the processor 1210 of the device 1200, by hardware, or by a combination of software and hardware. The processor 1210 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 1210 and the memory 1220 may form a processing means 1250 suitable for implementing various embodiments of the present disclosure.

[0197] Memory 1220 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. While only one memory 1220 is shown in device 1200, several physically distinct memory modules may be present within device 1200. Processor 1210 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 1200 may have multiple processors, for example, application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0198] Overall, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. While various aspects of embodiments of the present disclosure have been illustrated and described using block diagrams, flowcharts, or other pictorial representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented, by way of non-limiting example, in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or any combination thereof.

[0199] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules, that execute within a device on a target real or virtual processor to perform the processes or methods described above with reference to FIGS. 2 through 11. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. The machine-executable instructions of the program modules may be executed within local or distributed devices. In a distributed device, program modules may be located in both local and remote storage media.

[0200] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, and when executed by the processor or controller, cause the program code to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, as a separate software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0201] The above-mentioned program code may be embodied in a machine-readable medium, which may be any tangible medium that can contain or store a program used by or associated with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the aforementioned media. More specific examples of a machine-readable storage medium may include an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0202] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order shown, or in any sequential order, or performing all of the operations described, is required to achieve desirable results. In some cases, multitasking or parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features that are described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0203] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the present disclosure, as defined in the appended claims, is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A communication method executed by a terminal device, comprising: receiving, from a network device, downlink control information (DCI) for scheduling one physical uplink shared channel (PUSCH), the DCI including a first field, a second field, and a third field; transmitting the PUSCH to the network device based on a rank value; When the third field indicates a third value, the rank value is the sum of a first value determined based on the first field and a second value determined based on the second field, and when the third field indicates a fourth value, the rank value is determined based on the first field. Communication method.

2. If the PUSCH is non-codebook based, the first field is a sounding reference signal (SRS) resource indicator field, and the second field is a second SRS resource indicator field. If the PUSCH is codebook based, the first field is a precoding information and layer number field, and the second field is a second precoding information field. The communication method according to claim 1 .

3. The first field is used to indicate a precoder applied to a first layer number, and the second field is used to indicate a precoder applied to a second layer number, or the first field is used to indicate resources associated with a first layer number, and the second field is used to indicate resources associated with a second layer number. The communication method according to claim 1 .

4. If the rank value is 3, the DCI includes a fourth field indicating that the demodulation reference signal (DMRS) port is {0, 2, 3}. The communication method according to claim 1 .

5. 1. A communication method performed by a network device, comprising: Transmitting, to a terminal device, downlink control information (DCI) for scheduling one physical uplink shared channel (PUSCH), the DCI including a first field, a second field, and a third field; receiving the PUSCH from the terminal device based on a rank value; When the third field indicates a third value, the rank value is the sum of a first value determined based on the first field and a second value determined based on the second field, and when the third field indicates a fourth value, the rank value is determined based on the first field. Communication method.

6. If the PUSCH is non-codebook based, the first field is an SRS resource indicator field and the second field is a second SRS resource indicator field; if the PUSCH is codebook based, the first field is a precoding information and layer number field and the second field is a second precoding information field. The communication method according to claim 5.

7. The first field is used to indicate a precoder applied to a first layer number, and the second field is used to indicate a precoder applied to a second layer number, or the first field is used to indicate resources associated with a first layer number, and the second field is used to indicate resources associated with a second layer number. The communication method according to claim 5.

8. If the rank value is 3, the DCI includes a fourth field indicating that the DMRS port is {0, 2, 3}. The communication method according to claim 5.

9. A method for scheduling one physical uplink shared channel (PUSCH), comprising: receiving downlink control information (DCI) from a network device, the DCI including a first field, a second field, and a third field; means for transmitting the PUSCH to the network device based on a rank value; When the third field indicates a third value, the rank value is the sum of a first value determined based on the first field and a second value determined based on the second field, and when the third field indicates a fourth value, the rank value is determined based on the first field. Terminal device.

10. If the PUSCH is non-codebook based, the first field is an SRS resource indicator field and the second field is a second SRS resource indicator field; if the PUSCH is codebook based, the first field is a precoding information and layer number field and the second field is a second precoding information field. The terminal device according to claim 9.

11. The first field is used to indicate a precoder applied to a first layer number, and the second field is used to indicate a precoder applied to a second layer number, or the first field is used to indicate resources associated with a first layer number, and the second field is used to indicate resources associated with a second layer number. The terminal device according to claim 9.

12. If the rank value is 3, the DCI includes a fourth field indicating that the DMRS port is {0, 2, 3}. The terminal device according to claim 9.

13. A means for transmitting downlink control information (DCI) to a terminal device, the DCI including a first field, a second field, and a third field for scheduling one physical uplink shared channel (PUSCH); means for receiving the PUSCH from the terminal device based on a rank value; When the third field indicates a third value, the rank value is the sum of a first value determined based on the first field and a second value determined based on the second field, and when the third field indicates a fourth value, the rank value is determined based on the first field. Network equipment.

14. If the PUSCH is non-codebook based, the first field is an SRS resource indicator field and the second field is a second SRS resource indicator field; if the PUSCH is codebook based, the first field is a precoding information and layer number field and the second field is a second precoding information field.

14. The network device of claim 13.

15. The first field is used to indicate a precoder applied to a first layer number, and the second field is used to indicate a precoder applied to a second layer number, or the first field is used to indicate resources associated with a first layer number, and the second field is used to indicate resources associated with a second layer number.

14. The network device of claim 13.

Images