Uplink data transmission device and method, and uplink data reception device and method

CN119547538APending Publication Date: 2025-02-281FINITY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280098084.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-08-05
Publication Date
2025-02-28

AI Technical Summary

Technical Problem

In Rel-18, how can we determine the UL TCI state and SRS resource set associated with PUSCH during uplink data transmission to avoid transmission failure due to parameter ambiguity?

Method used

Based on the parameters indicated by the third downlink control information and/or the uplink transmission configuration indication status, the terminal device determines the uplink data transmission method at a single transmit/receive point or multiple transmit/receive points, and clarifies the PUSCH transmission strategy.

Benefits of technology

This avoids parameter ambiguity in uplink data transmission and ensures successful data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119547538A_ABST
    Figure CN119547538A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides an uplink data sending device and method and an uplink data receiving device and method. And the terminal equipment determines related parameters for uplink data transmission in the second action time based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. In this way, ambiguity can be prevented from occurring in use of related parameters for uplink data transmission, and thus uplink data transmission failure caused by ambiguity can be avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Uplink data sending and receiving device and method Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] During the standardization process of Release 17 (Rel-17), the 3GPP standardization organization carried out standardization work on the unified transmission configuration indication (TCI). The unified TCI in Rel-17 is designed primarily for the sTRP (single transmission and reception point) scenario.

[0003] With the advancement of standardization, multiple transmission and reception point (mTRP) has become an important scenario in 5G NR systems. Through mTRP-based transmission, the goal of improving throughput or reliability can be achieved.

[0004] In previous standardization work, the transmission of the Physical Downlink Shared Channel (PDSCH) based on mTRP was standardized in Rel-16; and the transmission of the Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), and Physical Uplink Control Channel (PUCCH) based on mTRP were standardized in Rel-17. Among them, mTRP transmission includes mTRP transmission based on single Downlink Control Information (sDCI) and mTRP transmission based on multiple DCI (mDCI).

[0005] It should be noted that the above introduction to the technical background is only for the convenience of providing a clear and complete description of the technical solutions of this application and for the convenience of understanding by those skilled in the art. It cannot be considered that the above technical solutions are well known to those skilled in the art simply because these solutions are explained in the background technology part of this application.

[0006] Summary of the Invention

[0007] In the Rel-17 unified TCI scenario for sTRP (single transmission and reception point), the network device uses RRC signaling to configure M (M ≥ 1) TCI states for the terminal device, uses the medium access control (MAC) control element (CE) to activate N (1 ≤ N ≤ M) TCI states in the M TCI states, and uses DCI to indicate L (1 ≤ L ≤ N) TCI states in the N TCI states. Among them, the transmission configuration indication (TCI) field of DCI format 1_1 or DCI format 1_2 indicates one or more TCI states. In addition, DCI format 1_1 or DCI format 1_2 can schedule downlink data, which is called DCI format 1_1 / 1_2 with DL assignment, or it can not schedule downlink data, which is called DCI format 1_1 / 1_2 without DL assignment.

[0008] A TCI state (TCI for short) may include or correspond to one or two source reference signals (source RS, source Reference Signal). The source reference signal may provide quasi co-location (QCL, Quasi Co-Location) information for downlink reception, and is referred to as a downlink source reference signal. The source reference signal may provide a reference for an uplink transmit spatial filter (UL TX spatial filter, uplink transmission spatial filter), and is referred to as an uplink source reference signal. The source reference signal may provide beam information for the destination channel / signal. For example, the beam used by the terminal device to receive the destination channel / signal is the same as the beam used to receive the downlink source reference signal. For another example, the beam used by the terminal device to send the destination channel / signal is the same as the beam used to send the uplink source reference signal. For another example, the beam used by the terminal device to send the destination channel / signal and the beam used to receive the downlink source reference signal are reciprocal, that is, beams in opposite directions are used.

[0009] Therefore, the indication or update of the TCI state actually also includes the indication or update of the beam used by the terminal device. The TCI state includes a joint TCI state, a downlink TCI state (DL only TCI state), and an uplink TCI state (UL only TCI state). The source reference signal included in the downlink TCI state is a downlink source reference signal, and the source reference signal included in the uplink TCI state is an uplink source reference signal. The source reference signal included in the joint TCI state is both a downlink source reference signal and an uplink source reference signal. The joint TCI state acts on both the downlink beam (receive beam) and the uplink beam (transmit beam). In other words, the downlink beam and the uplink beam use the same beam, but the beam directions are opposite, that is, there is reciprocity between the uplink and downlink beams. The downlink TCI state only acts on the downlink beam. The uplink TCI state only acts on the uplink beam. The uplink beam is also called the uplink transmit spatial filter. The TCI field can indicate a joint TCI state (joint DL / UL TCI) or a downlink TCI state and / or an uplink TCI state (separate DL / UL TCI). These two modes can be configured through RRC signaling. For Rel-17 unified TCI, a TCI field indicates a joint TCI state, a downlink TCI state, an uplink TCI state, or a downlink TCI state and an uplink TCI state. The TCI state indicated by a DCI is valid for a period of time until another DCI indicates a newer TCI state. This period is called the TCI state validity period.

[0010] Multiple transmission and reception point (mTRP) is an important scenario in the 5G NR system. Through transmission based on mTRP, the purpose of improving throughput or reliability can be achieved. Rel-16 standardized PDSCH transmission based on mTRP, and Rel-17 standardized PDCCH, PUSCH, and PUCCH transmission based on mTRP. In addition, the current mTRP transmission in Rel-17 includes mTRP transmission based on sDCI (single DCI) and mTRP transmission based on mDCI (multiple DCI). For sDCI mTRP, one DCI schedules the uplink and downlink transmission of two TRPs, which is more suitable for situations where the backhaul between TRPs is relatively ideal; for mDCI mTRP, two TRPs use two DCIs to schedule the uplink and downlink transmission of their respective TRPs, which is more suitable for situations where the backhaul between TRPs is not ideal.

[0011] However, the inventors found that for Rel-18, when the UL DCI and its scheduled PUSCH are in different action times, how to determine the UL TCI state and SRS resource set associated with the PUSCH, and how to send the PUSCH based on the determined UL TCI state and SRS resource set, are problems that need to be solved.

[0012] To address at least one of the above-mentioned issues, embodiments of the present application provide a method and apparatus for uplink data transmission and uplink data reception. A terminal device determines relevant parameters for uplink data transmission within the second action time based on parameters indicated by third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby preventing uplink data transmission failures caused by this.

[0013] According to one aspect of an embodiment of the present application, a method for transmitting uplink data is provided, which is applied to a terminal device, wherein the terminal device is configured with two SRS resource sets. The method includes:

[0014] The terminal device receives third downlink control information for scheduling uplink data within the first action time, wherein at least part of the uplink data is within the second action time; and

[0015] The terminal device determines, based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data within the second action time based on a single transmission and reception point (sTRP), or to send uplink data based on multiple transmission and reception points (mTRP).

[0016] According to another aspect of an embodiment of the present application, a method for sending uplink data is applied to a terminal device, wherein the terminal device is configured with two SRS resource sets. The method includes:

[0017] The terminal device receives third downlink control information for scheduling uplink data within a first action time, and the terminal device sends the uplink data within the first action time; and

[0018] The terminal device determines to send the uplink data based on a single transmission and reception point (sTRP) based on at least one of the SRS resource set, SRS resource, or TPMI indicated by the third downlink control information, or to send the uplink data based on multiple transmission and reception points (mTRP).

[0019] According to another aspect of an embodiment of the present application, a method for transmitting uplink data is provided, which is applied to a terminal device, wherein the terminal device is configured with two SRS resource sets. The method includes:

[0020] The terminal device receives third downlink control information for scheduling uplink data within the first action time, wherein at least part of the uplink data is within the second action time; and

[0021] The terminal device does not send uplink data within the second action time.

[0022] According to another aspect of an embodiment of the present application, a method for receiving uplink data is provided, which is applied to a network device, wherein the terminal device is configured with two SRS resource sets. The method includes:

[0023] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time, wherein at least part of the uplink data is within the second action time; and

[0024] The network device receives uplink data within the second action time, wherein the terminal device determines, based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, to send uplink data based on a single transmission and reception point (sTRP) or to send uplink data based on multiple transmission and reception points (mTRP).

[0025] According to another aspect of an embodiment of the present application, a method for receiving uplink data is provided, which is applied to a network device, wherein the terminal device is configured with two SRS resource sets. The method includes:

[0026] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time;

[0027] The network device receives the uplink data within the first action time, wherein:

[0028] The terminal device determines to send the uplink data based on a single transmission and reception point (sTRP) based on at least one of the SRS resource set, SRS resource, or TPMI indicated by the third downlink control information, or to send the uplink data based on multiple transmission and reception points (mTRP).

[0029] According to another aspect of an embodiment of the present application, a method for receiving uplink data is provided, which is applied to a network device, wherein the terminal device is configured with two SRS resource sets. The method includes:

[0030] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time, wherein at least part of the uplink data is within the second action time; and

[0031] The network device does not receive the uplink data within the second action time during the second action time, wherein the terminal device does not send the uplink data within the second action time.

[0032] According to another aspect of an embodiment of the present application, an uplink data transmitting apparatus is provided, configured in a terminal device, wherein the terminal device is configured with two SRS resource sets (SRS resource sets), and the uplink data transmitting apparatus includes:

[0033] a first receiving unit configured to receive, within a first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within a second action time; and

[0034] a first sending unit, which determines, according to the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data based on a single transmission and reception point (sTRP) for the uplink data within the second action time, or to send uplink data based on multiple transmission and reception points (mTRP).

[0035] According to another aspect of an embodiment of the present application, an uplink data transmitting apparatus is provided, configured in a terminal device, wherein the terminal device is configured with two SRS resource sets (SRS resource sets), and the uplink data transmitting apparatus includes:

[0036] a second receiving unit, which receives third downlink control information for scheduling uplink data within a first action time, and the terminal device sends the uplink data within the first action time; and

[0037] a second sending unit, which determines, based on at least one of an SRS resource set (SRS resource set), an SRS resource (SRS resource), or an uplink precoding index (TPMI) indicated by the third downlink control information, to send uplink data based on a single transmission and reception point (sTRP), or to send uplink data based on multiple transmission and reception points (mTRP).

[0038] According to another aspect of an embodiment of the present application, an uplink data transmitting apparatus is provided, configured in a terminal device, wherein the terminal device is configured with two SRS resource sets (SRS resource sets), and the uplink data transmitting apparatus includes:

[0039] a third receiving unit configured to receive, within the first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within the second action time; and

[0040] The third sending unit does not send the uplink data within the second action time.

[0041] According to another aspect of an embodiment of the present application, there is provided an uplink data receiving apparatus, configured in a network device, the uplink data receiving apparatus comprising:

[0042] a first transmitting unit configured to transmit, to a terminal device within a first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within a second action time; wherein the terminal device is configured with two SRS resource sets; and

[0043] A first receiving unit receives uplink data within the second action time, wherein the terminal device determines, based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data based on a single transmission and reception point (sTRP) or to send uplink data based on multiple transmission and reception points (mTRP) for the uplink data within the second action time.

[0044] According to another aspect of an embodiment of the present application, there is provided an uplink data receiving apparatus, configured in a network device, the uplink data receiving apparatus comprising:

[0045] a second sending unit configured to send third downlink control information for scheduling uplink data to a terminal device within a first action time; wherein the terminal device is configured with two SRS resource sets; and

[0046] a second receiving unit, which receives the uplink data within the first action time,

[0047] The terminal device determines whether to send uplink data based on a single transmission and reception point (sTRP) or multiple transmission and reception points (mTRP) based on at least one of the SRS resource set (SRS resource set), SRS resource (SRS resource), or TPMI indicated by the third downlink control information.

[0048] According to another aspect of an embodiment of the present application, there is provided an uplink data receiving apparatus, configured in a network device, the uplink data receiving apparatus comprising:

[0049] a third receiving unit, which sends third downlink control information for scheduling uplink data to the terminal device within the first action time, wherein the uplink data is at least partially within the second action time; wherein the terminal device is configured with two SRS resource sets (SRS resource sets), and

[0050] A third sending unit does not receive the uplink data within the second action time during the second action time, wherein the terminal device does not send the uplink data within the second action time.

[0051] One of the beneficial effects of the embodiments of the present application is that the terminal device determines relevant parameters for uplink data transmission within the second action time based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. As a result, ambiguity in the use of relevant parameters for uplink data transmission can be avoided, thereby avoiding uplink data transmission failure caused by this.

[0052] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0053] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0054] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0056] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0057] FIG2 is a schematic diagram of a signaling sending process according to an embodiment of the present application;

[0058] FIG3 is another schematic diagram of the signaling sending process according to an embodiment of the present application;

[0059] FIG4 is a schematic diagram of a method for sending uplink data according to an embodiment of the present application;

[0060] FIG5 is a schematic diagram of the association relationship of mTRP PUSCH related parameters according to an embodiment of the present application;

[0061] FIG6 is a schematic diagram of the association relationship of sTRP PUSCH related parameters according to an embodiment of the present application;

[0062] FIG7 is another schematic diagram of the signaling sending process according to an embodiment of the present application;

[0063] FIG8 is an example diagram of a method for determining uplink data related parameters in Case 1 of an embodiment of the present application;

[0064] FIG9 is an example diagram of a method for determining uplink data related parameters in Case 2 of an embodiment of the present application;

[0065] FIG10 is an example diagram of a method for determining uplink data related parameters in Case 3 of an embodiment of the present application;

[0066] FIG11 is an example diagram of a method for determining uplink data related parameters in Case 4 of an embodiment of the present application;

[0067] FIG12 is a schematic diagram of PUSCH transmission according to an embodiment of the present application;

[0068] FIG13 is another schematic diagram of PUSCH transmission according to an embodiment of the present application;

[0069] FIG14 is another schematic diagram of PUSCH transmission according to an embodiment of the present application;

[0070] FIG15 is another schematic diagram of PUSCH transmission according to an embodiment of the present application;

[0071] FIG16 is another schematic diagram of the uplink data sending method according to an embodiment of the present application;

[0072] FIG17 is another schematic diagram of the signaling sending process according to an embodiment of the present application;

[0073] FIG18 is another schematic diagram of the uplink data sending method according to an embodiment of the present application;

[0074] FIG19 is another schematic diagram of the signaling sending process according to an embodiment of the present application;

[0075] FIG20 is a schematic diagram of a method for receiving uplink data according to an embodiment of the present application;

[0076] FIG. 21 is another schematic diagram of the uplink data receiving method according to an embodiment of the present application.

[0077] FIG22 is another schematic diagram of the uplink data receiving method according to an embodiment of the present application;

[0078] FIG23 is a schematic diagram of an uplink data transmitting apparatus according to an embodiment of the present application;

[0079] FIG24 is another schematic diagram of the uplink data sending device according to an embodiment of the present application;

[0080] FIG25 is another schematic diagram of an uplink data transmitting apparatus according to an embodiment of the present application;

[0081] FIG26 is a schematic diagram of an uplink data receiving device according to an embodiment of the present application;

[0082] FIG27 is another schematic diagram of the uplink data receiving device according to an embodiment of the present application;

[0083] FIG28 is another schematic diagram of an uplink data receiving device according to an embodiment of the present application;

[0084] FIG29 is a schematic diagram of the structure of a network device according to an embodiment of the present application;

[0085] Figure 30 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0086] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0087] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0088] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0089] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0090] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0091] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0092] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0093] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, and so on.

[0094] Among them, terminal devices may include but are not limited to the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smart phones, smart watches, digital cameras, etc.

[0095] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0096] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0097] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0098] Figure 1 is a schematic diagram of a communication system according to an embodiment of the present application, illustrating a situation using a terminal device and a network device as an example. As shown in Figure 1 , communication system 100 may include a first TRP 101, a second TRP 102, and a terminal device 103. The first TRP 101 and the second TRP 102 may be network devices. For simplicity, Figure 1 illustrates only two network devices and one terminal device as an example, but the embodiments of the present application are not limited thereto.

[0099] In the embodiment of the present application, existing services or future services can be transmitted between the first TRP 101, the second TRP 102, and the terminal device 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0100] Rel-16 standardized PDSCH transmission based on mTRP, and Rel-17 standardized PDCCH, PUSCH, and PUCCH transmission based on mTRP. mTRP transmission includes mTRP transmission based on sDCI (single DCI) and mTRP transmission based on mDCI (multiple DCI). For sDCI mTRP, one DCI schedules the uplink and downlink transmissions of two TRPs, which is more suitable for situations where the backhaul between TRPs is ideal. For mDCI mTRP, two TRPs use two DCIs to schedule the uplink and downlink transmissions of their respective TRPs, which is more suitable for situations where the backhaul between TRPs is not ideal.

[0101] Taking the terminal device 103 transmitting PUSCH in the mTRP scenario as an example, as shown in Figure 1, the terminal device 103 transmits PUSCH in a PUSCH repetition manner. For example, it transmits to the first TRP 101 in time slot 1, transmits to the second TRP 102 in time slot 2, and so on.

[0102] In the mTRP scenario, the terminal device is configured with two SRS resource sets (SRS resource set), corresponding to two TRPs respectively. For example, the terminal device is configured with two SRS resource sets (SRS resource set), for example, the first SRS resource set (1st SRS resource set) corresponding to the first TRP101 is configured for the terminal device 103; and the second SRS resource set (2nd SRS resource set) corresponding to the second TRP102 is configured for the terminal device 103.

[0103] Due to the geographical differences between the first TRP 101 and the second TRP 102, the terminal device may send PUSCH to the first TRP 101 and / or the second TRP 102 based on different transmission parameters such as precoding matrices, SRIs (SRS resource indicators), and power control parameters. In addition, the terminal device obtains the transmission parameters for the first TRP 101 and the second TRP 102 based on the first SRS resource set and the second SRS resource set.

[0104] Taking the SRS resource indicator (SRI) as an example, for a dynamic uplink grant, the two SRI fields in the DCI indicate the SRS resources in two SRS resource sets respectively; for a configured grant, the two SRIs are configured by RRC to two SRS resource sets. Therefore, the terminal device needs to know the mapping relationship between PUSCH repetition and SRS resource set, that is, to know which SRS resource set each PUSCH repetition should be sent based on.

[0105] The UL DCI that schedules PUSCH can instruct the terminal device to perform sTRP PUSCH transmission or mTRP PUSCH transmission through the "SRS resource set indicator" field. For sTRP PUSCH transmission, this field can indicate based on which of the two SRS resource sets the transmission is based. For mTRP PUSCH transmission, this field can indicate in which mapping order the two SRS resource sets are mapped to the PUSCH repetition. For example, in the order of "first the first SRS resource set, then the second SRS resource set" (expressed as #1, #2), to achieve the purpose of "first sending to the first TRP101, then sending to the second TRP102", as shown in Figure 1; or, in the order of "first the second SRS resource set, then the first SRS resource set" (expressed as #2, #1), to achieve the purpose of "first sending to the second TRP102, then sending to the first TRP101", that is, to exchange the mapping order in Figure 1. When the higher-layer parameter "cyclicMapping" is enabled, the order of mapping to PUSCH repetition is #1, #2, #1, #2...; when the higher-layer parameter "sequentialMapping" is enabled, the order of mapping to PUSCH repetition is #1, #1, #2, #2...

[0106] Rel-17 unified TCI is only applicable to sTRP scenarios. Given the importance of mTRP, it is necessary to design a corresponding unified TCI mechanism for mTRP scenarios. 3GPP will standardize the unified TCI for mTRP in Rel-18. Currently, the unified TCI for mTRP has been identified as one of the projects for Rel-18, but standardization work for Rel-18 has not yet begun. Functionally, the unified TCI for mTRP needs to be able to indicate the TCI status of two TRPs to support mTRP PUSCH transmission, and also indicate the TCI status of a single TRP to support sTRP PUSCH transmission.

[0107] The following describes the specific uplink and downlink signaling.

[0108] Figure 2 is a schematic diagram of the signaling sending process of an embodiment of the present application. For unified TCI, DL DCI indicates the application time (Application time) of at least one UL TCI state, such as DL DCI 1 or DL ​​DCI 2 in Figure 2. The UL TCI state can be indicated by a joint DL / UL TCI state or a separate DL / UL TCI state. The terminal device receives DL DCI 1 indicating at least one UL TCI state, wherein the UL TCI state indicated by DL DCI 1 is different from the UL TCI state indicated by the previous DL DCI (such as DL DCI 0, not shown in Figure 2) (including a different number of UL TCI states). The terminal device sends an ACK (ACK 1) for DL ​​DCI 1 to the network device. DL DCI 1 can be a DCI format for scheduling PDSCH or a DCI format for not scheduling PDSCH (DCI format without DL assignment). The first time slot in which the UL TCI state indicated by DL DCI 1 is applied is the first time slot after Y symbols following the last symbol of ACK1, and the starting time of this time slot is denoted as t1. Assuming that DL DCI 2 is the first DL DCI after DL DCI 1 indicating a UL TCI state different from the UL TCI state indicated by DL DCI 1, the same method can be used to determine the first time slot in which the UL TCI state indicated by DL DCI 2 is applied, and the starting time of this time slot is denoted as t2. The application time of the UL TCI state indicated by DL DCI 1 (first application time: application time 1) includes all time slots between t1 and t2. In other words, the UL TCI state effective during application time 1 is indicated by DL DCI 1. Similarly, the application time of the UL TCI state indicated by DL DCI 2 (second application time: application time 2, Application time 2) can be expressed as all time slots between t2 and t3, where t3 corresponds to the time slot of the first application of a UL TCI state different from the UL TCI state indicated by DL DCI 2, and the different UL TCI state is indicated by DL DCI 3 located after DL DCI 2 (not shown in Figure 2).To avoid downlink HARQ out-of-order, for DL ​​DCI 2 located after DL DCI 1, its associated ACK 2 is located after ACK 1, and cannot be located before ACK 1.

[0109] For the PUSCH scheduled by UL DCI in the sDCI mTRP scenario, the terminal device configured with two SRS resource sets can determine the UL TCI state and SRS resource set used by the PUSCH according to the following method: the UL TCI state used by the PUSCH is the UL TCI state within the action time of the PUSCH (that is, the latest UL TCI state is used), and the SRS resource set used by the PUSCH is indicated by the SRS resource set indicator field of the UL DCI (that is, the UL DCI can indicate the switching between different PUSCH schemes, such as the switching between sTRP PUSCH and mTRP PUSCH). However, when the UL DCI and the PUSCH scheduled by it are respectively in different action times, the UL TCI state and SRS resource set determined according to the above method will conflict with each other, resulting in ambiguity in the use of the UL TCI state and SRS resource set, and thus causing PUSCH transmission failure.

[0110] Figure 3 schematically illustrates the above problem. Figure 3 is another schematic diagram of the signaling transmission process of an embodiment of the present application, and the similarities with Figure 2 are not repeated here. As shown in Figure 3, two UL TCI states are scheduled within the action time 1 of DL DCI 1, and one UL TCI state is scheduled within the action time 2 of DL DCI 2; and within the action time 1, one UL DCI schedules at least one PUSCH to be sent, the UL DCI is within the action time of two UL TCI states (action time 1), and at least one PUSCH is within the action time of one UL TCI state (action time 2). The following PUSCH refers to the PUSCH within the action time 2. At the scheduling moment of UL DCI, the number of UL TCI states is 2. The network device cannot predict that the UL TCI state will become 1 in the future (at time t2). For example, there is suddenly a URLLC service that needs to be scheduled by DL DCI 2, and DL DCI 2 can take the opportunity to indicate the updated UL TCI state. Therefore, the SRS resource set indicator field of the UL DCI is still determined based on the assumption of 2 UL TCI states. Assume that the SRS resource set indicator field instructs the terminal device to use 2 SRS resource sets, which correspond one to one with 2 UL TCI states. Following the above method will have the following consequences: PUSCH uses 1 UL TCI state within the action time 2, and uses 2 SRS resource sets indicated by UL DCI. In this case, the number of UL TCI states does not match the number of SRS resource sets. Since PUSCH transmission based on 1 UL TCI state only requires one SRS resource set, on the one hand, the above method produces an incorrect configuration or undefined behavior, which makes the terminal device not know how to send PUSCH; on the other hand, the above method cannot make the terminal device and the network device have the same understanding of which SRS resource set is used for PUSCH transmission. In the case of inconsistent understanding between the two parties, it will lead to failure of PUSCH demodulation.

[0111] Therefore, when the UL DCI and its scheduled PUSCH are in different action times, how to determine the UL TCI state and SRS resource set associated with the PUSCH, and how to send the PUSCH based on the determined UL TCI state and SRS resource set, are problems that need to be solved.

[0112] To address at least one of the above problems, embodiments of the present application provide a method and apparatus for sending and receiving uplink data.

[0113] Embodiments of the first aspect

[0114] An embodiment of the present application provides an uplink data sending method, which is applied to a terminal device side. The terminal device is configured with two SRS resource sets (SRS resource sets).

[0115] FIG4 is a schematic diagram of a method for sending uplink data according to an embodiment of the present application. As shown in FIG4 , the method includes:

[0116] 401. The terminal device receives, within a first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within a second action time; and

[0117] 402. The terminal device determines, according to the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data within the second action time based on a single transmission and reception point (sTRP), or to send uplink data based on multiple transmission and reception points (mTRP).

[0118] It is worth noting that FIG4 above is merely a schematic illustration of an embodiment of the present application, using a terminal device as an example, but the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, other operations may be added or some operations may be reduced, and the objects of the aforementioned operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG4 above.

[0119] In some embodiments, the terms "TRP" and "SRS resource set" may be used interchangeably. The terms "TRP" and "CSI-RS resource set" may be used interchangeably. The terms "corresponding," "associated," and "including" may be used interchangeably, and "uplink TCI state" and "joint TCI state" may be used interchangeably. The terms "PUSCH", "PUSCH transmission" and "PUSCH sending" can be used interchangeably; "DL TCI state" or "UL TCI state" can be indicated by "joint DL / UL TCI state" or "separate DL / UL TCI state"; "DL TCI state" can be "DL only TCI state" or "joint TCI state"; "UL TCI state" can be "UL only TCI state" or "joint TCI state"; "TPMI" refers to the information indicated by the "Precoding information and number of layers" field or "Second Precoding information" field in DCI, including precoding matrix information and number of layers information. The above field can be referred to as "TPMI field"; the above is only an exemplary description, and the embodiments of the present application are not limited to this.

[0120] Thus, the terminal device determines the relevant parameters for uplink data transmission within the second action time based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. Thus, ambiguity in the use of the relevant parameters for uplink data transmission can be avoided, thereby avoiding the resulting uplink data transmission failure.

[0121] In some embodiments, the terminal device receives first downlink control information corresponding to a first action time; and receives second downlink control information corresponding to a second action time within the first action time.

[0122] For example, the first downlink control information is DL DCI 1 shown in Figure 2, and the first action time is the action time of the UL TCI state indicated by DL DCI 1 (for example, action time 1, Application time 1); the second downlink control information is DL DCI 2 shown in Figure 2, and the second action time is the action time of the UL TCI state indicated by DL DCI 2 (for example, action time 2, Application time 2).

[0123] In some implementations, the second downlink control information indicates at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0124] For example, DL DCI 2 shown in FIG3 indicates one UL TCI state, and its effective time is Application time 2. Optionally, DL DCI 2 may also indicate two UL TCI states (not shown in FIG3 ).

[0125] In some implementations, the third downlink control information may be UL DCI, which may also be called an uplink grant (UL grant).

[0126] For example, the third downlink control information may be the UL DCI shown in FIG3 . For example, the third downlink control information further includes parameters required for scheduled uplink data, such as at least one of an SRS resource set, an SRS resource, or a transmit precoding matrix indicator (TPMI). In some embodiments, the parameter is indicated by at least one of an SRS resource set indicator field, an SRI field, or a TPMI field in the third downlink control information.

[0127] In some embodiments, the uplink data includes at least one of the following uplink data types: uplink repetition (PUSCH repetition) type A (Type A); uplink repetition (PUSCH repetition) type B (Type B); or PUSCHs sent simultaneously by multiple panels.

[0128] In some implementations, for the sDCI mTRP scenario, the PUSCH may be a PUSCH or a PUSCH repetition.

[0129] For example, for the specific transmission methods of PUSCH repetition Type A and PUSCH repetition Type B, please refer to the relevant parts of standard TS 38.214 V17.1.0, and this application does not limit this.

[0130] In some implementations, the mTRP PUSCH is equivalent to a PUSCH based on two SRS resource sets, or a PUSCH based on two UL TCI states.

[0131] FIG5 is a schematic diagram of the association relationship of mTRP PUSCH related parameters according to an embodiment of the present application.

[0132] For mTRP PUSCH, taking two TRPs as an example, the terminal device performs uplink transmission (UL transmission) to the two TRPs. Figure 5 illustrates this schematically. The two uplink transmissions may belong to two PUSCH repetitions (corresponding to two redundancy versions (RV)). For example, the terminal device sends PUSCH repetitions to the two TRPs in a time division multiplexing manner, that is, the mTRP PUSCH of Rel-17. In addition, for the mTRP PUSCH to be standardized in Rel-18, it can also be called simultaneous multi-panel UL transmission (STxMP), the terminal device can use two panels (panels) to simultaneously send PUSCH to the two TRPs in a frequency division multiplexing or space division multiplexing or SFN (Single Frequency Network) manner (also referred to as PUSCH sent simultaneously by multiple panels), that is, the two uplink transmissions may belong to one PUSCH (corresponding to one RV) or two PUSCH repetitions (corresponding to two RVs). For example, the mTRP PUSCH of Rel-18 can also be called a PUSCH based on two panels. The present application is applicable to all forms of mTRP PUSCH mentioned above. Figure 5 illustrates the association between UL TCI state, panel, uplink transmission, TRP, SRS resource set, SRS resource and TPMI. For a TRP, it is associated with an SRS resource set, a UL TCI state, an SRS resource, a TPMI, and an uplink transmission. For the mTRP PUSCH of Rel-18, a panel can be associated with a TRP, and then associated with an SRS resource set, a UL TCI state, an SRS resource, a TPMI, and an uplink transmission. Based on the above association, a TRP can be equivalent to an SRS resource set, and a panel can be equivalent to an SRS resource set.

[0133] In some embodiments, sTRP PUSCH refers to sTRP PUSCH performed by a terminal device configured with two SRS resource sets. sTRP PUSCH is equivalent to PUSCH based on one SRS resource set, or PUSCH based on one UL TCI state.

[0134] In some embodiments, the terminal device receives a DL DCI indicating a UL TCI state and uses the UL TCI state to send sTRP PUSCH.

[0135] FIG6 is a schematic diagram of the association relationship of sTRP PUSCH related parameters in an embodiment of the present application.

[0136] For sTRP PUSCH, the terminal device performs uplink transmission to one of the two TRPs. Figure 6 illustrates this schematically. For terminal devices configured with two SRS resource sets, dynamic switching can be performed between sTRP PUSCH and mTRP PUSCH. For example, UL DCI indicates one or two SRS resource sets, which respectively indicate sTRP PUSCH or mTRP PUSCH transmission. For example, DL DCI indicates one or two UL TCI states, which respectively indicate sTRP PUSCH or mTRP PUSCH transmission. As shown in Figure 6, the terminal device can perform uplink transmission to the first TRP, using the SRS resource set, UL TCI state, SRS resource and TPMI associated with the first TRP; the terminal device can perform uplink transmission to the second TRP, using the SRS resource set, UL TCI state, SRS resource and TPMI associated with the second TRP. The uplink transmission can be a PUSCH or a PUSCH repetition.

[0137] FIG7 is another schematic diagram of the signaling sending process of an embodiment of the present application.

[0138] The following description is made using FIG7 as an example. Without loss of generality, the figure only shows action time 1 (first action time), action time 2 (second action time), UL DCI in action time 1, and PUSCH in action time 2.

[0139] For example, the terminal device is configured with two SRS resource sets. During the action time 1, the effective UL TCI state may be 1 or 2. Under the premise of knowing the UL TCI state, the SRS resource set indicated by the UL DCI may be 1 or 2, corresponding to 1 or 2 UL TCI states respectively. During the action time 2, the effective UL TCI state may be 1 or 2, which is different from the UL TCI state during the action time 1. Table 1 lists all possible combinations of UL TCI states in different action times, including Case 1 to Case 4. The UL TCI state in action time 2 is different from the UL TCI state in action time 1. From action time 1 to action time 2, for Case 1 and Case 2, the number of UL TCI states changes, and for Case 3 and Case 4, the number of UL TCI states does not change. UL DCI indicates the SRS resource set, SRS resource and TPMI according to the UL TCI state in action time 1.

[0140] Table 1: Possible combinations of UL TCI states at different action times

[0141] Action time 1 Action time 2Case 1UL TCI state 1-1,UL TCI state 2-1UL TCI state 1-2Case 2UL TCI state 1-1UL TCI state 1-2,UL TCI state 2-2Case 3UL TCI state 1-1,UL TCI state 2-1UL TCI state 1-2,UL TCI state 2-2Case 4UL TCI state 1-1UL TCI state 1-2

[0142] In some embodiments, for the uplink data within the first action time and / or the uplink data within the second action time, at least the following information needs to be determined: whether the uplink data is sent based on sTPR PUSCH or based on mTRP PUSCH; the number of UL TCI states used for the uplink data and the specific UL TCI state; specific parameters for sending the uplink data, for example, at least one of an SRS resource set (SRS resource set), an SRS resource (SRS resource), or an uplink precoding index (transmit precoding matrix indicator, TPMI).

[0143] In some implementations, uplink data within the second action time is transmitted using part or all of at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0144] In some embodiments, when the parameter indicated by the third downlink control information includes an SRS resource set, uplink data transmission (sTRP PUSCH) based on a single transmission and reception point (sTRP) is performed for the uplink data within the second action time; when the parameter includes more than one SRS resource set, uplink data transmission (mTRP PUSCH) based on multiple transmission and reception points (mTRP) is performed for the uplink data within the second action time.

[0145] For example, the terminal device determines to send sTRP PUSCH or mTRP PUSCH within the second action time based on at least one of the SRS resource set, SRS resource, or TPMI indicated by the UL DCI.

[0146] For example, when the UL DCI indicates two SRS resource sets, two SRS resources and two TPMIs, the terminal device sends mTRP PUSCH within the second action time; when the UL DCI indicates one SRS resource set, one SRS resource and one TPMI, the terminal device sends sTRP PUSCH within the second action time.

[0147] For example, as shown in Case 1, although the number of UL TCI states changes from two in action time 1 to one in action time 2, since the UL DCI indicates mTRP PUSCH transmission according to action time 1, the terminal device still performs mTRP PUSCH transmission in action time 2 instead of switching to sTRP PUSCH transmission. As shown in Case 2, although the number of UL TCI states changes from one in action time 1 to two in action time 2, since the UL DCI indicates sTRP PUSCH transmission according to action time 1, the terminal device still performs sTRP PUSCH transmission in action time 2 instead of switching to mTRP PUSCH transmission.

[0148] In some embodiments, an uplink transmission configuration indication state (UL TCI state) associated with a parameter indicated by the third downlink control information in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time is used, or a predefined uplink transmission configuration indication state (UL TCI state) in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time is used to send uplink data within the second action time.

[0149] In some implementations, the predefined uplink transmission configuration indication state (UL TCI state) is an uplink transmission configuration indication state (UL TCI state) at a specific position in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0150] In some embodiments, the terminal device uses part or all of the UL TCI states within the second active time.

[0151] For example, for Case 2, the terminal device determines to send sTRP PUSCH within action time 2 based on the SRS resource set, SRS resource and TPMI indicated by the UL DCI. There are two UL TCI states within action time 2, and the terminal device uses one of the UL TCI states to send sTRP PUSCH.

[0152] For example, for Case 3 and Case 4, the number of UL TCI states within action time 1 and action time 2 is the same. Regardless of whether it is based on UL DCI or the UL TCI state within action time 2, the PUSCH transmission mode (sTRP PUSCH or mTRP PUSCH) determined by the terminal device within action time 2 is the same as the PUSCH transmission mode within action time 1, and therefore all UL TCI states within action time 2 are used.

[0153] In some embodiments, the terminal device uses a portion of the UL TCI state within the second active time, and the terminal device determines the UL TCI state according to one of the following:

[0154] UL TCI state associated with the SRS resource set;

[0155] Default (predefined) UL TCI state.

[0156] For example, there are two UL TCI states within the second action time, and the terminal device determines to use the second SRS resource set within the second action time. For example, the UL DCI indicates the "second SRS resource set", and the "second SRS resource set" is associated with the second UL TCI state, then the UL TCI state associated with the "second SRS resource set" is used, that is, the second UL TCI state.

[0157] For example, the terminal device uses the default (predefined) UL TCI state, that is, the first UL TCI state of the two UL TCI states.

[0158] In some implementations, at least one of the following information in the parameter is used: SRS resource set; SRS resource; or TPMI to send uplink data within the second action time.

[0159] For example, how to use at least one of the following information in the parameter in Case 1-Case 4: SRS resource set; SRS resource; or TPMI to send uplink data within the second action time will be described later, for example, see method 1 in Figures 8-11.

[0160] In some embodiments, at least one of the SRS resource set, the SRS resource, and the TPMI is indicated by an SRS resource set indicator field of the UL DCI.

[0161] For example, the SRS resource set indicator field of the UL DCI includes two bits, indicating the used SRS resource set, SRS resource, and TPMI according to Table 2 below. The SRS resource set indicator field indicates the used SRS resource set and the associated SRI field and TPMI field, which indicate the SRS resource and TPMI respectively.

[0162] Table 2: SRS resource set indicator fields

[0163]

[0164] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes one uplink transmission configuration indication state (UL TCI state), uplink data within the second action time is sent based on a single transmission and reception point (sTRP) (sTRP PUSCH); when the uplink transmission configuration indication state corresponding to the second action time includes more than one uplink transmission configuration indication state (UL TCI state), uplink data within the second action time is sent based on multiple transmission and reception points (mTRP) (mTRP PUSCH).

[0165] In some implementations, uplink data within the second action time is sent using at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0166] In some embodiments, the terminal device determines whether to send sTRP PUSCH or mTRP PUSCH within the second action time based on the UL TCI state within the second action time.

[0167] For example, when there are two UL TCI states in the second action time, the terminal device sends mTRP PUSCH; when there is one UL TCI state in the second action time, the terminal device sends sTRP PUSCH.

[0168] For example, as shown in Case 1, if the number of UL TCI states changes from two within the action time 1 to one within the action time 2, the terminal device switches to sTRP PUSCH transmission within the action time 2. As shown in Case 2, if the number of UL TCI states changes from one within the action time 1 to two within the action time 2, the terminal device switches to mTRP PUSCH transmission within the action time 2.

[0169] The following briefly describes "at least one of the following information included and / or predefined in the parameters indicated by the third downlink control information: an SRS resource set; an SRS resource; or a TPMI." Cases 1-4 will be described later on how to use at least one of the following information included and / or predefined in the parameters indicated by the third downlink control information: an SRS resource set; an SRS resource; or a TPMI to send uplink data within the second action time. For example, refer to methods other than Method 1 in Figures 8-11.

[0170] In some implementations, the parameters indicated by the third downlink control information include and / or predefined at least one of the following information: SRS resource set; SRS resource; or TPMI sends uplink data within the second action time.

[0171] In some embodiments, the predefined at least one of the following information: SRS resource set; SRS resource; or TPMI is determined according to one of the following:

[0172] Two SRS resource sets configured;

[0173] An SRS resource set at a specific location in the two configured SRS resource sets;

[0174] An SRS resource at a specific location in at least one SRS resource within an SRS resource set;

[0175] The first SRS resource with the smallest number of SRS ports among at least one SRS resource in an SRS resource set;

[0176] An SRS resource has a TPMI at a specific location among at least one TPMI available.

[0177] For example, the SRS resource set, SRS resource, or TPMI used by the terminal device during the second action time is determined according to one of the following:

[0178] SRS resource set, SRS resource, or TPMI indicated by UL DCI;

[0179] Default (predefined) SRS resource set, SRS resource, or TPMI

[0180] For example, the terminal device determines whether to send sTRP PUSCH or mTRP PUSCH within the second action time based on the UL TCI state within the second action time, and uses the SRS resource set, SRS resource and TPMI indicated by the UL DCI within the second action time.

[0181] For example, the terminal device determines whether to send sTRP PUSCH or mTRP PUSCH within the second action time based on the UL TCI state within the second action time, and uses the default (predefined) SRS resource set, SRS resource and TPMI within the second action time.

[0182] For example, the terminal device determines one or two SRS resource sets to be used within the second action time. For example, in the case of one UL TCI state, one SRS resource set is used; in the case of two UL TCI states, two SRS resource sets are used. This is only a simple example. For how to determine the above-mentioned SRS resource set, please refer to the methods in subsequent Case 1-Case 4. For any SRS resource set, if the UL DCI indicates the SRS resource and TPMI associated therewith, the SRS resource and TPMI indicated by the UL DCI are used. If the UL DCI does not indicate the SRS resource and TPMI associated therewith, the default (predefined) SRS resource and TPMI are used.

[0183] In some embodiments, two default (predefined) SRS resource sets are the two configured SRS resource sets.

[0184] For example, the terminal device performs mTRP PUSCH transmission within the second action time and uses two default (predefined) SRS resource sets. These two default (predefined) SRS resource sets are two SRS resource sets configured by RRC signaling for mTRP PUSCH transmission.

[0185] In some embodiments, a default (predefined) SRS resource set is the first or second SRS resource set of the two configured SRS resource sets.

[0186] For example, the terminal device performs sTRP PUSCH transmission within the second action time and uses a default (predefined) SRS resource set, which is the first SRS resource set of the two configured SRS resource sets.

[0187] In some embodiments, a default (predefined) SRS resource is the first SRS resource in the SRS resource set.

[0188] For example, the terminal device performs sTRP PUSCH transmission or mTRP PUSCH transmission based on one SRS resource set or two SRS resource sets within the second action time, and uses a default (predefined) SRS resource in each SRS resource set. The default (predefined) SRS resource is the first SRS resource in the SRS resource set in which it is located.

[0189] In some embodiments, a default (predefined) SRS resource is the first SRS resource with the smallest SRS port number in the SRS resource set.

[0190] For example, the terminal device performs sTRP PUSCH transmission or mTRP PUSCH transmission based on one SRS resource set or two SRS resource sets within the second action time, and uses a default (predefined) SRS resource in each SRS resource set. The default (predefined) SRS resource is the SRS resource with the smallest number of SRS ports in the SRS resource set in which it is located. When there are multiple SRS resources with the smallest number of SRS ports, the default (predefined) SRS resource is the first SRS resource among the multiple SRS resources with the smallest number of SRS ports.

[0191] In some embodiments, a default (predefined) TPMI is the first TPMI among the TPMIs available for the SRS resource.

[0192] For example, the terminal device performs sTRP PUSCH transmission or mTRP PUSCH transmission based on one SRS resource or two SRS resources within the second action time, and a default (predefined) TPMI is associated with each SRS resource. Based on the number of SRS ports of the SRS resource and other configured parameters, multiple TPMIs (including the number of layers and precoding matrix information) available for the SRS resource can be determined, and the default (predefined) TPMI is the first TPMI among all available TPMIs.

[0193] In some embodiments, at least one of the following information associated with the uplink transmission configuration indication state (UL TCI state) within the second action time is used: an SRS resource set; an SRS resource; or TPMI is used to send uplink data within the second action time.

[0194] For example, there is a UL TCI state (UL TCI state X) within the second action time, so the terminal device determines to send sTRP PUSCH within the second action time. The terminal device determines an SRS resource set associated with UL TCI state X: for example, the source reference signal contained in UL TCI state X is an SRS resource belonging to a certain SRS resource set (SRS resource set A), then the SRS resource set associated with UL TCI state X is SRS resource set A; for another example, UL DCI has instructed the terminal device to use SRS resource set A to send PUSCH within the action time of UL TCI state X, then the SRS resource set associated with UL TCI state X is SRS resource set A. The terminal device uses SRS resource set A to send PUSCH. The SRS resource and TPMI used by the terminal device can be obtained according to any of the above methods. For example, there are two UL TCI states (UL TCI state 1-2 and UL TCI state 2-2) within the second action time, so the terminal device determines to send mTRP PUSCH within the second action time. Since SRS resource set 1 and SRS resource set 2 are associated with UL TCI state 1-2 and UL TCI state 2-2 respectively, the terminal device sends PUSCH using SRS resource set 1 and SRS resource set 2. The SRS resource and TPMI used by the terminal device can be obtained according to any of the above methods.

[0195] The following provides examples for illustrating how to determine uplink data related parameters for various cases.

[0196] The method for determining the UL TCI state, SRS resource set, SRS resource, and TPMI for Case 1-Case 4 may use any combination of the above methods, which is schematically illustrated below.

[0197] Case 1: There are 2 UL TCI states in action time 1, UL DCI indicates 2 SRS resource sets, and there is 1 UL TCI state in action time 2.

[0198] Figure 8 is an example diagram of a method for determining uplink data related parameters in Case 1 of an embodiment of the present application. Figure 8 schematically illustrates a method for determining UL TCI state, SRS resource set, SRS resource, and TPMI for PUSCH during action time 2 of Case 1.

[0199] In some embodiments, when there is a UL TCI state within the second action time, the terminal device performs mTRP PUSCH transmission within the second action time, the UL TCI state associated with the first SRS resource set is a UL TCI state within the second action time, and the UL TCI state associated with the second SRS resource set is a UL TCI state within the second action time.

[0200] In some embodiments, the terminal device sends mTRP PUSCH based on two SRS resource sets according to the parameters indicated by the third downlink control information within the second action time, and there is one UL TCI state within the second action time. In this case, the one UL TCI state is associated with two SRS resource sets.

[0201] For method 1, during action time 2, PUSCH uses two SRS resource sets, two SRS resources, and two TPMIs indicated by UL DCI, which is the same as action time 1; PUSCH uses one UL TCI state within action time 2, namely UL TCI state 1-2 (for example, indicated by DL DCI 2 in Figure 3), and the terminal device considers that the two UL TCI states associated with the two SRS resource sets are the same, both are UL TCI state 1-2. From action time 1 to action time 2, although the number of UL TCI states changes from two to one, the terminal device does not switch to sTRP PUSCH transmission during action time 2, but still performs mTRP PUSCH transmission, but considers that the two UL TCI states of mTRP PUSCH are the same, both are UL TCI state 1-2.

[0202] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes an uplink transmission configuration indication state (UL TCI state), the terminal device performs sTRP PUSCH transmission within the second action time, and uses at least one of the following information included in the parameters indicated by the third downlink control information: SRS resource set; SRS resource; or, TPMI sends uplink data within the second action time.

[0203] For method 2, within action time 2, PUSCH uses a UL TCI state within action time 2, namely UL TCI state 1-2 (for example, indicated by DL DCI 2 in Figure 3), and the terminal device considers that it switches to sTRP PUSCH transmission; PUSCH uses a default (predefined) SRS resource set (for example, the first SRS resource set), namely SRS resource set 1; since an SRS field of UL DCI indicates the SRS resource in SRS resource set 1, namely SRS resource 1, PUSCH uses SRS resource 1 indicated by UL DCI; since a TPMI field of UL DCI indicates the TPMI associated with SRS resource 1, namely TPMI 1, PUSCH uses TPMI 1 indicated by UL DCI. Similarly, the above-mentioned default (predefined) SRS resource set can also be SRS resource set 2. Accordingly, PUSCH uses SRS resource 2 and TPMI 2. For simplicity, they are not shown in the figure. From action time 1 to action time 2, the number of UL TCI states changes from two to one, so that the terminal device switches to sTRP PUSCH transmission within action time 2, and the SRS resource set used is a default (predefined) SRS resource set (SRS resource set 1 or SRS resource set 2), and the SRS resource and TPMI used are the SRS resource and TPMI associated with the SRS resource set indicated by UL DCI.

[0204] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes an uplink transmission configuration indication state (UL TCI state), the terminal device performs sTRP PUSCH transmission within the second action time and uses at least one of the following predefined information: SRS resource set; SRS resource; or TPMI to send uplink data within the second action time.

[0205] For method 3, the use of UL TCI state 1-2 and SRS resource set 1 by PUSCH is determined in the same way as method 2, and the terminal device considers that it has switched to sTRP PUSCH transmission; PUSCH uses a default (predefined) SRS resource (e.g., the first SRS resource) in SRS resource set 1; PUSCH uses a default (predefined) TPMI. For example, the default (predefined) TPMI can be obtained in the following manner: the SRS port number of the SRS resource is used as the antenna port number, and the TPMI available for the SRS resource can be obtained based on the antenna port number. The TPMI includes a precoding matrix determined by the TPMI index and the number of layers. PUSCH uses the first TPMI among the available TPMIs. Taking Table 7.3.1.1.2-2 of standard TS 38.214 V17.1.0 as an example, the table lists all TPMIs available for 4 antenna ports under certain configurations, where each row corresponds to an available TPMI. "PUSCH uses the first TPMI among the available TPMIs" is equivalent to "PUSCH uses the TPMI corresponding to the first row", that is, "1 layer: TPMI = 0".

[0206] Table 7.3.1.1.2-2: Precoding information and number of layers,for 4 antenna ports,if transform precoder is disabled,maxRank=2 or 3 or 4,and ul-FullPowerTransmission is not configured or configured to fullpowerMode2 or configured to fullpower

[0207]

[0208]

[0209] For method 4, the use of UL TCI state 1-2 and SRS resource set 1 by PUSCH is determined according to the same method as method 2, and the terminal device considers that it is switched to sTRP PUSCH transmission; PUSCH uses a default (predefined) SRS resource in SRS resource set 1; PUSCH uses a default (predefined) TPMI. The default (predefined) SRS resource can be obtained in the following way. The multiple SRS resources contained in SRS resource set 1 may have different numbers of SRS ports. The default (predefined) SRS resource is the SRS resource with the smallest number of SRS ports in SRS resource set 1. If there are multiple SRS resources with the smallest number of SRS ports, the first SRS resource among them is selected. The determination of the SRS resource here is mainly for robustness considerations. It is beneficial to ensure the robustness of the transmission by allowing the terminal device to use the simplest possible PUSCH transmission method within the action time 2. The default (predefined) TPMI can be obtained in the same way as method 3. Usually, the first TPMI corresponds to the smallest number of layers, for example, 1 layer in the above table, and thus is also conducive to ensuring transmission robustness.

[0210] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes an uplink transmission configuration indication state (UL TCI state), the terminal device performs sTRP PUSCH transmission within the second action time, and uses at least one of the following information associated with the one uplink transmission configuration indication state (UL TCI state): SRS resource set; SRS resource; or, TPMI sends uplink data within the second action time.

[0211] For method 5 or method 6, within action time 2, PUSCH uses a UL TCI state within action time 2, that is, UL TCI state 1-2, and the terminal device considers that it is switched to sTRP PUSCH transmission; the terminal device determines an SRS resource set associated with UL TCI state 1-2. For example, the source reference signal contained in UL TCI state 1-2 is an SRS resource belonging to SRS resource set 2, then the SRS resource set associated with UL TCI state 1-2 is SRS resource set 2, and the terminal device uses SRS resource set 2 to send PUSCH. For determining the SRS resource and TPMI, any of the methods described above can be used: for example, method 5, PUSCH uses a default (predefined) SRS resource (for example, the first SRS resource) in SRS resource set 2, and PUSCH uses a default (predefined) TPMI (for example, the first TPMI); for example, method 6, since UL DCI has indicated the SRS resource and TPMI associated with SRS resource set 2, PUSCH uses SRS resource 2 and TPMI2 associated with SRS resource set 2 indicated by UL DCI.

[0212] Case 2: There is one UL TCI state in action time 1, the UL DCI indicates one SRS resource set, and there are two UL TCI states in action time 2.

[0213] Figure 9 is an example diagram of a method for determining uplink data-related parameters in Case 2 of an embodiment of the present application. Taking the case where the UL DCI indicates SRS resource set 2, SRS resource 2, and TPMI 2 as an example, Figure 9 schematically illustrates the method for determining the UL TCI state, SRS resource set, SRS resource, and TPMI for the PUSCH during Action Time 2 in Case 2.

[0214] In some embodiments, when there are two UL TCI states within the second action time, the terminal device sends sTRP PUSCH according to the parameters indicated by the third downlink control information within the second action time, and uses the uplink transmission configuration indication state (UL TCI state) associated with the parameters indicated by the third downlink control information in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time to send uplink data within the second action time.

[0215] For method 1, during action time 2, PUSCH uses an SRS resource set, an SRS resource, and a TPMI indicated by UL DCI, which is the same as action time 1. The figure takes SRS resource set 2, SRS resource 2, and TPMI 2 as an example; PUSCH uses one of the two UL TCI states during action time 2. This UL TCI state is the UL TCI state associated with the SRS resource set 2 indicated by UL DCI, that is, UL TCI state 2-2. The terminal device considers that sTRP PUSCH is being sent. From action time 1 to action time 2, although the number of UL TCI states changes from one to two, the terminal device does not switch to mTRP PUSCH transmission during action time 2, but still performs sTRP PUSCH transmission. Similarly, UL DCI can also indicate SRS resource set 1, SRS resource 1, and TPMI 1. Accordingly, PUSCH uses UL TCI state 1-2. For simplicity, it is not shown in the figure.

[0216] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes two uplink transmission configuration indication states (UL TCI state), the terminal device performs mTRP PUSCH transmission within the second action time, and uses at least one of the following information included and predefined by the parameters indicated by the third downlink control information: SRS resource set; SRS resource; or TPMI to send uplink data within the second action time.

[0217] For method 2, within action time 2, PUSCH uses two UL TCI states within action time 2, namely UL TCI state 1-2 and UL TCI state 2-2, and the terminal device considers that it is switched to mTRP PUSCH transmission; since each UL TCI state needs to be associated with an SRS resource set, the terminal device uses all two SRS resource sets; PUSCH uses two SRS resource sets, namely SRS resource set 1 and SRS resource set 2; for the SRS resource associated with SRS resource set 2, since an SRS field of UL DCI indicates the SRS resource in SRS resource set 2, namely SRS resource 2, PUSCH uses SRS resource 2 indicated by UL DCI; for the SRS resource associated with SRS resource set 1, UL DCI does not indicate it, and PUSCH uses a default (predefined) SRS resource in SRS resource set 1 (for example, the first SRS resource); for the TPMI associated with SRS resource set 2, since a TPMI field of UL DCI indicates the SRS resource associated with SRS resource set 2, namely SRS resource 2, PUSCH uses SRS resource 2 indicated by UL DCI; for the SRS resource associated with SRS resource set 1, UL DCI does not indicate it, and PUSCH uses a default (predefined) SRS resource in SRS resource set 1 (for example, the first SRS resource); 2, that is, TPMI 2, PUSCH uses TPMI 2 indicated by UL DCI; for the TPMI associated with SRS resource set 1, UL DCI does not indicate it, and PUSCH uses a default (predefined) TPMI. For example, the default (predefined) TPMI can be obtained in the following way. Since the SRS resource associated with SRS resource set 1 has been obtained, the default (predefined) TPMI is the first TPMI among the TPMIs available for the SRS resource. From action time 1 to action time 2, the number of UL TCI states changes from one to two, so that the terminal device switches to mTRP PUSCH transmission within action time 2. For the SRS resource set indicated by UL DCI, the SRS resource and TPMI indicated by UL DCI are used, and for the SRS resource set not indicated by UL DCI, the default (predefined) SRS resource and TPMI are used.

[0218] Method 3 differs from Method 2 in how a default (predefined) SRS resource and a default (predefined) TPMI are determined for SRS resource set 1. In Method 3, the default (predefined) SRS resource is the first SRS resource with the smallest number of SRS ports in SRS resource set 1 (denoted as SRS resource F), and the default (predefined) TPMI is the first TPMI among the available TPMIs for SRS resource F.

[0219] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes two uplink transmission configuration indication states (UL TCI state), the terminal device performs mTRP PUSCH transmission within the second action time, and uses at least one of the following predefined information: SRS resource set; SRS resource; or TPMI to send uplink data within the second action time.

[0220] For method 4, during action time 2, PUSCH uses two UL TCI states within action time 2, namely UL TCI state 1-2 and UL TCI state 2-2, and the terminal device considers that it has switched to mTRP PUSCH transmission; PUSCH uses two SRS resource sets, namely SRS resource set 1 and SRS resource set 2; the terminal device determines two default (predefined) SRS resources and two default (predefined) TPMIs for the two SRS resource sets. For example, for each SRS resource set, PUSCH uses the first SRS resource in the SRS resource set; for each SRS resource, PUSCH uses the first TPMI among the TPMIs available for the SRS resource.

[0221] Method 5 differs from Method 4 in how two default (predefined) SRS resources and two default (predefined) TPMIs are determined for the two SRS resource sets. In Method 5, for each SRS resource set, PUSCH uses the first SRS resource with the smallest number of SRS ports in the SRS resource set; for each SRS resource, PUSCH uses the first TPMI among the available TPMIs for that SRS resource.

[0222] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes two uplink transmission configuration indication states (UL TCI state), the terminal device performs mTRP PUSCH transmission within the second action time, and uses at least one of the following information associated with the two uplink transmission configuration indication states (UL TCI state): SRS resource set; SRS resource; or, TPMI sends uplink data within the second action time.

[0223] For method 6, during action time 2, PUSCH uses the two UL TCI states within action time 2, and the terminal device considers that it has switched to mTRP PUSCH transmission; since the SRS resource sets associated with the two UL TCI states are SRS resource set 1 and SRS resource set 2, the terminal device uses these two SRS resource sets. The terminal device determines the SRS resource and TPMI for each SRS resource set and may use any of the methods described above, so method 6 may be equivalent to method 4 or method 5; for example, Figure 9 shows that method 6 uses the method of determining the SRS resource and TPMI for each SRS resource set in method 5. Alternatively, method 6 may also use the method of determining the SRS resource and TPMI for each SRS resource set in method 4, which are not listed here one by one.

[0224] Case 3: There are two UL TCI states in action time 1, the UL DCI indicates two SRS resource sets, and there are two UL TCI states in action time 2.

[0225] Figure 10 is an example diagram of a method for determining uplink data related parameters in Case 3 of an embodiment of the present application. Figure 10 schematically illustrates a method for determining UL TCI state, SRS resource set, SRS resource, and TPMI for PUSCH within action time 2 of Case 3.

[0226] In some embodiments, when there are two UL TCI states within the second action time, the terminal device sends mTRP PUSCH according to the parameters indicated by the third downlink control information within the second action time, and uses the uplink transmission configuration indication state (UL TCI state) associated with the parameters indicated by the third downlink control information in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time to send uplink data within the second action time.

[0227] For method 1, during action time 2, PUSCH uses two SRS resource sets, two SRS resources and two TPMIs indicated by UL DCI, which is the same as action time 1, and the terminal device considers that mTRP PUSCH is sent; PUSCH uses two UL TCI states associated with two SRS resource sets during action time 2, namely UL TCI state 1-2 and UL TCI state 2-2 associated with SRS resource set 1 and SRS resource set 2 respectively.

[0228] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes two uplink transmission configuration indication states (UL TCI state), the terminal device performs mTRP PUSCH transmission during the second action time, and uses at least one of the following predefined information: SRS resource set; SRS resource; or, TPMI sends uplink data within the second action time.

[0229] For Method 2, PUSCH uses two UL TCI states within Action Time 2. Since each UL TCI state must be associated with an SRS resource set, the terminal device uses both SRS resource sets. The terminal device determines two default (predefined) SRS resources and two default (predefined) TPMIs for the two SRS resource sets. For example, for each SRS resource set, PUSCH uses the first SRS resource in the SRS resource set; for each SRS resource, PUSCH uses the first TPMI among the available TPMIs for that SRS resource.

[0230] Method 3 differs from Method 2 in how two default (predefined) SRS resources and two default (predefined) TPMIs are determined for the two SRS resource sets. In Method 3, for each SRS resource set, PUSCH uses the first SRS resource with the smallest number of SRS ports in that SRS resource set; for each SRS resource, PUSCH uses the first TPMI among the available TPMIs for that SRS resource.

[0231] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes two uplink transmission configuration indication states (UL TCI state), the terminal device performs mTRP PUSCH transmission within the second action time, and uses at least one of the following information associated with the two uplink transmission configuration indication states (UL TCI state): SRS resource set; SRS resource; or, TPMI sends uplink data within the second action time.

[0232] For method 4, during action time 2, PUSCH uses the two UL TCI states within action time 2, and the terminal device considers that it has switched to mTRP PUSCH transmission; since the SRS resource sets associated with the two UL TCI states are SRS resource set 1 and SRS resource set 2, the terminal device uses these two SRS resource sets. The terminal device determines the SRS resource and TPMI for each SRS resource set and can use any of the methods described above. Therefore, method 4 can be equivalent to method 2 or method 3; for example, Figure 10 shows that method 4 uses the method of determining the SRS resource and TPMI for each SRS resource set in method 3. Alternatively, method 4 can also use the method of determining the SRS resource and TPMI for each SRS resource set in method 2, which are not listed here one by one.

[0233] Case 4: There is one UL TCI state in action time 1, the UL DCI indicates one SRS resource set, and there is one UL TCI state in action time 2.

[0234] Figure 11 is an example diagram of a method for determining uplink data-related parameters in Case 4 of an embodiment of the present application. Taking UL DCI indicating SRS resource set 2, SRS resource 2, and TPMI 2 as an example, Figure 11 schematically illustrates the method for determining the UL TCI state, SRS resource set, SRS resource, and TPMI for PUSCH during action time 2 in Case 4.

[0235] In some embodiments, when there is a UL TCI state within the second action time, the terminal device performs sTRP PUSCH transmission according to the parameters indicated by the third downlink control information within the second action time, and uses the one uplink transmission configuration indication state (UL TCI state) to send the uplink data within the second action time. For method 1, within action time 2, PUSCH uses an SRS resource set, an SRS resource, and a TPMI indicated by UL DCI, which is the same as action time 1, and the terminal device considers that sTRP PUSCH transmission is performed; since there is only one UL TCI state within action time 2, namely UL TCI state 1-2, the terminal device uses this UL TCI state to send PUSCH.

[0236] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes an uplink transmission configuration indication state (UL TCI state), the terminal device performs sTRP PUSCH transmission within the second action time, and uses at least one of the following predefined information: SRS resource set; SRS resource; or, TPMI sends uplink data within the second action time.

[0237] For method 2, PUSCH uses a UL TCI state within action time 2 for sTRP PUSCH transmission, and the terminal device determines a default (predefined) SRS resource set, a default (predefined) SRS resource, and a default (predefined) TPMI. For example, PUSCH uses the first SRS resource set, that is, SRS resource set 1, uses the first SRS resource in SRS resource set 1 (denoted as SRS resource F), and uses the first TPMI among the TPMIs available for SRS resource F.

[0238] Method 3 differs from Method 2 in how to determine a default (predefined) SRS resource and a default (predefined) TPMI. In Method 3, PUSCH uses the first SRS resource with the smallest SRS port number in SRS resource set 1 and the first TPMI available for that SRS resource.

[0239] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes an uplink transmission configuration indication state (UL TCI state), the terminal device performs sTRP PUSCH transmission within the second action time, and uses at least one of the following information associated with the one uplink transmission configuration indication state (UL TCI state): SRS resource set; SRS resource; or, TPMI sends uplink data within the second action time.

[0240] For method 4, within action time 2, PUSCH uses a UL TCI state within action time 2, namely UL TCI state 1-2, and the terminal device considers that it is switched to sTRP PUSCH transmission; the terminal device determines an SRS resource set associated with UL TCI state 1-2, for example, the source reference signal contained in UL TCI state 1-2 is an SRS resource belonging to SRS resource set 1, then the SRS resource set associated with UL TCI state 1-2 is SRS resource set 1, and the terminal device uses SRS resource set 1 to send PUSCH; for the determination of SRS resource and TPMI, any of the methods described above can be used, so method 4 can be equivalent to method 2 or method 3; for example, Figure 11 shows that method 4 uses the method for determining SRS resource and TPMI in method 3. Alternatively, method 4 can also use the method for determining SRS resource and TPMI in method 2, which are not listed one by one here.

[0241] The above description is made by taking codebook-based PUSCH transmission as an example. The following description is made of non-codebook-based PUSCH transmission.

[0242] For non-codebook based PUSCH, since TPMI does not need to be indicated, the TPMI field does not exist in the UL DCI. The SRS port number of all SRS resources in an SRS resource set is 1, so the "first SRS resource in the SRS resource set" is equivalent to the "first SRS resource with the smallest SRS port number in the SRS resource set".

[0243] In some implementations, for non-codebook based PUSCH transmission, relevant parameters may still be determined based on the methods shown in Figures 8 to 11. For example, by deleting the row containing the TPMI in Figures 8 to 11 and deleting the column containing the "first SRS resource with the smallest number of SRS ports" in Figures 8 to 11, a method for non-codebook based PUSCH transmission may be obtained, which will not be repeated here.

[0244] In some implementations, uplink data within the second action time is transmitted using part or all of the at least one uplink transmission configuration indication state (UL TCI state) corresponding to the first action time.

[0245] In some implementations, an uplink transmission configuration indication state (UL TCI state) associated with a parameter indicated by the third downlink control information among at least one uplink transmission configuration indication state (UL TCI state) corresponding to the first action time is used.

[0246] For example, the terminal device determines the UL TCI state within the second action time according to the UL TCI state indicated by the first downlink control information; the terminal device determines the relevant parameters for sending PUSCH within the second action time according to the parameters indicated by the third downlink control information; the terminal device determines whether to send sTRP PUSCH or mTRP PUSCH according to the number of UL TCI states indicated by the first downlink control information or the parameters indicated by the third downlink control information, such as the number of SRS resource sets.

[0247] For example, although there is an updated UL TCI state within the second action time (for example, DL DCI 2 in Figure 3 indicates an updated UL TCI state), the terminal device does not use the updated UL TCI state and still sends PUSCH in the same manner as when UL DCI and PUSCH are in the first action time, that is, ignores the existence of the second action time.

[0248] For example, DL DCI 1 in Figure 3 indicates UL TCI state 1-1. During the second action time, UL TCI state 1-1 is used to send uplink data; and under the premise that DL DCI 1 indicates UL TCI state 1-1, UL DCI will indicate SRS resource set 1 corresponding to UL TCI state 1-1, and then the terminal device sends sTRP PUSCH, and sends sTRP PUSCH according to at least one of SRS resource set 1, SRS resource 1, or TPMI 1 indicated by UL DCI; when DL DCI 1 indicates two UL TCI states, the uplink data sending method is similar to the above method, and they are not listed one by one here.

[0249] After determining the relevant parameters for sending the PUSCH as described above, how to send the PUSCH is described below.

[0250] In some implementations, for at least one uplink repetition (PUSCH repetition) spanning a first action time and a second action time, uplink data in the second action time starts from the first uplink repetition (PUSCH repetition) after the start time of the second action time. The uplink repetition (PUSCH repetition) includes at least one of a nominal repetition, an actual repetition, a symbol, and a time slot.

[0251] In some implementations, for a PUSCH repetition spanning at least two active times, starting from the first nominal repetition after the start time of the second active time, the PUSCH uses the UL TCI state, SRS resource set, SRS resource, and TPMI within the active time.

[0252] In some embodiments, starting from the first uplink repetition (PUSCH repetition) after the start time of the second action time, at least one uplink transmission configuration indication state (UL TCI state) and / or SRS resource set used for uplink data transmission is associated or mapped to K uplink repetitions (PUSCH repetitions), wherein the start time of the K uplink repetitions (PUSCH repetitions) is within the second action time. For example, the use of the UL TCI state, SRS resource set, SRS resource, and TPMI in the current action time continues until the first nominal repetition after the start time of the next action time. Starting from the nominal repetition, the PUSCH uses the UL TCI state, SRS resource set, SRS resource, and TPMI in the next action time, and so on.

[0253] FIG12 is a schematic diagram of PUSCH transmission according to an embodiment of the present application. For example, for PUSCH repetition type B, the PUSCH repetition spans action time 1 and action time 2. Action time 2 starts at time t2, and one nominal repetition (nominal repetition j) spans t2, i.e., crosses a slot boundary. Starting from the first nominal repetition (nominal repetition k) after t2, the PUSCH repetition uses the UL TCI state, SRS resource set, SRS resource, and TPMI within action time 2. For PUSCH repetitions before nominal repetition k, they use the UL TCI state, SRS resource set, SRS resource, and TPMI within action time 1.

[0254] FIG13 is another schematic diagram of PUSCH transmission according to an embodiment of the present application. FIG13 schematically illustrates the situation where PUSCH spans three action times, and the similarities with FIG12 are not repeated here. For PUSCH repetition type B, nominal repetition k is the first nominal repetition after the start time t2 of action time 2, and nominal repetition i is the first nominal repetition after the start time t3 of action time 3. Therefore, from nominal repetition k to nominal repetition h, the UL TCI state, SRS resource set, SRS resource, and TPMI within action time 2 are used. From nominal repetition i to the last nominal repetition in the figure, the UL TCI state, SRS resource set, SRS resource, and TPMI within action time 3 are used.

[0255] In some embodiments, when two uplink transmission configuration indication states (UL TCI states) and / or SRS resource sets are used for sending uplink data, at least two uplink transmission configuration indication states (UL TCI states) and / or SRS resource sets are mapped to the K uplink repetitions (PUSCH repetitions) in a predefined order.

[0256] In some embodiments, the predefined order is: first the first uplink transmission configuration indication state (UL TCI state) and / or SRS resource set, then the second uplink transmission configuration indication state (UL TCI state) and / or SRS resource set, or; first the second uplink transmission configuration indication state (UL TCI state) and / or SRS resource set, then the first uplink transmission configuration indication state (UL TCI state) and / or SRS resource set.

[0257] In some embodiments, for a PUSCH repetition spanning at least two action times, starting from the first nominal repetition after the start moment of the second action time, the UL TCI state and / or SRS resource set within the action time is associated or mapped to K nominal repetitions, where the start moments of the K nominal repetitions are all within the action time, also referred to as K nominal repetitions within the action time.

[0258] For example, in some action times, the association between the UL TCI state and / or SRS resource set and the nominal repetition is independently determined in each action time, that is, the association or mapping is performed again in each action time.

[0259] For example, from action time 1 to action time 2, if the number of UL TCI states changes from 1 to 2, or from 2 to 1, the previously determined association is obviously no longer applicable and needs to be re-associated or mapped within action time 2.

[0260] For example, as shown in FIG12 , the K nominal repetitions include the nominal repetitions starting from nominal repetition k within the action time 2.

[0261] For example, as shown in FIG13 , the K nominal repetitions include nominal repetition k to nominal repetition h within the action time 2.

[0262] In some embodiments, when there are two UL TCI states and / or two SRS resource sets within the second action time, the two UL TCI states and / or two SRS resource sets are mapped to K nominal repetitions in a predefined order. The predefined order is "first SRS resource set and / or UL TCI state, then second SRS resource set and / or UL TCI state", or "second SRS resource set and / or UL TCI state, then first SRS resource set and / or UL TCI state".

[0263] For example, from action time 1 to action time 2, the terminal device changes from sTRP PUSCH transmission to mTRP PUSCH transmission. Since the UL DCI determined according to action time 1 does not indicate the mapping order of mTRP PUSCH, the terminal device maps two UL TCI states and / or two SRS resource sets to K nominal repetitions according to a predefined order.

[0264] For example, as shown in Figure 12, the K nominal repetitions include the nominal repetition starting from nominal repetition k within the action time 2. When K>2 and cyclicMapping is enabled, the first and second UL TCI state and / or SRS resource set are respectively applied to the first and second nominal repetitions in the K consecutive nominal repetitions, and the same mapping method is applied to the remaining nominal repetitions in the K consecutive nominal repetitions; when K>2 and sequentialMapping is enabled, the first UL TCI state and / or SRS resource set is applied to the first and second nominal repetitions in the K consecutive nominal repetitions, the second UL TCI state and / or SRS resource set is applied to the third and fourth nominal repetitions in the K consecutive nominal repetitions, and the same mapping method is applied to the remaining nominal repetitions in the K consecutive nominal repetitions.

[0265] For example, the number of UL TCI states within action time 1 is 2. According to the indication of UL DCI, the terminal device maps the first (denoted as #1) and the second (denoted as #2) UL TCI state and SRS resource set to K=8 nominal repetitions in the order of #2, #1, #2, #1, #2, #1, #2, #1. At some point later, DL DCI indicates 2 different UL TCI states within action time 2, so that the last 4 nominal repetitions are in action time 2. The terminal device maps to the last 4 nominal repetitions in the order of #1, #2, #1, #2 (predefined order), which is equivalent to mapping to 8 nominal repetitions in the order of #2, #1, #2, #1, #1, #2, #1, #2.

[0266] In some embodiments, when an uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is used for uplink data transmission, the uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is mapped to the K uplink repetitions (PUSCH repetitions).

[0267] In some embodiments, when there is one UL TCI state and / or one SRS resource set within the second action time, the UL TCI state and / or SRS resource set is mapped to K nominal repetitions.

[0268] For example, from action time 1 to action time 2, if one UL TCI state associated with SRS resource set 2 changes to a different UL TCI state, or two UL TCI states associated with SRS resource set 1 and SRS resource set 2 respectively change to one UL TCI state, the terminal device maps one UL TCI state within action time 2 to K nominal repetitions, and maps the SRS resource set associated with the one UL TCI state to K nominal repetitions.

[0269] In some implementations, the K uplink repetitions (PUSCH repetitions) use a mapping method between an SRS resource set and an uplink repetition (PUSCH repetition) determined according to the third downlink control information.

[0270] In some embodiments, for a PUSCH repetition spanning at least two action times, the mapping method of the SRS resource set to the nominal repetition determined in the first action time before it continues to be used in the second action time, but the UL TCI state in the second action time is mapped to the nominal repetition in the second action time.

[0271] For example, the number of UL TCI states within the action time 1 is 2. According to the indication of UL DCI, the terminal device maps the first (denoted as #1) and the second (denoted as #2) UL TCI state and SRS resource set to K=8 nominal repetitions in the order of #2, #1, #2, #1, #2, #1, #2, #1. At some point later, DL DCI indicates two different UL TCI states within the action time 2, so that the last four nominal repetitions are in the action time 2. The terminal device still maps the two SRS resource sets to the last four nominal repetitions in the order of #2, #1, #2, #1, but replaces the two UL TCI states applied to the last four nominal repetitions with the two UL TCI states within the action time 2. Overall, it is equivalent to mapping the two SRS resource sets to K=8 nominal repetitions in the order of #2, #1, #2, #1, #2, #1, #2, #1. repetition, map the two UL TCI states in action time 1 to the first four nominal repetitions in the order #2, #1, #2, #1, and map the two UL TCI states in action time 2 to the last four nominal repetitions in the order #2, #1, #2, #1.

[0272] In some embodiments, the aforementioned nominal repetition may be replaced by symbols, or time slots, or actual repetitions, and other similarities are not repeated here.

[0273] For example, for a PUSCH spanning at least two action times, starting from the first symbol or time slot or actual repetition after the start time of the second action time, the PUSCH uses the UL TCI state and SRS resource set within the action time.

[0274] This is schematically illustrated in Figures 14 and 15. Figure 14 is another schematic diagram of PUSCH transmission according to an embodiment of the present application; Figure 15 is another schematic diagram of PUSCH transmission according to an embodiment of the present application.

[0275] As shown in Figures 14 and 15 , both start from the first symbol after action time 2, starting time t2. PUSCH uses the UL TCI state and SRS resource set within action time 2. Figure 14 takes PUSCH repetition type A as an example. In this case, "starting from the first symbol after t2" is equivalent to "starting from the first time slot after t2." Figure 15 takes PUSCH repetition type B as an example. A nominal repetition crosses the time slot boundary t2 and is therefore split into two actual repetitions (j, k). In this case, "starting from the first symbol after t2" is equivalent to "starting from the first actual repetition after t2."

[0276] For example, when there are two UL TCI states and / or two SRS resource sets within the second action time, the two UL TCI states and / or two SRS resource sets are mapped to K′ actual repetitions within the second action time according to a predefined order.

[0277] Figure 15 illustrates this. Starting from the first actual repetition after t2, the two UL TCI states and / or two SRS resource sets are mapped to K' actual repetitions within action time 2. The mapping method is the same as before, except that the previous "nominal repetition" is replaced by "actual repetition".

[0278] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0279] As can be seen from the above embodiment, the terminal device determines the relevant parameters for uplink data transmission within the second action time based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. As a result, ambiguity in the use of the relevant parameters for uplink data transmission can be avoided, thereby avoiding the resulting uplink data transmission failure.

[0280] Embodiments of the second aspect

[0281] The embodiment of the present application provides an uplink data transmission method, which is applied to a terminal device side. The embodiment of the present application can be combined with the embodiment of the first aspect, or can be implemented independently. The content that is the same as the embodiment of the first aspect is not repeated here.

[0282] FIG16 is another schematic diagram of the uplink data sending method according to an embodiment of the present application. As shown in FIG16 , the method includes:

[0283] 1601, the terminal device receives third downlink control information for scheduling uplink data within a first action time, and the terminal device sends the uplink data within the first action time; and

[0284] 1602. The terminal device determines, based on at least one of the SRS resource set, SRS resource, or TPMI indicated by the third downlink control information, whether to send the uplink data based on a single transmission and reception point (sTRP), or to send the uplink data based on multiple transmission and reception points (mTRP).

[0285] Thus, the terminal device only transmits uplink data during the first action time, and can determine relevant parameters associated with the uplink data, such as at least one of the SRS resource set, SRS resource, or TPMI. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failures caused by this.

[0286] For the specific definitions of the above-mentioned “first action time”, “third downlink control information”, “uplink data transmission based on a single transmission and reception point (sTRP)”, “uplink data transmission based on multiple transmission and reception points (mTRP)” and “SRS resource set, SRS resource, or TPMI”, please refer to the embodiments of the first aspect and will not be repeated here.

[0287] Figure 17 is another schematic diagram of the signaling transmission process of an embodiment of the present application. For example, as shown in Figure 17, the PUSCH scheduling based on UL DCI is restricted, for example, UL DCI and PUSCH are restricted to be at the same action time. In other words, the terminal device expects UL DCI and its scheduled PUSCH to be at the same action time. In this case, the terminal device uses the UL TCI state within the action time (for example, the UL TCI state indicated by DL DCI 1), and determines the SRS resource set, UL TCI state and SRS resource set based on the SRS resource set indicator field of UL DCI; and determines whether to send based on sTRP PUSCH or mTRP PUSCH according to the SRS resource set. Thus, the relevant parameters associated with the uplink data can be determined.

[0288] It is worth noting that Figures 16 and 17 above are merely schematic illustrations of the embodiments of the present application, using a terminal device as an example, but the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, other operations may be added or some operations may be removed, and the objects of the aforementioned operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the descriptions of Figures 16 and 17 above.

[0289] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0290] As can be seen from the above embodiment, the terminal device only transmits uplink data during the first action time, and is able to determine relevant parameters associated with the uplink data, such as at least one of the SRS resource set, SRS resource, or TPMI. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failures caused by this.

[0291] Embodiments of the third aspect

[0292] The embodiment of the present application provides an uplink data transmission method, which is applied to a terminal device. The embodiment of the present application can be combined with the embodiment of the first aspect, or can be implemented independently. The contents that are the same as those of the embodiments of the first and second aspects are not repeated here.

[0293] FIG18 is another schematic diagram of the uplink data sending method according to an embodiment of the present application. As shown in FIG18 , the method includes:

[0294] 1801. The terminal device receives, within a first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within a second action time; and

[0295] 1802. The terminal device does not send uplink data within the second action time.

[0296] As a result, the terminal device only sends uplink data during the first operating time and does not send uplink data during the second operating time, thereby being able to determine the relevant parameters associated with the uplink data during the first operating time. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failure caused by this.

[0297] For the specific limitations of the above-mentioned "first action time", "third downlink control information" and other contents, please refer to the embodiments of the first aspect and will not be repeated here; for example, the relevant parameters of the uplink data within the first action time can be determined by referring to the embodiments of the above-mentioned second scheme.

[0298] Figure 19 is another schematic diagram of the signaling sending process of an embodiment of the present application. For example, as shown in Figure 19, the action time of the UL TCI state indicated by DL DCI 1 (the first action time: action time 1, Application time 1), the terminal device uses the UL TCI state within the action time (for example, the UL TCI state indicated by DL DCI 1), and determines the SRS resource set, UL TCI state and SRS resource set based on the SRS resource set indicator field of UL DCI; and determines whether to send based on sTRP PUSCH or mTRP PUSCH according to the SRS resource set, thereby determining the relevant parameters associated with the uplink data; for the second action time (Application time 2), the terminal device discards PUSCH, that is, does not send PUSCH at the second action time. Thus, ambiguity in the use of relevant parameters for uplink data transmission can be avoided, thereby avoiding the resulting uplink data transmission failure.

[0299] It is worth noting that Figures 18 and 19 above are merely schematic illustrations of embodiments of the present application, using a terminal device as an example, but the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, other operations may be added or some operations may be removed, and the objects of the aforementioned operations may be adjusted. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the descriptions of Figures 18 and 19 above.

[0300] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0301] As can be seen from the above embodiment, the terminal device only sends uplink data during the first active time and does not send uplink data during the second active time. Therefore, it is possible to determine the relevant parameters associated with the uplink data during the first active time. This avoids ambiguity in the use of the relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failure caused by this.

[0302] Embodiments of the fourth aspect

[0303] The embodiment of the present application provides an uplink data receiving method, which is applied to a network device. The embodiment of the present application can be combined with the embodiment of the first aspect, or can be implemented independently. The contents that are the same as those of the embodiment of the first aspect are not repeated here.

[0304] FIG20 is a schematic diagram of a method for receiving uplink data according to an embodiment of the present application. As shown in FIG20 , the method includes:

[0305] At 2001, the network device sends, to a terminal device within a first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within a second action time; wherein the terminal device is configured with two SRS resource sets;

[0306] 2002, the network device receives the uplink data within the second action time, wherein the terminal device determines, according to the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, to send the uplink data within the second action time based on a single transmission and reception point (sTRP) or to send the uplink data based on multiple transmission and reception points (mTRP).

[0307] It is worth noting that FIG20 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be removed. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG20 above.

[0308] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0309] As can be seen from the above embodiment, the terminal device determines the relevant parameters for uplink data transmission within the second action time based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. As a result, ambiguity in the use of the relevant parameters for uplink data transmission can be avoided, thereby avoiding the resulting uplink data transmission failure.

[0310] Embodiments of the fifth aspect

[0311] The embodiment of the present application provides an uplink data receiving method, which is applied to a network device. The embodiment of the present application can be combined with the embodiment of the first aspect, or implemented independently. The contents that are the same as those of the embodiment of the second aspect are not repeated here.

[0312] FIG21 is another schematic diagram of the uplink data receiving method according to an embodiment of the present application. As shown in FIG21 , the method includes:

[0313] 2101. The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time; wherein the terminal device is configured with two SRS resource sets.

[0314] 2102, the network device receives the uplink data within the first action time, wherein the terminal device determines, based on at least one of the SRS resource set, SRS resource, or TPMI indicated by the third downlink control information, to send the uplink data based on a single transmission and reception point (sTRP), or to send the uplink data based on multiple transmission and reception points (mTRP).

[0315] It is worth noting that FIG21 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be removed. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG21 above.

[0316] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0317] As can be seen from the above embodiment, the terminal device only transmits uplink data during the first action time, and is able to determine relevant parameters associated with the uplink data, such as at least one of the SRS resource set, SRS resource, or TPMI. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failures caused by this.

[0318] Embodiments of the sixth aspect

[0319] The embodiment of the present application provides an uplink data receiving method, which is applied to a network device. The embodiment of the present application can be combined with the embodiment of the first aspect, or implemented independently. The contents that are the same as those of the embodiment of the third aspect are not repeated here.

[0320] FIG22 is another schematic diagram of the uplink data receiving method according to an embodiment of the present application. As shown in FIG22 , the method includes:

[0321] 2201. The network device sends, to a terminal device within a first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within a second action time; wherein the terminal device is configured with two SRS resource sets;

[0322] 2202. The network device does not receive uplink data within the second action time within the second action time, wherein the terminal device does not send uplink data within the second action time.

[0323] It is worth noting that FIG22 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG22 above.

[0324] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0325] As can be seen from the above embodiment, the terminal device only sends uplink data during the first active time and does not send uplink data during the second active time. Therefore, it is possible to determine the relevant parameters associated with the uplink data during the first active time. This avoids ambiguity in the use of the relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failure caused by this.

[0326] Embodiments of the seventh aspect

[0327] An embodiment of the present application provides an uplink data transmission device. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device, wherein the terminal device is configured with two SRS resource sets. In addition, the same contents as those in the embodiment of the first aspect are not repeated here.

[0328] FIG23 is a schematic diagram of an uplink data transmitting apparatus according to an embodiment of the present application. As shown in FIG23 , the uplink data transmitting apparatus 2300 includes:

[0329] The first receiving unit 2301 receives third downlink control information for scheduling uplink data during a first action time, wherein at least part of the uplink data is within a second action time.

[0330] The first sending unit 2302 determines, according to the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data based on a single transmission and reception point (sTRP) for the uplink data within the second action time, or to send uplink data based on multiple transmission and reception points (mTRP).

[0331] In some embodiments, the uplink data includes at least one of the following uplink data types:

[0332] Uplink repetition (PUSCH repetition) Type A (Type A);

[0333] Uplink repetition (PUSCH repetition) Type B (Type B); or

[0334] PUSCH sent simultaneously by multiple panels.

[0335] In some implementations, the first receiving unit receives first downlink control information corresponding to a first action time; and receives second downlink control information corresponding to a second action time within the first action time.

[0336] In some implementations, the parameter indicated by the third downlink control information includes at least one of an SRS resource set, an SRS resource, or an uplink precoding index (TPMI).

[0337] In some implementations, the parameter is indicated by an SRS resource set indicator field in the third downlink control information.

[0338] In some implementations, the second downlink control information indicates at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0339] In some embodiments, uplink data within the second action time is sent using part or all of at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time or corresponding to the first action time.

[0340] In some embodiments, when the parameter indicated by the third downlink control information includes an SRS resource set (SRS resource set), uplink data within the second action time is sent based on a single transmission and reception point (sTRP); when the parameter includes more than one SRS resource set (SRS resource set), uplink data within the second action time is sent based on multiple transmission and reception points (mTRP).

[0341] In some embodiments, when uplink data within the second action time is sent based on multiple transmission and reception points (mTRP), and the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes an uplink transmission configuration indication state (UL TCI state), the one uplink transmission configuration indication state (UL TCI state) is associated with more than one SRS resource set.

[0342] In some embodiments, an uplink transmission configuration indication state (UL TCI state) associated with the parameter in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time or the first action time is used, or a predefined uplink transmission configuration indication state (UL TCI state) in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time is used to send uplink data within the second action time.

[0343] In some implementations, the predefined uplink transmission configuration indication state (UL TCI state) is an uplink transmission configuration indication state (UL TCI state) at a specific position in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0344] In some implementations, at least one of the following information in the parameter: an SRS resource set, an SRS resource, or a transmit precoding matrix indicator (TPMI) is used to transmit uplink data within the second action time.

[0345] In some embodiments, when the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes one uplink transmission configuration indication state (UL TCI state), uplink data in the second action time is sent based on a single transmission and reception point (sTRP); when the uplink transmission configuration indication state corresponding to the second action time includes more than one uplink transmission configuration indication state (UL TCI state), uplink data in the second action time is sent based on multiple transmission and reception points (mTRP).

[0346] In some implementations, at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time is used to send the uplink data within the second action time.

[0347] In some embodiments, at least one of the following information included and / or predefined by the parameter is used: an SRS resource set, an SRS resource, or a transmit precoding matrix indicator (TPMI) to send uplink data within the second action time.

[0348] In some implementations, the at least one of the predefined information: SRS resource set, SRS resource, or TPMI is determined according to one of the following:

[0349] Two configured SRS resource sets (SRS resource sets);

[0350] An SRS resource set (SRS resource set) at a specific location in the two configured SRS resource sets (SRS resource sets);

[0351] An SRS resource at a specific location in at least one SRS resource within an SRS resource set;

[0352] The first SRS resource with the smallest number of SRS ports among at least one SRS resource in an SRS resource set;

[0353] An SRS resource is a TPMI at a specific location in at least one TPMI available to it.

[0354] In some embodiments, at least one of the following information associated with the one uplink transmission configuration indication state (UL TCI state) or the more than one uplink transmission configuration indication state (UL TCI state) is used: SRS resource set; SRS resource; or TPMI sends uplink data within the second action time

[0355] In some embodiments, for at least one uplink repetition (PUSCH repetition) spanning a first action time and a second action time, uplink data in the second action time starts from the first uplink repetition (PUSCH repetition) after the start time of the second action time.

[0356] In some embodiments, starting from the first uplink repetition (PUSCH repetition) after the start moment of the second action time, at least one uplink transmission configuration indication state (UL TCI state) and / or SRS resource set used for sending the uplink data is associated or mapped to K uplink repetitions (PUSCH repetitions), wherein the start moment of the K uplink repetitions (PUSCH repetitions) is within the second action time.

[0357] In some embodiments, when two uplink transmission configuration indication states (UL TCI states) and / or SRS resource sets are used for sending uplink data, the at least two uplink transmission configuration indication states (UL TCI states) and / or SRS resource sets are mapped to the K uplink repetitions (PUSCH repetitions) in a predefined order.

[0358] In some embodiments, the predefined order is:

[0359] First, the first uplink transmission configuration indication state (UL TCI state) and / or SRS resource set, and then the second uplink transmission configuration indication state (UL TCI state) and / or SRS resource set, or;

[0360] The second uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is displayed first, and then the first uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is displayed.

[0361] In some embodiments, when an uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is used for uplink data transmission, the uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is mapped to K uplink repetitions (PUSCH repetitions).

[0362] In some implementations, the K uplink repetitions (PUSCH repetitions) use a mapping method between the SRS resource set and the uplink repetition (PUSCH repetition) determined according to the third downlink control information.

[0363] In some implementations, the uplink repetition (PUSCH repetition) includes at least one of nominal repetition, actual repetition, symbol, and time slot.

[0364] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0365] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data transmitting apparatus 2300 may also include other components or modules, and for the specific contents of these components or modules, reference may be made to the relevant art.

[0366] In addition, for the sake of simplicity, FIG23 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0367] As can be seen from the above embodiment, the terminal device determines the relevant parameters for uplink data transmission within the second action time based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. As a result, ambiguity in the use of the relevant parameters for uplink data transmission can be avoided, thereby avoiding the resulting uplink data transmission failure.

[0368] Embodiments of the eighth aspect

[0369] An embodiment of the present application provides an uplink data transmission device. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device, wherein the terminal device is configured with two SRS resource sets. In addition, the contents identical to those in the embodiment of the second aspect are not repeated here.

[0370] FIG24 is another schematic diagram of an uplink data transmitting apparatus according to an embodiment of the present application. As shown in FIG24 , an uplink data transmitting apparatus 2400 includes:

[0371] The second receiving unit 2401 receives, within a first action time, third downlink control information for scheduling uplink data, and the terminal device sends the uplink data within the first action time;

[0372] The second sending unit 2402 determines, based on at least one of the SRS resource set (SRS resource set), the SRS resource (SRS resource), or the TPMI indicated by the third downlink control information, whether to send uplink data based on a single transmission and reception point (sTRP) for the uplink data, or to send uplink data based on multiple transmission and reception points (mTRP).

[0373] Thus, the terminal device only transmits uplink data during the first action time, and can determine relevant parameters associated with the uplink data, such as at least one of the SRS resource set, SRS resource, or TPMI. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failures caused by this.

[0374] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0375] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data sending device 2400 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0376] In addition, for the sake of simplicity, FIG24 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0377] As can be seen from the above embodiment, the terminal device only transmits uplink data during the first action time, and is able to determine relevant parameters associated with the uplink data, such as at least one of the SRS resource set, SRS resource, or TPMI. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failures caused by this.

[0378] Embodiments of the ninth aspect

[0379] An embodiment of the present application provides an uplink data transmission device. The device may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device, wherein the terminal device is configured with two SRS resource sets. In addition, the contents identical to those in the embodiment of the third aspect are not repeated here.

[0380] FIG25 is a schematic diagram of an uplink data transmitting apparatus according to an embodiment of the present application. As shown in FIG25 , an uplink data transmitting apparatus 2500 includes:

[0381] A third receiving unit 2501 is configured to receive, within the first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within the second action time;

[0382] The third sending unit 2502 does not send the uplink data within the second action time.

[0383] As a result, the terminal device only sends uplink data during the first operating time and does not send uplink data during the second operating time, thereby being able to determine the relevant parameters associated with the uplink data during the first operating time. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failure caused by this.

[0384] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0385] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data sending device 2500 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0386] In addition, for the sake of simplicity, FIG25 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0387] As can be seen from the above embodiment, the terminal device only sends uplink data during the first active time and does not send uplink data during the second active time. Therefore, it is possible to determine the relevant parameters associated with the uplink data during the first active time. This avoids ambiguity in the use of the relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failure caused by this.

[0388] Embodiments of the tenth aspect

[0389] The embodiment of the present application provides an uplink data receiving device, which may be, for example, a network device, or one or more components or assemblies configured in the network device, and the same contents as those in the embodiment of the first aspect will not be repeated.

[0390] FIG26 is a schematic diagram of an uplink data receiving apparatus according to an embodiment of the present application. As shown in FIG26 , the uplink data receiving apparatus 2600 includes:

[0391] A first transmitting unit 2601 transmits third downlink control information for scheduling uplink data to a terminal device within a first action time, wherein the uplink data is at least partially within a second action time; wherein the terminal device is configured with two SRS resource sets; and

[0392] A first receiving unit 2602 receives uplink data within the second action time, wherein the terminal device determines, based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data based on a single transmission and reception point (sTRP) for the uplink data within the second action time, or to send uplink data based on multiple transmission and reception points (mTRP).

[0393] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0394] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data receiving device 2600 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0395] In addition, for the sake of simplicity, FIG26 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0396] As can be seen from the above embodiment, the terminal device determines the relevant parameters for uplink data transmission within the second action time based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time. As a result, ambiguity in the use of the relevant parameters for uplink data transmission can be avoided, thereby avoiding the resulting uplink data transmission failure.

[0397] Embodiment of the eleventh aspect

[0398] The embodiment of the present application provides an uplink data receiving device, which may be, for example, a network device, or one or more components or assemblies configured in the network device, and the same contents as those in the embodiment of the second aspect will not be repeated here.

[0399] FIG27 is another schematic diagram of an uplink data receiving apparatus according to an embodiment of the present application. As shown in FIG27 , the uplink data receiving apparatus 2700 includes:

[0400] A second sending unit 2701 is configured to send third downlink control information for scheduling uplink data to a terminal device within a first action time; wherein the terminal device is configured with two SRS resource sets; and

[0401] The second receiving unit 2702 receives the uplink data within the first action time, wherein the terminal device determines, based on at least one of the SRS resource set (SRS resource set), SRS resource (SRS resource), or TPMI indicated by the third downlink control information, to send the uplink data based on a single transmission and reception point (sTRP), or to send the uplink data based on multiple transmission and reception points (mTRP).

[0402] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0403] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data receiving device 2700 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0404] In addition, for the sake of simplicity, FIG27 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0405] As can be seen from the above embodiment, the terminal device only transmits uplink data during the first action time, and is able to determine relevant parameters associated with the uplink data, such as at least one of the SRS resource set, SRS resource, or TPMI. This avoids ambiguity in the use of relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failures caused by this.

[0406] Embodiments of the twelfth aspect

[0407] The embodiment of the present application provides an uplink data receiving device, which may be, for example, a network device, or one or more components or assemblies configured in the network device, and the contents identical to those in the embodiment of the third aspect will not be repeated.

[0408] FIG28 is another schematic diagram of an uplink data receiving apparatus according to an embodiment of the present application. As shown in FIG28 , the uplink data receiving apparatus 2800 includes:

[0409] a third receiving unit 2801 configured to send, to a terminal device within the first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within the second action time; wherein the terminal device is configured with two SRS resource sets; and

[0410] The third sending unit 2802 does not receive the uplink data within the second action time within the second action time, wherein the terminal device does not send the uplink data within the second action time.

[0411] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0412] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The uplink data receiving device 2800 may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0413] In addition, for the sake of simplicity, FIG28 only illustrates the connection relationship or signal direction between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connection can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0414] As can be seen from the above embodiment, the terminal device only sends uplink data during the first active time and does not send uplink data during the second active time. Therefore, it is possible to determine the relevant parameters associated with the uplink data during the first active time. This avoids ambiguity in the use of the relevant parameters for uplink data transmission, thereby avoiding uplink data transmission failure caused by this.

[0415] Embodiments of the thirteenth aspect

[0416] An embodiment of the present application also provides a communication system, and reference may be made to FIG1 . The contents that are the same as those in the embodiments of the first to twelfth aspects will not be repeated here.

[0417] In some embodiments, the communication system 100 may include at least:

[0418] A network device that sends third downlink control information for scheduling uplink data to a terminal device within a first action time, wherein at least part of the uplink data is within a second action time; and

[0419] The terminal device is configured with two SRS resource sets (SRS resource sets); the terminal device determines, according to the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, to perform uplink data transmission based on a single transmission and reception point (sTRP) for the uplink data within the second action time, or to perform uplink data transmission based on multiple transmission and reception points (mTRP),

[0420] The network device receives uplink data within the second action time.

[0421] In some embodiments, the communication system 100 may further include at least:

[0422] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time; and

[0423] The terminal device is configured with two SRS resource sets (SRS resource sets), and the terminal device determines, based on at least one of the SRS resource set indicated by the third downlink control information, the SRS resource, and the TPMI, to send the uplink data based on a single transmission and reception point (sTRP), or to send the uplink data based on multiple transmission and reception points (mTRP),

[0424] The network device receives the uplink data within the first action time.

[0425] In some embodiments, the communication system 100 may further include at least:

[0426] A network device that sends, to the terminal device within the first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within the second action time; and

[0427] A terminal device is configured with two SRS resource sets; the terminal device does not send uplink data within the second action time; and

[0428] The network device does not receive uplink data within the second action time within the second action time.

[0429] An embodiment of the present application further provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0430] Figure 29 is a schematic diagram of the structure of a network device according to an embodiment of the present application. As shown in Figure 29, network device 2900 may include a processor 2910 (e.g., a central processing unit (CPU)) and a memory 2920; the memory 2920 is coupled to the processor 2910. The memory 2920 may store various data and may also store an information processing program 2930, which is executed under the control of the processor 2910.

[0431] In addition, as shown in Figure 29, network device 2900 may also include: a transceiver 2940 and an antenna 2950; wherein, the functions of the above components are similar to those in the prior art and are not described here in detail. It is worth noting that network device 2900 does not necessarily include all the components shown in Figure 29; in addition, network device 2900 may also include components not shown in Figure 29, and reference may be made to the prior art for details.

[0432] The embodiment of the present application also provides a terminal device, but the present application is not limited thereto and may also be other devices.

[0433] Figure 30 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 30 , the terminal device 3000 may include a processor 3010 and a memory 3020. The memory 3020 stores data and programs and is coupled to the processor 3010. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0434] For example, the processor 3010 may be configured to execute a program to implement the uplink data transmission method as described in the embodiment of the first aspect. For example, the processor 3010 may be configured to perform the following control: being configured with two SRS resource sets (SRS resource sets); receiving third downlink control information for scheduling uplink data within a first action time, wherein the uplink data is at least partially within a second action time; and determining, based on parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to perform uplink data transmission based on a single transmission and reception point (sTRP) for the uplink data within the second action time, or to perform uplink data transmission based on multiple transmission and reception points (mTRP).

[0435] As shown in Figure 30 , the terminal device 3000 may further include: a communication module 3030, an input unit 3040, a display 3050, and a power supply 3060. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 3000 does not necessarily include all of the components shown in Figure 30 , and these components are not essential. Furthermore, the terminal device 3000 may also include components not shown in Figure 30 , for which reference may be made to the prior art.

[0436] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the uplink data sending method described in the embodiments of the first to third aspects.

[0437] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the uplink data sending method described in the embodiments of the first to third aspects.

[0438] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program enables the terminal device to execute the uplink data receiving method described in the embodiments of the fourth to sixth aspects.

[0439] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the uplink data receiving method described in the embodiments of the fourth to sixth aspects.

[0440] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0441] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0442] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0443] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0444] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0445] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0446] 1. A method for transmitting uplink data, applied to a terminal device, wherein the terminal device is configured with two SRS resource sets, the method comprising:

[0447] The terminal device receives third downlink control information for scheduling uplink data within the first action time, wherein at least part of the uplink data is within the second action time; and

[0448] The terminal device determines, based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data within the second action time based on a single transmission and reception point (sTRP), or to send uplink data based on multiple transmission and reception points (mTRP).

[0449] 2. The method according to Supplement 1, wherein:

[0450] The uplink data includes at least one of the following uplink data types:

[0451] Uplink repetition (PUSCH repetition) Type A (Type A);

[0452] Uplink repetition (PUSCH repetition) Type B (Type B); or

[0453] PUSCH sent simultaneously by multiple panels.

[0454] 3. The method according to Note 1, wherein the terminal device receives first downlink control information corresponding to the first action time; and

[0455] Second downlink control information corresponding to the second action time is received within the first action time.

[0456] 4. The method according to Supplement 1, wherein:

[0457] The parameter includes at least one of SRS resource set, SRS resource, or TPMI.

[0458] 5. The method according to Supplement 4, wherein:

[0459] The parameter is indicated by an SRS resource set indicator field in the third downlink control information.

[0460] 6. The method according to Supplement 3, wherein:

[0461] The second downlink control information indicates the at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0462] 7. The method according to Supplement 1, wherein:

[0463] Uplink data within the second action time is sent using part or all of at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time or corresponding to the first action time.

[0464] 8. The method according to Supplementary Note 7, wherein:

[0465] When the parameter includes an SRS resource set, uplink data within the second action time is sent based on a single transmission and reception point (sTRP);

[0466] In a case where the parameter includes more than one SRS resource set, uplink data within the second action time is sent based on multiple transmission and reception points (mTRP).

[0467] 9. The method according to Supplementary Note 8, wherein:

[0468] When uplink data within the second action time is sent based on multiple transmission and reception points (mTRP), and the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes an uplink transmission configuration indication state (UL TCI state), the one uplink transmission configuration indication state (UL TCI state) is associated with the more than one SRS resource set.

[0469] 10. The method according to Supplementary Note 8, wherein:

[0470] The uplink data within the second action time is sent using an uplink transmission configuration indication state (UL TCI state) associated with the parameter in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time or corresponding to the first action time, or using a predefined uplink transmission configuration indication state (UL TCI state) in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0471] 11. The method according to Supplementary Note 10, wherein:

[0472] The predefined uplink transmission configuration indication state (UL TCI state) is an uplink transmission configuration indication state (UL TCI state) at a specific position in the at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0473] 12. The method according to Supplementary Note 8, wherein:

[0474] At least one of the following information in the parameters is used: SRS resource set; SRS resource; or TPMI to send the uplink data within the second action time.

[0475] 13. The method according to Supplementary Note 7, wherein:

[0476] When the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes one uplink transmission configuration indication state (UL TCI state), uplink data within the second action time is sent based on a single transmission and reception point (sTRP);

[0477] In a case where the uplink transmission configuration indication state corresponding to the second action time includes more than one uplink transmission configuration indication state (UL TCI state), uplink data within the second action time is sent based on multiple transmission and reception points (mTRP).

[0478] 14. The method according to Supplement 13, wherein:

[0479] Uplink data within the second action time is sent using at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

[0480] 15. The method according to Supplement 13, wherein:

[0481] At least one of the following information included in and / or predefined by the parameters is used: SRS resource set; SRS resource; or TPMI sends uplink data within the second action time.

[0482] 16. The method according to note 15, wherein at least one of the predefined information is: an SRS resource set; an SRS resource; or a TPMI is determined according to one of the following:

[0483] Two SRS resource sets configured;

[0484] An SRS resource set at a specific location in the two configured SRS resource sets;

[0485] An SRS resource at a specific location in at least one SRS resource within an SRS resource set;

[0486] The first SRS resource with the smallest number of SRS ports among at least one SRS resource in an SRS resource set;

[0487] An SRS resource has a TPMI at a specific location among at least one TPMI available.

[0488] 17. The method according to Supplement 13, wherein:

[0489] At least one of the following information associated with the one uplink transmission configuration indication state (UL TCI state) or the more than one uplink transmission configuration indication state (UL TCI state) is used: an SRS resource set; an SRS resource; or TPMI sends the uplink data within the second action time.

[0490] 18. The method according to any one of Notes 1 to 17, wherein:

[0491] For at least one uplink repetition (PUSCH repetition) spanning the first action time and the second action time, uplink data in the second action time starts from the first uplink repetition (PUSCH repetition) after the start time of the second action time.

[0492] 19. The method according to Supplement 18, wherein:

[0493] Starting from the first uplink repetition (PUSCH repetition) after the start moment of the second action time, at least one uplink transmission configuration indication state (UL TCI state) and / or SRS resource set used for sending the uplink data is associated or mapped to K uplink repetitions (PUSCH repetitions), wherein the start moment of the K uplink repetitions (PUSCH repetitions) is within the second action time.

[0494] 20. The method according to Supplement 19, wherein:

[0495] In a case where two uplink transmission configuration indication states (UL TCI states) and / or SRS resource sets are used for sending the uplink data, the at least two uplink transmission configuration indication states (UL TCI states) and / or SRS resource sets are mapped to the K uplink repetitions (PUSCH repetitions) in a predefined order.

[0496] 21. The method according to Supplementary Note 20, wherein the predefined order is:

[0497] First, the first uplink transmission configuration indication state (UL TCI state) and / or SRS resource set, and then the second uplink transmission configuration indication state (UL TCI state) and / or SRS resource set, or;

[0498] The second uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is displayed first, and then the first uplink transmission configuration indication state (UL TCI state) and / or SRS resource set is displayed.

[0499] 22. The method according to Supplement 19, wherein:

[0500] In a case where an uplink transmission configuration indication state (UL TCI state) and / or an SRS resource set is used for transmitting the uplink data, the uplink transmission configuration indication state (UL TCI state) and / or the SRS resource set is mapped to the K uplink repetitions (PUSCH repetitions).

[0501] 23. The method according to Supplement 19, wherein:

[0502] The K uplink repetitions (PUSCH repetitions) use a mapping method between the SRS resource set and the uplink repetition (PUSCH repetition) determined according to the third downlink control information.

[0503] 24. The method according to any one of Notes 18 to 23, wherein:

[0504] The uplink repetition (PUSCH repetition) includes at least one of nominal repetition, actual repetition, symbol, and time slot.

[0505] 25. A method for transmitting uplink data, applied to a terminal device, wherein the terminal device is configured with two SRS resource sets, the method comprising:

[0506] The terminal device receives third downlink control information for scheduling uplink data within a first action time, and the terminal device sends the uplink data within the first action time; and

[0507] The terminal device determines to send the uplink data based on a single transmission and reception point (sTRP) based on at least one of the SRS resource set, SRS resource, or TPMI indicated by the third downlink control information, or to send the uplink data based on multiple transmission and reception points (mTRP).

[0508] 26. A method for transmitting uplink data, applied to a terminal device, wherein the terminal device is configured with two SRS resource sets, the method comprising:

[0509] The terminal device receives third downlink control information for scheduling uplink data within the first action time, wherein at least part of the uplink data is within the second action time; and

[0510] The terminal device does not send uplink data within the second action time.

[0511] 27. A method for receiving uplink data, applied to a network device, wherein the terminal device is configured with two SRS resource sets, the method comprising:

[0512] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time, wherein at least part of the uplink data is within the second action time; and

[0513] The network device receives uplink data within the second action time, wherein the terminal device determines, based on the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, to send uplink data based on a single transmission and reception point (sTRP) or to send uplink data based on multiple transmission and reception points (mTRP).

[0514] 28. A method for receiving uplink data, applied to a network device, wherein a terminal device is configured with two SRS resource sets, the method comprising:

[0515] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time;

[0516] The network device receives the uplink data within the first action time, wherein:

[0517] The terminal device determines to send the uplink data based on a single transmission and reception point (sTRP) based on at least one of the SRS resource set, SRS resource, or TPMI indicated by the third downlink control information, or to send the uplink data based on multiple transmission and reception points (mTRP).

[0518] 29. A method for receiving uplink data, applied to a network device, wherein the terminal device is configured with two SRS resource sets, the method comprising:

[0519] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time, wherein at least part of the uplink data is within the second action time; and

[0520] The network device does not receive the uplink data within the second action time during the second action time, wherein the terminal device does not send the uplink data within the second action time.

[0521] 30. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the uplink data sending method as described in any one of Notes 1 to 26.

[0522] 31. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the uplink data receiving method as described in any one of Notes 27 to 29.

[0523] 32. A communication system comprising:

[0524] A network device that sends third downlink control information for scheduling uplink data to a terminal device within a first action time, wherein at least part of the uplink data is within a second action time; and

[0525] The terminal device is configured with two SRS resource sets (SRS resource sets); the terminal device determines, according to the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, to send uplink data based on a single transmission and reception point (sTRP) for the uplink data within the second action time, or to send uplink data based on multiple transmission and reception points (mTRP),

[0526] The network device receives uplink data within the second action time.

[0527] 33. A communication system comprising:

[0528] The network device sends third downlink control information for scheduling uplink data to the terminal device within the first action time; and

[0529] The terminal device is configured with two SRS resource sets (SRS resource sets), and the terminal device determines, based on at least one of the SRS resource set, the SRS resource, and the TPMI indicated by the third downlink control information, to send the uplink data based on a single transmission and reception point (sTRP), or to send the uplink data based on multiple transmission and reception points (mTRP),

[0530] The network device receives the uplink data within the first action time.

[0531] 34. A communication system comprising:

[0532] A network device that sends third downlink control information for scheduling uplink data to a terminal device within a first action time, wherein at least part of the uplink data is within a second action time; and

[0533] The terminal device is configured with two SRS resource sets; the terminal device does not send uplink data within the second action time; and

[0534] The network device does not receive uplink data within the second action time within the second action time.

Claims

1. An uplink data sending device, configured in a terminal device, wherein: The terminal device is configured with two SRS resource sets (SRS resource sets), and the uplink data sending device includes: a first receiving unit configured to receive, within a first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within a second action time; and a first sending unit, which determines, according to the parameters indicated by the third downlink control information and / or at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time, whether to send uplink data based on a single transmission and reception point (sTRP) for the uplink data within the second action time, or to send uplink data based on multiple transmission and reception points (mTRP).

2. The device according to claim 1, wherein The uplink data includes at least one of the following uplink data types: Uplink repetition (PUSCH repetition) Type A (Type A); Uplink repetition (PUSCH repetition) Type B (Type B); or PUSCH sent simultaneously by multiple panels.

3. The device according to claim 1, wherein The first receiving unit receives first downlink control information corresponding to the first action time; and Second downlink control information corresponding to the second action time is received within the first action time.

4. The device according to claim 1, wherein The parameter includes at least one of an SRS resource set (SRS resource set), an SRS resource (SRS resource), or an uplink precoding index (transmit precoding matrix indicator, TPMI).

5. The device according to claim 4, wherein The parameter is indicated by an SRS resource set indicator field in the third downlink control information.

6. The device according to claim 3, wherein The second downlink control information indicates the at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

7. The device according to claim 1, wherein Uplink data within the second action time is sent using part or all of at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time or corresponding to the first action time.

8. The device according to claim 7, wherein When the parameter includes an SRS resource set, performing uplink data transmission based on a single transmission and reception point (sTRP) for the uplink data within the second action time; In a case where the parameter includes more than one SRS resource set, uplink data within the second action time is sent based on multiple transmission and reception points (mTRP).

9. The device according to claim 8, wherein When uplink data within the second action time is sent based on multiple transmission and reception points (mTRP), and an uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes one uplink transmission configuration indication state (UL TCI state), the one uplink transmission configuration indication state (UL TCI state) is associated with the more than one SRS resource sets (SRS resource sets).

10. The device according to claim 8, wherein The uplink data within the second action time is sent using an uplink transmission configuration indication state (UL TCI state) associated with the parameter in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time or corresponding to the first action time, or using a predefined uplink transmission configuration indication state (UL TCI state) in at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

11. The device according to claim 10, wherein The predefined uplink transmission configuration indication state (UL TCI state) is an uplink transmission configuration indication state (UL TCI state) at a specific position in the at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

12. The device according to claim 8, wherein At least one of the following information in the parameters is used: an SRS resource set, an SRS resource, or a transmit precoding matrix indicator (TPMI) to transmit uplink data within the second action time.

13. The device according to claim 7, wherein When the uplink transmission configuration indication state (UL TCI state) corresponding to the second action time includes one uplink transmission configuration indication state (UL TCI state), uplink data within the second action time is sent based on a single transmission and reception point (sTRP); In a case where the uplink transmission configuration indication state corresponding to the second action time includes more than one uplink transmission configuration indication state (UL TCI state), uplink data within the second action time is sent based on multiple transmission and reception points (mTRP).

14. The device according to claim 13, wherein Uplink data within the second action time is sent using at least one uplink transmission configuration indication state (UL TCI state) corresponding to the second action time.

15. The device according to claim 13, wherein Uplink data within the second action time is sent using at least one of the following information included in and / or predefined by the parameters: an SRS resource set, an SRS resource, or a transmit precoding matrix indicator (TPMI).

16. The device according to claim 15, wherein At least one of the predefined information: an SRS resource set, an SRS resource, or a transmit precoding matrix indicator (TPMI) is determined according to one of the following: Two configured SRS resource sets (SRS resource sets); An SRS resource set (SRS resource set) at a specific location in the two configured SRS resource sets (SRS resource sets); An SRS resource at a specific location in at least one SRS resource within an SRS resource set; The first SRS resource with the smallest number of SRS ports among at least one SRS resource in an SRS resource set; An uplink precoding matrix indicator (TPMI) at a specific position among at least one uplink precoding matrix indicator (TPMI) available for an SRS resource.

17. The device according to claim 13, wherein Uplink data within the second action time is sent using at least one of the following information associated with the uplink transmission configuration indication state (UL TCI state) within the second action time: an SRS resource set (SRS resource set), an SRS resource (SRS resource), or an uplink precoding matrix indicator (TPMI).

18. The device according to claim 3, wherein For at least one uplink repetition (PUSCH repetition) spanning the first action time and the second action time, the uplink data in the second action time starts from the first uplink repetition (PUSCH repetition) after the start time of the second action time.

19. An uplink data sending device, configured in a terminal device, wherein: The terminal device is configured with two SRS resource sets (SRS resource sets), and the uplink data sending device includes: a second receiving unit, which receives third downlink control information for scheduling uplink data within a first action time, and the terminal device sends the uplink data within the first action time; and a second sending unit, which determines, based on at least one of an SRS resource set (SRS resource set), an SRS resource (SRS resource), or an uplink precoding index (TPMI) indicated by the third downlink control information, to send uplink data based on a single transmission and reception point (sTRP), or to send uplink data based on multiple transmission and reception points (mTRP).

20. An uplink data sending device, configured in a terminal device, wherein: in, The terminal device is configured with two SRS resource sets (SRS resource sets), and the uplink data sending device includes: a third receiving unit configured to receive, within the first action time, third downlink control information for scheduling uplink data, wherein at least part of the uplink data is within the second action time; and The third sending unit does not send the uplink data within the second action time.