Transmission method, terminal equipment, network equipment and communication system

Abstract

This application relates to a transmission method, a terminal device, a network device, and a communication system. The transmission method includes: the terminal device determining a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or a first real physical uplink shared channel (PUSCH) for multiplexing the UCI, wherein the first real PUSCH is directed to a different first receiver and / or a different beam direction than the second real PUSCH is directed to a different second receiver and / or a different beam direction.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a transmission method, terminal equipment, network equipment, and communication system. Background Technology

[0002] To meet current demands for speed, latency, high-speed mobility, and energy efficiency, and to address the diversity and complexity of future services, the 3GPP (3rd Generation Partnership Project) international standards organization began developing 5G (fifth-generation) mobile communication technology. The main application scenarios for 5G include enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC).

[0003] 3GPP Release 17 introduced repetition transmission of PUSCH (Physical Uplink Shared Channel) based on multiple receivers (e.g., TRPs). The reliability of PUSCH is enhanced by instructing the PUSCH to be repeatedly sent to different TRPs through DCI (Downlink Control Information).

[0004] Since existing technologies only involve repeated transmission of PUSCH for a single TRP, there is no solution for determining multiple PUSCHs to carry UCI (Uplink Control Information) for multiple TRPs. Summary of the Invention

[0005] This application provides a transmission method, terminal device, network device, and communication system to determine a scheme for multiple PUSCHs used to carry UCI, at least for multiple TRPs.

[0006] This application provides a transmission method, including:

[0007] The terminal device determines a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI.

[0008] The first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0009] This application provides a transmission method, including:

[0010] The network device demodulates uplink control signaling (UCI) on resources used to transmit the Physical Uplink Shared Channel (PUSCH) via at least first and second receivers and / or at least first and second beam directions, including determining a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or a first real PUSCH for multiplexing the UCI.

[0011] The first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0012] This application provides a terminal device, including:

[0013] The processor is configured to determine a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or a first real physical uplink shared channel (PUSCH) for multiplexing the UCI.

[0014] The first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0015] This application provides a network device, including:

[0016] A processor configured to demodulate uplink control signaling UCI on resources used for transmitting physical uplink shared channel (PUSCH) via at least first and second receivers and / or at least first and second beam directions, including determining a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or a first real PUSCH for multiplexing the UCI.

[0017] The first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0018] This application provides a terminal device, including a transceiver, a processor, and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to execute the transmission method described above by the terminal device.

[0019] This application provides a network device including a transceiver, a processor, and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to execute the transmission method described above by the network device.

[0020] This application provides a communication system, including:

[0021] At least one of the aforementioned terminal devices; and

[0022] At least one of the aforementioned network devices.

[0023] This application provides a chip for implementing the above-described transmission method.

[0024] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned transmission method.

[0025] This application provides a computer-readable storage medium for storing a computer program that causes a computer to perform the above-described transmission method.

[0026] This application provides a computer program product, including computer program instructions that cause a computer to execute the above-described transmission method.

[0027] This application provides a computer program that, when run on a computer, causes the computer to perform the above-described transmission method.

[0028] This application provides at least one scheme for determining multiple PUSCHs for carrying UCI for multiple TRPs, thereby enabling at least one receiver to carry UCI in different PUSCHs. Attached Figure Description

[0029] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0030] Figure 2 This is a schematic flowchart of a transmission method according to an embodiment of this application.

[0031] Figure 3 This is a schematic flowchart of a transmission method according to another embodiment of this application.

[0032] Figure 4 This is a schematic flowchart illustrating a portion of the operation in a transmission method according to another embodiment of this application.

[0033] Figure 5 This is a schematic flowchart of a transmission method according to another embodiment of this application.

[0034] Figure 6 A schematic diagram of repeated transmissions is shown.

[0035] Figure 7 This is a schematic flowchart of a transmission method according to another embodiment of this application.

[0036] Figure 8 This is a schematic flowchart of a transmission method according to another embodiment of this application.

[0037] Figure 9 This is a schematic flowchart illustrating a portion of the operation in a transmission method according to another embodiment of this application.

[0038] Figure 10 This is a schematic flowchart of a transmission method according to another embodiment of this application.

[0039] Figure 11 This is a schematic block diagram of a terminal device according to an embodiment of this application.

[0040] Figure 12 This is a schematic block diagram of a network device according to an embodiment of this application.

[0041] Figure 13 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0042] Figure 14 This is a schematic block diagram of a chip according to an embodiment of this application.

[0043] Figure 15 This is a schematic block diagram of a communication system according to an embodiment of this application.

[0044] Figure 16 A schematic diagram of repeated PUSCH transmission is given. Detailed Implementation

[0045] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0046] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th Generation (5G) system, or other communication systems, etc.

[0047] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC) communication, and vehicle-to-vehicle (V2V) communication. The embodiments of this application can also be applied to these communication systems.

[0048] Optionally, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.

[0049] The embodiments of this application do not limit the spectrum to which the application is applied. For example, the embodiments of this application can be applied to licensed spectrum or unlicensed spectrum.

[0050] This application describes various embodiments in conjunction with network devices and terminal devices, wherein: the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, and next-generation communication system, such as terminal device in an NR network or terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0051] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0052] Network devices can be devices used to communicate with mobile devices. Network devices can be access points (APs) in WLANs, base stations (BTSs) in GSM or CDMA, base stations (NodeBs, NBs) in WCDMA, evolved base stations (eNBs or eNodeBs) in LTE, relay stations or access points, or in-vehicle devices, wearable devices, and network devices (gNBs) in NR networks, or network devices in future evolved PLMN networks, etc.

[0053] In this embodiment, the network device provides services to the cell, and the terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0054] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0055] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0056] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of this application.

[0057] Figure 1 An exemplary embodiment shows a network device 110 and two terminal devices 120. Optionally, the wireless communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include other numbers of terminal devices 120. This application embodiment does not limit this.

[0058] Optionally, the wireless communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which are not limited in this application embodiment.

[0059] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0060] Figure 2 This is a schematic flowchart of a transmission method 200 according to an embodiment of this application. The method can optionally be applied to... Figure 1 The system shown is not limited to this. The method includes at least a portion of the following.

[0061] S210, the terminal device (e.g., the aforementioned UE or other communication device) determines a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling UCI and / or the first real physical uplink shared channel PUSCH for multiplexing the UCI.

[0062] The first real PUSCH may target a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0063] Here, "PUSCH for reusing UCI" can refer to placing UCI on the PUSCH or a part thereof.

[0064] In this application, the term "symbol" may refer to an OFDM (Orthogonal Frequency Division Multiplexing) symbol or other transmission symbols.

[0065] In this application, by determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, it is possible to support carrying UCI in different PUSCHs for multiple receivers. This at least solves the technical problem of the lack of relevant technical solutions in technologies such as 5G. It should be noted that the technical problem described herein is only an example, and this application can actually solve other technical problems as well; therefore, it should not be taken as a limitation of this application.

[0066] Optionally, the receiving end may include a Transmitter-Receiver Point (TRP). Alternatively, the receiving end may also include a non-TRP receiving end.

[0067] Optionally, there can be a one-to-one correspondence between the receiver and the beam direction. For example, the first beam direction can correspond to the first receiver, and the second beam direction can correspond to the second receiver. Of course, the receiver and the beam direction can have a one-to-one correspondence, or they can not.

[0068] It should be noted that "first" and "second" here are not used to indicate which one is being referred to specifically.

[0069] Optionally, such as Figure 3 As shown, the transmission method according to the embodiments of this application may further include:

[0070] S209, the terminal device can determine the required symbol length for carrying UCI based on the symbol length of the nominal PUSCH.

[0071] For example, a method for determining the required symbol length for carrying UCI based on the symbol length of the nominal PUSCH can be found in, for example, 3GPP TS 38.213 V16.5.0 (2021-03). It should be noted that this application is not limited to this, and other methods may also be used to determine the required symbol length for carrying UCI.

[0072] Optionally, such as Figure 4 As shown, the terminal device in S210, based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines the second real PUSCH for multiplexing the UCI, which may include:

[0073] S2101, based on the required symbol length for carrying the UCI and / or the first real PUSCH, determine the symbol length that the UCI will occupy.

[0074] In this application, "the UCI will occupy symbol length" can mean that the UCI will occupy symbol length in the second real PUSCH.

[0075] Optionally, such as Figure 4 As shown, S2101's determination of the symbol length to be occupied by the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH may include:

[0076] If the determined symbol length required to carry the UCI is greater than the symbol length occupied by the first real PUSCH, then the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the symbol length required to carry the UCI.

[0077] Optionally, such as Figure 4 As shown, the terminal device in S210, based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, and may further include:

[0078] S2102, the terminal device determines each real PUSCH corresponding to the second receiver and / or the second beam direction.

[0079] Optionally, such as Figure 4 As shown, the terminal device in S210, based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, and may further include:

[0080] S2103, the terminal device determines the second real PUSCH based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction.

[0081] Optionally, the terminal device in S210, based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, which may include:

[0082] Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length required by the UCI, as the second real PUSCH.

[0083] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0084] Optionally, the terminal device in S210, based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, which may include:

[0085] The first real PUSCH among those corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by the UCI, is selected as the second real PUSCH.

[0086] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0087] Optionally, the terminal device in S210, based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, which may include:

[0088] The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

[0089] Optionally, the terminal device in S210, based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, which may include:

[0090] If, among the real PUSCHs corresponding to the second beam direction or the second receiver, there is no real PUSCH whose occupied symbol length is greater than or equal to the symbol length required by the UCI, the real PUSCH with the largest occupied symbol length is selected from among the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH.

[0091] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0092] Optionally, the transmission method according to the embodiments of this application may further include:

[0093] The terminal device updates the symbol length of the first real PUSCH to the symbol length of the second real PUSCH.

[0094] Optionally, such as Figure 5 As shown, the transmission method according to the embodiments of this application may further include:

[0095] S201, The terminal device receives the configuration regarding the type of uplink PUSCH retransmission.

[0096] Optionally, such as Figure 5 As shown, the transmission method according to the embodiments of this application may further include:

[0097] S202, the terminal device receives a downlink control signaling (DCI) indication, which triggers repeated transmission of PUSCH based on multiple beam directions and / or multiple receivers.

[0098] Optionally, the transmission method according to the embodiments of this application may further include:

[0099] If the terminal device receives a configuration of type B regarding the type of uplink PUSCH retransmission, the terminal device determines the symbol length occupied by the nominal PUSCH based on the downlink control signaling (DCI) indication; and

[0100] Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

[0101] To reduce latency, 3GPP Release 16 further enhanced uplink transmission by introducing a piggybacking retransmission mechanism. The piggybacking retransmission mechanism has the following main characteristics:

[0102] 1) Adjacent repeated transmission resources are connected end-to-end in the time domain;

[0103] 2) Resources scheduled in one go can span time slots, which ensures that services arriving later in the time slot can also be allocated sufficient resources or be scheduled in real time.

[0104] 3) The number of repetitions is indicated dynamically to adapt to dynamic changes in service and channel environment;

[0105] 4) Time-domain resource allocation is used to indicate the time-domain resources for the first repeated transmission. The time-domain resources for the remaining transmissions will be determined based on the time-domain resources of the first repeated transmission and information such as uplink and downlink transmission direction configurations. Furthermore, each repeated transmission occupies consecutive symbols, such as... Figure 6 As shown. In Figure 6 In this context, the symbol "DL" represents the downlink.

[0106] The uplink transmission enhancement time-domain resource indication can follow the 3GPP Release 15 time-domain resource indication mechanism, where higher-layer signaling configures multiple time-domain resource locations, and physical-layer signaling indicates one of these locations. In Release 15, each time-domain resource location configured by higher-layer signaling uses the SLIV (Start and Length Indicator Value) method. However, for uplink transmission enhancement, each time-domain resource location configured by higher-layer signaling includes three information fields: start symbol, time-domain resource length, and repetition count.

[0107] The aforementioned uplink repetitive transmission method is Type B PUSCH repetitive transmission. In Release 16, while introducing Type B PUSCH repetitive transmission, the slot-level repetitive transmission of Release 15 was also enhanced, meaning the number of repetitive transmissions can be dynamically indicated; this is called Type A PUSCH repetitive transmission. Type A and Type B PUSCH repetitive transmissions can be determined through higher-layer signaling configuration.

[0108] The resource indication method for repeated transmissions specifies the time-domain resource range for each repeated transmission. However, within this time-domain resource range, there may be some symbols that cannot be used for uplink transmission, such as downlink symbols and symbols used for periodic uplink probe signal transmission. Therefore, the actually usable uplink transmission resources need to be further defined. In the uplink transmission enhancements of R16, two types of time-domain resources are defined:

[0109] 1) Nominal PUSCH retransmission: This can be determined by the resource allocation indication information of the retransmission. Different nominal PUSCH retransmissions have the same symbol length. Nominal PUSCH retransmission is used to determine TBS (Transport Block Set), uplink power control, and UCI multiplexing resources, etc.

[0110] 2) True PUSCH Repeat Transmission: Within the time-domain resources determined by the resource allocation indication information used for repeat transmission, unusable symbols are removed to obtain the time-domain resources available for uplink transmission each time. The symbol lengths of different true PUSCH repeat transmissions are not necessarily the same. True PUSCH repeat transmission is used to determine DMRS (Demodulation Reference Signal) symbols, actual transmission rate, RV (Redundancy Version), and UCI multiplexing resources, etc.

[0111] UCI may include Channel State Information (CSI) and / or Hybrid Automatic Repeat Request (HARQ) acknowledgment (HARQ-ACK), etc.

[0112] For example, when UCI is CSI, and the uplink transmission enhancement is configured as PUSCH repetition transmission type B, if, for example, aperiodic CSI overlaps and intersects with PUSCH, aperiodic CSI can be multiplexed only on the actual PUSCH, for example, the first symbol with a length greater than 1, and the symbol length used for the aperiodic CSI transmission portion can be obtained based on the nominal length of the PUSCH retransmission and / or other relevant configurations.

[0113] Optionally, such as Figure 5 As shown, the transmission method according to the embodiments of this application may further include:

[0114] S203, the terminal device receives a UCI, which is triggered by downlink control signaling (DCI).

[0115] Optionally, as mentioned above, the UCI received by the terminal device may overlap or intersect with the PUSCH in terms of time domain resources.

[0116] Optionally, such as Figure 5 As shown, the transmission method according to the embodiments of this application may further include:

[0117] S211, the terminal device transmits UCI in the determined second real PUSCH.

[0118] Optionally, the type of UCI may include at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

[0119] Optionally, the UCI includes Channel State Information (CSI) and / or Hybrid Automatic Repeat reQuest (HARQ) Acknowledgment (HARQ-ACK), etc.

[0120] Optionally, the transmission method according to the embodiments of this application may further include:

[0121] Demodulation of UCI is performed on resources where the terminal device transmits PUSCH via at least the first and second receiving ends and / or at least the first and second beam directions.

[0122] Optionally, the transmission method according to the embodiments of this application may further include:

[0123] The terminal device determines the receiver and / or beam direction corresponding to each real PUSCH based on the beam mapping pattern.

[0124] Specifically, during repeated PUSCH transmissions, the time-domain position of sending the first real PUSCH used to carry UCI is earlier than the time-domain position of sending the second real PUSCH used to carry UCI.

[0125] Therefore, it is possible to transmit a UCI on a first PUSCH for the first receiver and / or beam direction before transmitting a UCI on a second PUSCH for the second receiver and / or beam direction.

[0126] Optionally, the transmission method according to the embodiments of this application may further include:

[0127] The terminal device determines the required symbol length for carrying the UCI based on the content of the UCI.

[0128] Here, the UCI content may include relevant information such as CSI and / or HARQ-ACK. In this application, the symbol length required to be transmitted on the PUSCH can be determined based on this relevant information.

[0129] Optionally, the symbol length of the first real PUSCH and / or the second real PUSCH can be greater than 1.

[0130] The above describes the transmission method according to this application. This method can support the transmission of UCI across multiple receivers in different PUSCHs, thereby addressing technical issues such as the lack of relevant technical solutions in 5G technology.

[0131] To make this application easier to understand, the following will provide a more specific description through some examples.

[0132] Figure 7 A transmission method according to another embodiment of this application is shown, which may include the following steps.

[0133] S310, the network device may demodulate uplink control signaling UCI on resources that transmit physical uplink shared channel (PUSCH) through at least first and second receivers and / or at least first and second beam directions, including determining a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or a first real PUSCH for multiplexing the UCI.

[0134] The first real PUSCH may target a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0135] In this application, by determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, it is possible to support carrying UCI in different PUSCHs for multiple receivers. This at least solves the technical problem of the lack of relevant technical solutions in technologies such as 5G. It should be noted that the technical problem described herein is only an example, and this application can actually solve other technical problems as well; therefore, it should not be taken as a limitation of this application.

[0136] Optionally, such as Figure 8 As shown, the transmission method according to the embodiments of this application may further include:

[0137] S309, the network device determines the required symbol length for carrying UCI based on the symbol length of the nominal PUSCH.

[0138] Optionally, such as Figure 9 As shown, S310's determination of the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI may include:

[0139] S3101, based on the required symbol length for carrying the UCI and / or the first real PUSCH, determine the symbol length that the UCI will occupy.

[0140] Optionally, determining the symbol length to be occupied by the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH may include:

[0141] If the determined symbol length required to carry the UCI is greater than the symbol length occupied by the first real PUSCH, then the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the symbol length required to carry the UCI.

[0142] Optionally, such as Figure 9 As shown, determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI may include:

[0143] S3102, determine each real PUSCH corresponding to the second receiver and / or the second beam direction.

[0144] Optionally, such as Figure 9 As shown, determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI may further include:

[0145] S3103, based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction, determine the second real PUSCH.

[0146] Optionally, determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI may include:

[0147] Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by UCI, as the second real PUSCH.

[0148] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0149] Optionally, determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI may include:

[0150] The first real PUSCH whose symbol length is greater than or equal to the symbol length to be occupied by the UCI is selected from the real PUSCHs corresponding to the second beam direction or the second receiver, and is used as the second real PUSCH.

[0151] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0152] Optionally, determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI may include:

[0153] The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

[0154] Optionally, determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI may include:

[0155] If there is no real PUSCH with a symbol length greater than or equal to the symbol length to be occupied by UCI among the real PUSCHs corresponding to the second beam direction or the second receiver, the real PUSCH with the largest symbol length is selected from the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH.

[0156] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0157] Optionally, such as Figure 9 As shown, the transmission method according to the embodiments of this application may further include:

[0158] Update the symbol length of the first real PUSCH to the symbol length of the second real PUSCH.

[0159] Optionally, such as Figure 10 As shown, the transmission method according to the embodiments of this application may further include:

[0160] S301, the network device configures the uplink PUSCH repeat transmission type for the terminal device.

[0161] Optionally, such as Figure 10 As shown, the transmission method according to the embodiments of this application may further include:

[0162] S302, the network device sends a downlink control signaling (DCI) indication, which triggers repeated transmission of PUSCH based on multiple beam directions and / or multiple receivers.

[0163] Optionally, such as Figure 10 As shown, the transmission method according to the embodiments of this application may further include:

[0164] S303, network devices trigger UCI reporting through downlink control signaling (DCI).

[0165] Optionally, the downlink control signaling (DCI) indicates the symbol length of the nominal PUSCH and / or the symbol length of each actual PUSCH.

[0166] Optionally, the transmission method according to the embodiments of this application may further include:

[0167] When the network device configures the uplink PUSCH retransmission type to type B, the symbol length occupied by the nominal PUSCH is determined based on the downlink control signaling (DCI) indication; and

[0168] Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

[0169] Optionally, such as Figure 10 As shown, the transmission method according to the embodiments of this application may further include:

[0170] S311, the network device receives a UCI, which is triggered by downlink control signaling (DCI).

[0171] Optionally, the received UCI may overlap or intersect with PUSCH in terms of time domain resources.

[0172] Optionally, such as Figure 10 As shown, the transmission method according to the embodiments of this application may further include:

[0173] S312, the network device demodulates the UCI carried in the determined second real PUSCH.

[0174] Optionally, the type of UCI includes at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

[0175] Optionally, the UCI includes Channel State Information (CSI) and / or Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

[0176] Optionally, the receiver and the beam direction have a one-to-one correspondence.

[0177] Of course, the receiver and the beam direction can be in a one-to-one correspondence or not.

[0178] Optionally, the receiving end includes a transmit-receive point (TRP).

[0179] Optionally, the transmission method according to the embodiments of this application may further include:

[0180] The network device determines the receiver and / or beam direction corresponding to each real PUSCH based on the beam mapping mode.

[0181] Specifically, during repeated PUSCH transmissions, the time-domain position of sending the first real PUSCH used to carry UCI is earlier than the time-domain position of sending the second real PUSCH used to carry UCI.

[0182] Therefore, it is possible to transmit a UCI on a first PUSCH for the first receiver and / or beam direction before transmitting a UCI on a second PUSCH for the second receiver and / or beam direction.

[0183] Optionally, the transmission method according to the embodiments of this application may further include:

[0184] Based on the content of the UCI, the network device determines the required symbol length for carrying the UCI.

[0185] Optionally, the symbol length of the first real PUSCH and / or the second real PUSCH is greater than 1.

[0186] This application provides a terminal device, such as... Figure 11 As shown, the terminal device 400 may include a processor 420.

[0187] The processor 420 can be configured to determine a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling UCI and / or a first real physical uplink shared channel (PUSCH) for multiplexing the UCI.

[0188] The first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0189] In this application, by determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, it is possible to support carrying UCI in different PUSCHs for multiple receivers. This at least solves the technical problem of the lack of relevant technical solutions in technologies such as 5G. It should be noted that the technical problem described herein is only an example, and this application can actually solve other technical problems as well; therefore, it should not be taken as a limitation of this application.

[0190] Optionally, the processor can also be configured to:

[0191] The required symbol length for carrying UCI is determined based on the symbol length of the nominal PUSCH.

[0192] Optionally, the processor can also be configured to:

[0193] The symbol length required to carry the UCI is determined based on the required symbol length and / or the first real PUSCH.

[0194] Optionally, the processor can also be configured to:

[0195] If the required symbol length for carrying the UCI is greater than the symbol length occupied by the first real PUSCH, the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the required symbol length for carrying the UCI.

[0196] Optionally, the processor can also be configured to:

[0197] Determine each actual PUSCH corresponding to the second receiver and / or the second beam direction.

[0198] Optionally, the processor can also be configured to:

[0199] The second real PUSCH is determined based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction.

[0200] Optionally, the processor can also be configured to:

[0201] Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by UCI, as the second real PUSCH.

[0202] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0203] Optionally, the processor can also be configured to:

[0204] The first real PUSCH whose symbol length is greater than or equal to the symbol length to be occupied by the UCI is selected from the real PUSCHs corresponding to the second beam direction or the second receiver, and is used as the second real PUSCH.

[0205] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0206] Optionally, the processor can also be configured to:

[0207] The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

[0208] Optionally, the processor can also be configured to:

[0209] If there is no real PUSCH with a symbol length greater than or equal to the symbol length to be occupied by UCI among the real PUSCHs corresponding to the second beam direction or the second receiver, the real PUSCH with the largest symbol length is selected from the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH.

[0210] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0211] Optionally, the processor can also be configured to:

[0212] Update the symbol length of the first real PUSCH to the symbol length of the second real PUSCH.

[0213] Optionally, such as Figure 11 As shown, the terminal device according to an embodiment of this application may further include:

[0214] Transceiver 410 can be configured to receive information about the type of uplink PUSCH repeat transmissions.

[0215] Optionally, the transceiver 410 can also be configured to:

[0216] Receive downlink control signaling (DCI) indication, which triggers PUSCH retransmission based on multiple beam directions and / or multiple receivers.

[0217] Optionally, the processor can also be configured to:

[0218] If the received configuration regarding the type of uplink PUSCH retransmission is type B, the symbol length occupied by the nominal PUSCH is determined based on the downlink control signaling (DCI) indication; and

[0219] Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

[0220] Optionally, the transceiver can also be configured to:

[0221] Receive UCI, which is triggered by downlink control signaling (DCI).

[0222] Optionally, the UCI received by the transceiver overlaps or intersects with the PUSCH in the time domain.

[0223] Optionally, the transceiver can also be configured to:

[0224] Transmit UCI in the determined second real PUSCH.

[0225] Optionally, the type of UCI includes at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

[0226] Optionally, the UCI includes Channel State Information (CSI) and / or Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

[0227] Optionally, the UCI is demodulated on resources that transmit PUSCH via at least first and second receivers and / or at least first and second beam directions.

[0228] Optionally, the receiver and the beam direction have a one-to-one correspondence.

[0229] Optionally, the receiving end includes a transmit-receive point (TRP).

[0230] Optionally, the processor can also be configured to:

[0231] Based on the beam mapping mode, determine the receiver and / or beam direction corresponding to each real PUSCH.

[0232] Specifically, during repeated PUSCH transmissions, the time-domain position of sending the first real PUSCH used to carry UCI is earlier than the time-domain position of sending the second real PUSCH used to carry UCI.

[0233] Therefore, it is possible to transmit a UCI on a first PUSCH for the first receiver and / or beam direction before transmitting a UCI on a second PUSCH for the second receiver and / or beam direction.

[0234] Optionally, the processor can also be configured to:

[0235] Based on the content of the UCI, determine the required symbol length for carrying the UCI.

[0236] Optionally, the symbol length of the first real PUSCH and / or the second real PUSCH is greater than 1.

[0237] This application provides a network device, such as... Figure 12As shown, the network device 500 may include a processor 510.

[0238] The processor 510 may be configured to demodulate uplink control signaling UCI on resources that transmit physical uplink shared channel (PUSCH) via at least first and second receivers and / or at least first and second beam directions, including determining a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or a first real PUSCH for multiplexing the UCI.

[0239] The first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different second beam direction.

[0240] In this application, by determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, it is possible to support carrying UCI in different PUSCHs for multiple receivers. This at least solves the technical problem of the lack of relevant technical solutions in technologies such as 5G. It should be noted that the technical problem described herein is only an example, and this application can actually solve other technical problems as well; therefore, it should not be taken as a limitation of this application.

[0241] Optionally, the processor 510 may also be configured to:

[0242] The required symbol length for carrying UCI is determined based on the symbol length of the nominal PUSCH.

[0243] Optionally, the processor 510 may also be configured to:

[0244] The symbol length required to carry the UCI is determined based on the required symbol length and / or the first real PUSCH.

[0245] Optionally, the processor 510 may also be configured to:

[0246] If the determined symbol length required to carry the UCI is greater than the symbol length occupied by the first real PUSCH, then the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the symbol length required to carry the UCI.

[0247] Optionally, the processor 510 may also be configured to:

[0248] Determine each actual PUSCH corresponding to the second receiver and / or the second beam direction.

[0249] Optionally, the processor 510 may also be configured to:

[0250] The second real PUSCH is determined based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction.

[0251] Optionally, the processor 510 may also be configured to:

[0252] Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length required by the UCI, as the second real PUSCH.

[0253] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0254] Optionally, the processor 510 may also be configured to:

[0255] The first real PUSCH among those corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by the UCI, is selected as the second real PUSCH.

[0256] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0257] Optionally, the processor 510 may also be configured to:

[0258] The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

[0259] Optionally, the processor 510 may also be configured to:

[0260] If, among the real PUSCHs corresponding to the second beam direction or the second receiver, there is no real PUSCH whose occupied symbol length is greater than or equal to the symbol length required by the UCI, the real PUSCH with the largest occupied symbol length is selected from among the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH.

[0261] The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

[0262] Optionally, the symbol length of the first real PUSCH is updated to the symbol length of the second real PUSCH.

[0263] Optionally, the processor 510 can also be configured to: configure the type of uplink PUSCH repeat transmission for the terminal device.

[0264] Optionally, the network device 500 may further include:

[0265] Transceiver 520 can be configured to send downlink control signaling (DCI) indications that trigger PUSCH repetitions based on multiple beam directions and / or multiple receivers.

[0266] Optionally, the processor 510 may also be configured to:

[0267] UCI reporting is triggered via downlink control signaling (DCI).

[0268] Optionally, the downlink control signaling (DCI) can indicate the symbol length of the nominal PUSCH and / or the symbol length of each actual PUSCH.

[0269] Optionally, the processor 510 may also be configured to:

[0270] When the uplink PUSCH retransmission type is configured as type B, the symbol length occupied by the nominal PUSCH is determined based on the downlink control signaling (DCI) indication; and

[0271] Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

[0272] Optionally, the transceiver 520 can also be configured to:

[0273] Receive UCI, which is triggered by downlink control signaling (DCI).

[0274] Optionally, the received UCI may overlap or intersect with PUSCH in the time domain.

[0275] Optionally, the processor 510 may also be configured to:

[0276] Demodulate the UCI carried in the determined second real PUSCH.

[0277] Optionally, the type of UCI may include at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

[0278] Optionally, the UCI may include Channel State Information (CSI) and / or Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

[0279] Optionally, the receiver and the beam direction can have a one-to-one correspondence.

[0280] Optionally, the receiving end may include a Transmit-Receive Point (TRP).

[0281] Optionally, the processor can also be configured to:

[0282] Based on the beam mapping mode, determine the receiver and / or beam direction corresponding to each real PUSCH.

[0283] Specifically, during repeated PUSCH transmissions, the time-domain position of sending the first real PUSCH used to carry UCI is earlier than the time-domain position of sending the second real PUSCH used to carry UCI.

[0284] Therefore, it is possible to transmit a UCI on a first PUSCH for the first receiver and / or beam direction before transmitting a UCI on a second PUSCH for the second receiver and / or beam direction.

[0285] Optionally, the processor can also be configured to:

[0286] Based on the content of the UCI, determine the required symbol length for carrying the UCI.

[0287] Optionally, the symbol length of the first real PUSCH and / or the second real PUSCH is greater than 1.

[0288] It should be understood that the operation and / or function of each device, unit, module, etc. in the network device according to the embodiments of this application (such as the transceivers 410, 520 and processors 420, 510, etc.) are respectively to implement the corresponding operation and / or function performed by the network device in the above transmission method. Therefore, for the sake of brevity, they will not be described in detail here.

[0289] Figure 13 This is a schematic structural diagram of a communication device 600 according to an embodiment of this application. Figure 13 The communication device 600 shown may include a processor 610 and a memory 620.

[0290] The processor 610 can call and run computer programs from the memory 620 to implement the transmission method in the embodiments of this application.

[0291] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0292] Optionally, such as Figure 13 As shown, the communication device 600 may also include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0293] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

[0294] Optionally, the communication device 600 may be a network device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the network device in the various transmission methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0295] Optionally, the communication device 600 may be a terminal device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the terminal device in the various transmission methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0296] Figure 14 This is a schematic structural diagram of chip 700 according to an embodiment of this application. Figure 14 The chip 700 shown may include a processor 710 and a memory 720. The processor 710 can call and run computer programs from the memory to implement the methods in the embodiments of this application. The memory 720 may be a separate device independent of the processor 710, or it may be integrated into the processor 710.

[0297] Optionally, the chip 700 may also include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0298] Optionally, the chip 700 may also include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0299] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in each transmission method of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0300] Optionally, the chip can be applied to the terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal device in each transmission method of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0301] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0302] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.

[0303] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).

[0304] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0305] Figure 15 This is a schematic block diagram of a communication system 800 according to an embodiment of this application. Figure 15 As shown, the communication system 800 may include a terminal device 810 and a network device 820.

[0306] The terminal device 810 can be used to implement the corresponding functions of the terminal device in the above transmission method, or it can be the terminal device 400 or the communication device 600 serving as a terminal device. The network device 820 can be used to implement the corresponding functions of the network device in the above transmission method, or it can be the network device 500 or the communication device 600 serving as a terminal device. For simplicity, further details are omitted here.

[0307] Example

[0308] The following two examples will be given to illustrate the technical solution of this application more clearly and comprehensively.

[0309] Assuming that the network side (network device side) is configured to repeat PUSCH transmission, where the parameter for the repeat transmission is 4*8 (i.e., the number of repeat transmissions is 4, the nominal PUSCH length is 8, and the starting position is the 4th OFDM symbol), the terminal side (terminal device side) can determine the actual PUSCH repeat transmission based on the slot boundary and / or other configurations.

[0310] like Figure 16 The example shown has 5 real PUSCH duplicate transmissions.

[0311] On the terminal side, the target receiver and / or beam direction (e.g., TRP) for each real PUSCH can be determined based on the beam mapping pattern indicated by the network side. Assuming real PUSCH 1 and real PUSCH 2 correspond to receiver 1 and / or beam direction 1 on the network side, respectively (e.g., they could correspond to target TRP 1), then real PUSCH 3 and 4 correspond to receiver 2 and / or beam direction 2 on the network side, respectively (e.g., they could correspond to target TRP 2), and real PUSCH 5 can correspond to receiver 1 or beam direction 1 on the network side (e.g., it could correspond to target TRP 1). The terminal side can determine, for example, the time-domain resource occupation of 7 OFDM symbols required for UCI (e.g., aperiodic CSI) based on the real PUSCH 1 of the first receiver and / or beam direction, and the terminal side can select real PUSCH 4 as the PUSCH for aperiodic CSI multiplexing in the second receiver and / or beam direction (i.e., the second real PUSCH) based on these 7 OFDM symbols. The terminal can perform aperiodic CSI multiplexing on the second real PUSCH.

[0312] For example, if the network side is configured to repeat PUSCH transmission, the terminal side can determine the target receiver and / or beam direction (e.g., TRP) for each real PUSCH transmission based on the beam mapping mode indicated by the network side. Assume that real PUSCH 1 (length 5) and real PUSCH 2 (length 4) correspond to receiver 1 and / or beam direction 1 (corresponding to target TRP 1) on the network side, respectively. Real PUSCH 3 and 4 (both length 4) both correspond to receiver 2 and / or beam direction 2 (corresponding to target TRP 2) on the network side. Then, the terminal side can, for example, calculate the time-domain resource requirement of 4 OFDM symbols for aperiodic CSI based on real PUSCH 1 at receiver 1 and / or beam direction 1. Based on these 4 OFDM symbols, the terminal side can select real PUSCH 3 as the PUSCH for aperiodic CSI multiplexing at receiver 2 and / or beam direction 2 (i.e., the second real PUSCH), and the terminal side can perform aperiodic CSI multiplexing on this PUSCH.

[0313] The examples given above are merely illustrative, and this application is not limited to such examples.

[0314] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0315] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0316] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0317] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A transmission method, comprising: The terminal device determines a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and a first real physical uplink shared channel (PUSCH) for multiplexing the UCI. At least a portion of the first real PUSCH for multiplexing the UCI and at least a portion of the second real PUSCH for multiplexing the UCI both carry the UCI. Wherein, the first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different beam direction. The terminal device determines a second real PUSCH for reusing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and a first real physical uplink shared channel (PUSCH) for reusing the UCI, including: The terminal device determines each real PUSCH corresponding to the second receiver and / or the second beam direction; The terminal device determines the second real PUSCH based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction; The method further includes: The terminal device updates the symbol length of the first real PUSCH to the symbol length of the second real PUSCH.

2. The transmission method according to claim 1, further comprising: The terminal device determines the required symbol length for carrying UCI based on the symbol length of the nominal PUSCH.

3. The transmission method according to claim 1, wherein, The terminal device, based on the required symbol length for carrying uplink control signaling (UCI) and the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, and further includes: The symbol length required to carry the UCI is determined based on the required symbol length and the first real PUSCH.

4. The transmission method according to claim 3, wherein, The determination of the symbol length required for the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH includes: If the determined symbol length required to carry the UCI is greater than the symbol length occupied by the first real PUSCH, then the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the symbol length required to carry the UCI.

5. The transmission method according to claim 1, wherein, The terminal device, based on the required symbol length for carrying uplink control signaling (UCI) and the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, and further includes: Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length required by the UCI, as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

6. The transmission method according to claim 1, wherein, The terminal device, based on the required symbol length for carrying uplink control signaling (UCI) and the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, and further includes: The first real PUSCH among those corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by the UCI, is selected as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

7. The transmission method according to claim 1, wherein, The terminal device determines a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying uplink control signaling (UCI) and / or the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, and further includes: The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

8. The transmission method according to claim 1, wherein, The terminal device, based on the required symbol length for carrying uplink control signaling (UCI) and the first real physical uplink shared channel (PUSCH) for multiplexing the UCI, determines a second real PUSCH for multiplexing the UCI, and further includes: If, among the real PUSCHs corresponding to the second beam direction or the second receiver, there is no real PUSCH whose occupied symbol length is greater than or equal to the symbol length required by the UCI, the real PUSCH with the largest occupied symbol length is selected from among the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

9. The transmission method according to any one of claims 1 to 8, further comprising: The terminal device receives configuration information regarding the type of uplink PUSCH retransmission.

10. The transmission method according to any one of claims 1 to 8, further comprising: The terminal device receives a downlink control signaling (DCI) indication, which triggers repeated transmission of PUSCH based on multiple beam directions and / or multiple receivers.

11. The transmission method according to any one of claims 1 to 8, further comprising: When the terminal device receives a configuration of type B regarding the type of uplink PUSCH retransmission, the terminal device determines the symbol length occupied by the nominal PUSCH based on the downlink control signaling (DCI) indication; and Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

12. The transmission method according to any one of claims 1 to 8, further comprising: The terminal device receives a UCI, which is triggered by downlink control signaling (DCI).

13. The transmission method according to any one of claims 1 to 8, wherein, The UCI received by the terminal device overlaps or intersects with PUSCH in terms of time domain resources.

14. The transmission method according to any one of claims 1 to 8, further comprising: The terminal device transmits UCI in the determined second real PUSCH.

15. The transmission method according to any one of claims 1 to 8, wherein, The types of UCI include at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

16. The transmission method according to any one of claims 1 to 8, wherein, The UCI includes Channel State Information (CSI) and / or Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

17. The transmission method according to any one of claims 1 to 8, further comprising: Demodulation of UCI is performed on resources where the terminal device transmits PUSCH via at least the first and second receiving ends and / or at least the first and second beam directions.

18. The transmission method according to any one of claims 1 to 8, wherein, There is a one-to-one correspondence between the receiver and the beam direction.

19. The transmission method according to any one of claims 1 to 8, wherein, The receiving end includes a transmit-receive point (TRP).

20. The transmission method according to any one of claims 1 to 8, further comprising: The terminal device determines the receiver and / or beam direction corresponding to each real PUSCH based on the beam mapping mode. Specifically, during PUSCH retransmission, the terminal device sends the time-domain position of the first real PUSCH used to carry UCI earlier than the time-domain position of the second real PUSCH used to carry UCI.

21. The transmission method according to any one of claims 1 to 8, further comprising: The terminal device determines the required symbol length for carrying the UCI based on the content of the UCI.

22. The transmission method according to any one of claims 1 to 8, wherein, The symbol length of the first real PUSCH and / or the second real PUSCH is greater than 1.

23. A transmission method, comprising: The network device demodulates uplink control signaling (UCI) on resources used to transmit Physical Uplink Shared Channel (PUSCH) via at least first and second receivers and / or at least first and second beam directions. This includes determining a second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and a first real PUSCH for multiplexing the UCI. At least a portion of the first real PUSCH of the multiplexed UCI and at least a portion of the second real PUSCH of the multiplexed UCI both carry the UCI. Wherein, the first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different beam direction. The step of determining the second real PUSCH for reusing the UCI based on the required symbol length for carrying the UCI and the first real PUSCH for reusing the UCI includes: Determine each actual PUSCH corresponding to the second receiver and / or the second beam direction; The second real PUSCH is determined based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction. In this process, the symbol length of the first real PUSCH is updated to the symbol length of the second real PUSCH.

24. The transmission method according to claim 23, further comprising: The network device determines the required symbol length for carrying UCI based on the symbol length of the nominal PUSCH.

25. The transmission method according to claim 23, wherein, The step of determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and the first real PUSCH for multiplexing the UCI further includes: The symbol length required to carry the UCI is determined based on the required symbol length and / or the first real PUSCH.

26. The transmission method according to claim 25, wherein, The step of determining the symbol length to be occupied by the UCI based on the required symbol length for carrying the UCI and the first real PUSCH further includes: If the determined symbol length required to carry the UCI is greater than the symbol length occupied by the first real PUSCH, then the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the symbol length required to carry the UCI.

27. The transmission method according to claim 23, wherein, The step of determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and the first real PUSCH for multiplexing the UCI further includes: Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length required by the UCI, as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

28. The transmission method according to claim 23, wherein, The step of determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI further includes: The first real PUSCH among those corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by the UCI, is selected as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

29. The transmission method according to claim 23, wherein, The step of determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI further includes: The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

30. The transmission method according to claim 23, wherein, The step of determining the second real PUSCH for multiplexing the UCI based on the required symbol length for carrying the UCI and / or the first real PUSCH for multiplexing the UCI further includes: If, among the real PUSCHs corresponding to the second beam direction or the second receiver, there is no real PUSCH whose occupied symbol length is greater than or equal to the symbol length required by the UCI, the real PUSCH with the largest occupied symbol length is selected from among the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

31. The transmission method according to any one of claims 23 to 30, further comprising: Network devices configure the type of uplink PUSCH repetitive transmission for terminal devices.

32. The transmission method according to any one of claims 23 to 30, further comprising: The network device sends a downlink control signaling (DCI) indication, which triggers repeated transmission of PUSCH based on multiple beam directions and / or multiple receivers.

33. The transmission method according to any one of claims 23 to 30, further comprising: Network devices trigger UCI reporting via downlink control signaling (DCI).

34. The transmission method according to any one of claims 23 to 30, wherein, Downlink control signaling (DCI) indicates the symbol length of the nominal PUSCH and / or the symbol length of each real PUSCH.

35. The transmission method according to any one of claims 23 to 30, further comprising: When the network device configures the uplink PUSCH retransmission type to type B, the symbol length occupied by the nominal PUSCH is determined based on the downlink control signaling DCI indication. as well as Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

36. The transmission method according to any one of claims 23 to 30, further comprising: The network device receives a UCI, which is triggered by downlink control signaling (DCI).

37. The transmission method according to any one of claims 23 to 30, wherein, The received UCI has overlap or intersection with PUSCH in the time domain.

38. The transmission method according to any one of claims 23 to 30, further comprising: The network device demodulates the UCI carried in the determined second real PUSCH.

39. The transmission method according to any one of claims 23 to 30, wherein, The types of UCI include at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

40. The transmission method according to any one of claims 23 to 30, wherein, The UCI includes Channel State Information (CSI) and / or Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

41. The transmission method according to any one of claims 23 to 30, wherein, There is a one-to-one correspondence between the receiver and the beam direction.

42. The transmission method according to any one of claims 23 to 30, wherein, The receiving end includes a transmit-receive point (TRP).

43. The transmission method according to any one of claims 23 to 30, further comprising: The network device determines the receiver and / or beam direction corresponding to each real PUSCH based on the beam mapping pattern. Specifically, during repeated PUSCH transmissions, the time-domain position of sending the first real PUSCH used to carry UCI is earlier than the time-domain position of sending the second real PUSCH used to carry UCI.

44. The transmission method according to any one of claims 23 to 30, further comprising: Based on the content of the UCI, the network device determines the required symbol length for carrying the UCI.

45. The transmission method according to any one of claims 23 to 30, wherein, The symbol length of the first real PUSCH and / or the second real PUSCH is greater than 1.

46. ​​A terminal device, comprising: A processor is configured to determine a second real PUSCH for multiplexing the UCI based on a required symbol length for carrying uplink control signaling (UCI) and a first real physical uplink shared channel (PUSCH) for multiplexing the UCI, wherein at least a portion of the first real PUSCH of the multiplexed UCI and at least a portion of the second real PUSCH of the multiplexed UCI both carry the UCI. Wherein, the first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different beam direction. The processor is further configured to: Determine each actual PUSCH corresponding to the second receiver and / or the second beam direction; The terminal device determines the second real PUSCH based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction; The processor is also configured to: Update the symbol length of the first real PUSCH to the symbol length of the second real PUSCH.

47. The terminal device according to claim 46, wherein, The processor is also configured to: The required symbol length for carrying UCI is determined based on the symbol length of the nominal PUSCH.

48. The terminal device according to claim 46, wherein, The processor is also configured to: The symbol length required to carry the UCI is determined based on the required symbol length and the first real PUSCH.

49. The terminal device according to claim 48, wherein, The processor is also configured to: If the required symbol length for carrying the UCI is greater than the symbol length occupied by the first real PUSCH, the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the required symbol length for carrying the UCI.

50. The terminal device according to claim 46, wherein, The processor is also configured to: Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length required by the UCI, as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and the symbol length occupied by the first real PUSCH.

51. The terminal device according to claim 46, wherein, The processor is also configured to: The first real PUSCH among those corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by the UCI, is selected as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and the symbol length occupied by the first real PUSCH.

52. The terminal device according to claim 46, wherein, The processor is also configured to: The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

53. The terminal device according to claim 46, wherein, The processor is also configured to: If, among the real PUSCHs corresponding to the second beam direction or the second receiver, there is no real PUSCH whose occupied symbol length is greater than or equal to the symbol length required by the UCI, the real PUSCH with the largest occupied symbol length is selected from among the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

54. The terminal device according to any one of claims 46 to 53, further comprising: Transceiver, configured to receive information about the type of uplink PUSCH repeat transmissions.

55. The terminal device according to claim 54, wherein, The transceiver is also configured to: Receive downlink control signaling (DCI) indication, which triggers PUSCH retransmission based on multiple beam directions and / or multiple receivers.

56. The terminal device according to any one of claims 46 to 53, wherein, The processor is also configured to: If the received configuration regarding the type of uplink PUSCH retransmission is type B, the symbol length occupied by the nominal PUSCH is determined based on the downlink control signaling (DCI) indication. as well as Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

57. The terminal device according to claim 54, wherein, The transceiver is also configured to: Receive UCI, which is triggered by downlink control signaling (DCI).

58. The terminal device according to claim 57, wherein, The UCI received by the transceiver overlaps or intersects with PUSCH in the time domain.

59. The terminal device according to claim 57, wherein, The transceiver is also configured to: Transmit UCI in the determined second real PUSCH.

60. The terminal device according to any one of claims 46 to 53, wherein, The types of UCI include at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

61. The terminal device according to any one of claims 46 to 53, wherein, The UCI includes Channel State Information (CSI) and / or Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

62. The terminal device according to any one of claims 46 to 53, wherein, The UCI is demodulated on resources that transmit PUSCH via at least first and second receivers and / or at least first and second beam directions.

63. The terminal device according to any one of claims 46 to 53, wherein, There is a one-to-one correspondence between the receiver and the beam direction.

64. The terminal device according to any one of claims 46 to 53, wherein, The receiving end includes a transmit-receive point (TRP).

65. The terminal device according to any one of claims 46 to 53, wherein, The processor is also configured to: Based on the beam mapping pattern, determine the receiver and / or beam direction corresponding to each real PUSCH. Specifically, during repeated PUSCH transmissions, the time-domain position of sending the first real PUSCH used to carry UCI is earlier than the time-domain position of sending the second real PUSCH used to carry UCI.

66. The terminal device according to any one of claims 46 to 53, wherein, The processor is also configured to: Based on the content of the UCI, determine the required symbol length for carrying the UCI.

67. The terminal device according to any one of claims 46 to 53, wherein, The symbol length of the first real PUSCH and / or the second real PUSCH is greater than 1.

68. A network device, comprising: A processor configured to demodulate uplink control signaling (UCI) on resources used for transmitting Physical Uplink Shared Channel (PUSCH) via at least first and second receivers and / or at least first and second beam directions, including determining a second real PUSCH for multiplexing the UCI based on a required symbol length for carrying the UCI and a first real PUSCH for multiplexing the UCI, wherein at least a portion of the first real PUSCH of the multiplexed UCI and at least a portion of the second real PUSCH of the multiplexed UCI both carry the UCI. Wherein, the first real PUSCH targets a different first receiver and / or a different first beam direction than the second real PUSCH targets a different second receiver and / or a different beam direction. The processor is further configured to: Determine each actual PUSCH corresponding to the second receiver and / or the second beam direction; The second real PUSCH is determined based on the symbol length to be occupied by the UCI and each real PUSCH corresponding to the second receiver and / or the second beam direction. In this process, the symbol length of the first real PUSCH is updated to the symbol length of the second real PUSCH.

69. The network device according to claim 68, wherein, The processor is also configured to: The required symbol length for carrying UCI is determined based on the symbol length of the nominal PUSCH.

70. The network device according to claim 68, wherein, The processor is also configured to: The symbol length required to carry the UCI is determined based on the required symbol length and the first real PUSCH.

71. The network device according to claim 70, wherein, The processor is also configured to: If the determined symbol length required to carry the UCI is greater than the symbol length occupied by the first real PUSCH, then the symbol length to be occupied by the UCI is determined to be the symbol length occupied by the first real PUSCH; otherwise, the symbol length to be occupied by the UCI is determined to be the symbol length required to carry the UCI.

72. The network device according to claim 68, wherein, The processor is also configured to: Select one of the real PUSCHs corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length required by the UCI, as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and the symbol length occupied by the first real PUSCH.

73. The network device according to claim 68, wherein, The processor is also configured to: The first real PUSCH among those corresponding to the second beam direction or the second receiver, whose symbol length is greater than or equal to the symbol length to be occupied by the UCI, is selected as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and the symbol length occupied by the first real PUSCH.

74. The network device according to claim 68, wherein, The processor is also configured to: The real PUSCH with the largest symbol length among all the real PUSCHs corresponding to the second beam direction or the second receiver is selected as the second real PUSCH.

75. The network device according to claim 68, wherein, The processor is also configured to: If, among the real PUSCHs corresponding to the second beam direction or the second receiver, there is no real PUSCH whose occupied symbol length is greater than or equal to the symbol length required by the UCI, the real PUSCH with the largest occupied symbol length is selected from among the real PUSCHs corresponding to the second beam direction or the second receiver as the second real PUSCH. The symbol length required for the UCI is obtained based on the required symbol length for carrying the UCI and / or the symbol length occupied by the first real PUSCH.

76. The network device according to any one of claims 68 to 75, wherein, The processor is also configured to: Configure the type of uplink PUSCH retransmission for the terminal device.

77. The network device according to any one of claims 68 to 75, further comprising: A transceiver configured to transmit downlink control signaling (DCI) indications that trigger repeated PUSCH transmissions based on multiple beam directions and / or multiple receivers.

78. The network device according to any one of claims 68 to 75, wherein, The processor is also configured to: UCI reporting is triggered via downlink control signaling (DCI).

79. The network device according to any one of claims 68 to 75, wherein, Downlink control signaling (DCI) indicates the symbol length of the nominal PUSCH and / or the symbol length of each real PUSCH.

80. The network device according to any one of claims 68 to 75, wherein, The processor is also configured to: When the uplink PUSCH retransmission type is configured as type B, the symbol length occupied by the nominal PUSCH is determined based on the downlink control signaling (DCI) indication; and Based on the determined symbol length occupied by the nominal PUSCH, the symbol length occupied by the corresponding real PUSCH and the beam direction and / or receiver corresponding to each real PUSCH are determined.

81. The network device according to claim 77, wherein, The transceiver is also configured to: Receive UCI, which is triggered by downlink control signaling (DCI).

82. The network device according to claim 81, wherein, The received UCI has overlap or intersection with PUSCH in the time domain.

83. The network device according to any one of claims 68 to 75, wherein, The processor is also configured to: Demodulate the UCI carried in the determined second real PUSCH.

84. The network device according to any one of claims 68 to 75, wherein, The types of UCI include at least one of the following: periodic UCI; aperiodic UCI; quasi-periodic UCI.

85. The network device according to any one of claims 68 to 75, wherein, The UCI includes Channel State Information (CSI) and / or Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK).

86. The network device according to any one of claims 68 to 75, wherein, There is a one-to-one correspondence between the receiver and the beam direction.

87. The network device according to any one of claims 68 to 75, wherein, The receiving end includes a transmit-receive point (TRP).

88. The network device according to any one of claims 68 to 75, wherein, The processor is also configured to: Based on the beam mapping pattern, determine the receiver and / or beam direction corresponding to each real PUSCH. Specifically, during repeated PUSCH transmissions, the time-domain position of sending the first real PUSCH used to carry UCI is earlier than the time-domain position of sending the second real PUSCH used to carry UCI.

89. The network device according to any one of claims 68 to 75, wherein, The processor is also configured to: Based on the content of the UCI, determine the required symbol length for carrying the UCI.

90. The network device according to any one of claims 68 to 75, wherein, The symbol length of the first real PUSCH and / or the second real PUSCH is greater than 1.

91. A terminal device, comprising: A transceiver, a processor, and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the transmission method as described in any one of claims 1 to 22.

92. A network device, comprising: A transceiver, a processor, and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the transmission method as described in any one of claims 23 to 45.

93. A communication system, comprising: At least one terminal device according to any one of claims 46-67 and 91; as well as At least one network device according to any one of claims 68 to 90 and 92.

94. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the transmission method as described in any one of claims 1 to 22.

95. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the transmission method as described in any one of claims 23 to 45.

96. A computer-readable storage medium for storing a computer program that causes a computer to perform the transmission method as described in any one of claims 1 to 22.

97. A computer-readable storage medium for storing a computer program that causes a computer to perform the transmission method as described in any one of claims 23 to 45.

98. A computer program product comprising computer program instructions that cause a computer to perform the transmission method as described in any one of claims 1 to 22.

99. A computer program product comprising computer program instructions that cause a computer to perform the transmission method as described in any one of claims 23 to 45.

Images