Communication methods and apparatuses, storage medium and program product

Abstract

Provided are communication methods and apparatuses, a storage medium and a program product, relating to the technical field of communications. A method comprises: acquiring a code sequence; and performing PUSCH transmission by means of using the code sequence, wherein PUSCHs comprise a plurality of PUSCH repetition units.

Description

Communication methods, devices, storage media and software products

[0001] This disclosure claims priority to Chinese patent application No. 202510113787.0, filed on January 22, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This disclosure relates to the field of communication technology, and in particular to a communication method, apparatus, storage medium, and program product. Background Technology

[0003] With the evolution of 5G technology and the trend towards 6G, the upgraded version of 5G has begun to adopt non-terrestrial networks (NTN) as a key technology for next-generation communication, including satellite communication technology. Improving system capacity in NTN and / or terrestrial network scenarios has become an urgent problem to be solved. Summary of the Invention

[0004] Firstly, a communication method is provided, including:

[0005] Obtain the code sequence;

[0006] The application code sequence is used for uplink physical shared channel (PUSCH) transmission. Here, PUSCH contains multiple PUSCH repeating units.

[0007] Secondly, a communication method is provided, including:

[0008] Receive PUSCH, where PUSCH contains multiple PUSCH repeat units, and PUSCH is transmitted based on code sequence.

[0009] Thirdly, a communication device is provided, comprising:

[0010] Acquisition unit, used to acquire code sequences;

[0011] The transmitting unit is used to transmit the PUSCH using the application code sequence. Here, the PUSCH contains multiple PUSCH repeating units.

[0012] Fourthly, a communication device is provided, comprising:

[0013] The receiving unit is used to receive PUSCH. Here, PUSCH contains multiple PUSCH repeating units, and PUSCH is transmitted based on code sequence.

[0014] Fifthly, a communication device is provided, comprising: a processor and a memory; the memory and the processor are coupled; the memory is used to store instructions executable by the processor, the memory storing the processor-executable instructions; when the processor is configured to execute the instructions, the communication device implements the method provided by either the first or second aspect above.

[0015] A sixth aspect provides a computer-readable storage medium, including a non-transitory computer-readable storage medium storing computer instructions that, when executed on a computer, cause the computer to perform the method provided in either the first or second aspect.

[0016] In a seventh aspect, a computer program product comprising computer instructions is provided, which, when executed on a computer, cause the computer to perform the method provided in either the first or the second aspect. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly described below. Obviously, the drawings described below are merely drawings of some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings.

[0018] Figure 1 is a PUSCH multiplexing diagram provided according to an embodiment of the present disclosure.

[0019] Figure 2 is an application code sequence diagram provided according to an embodiment of the present disclosure.

[0020] Figure 3 is a structural diagram of a communication system provided according to an embodiment of the present disclosure.

[0021] Figure 4 is a flowchart of a communication method provided according to an embodiment of the present disclosure.

[0022] Figure 5 is a flowchart of another communication method provided according to an embodiment of the present disclosure.

[0023] Figure 6 is a diagram showing the time-domain overlap of a PUSCH and a repeating PUCCH according to an embodiment of the present disclosure.

[0024] Figure 7 is a diagram showing the time-domain overlap of a PUSCH and a non-repeating PUCCH according to an embodiment of the present disclosure.

[0025] Figure 8 is a diagram of the first and second parts of a PUSCH provided according to an embodiment of the present disclosure.

[0026] Figure 9 is a diagram of the first and second parts of another PUSCH provided according to an embodiment of the present disclosure.

[0027] Figure 10 is a diagram of the first and second portions of another PUSCH provided for an embodiment of this disclosure.

[0028] Figure 11 is a diagram of the first and second portions of another PUSCH provided for an embodiment of this disclosure.

[0029] Figure 12 is a flowchart of another communication method provided for an embodiment of this disclosure.

[0030] Figure 13 is a block diagram of a communication device provided for an embodiment of the present disclosure.

[0031] Figure 14 is a block diagram of another communication device provided for an embodiment of the present disclosure.

[0032] Figure 15 is a block diagram of another communication device provided for an embodiment of the present disclosure. Detailed Implementation

[0033] To enable those skilled in the art to better understand the technical solutions of the embodiments of this disclosure, the technical solutions of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0034] Unless the context otherwise requires, throughout the specification and claims, the term "comprise" and other forms such as the third-person singular "comprises" and the present participle "comprising" are interpreted as open-ended and encompassing, meaning "including, but not limited to." In the description of the specification, terms such as "one embodiment," "some embodiments," "exemplary embodiments," "example," "specific example," or "some examples" are intended to indicate that a particular feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of this disclosure. The illustrative representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics mentioned may be included in any suitable manner in any one or more embodiments or examples.

[0035] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this disclosure, unless otherwise stated, "a plurality of" means two or more.

[0036] In this disclosure, the terms "exemplarily" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplarily" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the terms "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0037] In addition, the use of “based on” implies openness and inclusivity, because processes, steps, calculations or other actions “based on” one or more of the stated conditions or values ​​may in practice be based on additional conditions or values ​​beyond those stated.

[0038] Before describing the technical solutions of the embodiments of this disclosure, the technical terms involved in the embodiments of this disclosure will be explained first.

[0039] PUSCH multiplexing based on code sequence.

[0040] For example, consider the code sequence [+1 +1; +1 -1] multiplexed between two user equipment (UEs), as shown in Figure 1. UE1 uses the sequence [+1+1], and UE2 uses the sequence [+1 -1]. Each UE's signal is transmitted twice. Assuming UE1 transmits signal X1 and UE2 transmits signal X2, after multiplexing, the signals of the superimposed signals in the first and second repetitions are Y1 = H1,1X1 + H2,1X2 and Y2 = H1,2X1 + H2,2X2, respectively, where Hm,n is the channel of UEm in the nth repetition. Assuming the channel remains consistent at different repetition points, i.e., H1 = H1,1 = H1,2 and H2 = H2,1 = H2,2, then the signals of UE1 and UE2 can be demultiplexed and obtained as follows: X1 = (Y1 + Y2) / H1, X2 = (Y1 - Y2) / H2.

[0041] Redundancy version (RV) cycling.

[0042] The related technologies describe redundant version loops as follows:

[0043] For PUSCH transmissions scheduled using downlink control information (DCI) format 0_1, 0_2 or 0_3, or 0_0 and cyclic redundancy check (CRC) scrambled with temporary cell radio network temporary identifier (TC-RNTI), the redundancy version applied in the nth transmission of the transport block (TB) is determined by Table 6.1.2.1-2, where n = 0, 1, ..., N·K-1, K is the number of repetitions, and N is the number of time slots in TBoMS.

[0044] For PUSCH transmissions of type A repetition scheduled by random access response uplink grant (RAR UL), the redundant version applied in the nth transmission of TB (here, n = 0, 1, ... - 1) is determined according to the first row of Table 6.1.2.1-2, where K is the number of repetitions and N is the number of slots in TBoMS.

[0045] Table 6.1.2.1-2 can be shown in Table 1 below:

[0046] Table 1

[0047] Uplink control information (UCI) multiplexing.

[0048] Regarding the overlap between the physical uplink control channel (PUCCH) and the PUSCH in related technologies:

[0049] If the PUCCH has a higher priority index, then transmit the PUCCH and discard or cancel overlapping PUSCH transmissions.

[0050] If PUSCH has a higher priority index, then PUSCH is transmitted, and overlapping PUCCH transmissions are discarded or canceled.

[0051] If PUSCH and PUCCH have the same priority index:

[0052] If the PUCCH includes duplicates, the PUCCH is sent on the overlapping resources instead of the PUSCH, or the PUSCH is discarded.

[0053] If the PUCCH does not contain duplicates, it is processed according to the different contents carried by the PUCCH or PUSCH as shown in Table 2 below.

[0054] Table 2

[0055] For PUSCH transmissions with configured code sequences, if PUSCH and PUCCH overlap, rules similar to those of existing protocols can be maintained, while also ensuring the orthogonality between code sequences.

[0056] Related technological advancements.

[0057] In the radio access network (RAN) 1#119 meeting, an agreement was reached on a solution for overlapping PUCCH and PUSCH. However, this solution did not take into account the specific content of PUCCH or how to handle situations where timing requirements are not met. Therefore, in this disclosure, further solutions are proposed for different PUCCH content and timing.

[0058] In this embodiment of the disclosure, the uplink transmission includes at least one of the following: multiple repetitions of PUSCH transmission scheduled by DCI; multiple repetitions of PUSCH transmission scheduled by at least one of random access response (RAR) message or fallback RAR message; multiple repetitions of PUSCH transmission during random access; multiple repetitions of configuration-granted PUSCH transmission; multiple repetitions of PUSCH transmission in pre-configured uplink resources (PUR); and multiple repetitions of PUSCH transmission in early data transmission (EDT).

[0059] For example, multiple repetitions of PUSCH transmissions scheduled by RAR messages can be msg3 scheduled by RAR(msg2) during a 4-step random access channel (RACH) process. As another example, multiple repetitions of PUSCH transmissions scheduled by fallback RAR messages can be msg3 scheduled by fallback RAR(msgB) during a 2-step RACH process.

[0060] In some embodiments, the physical uplink shared channel may include at least one of the following: narrow band internet of things physical uplink shared channel (NPUSCH), enhanced mobile broadband physical uplink shared channel (eMBB PUSCH), ultra-reliable and low-latency communications physical uplink shared channel (uRLLC PUSCH), and massive machine type communications physical uplink shared channel (mMTC PUSCH).

[0061] Code division multiplexing is performed on the UE.

[0062] This involves adding a corresponding code sequence (e.g., orthogonal cover code (OCC) sequence) to the signals repeatedly transmitted by the UE (e.g., PUSCH, PUCCH), and then transmitting the signals of multiple UEs on the same time-frequency resources. At the receiving end, the transmitted signals of each UE can be obtained through operations such as interference cancellation, OCC combining, and decoding.

[0063] A code sequence can be applied to one or more time slots, meaning one or more time slots are multiplied by an OCC codeword. For example, with a time granularity of one time slot, as shown in Figure 2, assuming there are two UEs (UE1 and UE2), a 4-length OCC sequence is used, with the sequence [Si,1,Si,2,Si,3,Si,4], where i is the user's number. The data from each time slot is repeated four times consecutively and mapped to the four time slots, with each time slot multiplied by an OCC codeword.

[0064] PUSCH transmission can contain one or more PUSCH groups, also known as PUSCH repetition unit groups. Each group contains M PUSCH repetition units, where M is the code sequence length (e.g., OCC length), which can be represented by the number of elements in the code sequence used, or understood as the maximum number of multiplexed users that can be supported under that code sequence. The PUSCH groups within a PUSCH are defined chronologically. For example, the first PUSCH group contains the earliest M PUSCH repetition units, the second PUSCH group contains the M PUSCH repetition units after the first PUSCH group, and so on. The number of PUSCH repetition units sent by the UE can be greater than the code sequence length. For example, the UE can send 16 repetitions, and the UE's code sequence length is 4. These 16 repetition units can be divided into 4 PUSCH groups. Within each group, the content of each repetition must be exactly the same before code sequence merging can be performed.

[0065] throw away.

[0066] Discarding a transmission can also be understood as not sending the transmission at all, or that the transmission is invalid.

[0067] HARQ disabling.

[0068] In NTN, the network side can disable the HARQ feedback function through configuration. This means that when HARQ feedback is disabled, the UE does not need to send HARQ ACK information. HARQ disabling can be configured at the granularity of the HARQ process; that is, HARQ feedback can be disabled for some HARQ processes and enabled for others.

[0069] The embodiments of this disclosure will now be described in conjunction with the accompanying drawings.

[0070] The specific implementations described herein are for illustrative purposes only and are not intended to limit the scope of this disclosure.

[0071] The technical solutions provided in this disclosure can be applied to various mobile communication networks, such as 5G new radio (NR) mobile communication networks, future mobile communication networks, such as 6G mobile communication networks, or multiple communication convergence systems, etc. This disclosure does not limit them.

[0072] Figure 3 is a schematic diagram of a communication system provided according to an embodiment of the present disclosure. As shown in Figure 3, the communication system includes, but is not limited to, a satellite 10, an access network device 20, and multiple terminals (e.g., terminal 31 and terminal 32).

[0073] Here, satellite 10 can be a high-orbit satellite, a medium-orbit (MEO) satellite, or a low-orbit (LEO) satellite, etc., and this disclosure does not limit this.

[0074] In some embodiments, satellite 10 may be a satellite of a non-terrestrial communication network, which is a communication network that utilizes high-altitude or high-sky platforms. The main characteristic of a non-terrestrial communication network is that it does not rely on traditional ground infrastructure. These high-altitude or high-sky platforms include communication satellites, satellite networks, drones, high-altitude airships, etc. High-altitude platforms are typically equipped with radio frequency resources, enabling them to provide wide-area or global coverage, thereby meeting the needs of areas that traditional terrestrial networks cannot cover.

[0075] In some embodiments, satellites 10 are connected to each other via an inter-satellite link, which may be a microwave or laser link.

[0076] In some embodiments, the access network device 20 includes a base station and a gateway station. The base station can be any of the following: an evolved NodeB (eNB), a next-generation NodeB (gNB), a transmission receive point (TRP), a transmission point (TP), a relay node, a smart metasurface (RIS), or some other access node. Based on the size of the service coverage area provided, base stations can be further classified as macro base stations for providing macrocells, micro base stations for providing microcells, and femto base stations for providing femtocells. With the continuous evolution of wireless communication technology, future base stations may also adopt other names.

[0077] In some embodiments, for each of the multiple terminals, such as terminal 31, the terminal includes a terminal capable of communication based on a satellite network. The terminal can be a fixed-location terminal, a personal handheld satellite mobile terminal (e.g., a satellite phone, Iridium phone, etc.), a vehicle-mounted mobile terminal (e.g., a vehicle-mounted satellite phone, etc.), an airborne mobile terminal on an aircraft, or any mobile terminal flying within the atmosphere, such as a drone, airship, or balloon. This disclosure does not impose any special limitations on the specific form of the terminal. In this disclosure, the device for implementing the terminal's function can be the terminal itself, or a device that supports the terminal in implementing that function (e.g., a chip system within the terminal).

[0078] As shown in Figure 3, in the communication system, the link between the terminal and satellite 10 is a service link, and the link between the access network equipment 20 (such as a base station or gateway station) and satellite 10 is a feeder link, which is common to all terminals in the same cell (terminals 31 and 32 shown in Figure 3).

[0079] Figure 3 is an exemplary structural diagram. The number of devices included in the communication system shown in Figure 3 is unlimited, such as the number of satellites and terminals. Furthermore, in addition to the devices shown in Figure 3, the communication system shown in Figure 3 may include other devices, which are not limited thereto.

[0080] Next, as shown in Figure 4, a communication method is provided according to an embodiment of this disclosure. This method is applied to a terminal, which can be any one of the multiple terminals shown in Figure 3 above, such as terminal 31, and may include the following steps:

[0081] S101, Obtain the code sequence.

[0082] In some embodiments, when the terminal needs to perform PUSCH transmission, the terminal obtains a code sequence. Here, the code sequence includes at least one of the following: OCC sequence, non-orthogonal multiple access (NOMA) sequence, discrete fourier transform (DFT) sequence, Walsh sequence, Zadoff-Chu sequence, and Hadamard sequence.

[0083] As an example, a configuration information acquisition code sequence is used. Here, the configuration information is carried in at least one of the following: radio resource control (RRC) signaling, medium access control control element (MAC CE), or DCI. The configuration information can be sent by the access network device (network side). That is, the access network device sends the configuration information to the terminal through at least one of RRC signaling, MAC CE, and DCI, and then the terminal acquires the code sequence based on the configuration information.

[0084] In some embodiments, the configuration information includes at least one of the following:

[0085] Code sequence index, code sequence length, code sequence enable indicator, multiple of code sequence length, number of PUSCH groups, redundancy version cycle enable indicator, redundancy version indicator, frequency hopping enable indicator. Here, the number of PUSCH repeating units contained in the PUSCH group is the code sequence length.

[0086] In some embodiments, the number of PUSCH groups is configured, or determined based on at least one of the following: code sequence length, whether redundant version cycling is enabled, and whether frequency hopping is enabled.

[0087] Configuration information can be used to indicate whether code sequences are used for PUSCH transmission, hereinafter referred to as code sequence function enabling or disabling. When code sequence function is enabled, code sequences are used for PUSCH transmission. When code sequence is disabled or deactivated, code sequences are not used for PUSCH transmission.

[0088] The following provides an example of how at least one of RRC signaling, MAC CE, and DCI can indicate various items in the configuration information.

[0089] The parameters involved in RRC configuration in this embodiment can be configured using the following dimensions of RRC.

[0090] The configuration in RRC can be per UE, meaning that the UE uses this parameter in all PUSCH transmissions, including those with configured grants (CG) and dynamic grants (DG). For example, it can be configured in PUSCH-Config. Here, DG represents a PUSCH transmission scheduled by DCI.

[0091] The configuration in RRC can be limited to CG transport, for example, it can be configured in the Configuration Grant Configuration.

[0092] The configuration in RRC can be for a PUSCH scheduling in DG transmission. For example, it can be configured in PUSCH time domain resource allocation (TimeDomainResourceAllocation) or PUSCH-allocation (Allocation). When DCI schedules a PUSCH transmission, a corresponding TDRA configuration is selected through the time domain resource allocation (TDRA) field in DCI, and then the corresponding code sequence configuration can be selected.

[0093] A code sequence index is used to indicate a code sequence used for PUSCH transmission. One or more of the following schemes can be used to indicate the code sequence index.

[0094] Option 1: Configure a code sequence index in RRC, and then in DCI you can indicate a code sequence index to override the index configured in RRC.

[0095] Option 2: Configure a code sequence index in RRC, and then use MAC CE to indicate a code sequence index to override the index configured in RRC.

[0096] Option 3: Configure a subset of the code sequence index in the RRC, and then indicate a code sequence index in that subset in the DCI.

[0097] For example, for a 4-length code sequence, there are a total of 4 indices. Two of these indices can be indicated in the RRC, and then one of the two indices can be indicated in the DCI.

[0098] The advantage of this scheme is that it can save signaling overhead in DCI. Originally, 2 bits were needed to indicate the index of a 4-bit code sequence, but in this scheme, only 1 bit in DCI is needed to indicate the code sequence index.

[0099] Option 4: Configure the code sequence index in each TDRA configuration in the RRC's TDRA list (e.g., in PUSCH-TimeDomainResourceAllocation or PUSCH-Allocation), and then select the corresponding TDRA index in the DCI's TDRA field to indicate the code sequence index.

[0100] Option 5: Reuse an existing field in the DCI or use a new field to indicate the code sequence index.

[0101] For schemes 1, 3, and 5, which reuse existing fields in the DCI to indicate code sequence indexes, the following can be used:

[0102] The frequency hopping flag field, or the redundancy version field, or the MCS field.

[0103] The reason is that when using code sequence-based PUSCH transmission, frequency hopping or redundant versions may be disabled. Therefore, when code sequence is enabled, these two fields can be used to directly indicate the code sequence index or to override the code sequence index configured by RRC. As for the MCS field, it considers that code sequence-based PUSCH transmission may not be able to use higher modulation orders. For example, 16-quadrature amplitude modulation (QAM) and higher modulation are not used for code sequence-based PUSCH transmission; therefore, the corresponding MCS index can be used to indicate the code sequence index.

[0104] Taking the MCS table in related technologies as an example, DCI uses a total of 5 bits to indicate the MCS index. When the MCS index is 0-9, the corresponding modulation order is below 4, i.e., pi / 2 binary phase shift keying (BPSK) and quadrature phase shift keying (QPSK). 10-16 corresponds to 16QAM, and 17 and above corresponds to 64QAM or reserved codepoints. For PUSCH transmission based on code sequences, due to the influence of frequency offset, the phase rotation has a significant impact at higher modulation orders, making correct decoding impossible. Therefore, the 5-bit MCS field can use some codepoints to indicate the code sequence index. For example, MCS indices 10-13 or 17-20 can be used to indicate the code sequence index.

[0105] For code sequence enable indication, one or more of the following schemes can be used:

[0106] Option 1: In RRC, explicitly indicate whether the code sequence function is enabled using 1 bit.

[0107] Option 2: In the RRC, explicitly indicate whether the code sequence function is enabled using 1 bit, and then indicate whether the code sequence function is disabled or enabled via DCI or MAC CE.

[0108] Option 3: Implicitly indicate whether the code sequence function is enabled through the code sequence index in the RRC (e.g., when the code sequence index is not configured, it indicates that the code sequence is disabled, and when it is configured, it indicates that the code sequence is enabled). Then, the DCI or MAC CE can be used to indicate whether the OCC function is disabled or enabled.

[0109] Option 4: Implicitly enable or disable the code sequence function through the code sequence length in the RRC (e.g., by indicating that the code sequence length is not 1 to indicate enable, and that the code sequence function is disabled when the code sequence length is 1 or not configured). Then, the code sequence function can be disabled or enabled through DCI or MAC CE.

[0110] For schemes 2, 3, and 4, which use DCI to disable or enable code sequence functionality, existing fields in the DCI can be reused to indicate the disabling or enabling of code sequence functionality. For example, the following can be used:

[0111] The frequency hopping flag field, or the redundancy version field, or the MCS field.

[0112] For redundant version cycle enable or redundant version indicator, one or more of the following schemes can be used.

[0113] Option 1: In the RRC, use a parameter (e.g., Redundancy Version Cycling Enable Indicator) to indicate whether Redundancy Version Cycling is enabled, while in the DCI, use 2 bits to indicate the RV on the M repeating units of the first PUSCH group. For example, when Redundancy Version Cycling is enabled and Redundancy Version Cycling is performed across a PUSCH group, and the RV field in the DCI indicates that the RV is 0, it means that the RV of all repeating units in the first PUSCH group is 0, the RV of all repeating units in the second PUSCH group is 2, the RV of all repeating units in the third PUSCH group is 3, the RV of all repeating units in the fourth PUSCH group is 1, and so on, that is, to execute the Redundancy Version Cycling sequence in Table 6.1.2.1-2 of the related technology.

[0114] For example, when redundant version cycling is enabled and performs redundant version cycling across two PUSCH groups, and the RV field in the DCI indicates that the RV is 0, it means that the RV of all PUSCH repeating units in the first and second PUSCH groups is 0, the RV of all PUSCH repeating units in the third and fourth PUSCH groups is 2, the RV of all PUSCH repeating units in the fifth and sixth PUSCH groups is 3, the RV of all PUSCH repeating units in the seventh and eighth PUSCH groups is 1, and so on, that is, the order of redundant version cycling in Table 6.1.2.1-2 of the related technology is executed.

[0115] Option 2: Use a parameter (e.g., Redundancy Version Cycle Enable Indicator) in the RRC to indicate whether Redundancy Version Cycle is enabled. Use another parameter (e.g., Redundancy Version Indicator) in the RRC to indicate the RV of the first PUSCH group. In the DCI, a 2-bit RV field can be used to rewrite or overwrite the RV indicated in the RRC. The RVs of subsequent PUSCH groups follow the Redundancy Version Cycle order in Table 6.1.2.1-2 of the relevant technology.

[0116] Option 3: Use a parameter (e.g., redundancy version indicator, or repK-RV) in RRC to indicate the RV values ​​of multiple PUSCH groups. Here, when the indicated RV value is [0, 0, 0, 0], it can implicitly indicate that redundancy version looping is not enabled, all repeated RVs are 0, and the terminal will ignore the RV field in DCI. When the RV value indicated by the RRC parameter is not all 0, it indicates the order of RV values ​​across one or more PUSCH groups. For example, when the redundancy version loop spans one PUSCH group, the value indicated by the RRC parameter is [0 2 3 1], then the RVs in the first to fourth PUSCH groups are [0 2 3 1], and so on for the subsequent parts.

[0117] Option 4: Use a parameter (e.g., redundancy version indicator, or repK-RV) in the RRC to indicate the RV values ​​of multiple PUSCH groups. Here, when the indicated RV value is [0, 0, 0, 0], it can implicitly indicate that redundancy version cycling is not enabled, all repeated RVs are 0, and the terminal will ignore the RV field in the DCI. When the RV value indicated by the RRC parameter is not all 0, it indicates the order of RV values ​​across one or more PUSCH groups. At the same time, the RV field in the DCI can overwrite or cover the RV value indicated in the RRC, indicating the RV used by all repeated PUSCH units in the first PUSCH group, while the RV values ​​in subsequent PUSCH groups are executed according to the order of redundancy version cycling in Table 6.1.2.1-2 of the related technology.

[0118] The number S of PUSCH groups can be used to indicate one or more of the following:

[0119] The redundant version cycles across S*M PUSCH repeat units, where M is the code sequence length. This means that the same RV is used within S*M PUSCH repeat units, while different RVs can be used between each S*M PUSCH repeat unit.

[0120] UCI is multiplexed on S*M PUSCH repeating units.

[0121] Frequency hopping occurs between every S*M PUSCH repetition units.

[0122] For the indication of one or more of the number S of PUSCH groups and the code sequence length M, one or more of the following schemes can be used.

[0123] Option 1: Explicitly configure it in RRC.

[0124] Option 2: Indicate implicitly.

[0125] The code sequence length M can be implicitly obtained from the number of PUSCH repeating units. For example, when the number of PUSCH repeating units is greater than or equal to 4, the code sequence length M is 4, while when the number of PUSCH repeating units is less than 4, the code sequence length M is 2.

[0126] The number S of PUSCH groups can be implicitly obtained from the code sequence length. For example, when the code sequence length is 4, the number S of PUSCH groups is 2, and when the code sequence length is 2, the number S of PUSCH groups is 1.

[0127] In some embodiments, the number of PUSCH groups is configured, or determined based on at least one of the following: code sequence length, whether redundant version cycling is enabled, and whether frequency hopping is enabled.

[0128] S102, Use the application code sequence to transmit PUSCH.

[0129] Here, PUSCH contains multiple PUSCH repeating units.

[0130] A PUSCH repeat unit can occupy one or more time slots, one or more symbols, one millisecond, etc.

[0131] In some embodiments, the application code sequence includes at least one of the following:

[0132] Each element in the code sequence is applied to a PUSCH repeating unit;

[0133] Each element in the code sequence is multiplied by a PUSCH repeat unit;

[0134] The number of elements in a code sequence is equal to the length of the code sequence;

[0135] The number of PUSCH repeating units in a PUSCH is a multiple of the code sequence length;

[0136] The code sequence is applied to one or more PUSCH groups in the PUSCH, where the number of PUSCH repeating units in the PUSCH group is the code sequence length.

[0137] Each element in the code sequence is applied sequentially to each PUSCH repeating unit in a PUSCH group within a PUSCH.

[0138] Based on the embodiment shown in Figure 4, PUSCH transmission is performed using code sequences, and PUSCH contains multiple PUSCH repeating units, that is, PUSCH is repeatedly transmitted based on code sequences, which increases the number of users transmitting at the same time, thereby improving the system capacity in NTN scenarios and / or terrestrial network scenarios.

[0139] Current 5G systems employ a redundant version cycle mechanism. This means that when PUSCH is repeatedly transmitted, different RV values ​​are configured on different repeating units. However, this redundant version cycle is mandatory for dynamically scheduled PUSCHs, making it impossible to configure the same RV value for different repeating units. Furthermore, currently, when PUCCH and PUSCH overlap in the time domain, UCI can be multiplexed onto the PUSCH. However, in code sequence-based PUSCH repeated transmissions, if UCI is multiplexed onto a specific PUSCH repeating unit, it will disrupt the orthogonality between the repeating units. Similarly, frequency hopping configurations will also disrupt the orthogonality between code sequences.

[0140] Based on this, in some embodiments, as shown in Figure 5, the method may further include the following steps:

[0141] S103. Execute the target behavior based on the transmission conditions.

[0142] Here, the transmission conditions include at least one of the following:

[0143] Whether to enable redundant version cycling, whether PUSCH overlaps with duplicate PUCCH in the time domain, whether PUSCH overlaps with non-duplicate PUCCH in the time domain, whether PUSCH multiplexes Channel State Information (CSI) reports, and whether to enable frequency hopping.

[0144] Here, a repeated PUCCH can be understood as performing repeated PUCCH transmission, while a non-repeated PUCCH can be understood as sending a PUCCH without performing repeated PUCCH transmission.

[0145] The following explains the concepts of repeating and non-repeating PUCCH.

[0146] A repetitive PUCCH is a PUCCH containing multiple PUCCH repetition units. The time-domain resources occupied by each PUCCH repetition unit can be at the time slot level, symbol level, or millisecond level, and the protocol language is PUCCH repetitions. The overlap of PUSCH and repetitive PUCCH in terms of time-domain resources is shown in Figure 6. Here, PUCCH repetition units 1, 2, and 3 overlap with PUSCH.

[0147] Non-repeating PUCCH: This is a PUCCH that does not contain multiple PUCCH repetition units. The protocol language is PUCCH without repetitions. There is only one transmission opportunity in a PUCCH. PUSCH and repetitive PUCCH overlap in the time domain resources, as shown in Figure 7.

[0148] As an example, given that transmission conditions include whether redundant version loops are enabled, the target behavior is executed based on these transmission conditions, including:

[0149] In response to the transmission condition enabling redundant version cycling, the redundancy version of every X PUSCH repetition units in the PUSCH is kept identical. Here, the redundant version of every X PUSCH repetition units is allocated sequentially and cyclically from the redundant version set. X is one of the following: the code sequence length, a multiple of the code sequence length, that is, X equals M, or X is a multiple of M; or...

[0150] In response to transmission conditions including disabling redundant version loops, the redundant versions of all PUSCH repeating units in the PUSCH are kept identical.

[0151] In this way, the same RV value can be configured for different PUSCH repeating units.

[0152] In other words, for a PUSCH transmission configured with a code sequence, when the redundancy version cycle is turned off, the RV remains the same on all repeated transmissions; for example, the RV on all repeated transmissions is 0. When the redundancy version cycle is turned on, the RV remains the same within one or more PUSCH groups, while the RV cycles between one or more PUSCH groups according to a certain pattern. Here, a PUSCH group includes M PUSCH repetition units, where M is the code sequence length.

[0153] For example, when a PUSCH group contains 2 PUSCH repeating units, if the redundant version cycle spans every two PUSCH groups, it means that the same RV is maintained within every 4 PUSCH repeating units (i.e., 2 PUSCH groups), while a redundant version cycle is used between every two PUSCH groups. In other words, the redundant version is kept the same within every 4 PUSCH repeating units, while a redundant version cycle is used between every 4 PUSCH repeating units.

[0154] Enabling and disabling the RV (Repeated Version Cycle) both have beneficial effects in certain scenarios. Disabling the RV is beneficial because when the frequency offset is significant, the orthogonality between code sequences is disrupted. The receiver can improve performance by merging all repeating units and their corresponding code sequences to reduce the impact of the frequency offset. Enabling the RV, on the other hand, is beneficial because when the frequency offset is not significant, the orthogonality between code sequences is good. The receiver can then perform merging only within a PUSCH group, and then obtain RV merging gain between different PUSCH groups through merging different RVs.

[0155] Therefore, the embodiments of this disclosure enable and disable redundant version cycling in a relatively flexible manner. Furthermore, the granularity of redundant version cycling can also be configured for the UE, for example, redundant version cycling is performed every N PUSCH groups as an intermediate balance between enabling and disabling.

[0156] In some embodiments, before or after step S103, the terminal may also determine at least one of the following based on the terminal's capability information or network-side configuration information:

[0157] Enable redundant version looping;

[0158] The number of PUSCH repeating units applied in each redundant version of the redundant version cycle;

[0159] The number of PUSCH groups applied to each redundant version in the redundant version cycle;

[0160] Enable frequency hopping;

[0161] The number of PUSCH repetition units between frequency hopping intervals;

[0162] The number of PUSCH groups between frequency hopping intervals.

[0163] Here, determining the number of PUSCH groups applied in each redundant version of the redundant version cycle can be understood as determining the number of PUSCH groups that the redundant version cycle needs to traverse. Here, the number of PUSCH repeating units contained in each PUSCH group is equal to the code sequence length.

[0164] For a description of the configuration information, please refer to the description of the configuration information in step S101 above, which will not be repeated here.

[0165] The following explains how to determine whether to enable redundant version cycling based on terminal capability information.

[0166] For example, the UE reports a capability bit, where '0' indicates that redundant version cycling is disabled and '1' indicates that redundant version cycling is enabled.

[0167] For example, when a UE reports a single bit of capability, if the UE uses code sequence-based PUSCH transmission, then '0' indicates that redundant version cycle is disabled, and '1' indicates that redundant version cycle is enabled. For PUSCH transmission that does not use code sequence-based transmission, the UE's capability can be ignored.

[0168] For example, if a UE reports its capabilities for a certain duration, such as N time slots or N ms, it means that the UE can maintain phase continuity within that duration. If the UE performs a PUSCH transmission with applied code sequences, and the number of repetitions, time slots, or ms occupied by the PUSCH transmission is greater than or equal to N, then the redundant version cycle is disabled; otherwise, the redundant version cycle is enabled.

[0169] For example, a UE reports its capabilities for a code sequence length. When the reported code sequence length is 2, redundant version cycling is enabled; when the reported code sequence length is 4, redundant version cycling is disabled. The underlying reason is that when the code sequence length is small, it is less affected by frequency offset, and redundant version cycling can be used to obtain the gain of RV combining. However, when the code sequence length is large, it is more affected by frequency offset, requiring more repetitions for code sequence combining, so redundant version cycling cannot be enabled.

[0170] The following explains how to determine whether to enable redundant version cycling based on network-side configuration information.

[0171] For example, a new RRC parameter can be defined to explicitly determine whether redundant version loop is enabled when the parameter is configured as 'enabled' or '1', and whether redundant version loop is disabled when the parameter is not configured, or is configured as 'disabled' or '0'.

[0172] For example, a codepoint in the RV field of DCI can be used as a switch. The existing RV field has two bits, indicating four codepoints (00, 01, 10, 11), representing the RVs of the first transmission in a repeated transmission as (0, 1, 2, 3). For PUSCH using code sequences, one codepoint can indicate that the redundant version cycle is disabled, while the other three codepoints indicate that the redundant version cycle is enabled. For example, '00' or '11' indicates that the redundant version cycle is disabled.

[0173] For example, the network side might configure the code sequence length to be used by the UE. This could be done explicitly via RRC, or configured via RRC parameters and indicated by the TDRA field in the DCI. When the configured code sequence length is less than a threshold, redundant version cycling is used; when the code sequence length is greater than or equal to the threshold, redundant version cycling is disabled. For instance, redundant version cycling is used when the configured code sequence length is 2, and disabled when the code sequence length is 4. The implicit reason here is that when the code sequence length is small, it is less affected by frequency offset, and redundant version cycling can be used to obtain RV combining gain. However, when the code sequence length is large, it is more affected by frequency offset, requiring more repetitions for code sequence combining, thus redundancy version cycling cannot be enabled.

[0174] For example, other parameters can be used to indicate whether redundant version cycling is enabled, such as MCS (Multiple Choice Sequence). In other words, the configuration information can include MCS. When the MCS is greater than a preset threshold, redundant version cycling is disabled; when the MCS is less than or equal to a preset threshold, redundant version cycling is enabled. This is because at higher code rates, the receiver needs to merge code sequences across multiple PUSCH groups to improve performance and reduce frequency offset interference. At lower code rates, merging can be done within a single PUSCH group, allowing redundant version cycling to improve the merging gain between repetitions.

[0175] The following explains how to determine the number of PUSCH repeating units or the number of PUSCH groups applied in each redundant version cycle based on network-side configuration information.

[0176] For example, a new RRC parameter can be defined and configured with a value N, indicating that the redundant version cycle spans N PUSCH groups. The value of N can be one or more of {0, 1, 2, 4, 5, 8, 10, 16}. For example, when N is 16, it can be combined with the code sequence length of 2 to indicate that the same RV is used on every 32 PUSCH repetition units, corresponding to a maximum configurable repetition count of 32, which can implicitly indicate that the redundant version cycle is not used.

[0177] For example, the network side can configure the code sequence length to be used by the terminal. This can be done explicitly via RRC, or configured via RRC parameters and then indicated by the TDRA field in the DCI. The UE can implicitly know how many PUSCH groups it will cycle through for redundant versions via the code sequence length. If the maximum configurable code sequence length is Y, then when a UE is configured with a code sequence length of M, that UE will cycle through redundant versions across every Y / M PUSCH groups. For example, when the maximum configurable code sequence length is 4, a UE with a code sequence length of 2 will cycle through redundant versions across every two PUSCH groups, and a UE with a code sequence length of 4 will cycle through redundant versions across every PUSCH group. This is done to ensure that the RV patterns of UEs with a code sequence length of 2 and UEs with a code sequence length of 4 are consistent, allowing them to reuse each other.

[0178] If redundant version cyclic is enabled, the RV identifier (identity, ID) on the nth repetition can be obtained by modifying Table 1 above. In the formulas in Table 1, N represents the number of time slots configured in TBoMS. This parameter can be replaced with a parameter related to the code sequence length or the number of PUSCH groups to obtain the RV ID when using code sequences. For example, N can be replaced with:

[0179] Alt 1: N*M, where M is the code sequence length.

[0180] Alt 2: N*M*S, where M is the code sequence length and S is the number of PUSCH groups that the redundant version cyclically traverses.

[0181] Alt 3:P, where P represents the product of the number of TBoMS slots, the code sequence length, and the number of PUSCH groups cyclically spanned by the redundant version, i.e., the number of repeating units cyclically spanned by the redundant version (e.g., the number of slots).

[0182] As another example, when the transmission conditions include the overlap of PUSCH and non-repeating PUCCH in the time domain, the target behavior is performed based on the transmission conditions, including:

[0183] The target behavior is performed based on at least one of the following, where at least one includes:

[0184] First item: Priority configuration of PUSCH and PUCCH;

[0185] The second item: The contents of the UCI carried by the PUCCH;

[0186] The third item: Whether the UCI multiplexing carried by the PUCCH meets the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH; Here, the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, and at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length.

[0187] Here, meeting the timing requirements means ensuring that the terminal has enough time to prepare for the reception of DCI and the transmission of PUSCH. For example, when PUCCH is transmitted on slot 2 and the PUSCH group spans slot 1 and slot 2, if UCI is to be multiplexed on all repetitions within the PUSCH group when PUCCH and PUSCH on slot 2 overlap, then the terminal needs to have enough time to prepare for the transmission of UCI and PUSCH on slot 1.

[0188] The first part of a PUSCH and a PUSCH group are different concepts. A PUSCH group contains M repeating units, defined chronologically, and each PUSCH group uses a code sequence. The first part of a PUSCH, however, can be understood as a PUSCH comprising multiple parts, each containing X repeating units. At least one of these X repeating units in the first part overlaps with a PUCCH. The first part of a PUSCH contains one or more PUSCH groups, where X equals M or is a multiple of M. In other words, the first part of a PUSCH is the portion containing the repeating units that overlap with a PUCCH.

[0189] Fourth item: Does the UCI carried by the PUCCH overlap with the first PUSCH repeating unit in the first part of the PUSCH?

[0190] Fifth item: Whether the last PUSCH repeating unit in the first part of PUSCH is the last PUSCH repeating unit in PUSCH;

[0191] Item 6: Whether to disable HARQ feedback;

[0192] Item 7: Whether CSI is reused in PUSCH;

[0193] Item 8: Does the PUSCH include the uplink shared channel UL-SCH?

[0194] The target behavior includes at least one of the following:

[0195] Discard the PUCCH;

[0196] Discard the PUSCH repeating units in the first part of the PUSCH. Here, the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, and at least one of the X PUSCH repeating units overlaps with the PUCCH. X is one of the following: code sequence length, multiple of code sequence length.

[0197] Multiplex the UCI carried by PUCCH into the first part of PUSCH;

[0198] The UCI carried by the PUCCH is multiplexed into the second part of the PUSCH. Here, the second part of the PUSCH is X PUSCH repeating units after the first part of the PUSCH.

[0199] Send PUCCH after PUSCH repeat transmission;

[0200] Discard the SR in the UCI carried by the PUCCH;

[0201] Discard the CSI in the UCI carried by the PUCCH.

[0202] The first part and the second part of PUSCH are explained below.

[0203] In some implementations, the first or second part of the PUSCH includes a PUSCH group, containing X PUSCH repeating units, where X equals the code sequence length M. The X PUSCH repeating units apply the code sequence sequentially; that is, the first repeating unit in the X PUSCH repeating units applies the first element of the code sequence, the last repeating unit in the X PUSCH repeating units applies the last element of the code sequence, and so on. At least one of the X PUSCH repeating units in the first part of the PUSCH overlaps with the PUCCH in the time domain. The second part of the PUSCH contains the X PUSCH repeating units following the first part of the PUSCH.

[0204] Example 1: The code sequence is 4 units long, i.e., [s1, s2, s3, s4]. The PUSCH contains 8 PUSCH repeat units, each PUSCH repeat unit being one time slot in length. If the PUSCH overlaps with PUSCH repeat unit 3, as shown in Figure 8, the first part of the PUSCH contains PUSCH repeat units 1-4, and the second part of the PUSCH contains PUSCH repeat units 5-7. In Figure 8, the first part of the PUSCH is the second PUSCH group, and the second part of the PUSCH is the third PUSCH group.

[0205] Example 2: The code sequence is 2-bit long, i.e., [s1, s2]. The PUSCH contains 8 PUSCH repeating units, each repeating unit being one time slot long. If the PUSCH overlaps with repeating unit 3, as shown in Figure 9, the first part of the PUSCH contains repeating units 3 and 4, and the second part of the PUSCH contains repeating units 5 and 6. In Figure 9, the first part of the PUSCH is the third PUSCH group, and the second part of the PUSCH is the third PUSCH group.

[0206] In some implementations, the first or second part of the PUSCH comprises multiple PUSCH groups, i.e., containing X PUSCH repeating units, where X is a multiple of the code sequence length M. These X repeating units apply the code sequence sequentially and repeatedly; that is, the same code sequence is applied to every M repeating units. If all repeating PUSCH units are divided equally into multiple parts of length X, then the first part of the PUSCH is the portion of these parts that overlaps with the PUCCH.

[0207] Example 1: The code sequence is 2-bit long, i.e., [s1, s2], where X is twice the code sequence length 2. The PUSCH contains 8 PUSCH repeating units, each repeating unit being one time slot in length. If the PUSCH overlaps with repeating unit 3, as shown in Figure 10, the first part of the PUSCH contains repeating units 1-4, and the second part of the PUSCH contains repeating units 5-7. In Figure 10, the first part of the PUSCH includes the first and second groups of the PUSCH, and the second part of the PUSCH includes the third and fourth groups of the PUSCH.

[0208] Example 2: The code sequence is 2 units long, i.e., [s1, s2], where X is twice the code sequence length 2. The PUSCH contains 8 PUSCH repeating units, each repeating unit being one time slot in length. If the PUSCH overlaps with repeating unit 3, as shown in Figure 11, the first part of the PUSCH contains repeating units 5 to 7. In Figure 11, the first part of the PUSCH includes the third and fourth groups of the PUSCH.

[0209] Regarding the first item above, the priority configuration of PUSCH and PUCCH can include one of the following:

[0210] PUSCH has a higher priority than PUCCH.

[0211] The priority of PUSCH is equal to the priority of PUCCH;

[0212] PUSCH has a lower priority than PUCCH.

[0213] The priority of PUSCH being greater than that of PUCCH includes situations where the priority index of PUSCH is greater than that of PUCCH, or where the priority index of PUSCH is not 0, while PUCCH is not configured with a priority index.

[0214] The priority of PUSCH being equal to the priority of PUCCH includes: the priority index of PUSCH being equal to the priority index of PUCCH; or, one of PUSCH and PUCCH having a configured priority index of 0, while the other of PUSCH and PUCCH has no configured priority index; or neither PUSCH nor PUCCH has a configured priority or no configured priority index.

[0215] The priority of PUSCH being lower than that of PUCCH includes situations where the priority index of PUSCH is lower than that of PUCCH, or where the priority index configured for PUCCH is not 0, while PUSCH is not configured with a priority index.

[0216] The UCI carried by the PUCCH includes at least one of the following:

[0217] HARQ ACK information, CSI report, SR.

[0218] Multiplexing the UCI carried by the PUCCH into the first part of the PUSCH includes at least one of the following:

[0219] Reuse all of the UCI content into the first part of PUSCH;

[0220] Reuse the CSI report from UCI into the first part of PUSCH;

[0221] The HARQ ACK information in the UCI is multiplexed into the first part of the PUSCH;

[0222] The CSI report and HARQ ACK information from UCI are reused in the first part of PUSCH;

[0223] Multiplexing the UCI carried by the PUCCH into the second part of the PUSCH includes at least one of the following:

[0224] Reuse all of the UCI content into the second part of PUSCH;

[0225] Reuse the CSI report from UCI into Part 2 of PUSCH;

[0226] The HARQ ACK information in the UCI is reused in the second part of the PUSCH;

[0227] The CSI report and HARQ ACK information from UCI are reused in the second part of PUSCH.

[0228] The term "discarding" in this disclosure can be understood as, or replaced by, not sending. For example, discarding a PUCCH can be understood as not sending the PUCCH.

[0229] Based on transmission conditions, executing the target behavior can include the following schemes:

[0230] Option 1-1: If the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, the terminal either does not send or discards all PUSCH repeating units in the overlapping PUSCH group. That is, it discards the PUSCH repeating units in the first part of the PUSCH. Here, the PUSCH can be divided into multiple PUSCH groups, each containing M PUSCH repeating units, where M is the code sequence length. Each PUSCH group uses the same code sequence.

[0231] Option 1-2: If the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, and if the PUCCH carries a HARQ ACK, then all PUSCH repeating units within the overlapping PUSCH group should not be sent or should be discarded. In other words, if the UCI carried by the PUCCH contains HARQ ACK information, the PUSCH repeating units in the first part of the PUSCH should be discarded.

[0232] Scheme 1-3: If the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group, and the PUCCH does not carry a HARQ ACK.

[0233] Scheme 1-3-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0234] In other words, if the first PUSCH repeating unit in the first part of PUCCH overlaps with the first PUSCH repeating unit, or if the timing requirements can be met by multiplexing the UCI carried by PUCCH on the first PUSCH repeating unit in the first part of PUSCH, the target behavior includes multiplexing the UCI carried by PUCCH into the first part of PUSCH.

[0235] Option 1-3-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within a PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0236] If the PUSCH group is not the last PUSCH group, then UCI reuses it on each PUSCH repeating unit in the next PUSCH group.

[0237] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0238] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI carried by the PUCCH cannot meet the timing requirements when multiplexed on the first PUSCH repeating unit in the first part of the PUSCH, then if the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, the UCI carried by the PUCCH will be multiplexed into the second part of the PUSCH.

[0239] If the last PUSCH repeat unit in the first part of the PUSCH is the last PUSCH repeat unit in the PUSCH, then the PUCCH is sent after the PUSCH repeat transmission.

[0240] In some implementations, schemes 1-1 to 1-3-2 above can be applied when the priority of PUSCH is lower than that of PUCCH.

[0241] Option 2-1: If the PUCCH overlaps with a PUSCH repetition unit within a PUSCH group, the terminal does not send or discards the PUCCH that overlaps with the PUSCH.

[0242] Option 2-2: If a PUCCH overlaps with a PUSCH repetition unit within a PUSCH group, and if the PUCCH does not carry a HARQ ACK, then the PUCCH overlapping with the PUSCH should not be sent or should be discarded.

[0243] Scheme 2-3: If the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group, and the PUCCH carries a HARQ ACK.

[0244] Scheme 2-3-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0245] In other words, if the first PUSCH repeating unit in the first part of PUCCH overlaps with the first PUSCH repeating unit, or if the timing requirements can be met by multiplexing the UCI carried by PUCCH on the first PUSCH repeating unit in the first part of PUSCH, the target behavior includes multiplexing the UCI carried by PUCCH into the first part of PUSCH.

[0246] Option 2-3-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0247] If the PUSCH group is not the last PUSCH group, then UCI reuses it on each PUSCH repeating unit in the next PUSCH group.

[0248] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0249] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI carried by the PUCCH cannot meet the timing requirements when multiplexed on the first PUSCH repeating unit in the first part of the PUSCH, then if the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, the UCI carried by the PUCCH will be multiplexed into the second part of the PUSCH.

[0250] If the last PUSCH repeat unit in the first part of the PUSCH is the last PUSCH repeat unit in the PUSCH, then the PUCCH is sent after the PUSCH repeat transmission.

[0251] In some implementations, schemes 2-1 to 2-3-2 above can be applied when the priority of PUSCH is greater than that of PUCCH.

[0252] Scheme 3-1: If the PUCCH overlaps with a PUSCH repetition unit within a PUSCH group, the UCI carried in the PUCCH channel includes one or more of the following: HARQ ACK information, CSI report, and SR.

[0253] Option 3-1-1: If the UCI in PUCCH contains SR.

[0254] If a PUSCH does not contain a UL-SCH, all duplicate PUSCHs within that PUSCH group are discarded, but the PUCCH is still sent.

[0255] If the PUSCH contains UL-SCH and the UCI in the PUCCH contains SR, then the SR is discarded.

[0256] In other words, if the UCI carried by the PUCCH contains an SR, and the PUSCH does not contain a UL-SCH, the PUSCH repeating unit in the first part of the PUSCH is discarded. If the PUSCH contains a UL-SCH, the SR in the UCI carried by the PUCCH is discarded.

[0257] Option 3-1-2: If the UCI in the PUCCH contains at least one of the HARQ ACK information and CSI report.

[0258] If the UCI contains only CSI, and the PUSCH already reuses the CSI (e.g., non-periodic CSI or semi-persistent CSI), then the CSI report in the UCI will be discarded and the PUSCH will not be sent.

[0259] Otherwise, adopt one of the schemes 3-X (X is not 1).

[0260] In other words, if the UCI carried by the PUCCH includes a CSI report and the CSI is reused in the PUSCH, discard the CSI in the UCI carried by the PUCCH, and discard the PUCCH itself. Otherwise, adopt one of Schemes 3-X (X is not 1).

[0261] Scheme 3-2-1: If the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group.

[0262] Scheme 3-2-1-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0263] In other words, when the first PUSCH repeating unit in the first part of PUCCH overlaps with the first PUSCH repeating unit, or when the timing requirements can be met by multiplexing the UCI carried by PUCCH on the first PUSCH repeating unit in the first part of PUSCH, the target behavior includes multiplexing the UCI carried by PUCCH into the first part of PUSCH.

[0264] Scheme 3-2-1-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0265] If the PUSCH group is not the last PUSCH group, then UCI reuses it on each PUSCH repeating unit in the next PUSCH group.

[0266] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0267] In other words, if the last PUSCH repeating unit in the first part of the PUSCH is the last PUSCH repeating unit in the PUSCH, or if the UCI carried by the PUCCH does not meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, the target behavior includes multiplexing the UCI carried by the PUCCH into the second part of the PUSCH.

[0268] If the last PUSCH repeat unit in the first part of the PUSCH is the last PUSCH repeat unit in the PUSCH, the target behavior includes sending the PUCCH after the PUSCH repeat transmission.

[0269] For scheme 3-2-1, the method of UCI multiplexing is adopted on all PUSCH repeating units within the first part of the PUSCH. First, it is determined whether multiplexing is possible in the first part. If multiplexing is not possible, the PUSCH is discarded or the transmission is postponed.

[0270] Scheme 3-2-2: If the PUCCH overlaps with a PUSCH repetition unit within a PUSCH group, the UCI carried in the PUCCH channel contains HARQ ACK information, one or more of the following in the CSI report:

[0271] Option 3-2-2-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group.

[0272] If aperiodic CSI or semi-persistent CSI has already been multiplexed in the PUSCH, then the HARQ ACK information in the UCI will only be multiplexed on each PUSCH repeating unit within the PUSCH group, and the PUCCH will no longer be transmitted.

[0273] If a non-periodic CSI or semi-persistent CSI is not multiplexed in the PUSCH, the HARQ ACK information and CSI report in the UCI are multiplexed on each PUSCH repeating unit in the PUSCH group, and the PUCCH is no longer transmitted.

[0274] In other words, if the PUCCH overlaps with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI carried by the PUCCH satisfies the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the CSI is multiplexed in the PUSCH, the target behavior includes multiplexing the HARQ ACK information in the UCI carried by the PUCCH into the first part of the PUSCH, and discarding the PUCCH.

[0275] If CSI is not reused in PUSCH, the target behavior includes reusing the HARQ ACK information and CSI report from the UCI carried by PUCCH into the first part of PUSCH, and discarding PUCCH.

[0276] Scheme 3-2-2-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0277] Option 3-2-2-2-1: If the PUSCH group is not the last PUSCH group.

[0278] If aperiodic CSI or semi-persistent CSI has already been multiplexed in the PUSCH, then the HARQ ACK information in the UCI will only be multiplexed in each PUSCH repetition unit in the next PUSCH group, and the PUCCH will no longer be transmitted.

[0279] If a non-periodic CSI or semi-persistent CSI is not multiplexed in the PUSCH, the HARQ ACK information and CSI report in the UCI are multiplexed on each PUSCH repeating unit in the next PUSCH group, and the PUCCH is no longer transmitted.

[0280] In other words, if the UCI carried by the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the timing requirement is not met when the UCI carried by the PUCCH is multiplexed onto the first PUSCH repeating unit in the first part of the PUSCH, and if the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, and the CSI is multiplexed in the PUSCH, the target behavior includes multiplexing the HARQ ACK information in the UCI carried by the PUCCH into the second part of the PUSCH, and discarding the PUCCH.

[0281] If the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, and the CSI is not reused in the PUSCH, the target behavior includes reusing the HARQ ACK information and CSI report in the UCI carried by the PUCCH into the second part of the PUSCH, and discarding the PUCCH.

[0282] Option 3-2-2-2-2: If the PUSCH group is the last PUSCH group in the PUSCH, then the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0283] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI multiplexing carried by the PUCCH does not meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the last PUSCH repeating unit in the first part of the PUSCH is the last PUSCH repeating unit in the PUSCH, the target behavior includes sending the PUCCH after the PUSCH repeating transmission.

[0284] For scheme 3-2-2, that is, for UCI containing HARQ ACK or CSI, the method of reusing all PUSCH repeating units in the first part is adopted. First, it is determined which part to reuse, and then based on the reuse of CSI in the PUSCH, it is determined which information of UCI to reuse. If it cannot be reused, the PUCCH is discarded or postponed, and special handling is performed for the discarding case.

[0285] Scheme 3-3-1: If the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, that is, the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group.

[0286] Option 3-3-1-1: If the UCI in PUCCH only carries CSI reports, that is, it does not carry HARQ ACK feedback.

[0287] Scheme 3-3-1-1-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0288] In other words, if the UCI carried by the PUCCH includes a CSI report but does not include HARQ ACK information, and if the UCI carried by the PUCCH overlaps with the first PUSCH repetition unit in the first part of the PUSCH, or if the UCI carried by the PUCCH is multiplexed on the first PUSCH repetition unit in the first part of the PUSCH to meet timing requirements, the target behavior includes multiplexing the UCI carried by the PUCCH into the first part of the PUSCH.

[0289] Scheme 3-3-1-1-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0290] If the PUSCH group is not the last PUSCH group, then UCI reuses it on each PUSCH repeating unit in the next PUSCH group.

[0291] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0292] In other words, if the UCI carried by the PUCCH includes the CSI report but does not include HARQ ACK information, and if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the timing requirements are not met when the UCI carried by the PUCCH is multiplexed onto the first PUSCH repeating unit in the first part of the PUSCH, and further, if the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, the target behavior includes multiplexing the UCI carried by the PUCCH into the second part of the PUSCH.

[0293] If the last PUSCH repeat unit in the first part of the PUSCH is the last PUSCH repeat unit in the PUSCH, the target behavior includes sending the PUCCH after the PUSCH repeat transmission.

[0294] Option 3-3-1-2: If the PUCCH carries HARQ ACK feedback.

[0295] UCI is still transmitted on PUCCH, while all PUSCH repeating units within the PUSCH group are discarded.

[0296] In other words, if the UCI carried by the PUCCH includes HARQ ACK information, the PUSCH repeating unit in the first part of the PUSCH is discarded.

[0297] Scheme 3-3-2: If the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, that is, the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group.

[0298] Option 3-3-2-1: If the UCI in PUCCH only carries CSI reports, that is, it does not carry HARQ ACK feedback.

[0299] If a non-periodic CSI or semi-persistent CSI has already been reused in the PUSCH, then the UCI is discarded and the PUCCH is no longer transmitted.

[0300] If non-periodic CSI or semi-persistent CSI is not reused in PUSCH.

[0301] Furthermore, if the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0302] If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0303] Furthermore, if the PUSCH group is not the last PUSCH group, then UCI multiplexes each PUSCH repeating unit within the next PUSCH group.

[0304] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0305] In other words, if the UCI carried by the PUCCH includes a CSI report but does not include HARQ ACK information, the default behavior includes discarding the PUCCH if the CSI is multiplexed in the PUSCH. If the CSI is not multiplexed in the PUSCH, and the PUCCH overlaps with the first PUSCH repetition unit in the first part of the PUSCH, or if the UCI carried by the PUCCH is multiplexed on the first PUSCH repetition unit in the first part of the PUSCH and meets the timing requirements, the target behavior includes multiplexing the UCI carried by the PUCCH into the first part of the PUSCH.

[0306] If the CSI is not multiplexed in the PUSCH, and the PUCCH does not overlap with the first PUSCH repetition unit in the first part of the PUSCH, or if the timing requirement is not met when the UCI carried by the PUCCH is multiplexed onto the first PUSCH repetition unit in the first part of the PUSCH, and if the last PUSCH repetition unit in the first part of the PUSCH is not the last PUSCH repetition unit in the PUSCH, then the target behavior includes multiplexing the UCI carried by the PUCCH into the second part of the PUSCH. If the last PUSCH repetition unit in the first part of the PUSCH is the last PUSCH repetition unit in the PUSCH, then the target behavior includes sending the PUCCH after the PUSCH repetition transmission.

[0307] Scheme 3-3-2-2: If the PUCCH carries HARQ ACK feedback.

[0308] The UCI is still transmitted on the PUCCH, while all PUSCH repeating units within the PUSCH group are discarded. That is, if the UCI carried by the PUCCH includes HARQ ACK information, the target behavior includes discarding the PUSCH repeating units in the first part of the PUSCH.

[0309] The difference between Scheme 3-3-2 and Scheme 3-3-1 is that the specific content of UCI is reused in PUSCH is determined based on whether CSI is reused in PUSCH.

[0310] Scheme 3-4-1: If the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, that is, the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group.

[0311] Scheme 3-4-1-1 If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0312] In other words, when the first PUSCH repeating unit in the first part of PUCCH overlaps with the first PUSCH repeating unit, or when the UCI carried by PUCCH satisfies the timing requirements on the first PUSCH repeating unit in the first part of PUSCH, the target behavior includes multiplexing the UCI carried by PUCCH into the first part of PUSCH.

[0313] Scheme 3-4-1-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0314] Scheme 3-4-1-2-1: If the PUCCH carries HARQ ACK feedback, the UCI is still transmitted on the PUCCH, while all PUSCH duplicate units in the PUSCH group are discarded.

[0315] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI carried by the PUCCH does not meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the UCI carried by the PUCCH contains HARQ ACK information, the target behavior includes discarding the PUSCH repeating unit in the first part of the PUSCH.

[0316] Option 3-4-1-2-2: If the PUCCH only carries CSI reports, that is, it does not carry HARQ ACK feedback.

[0317] Furthermore, if the PUSCH group is not the last PUSCH group, then UCI multiplexes each PUSCH repeating unit within the next PUSCH group.

[0318] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0319] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the timing requirements are not met when the UCI carried by the PUCCH is multiplexed onto the first PUSCH repeating unit in the first part of the PUSCH, and if the UCI carried by the PUCCH includes a CSI report but does not include HARQ ACK information, and further, if the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, the target behavior includes multiplexing the UCI carried by the PUCCH into the second part of the PUSCH. If the last PUSCH repeating unit in the first part of the PUSCH is the last PUSCH repeating unit in the PUSCH, the target behavior includes sending the PUCCH after the PUSCH repeating transmission.

[0320] For scheme 3-4-1, first determine if it can be directly multiplexed in the first overlapping part. If not, if the PUCCH contains a HARQ ACK, discard the PUSCH. If the PUCCH does not contain a HARQ ACK, then multiplex it in the second part. Scheme 3-4-1 indicates that HARQ ACK transmission has a high priority and cannot be delayed.

[0321] Scheme 3-4-2: If the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group, that is, the PUCCH overlaps with a PUSCH repeating unit within a PUSCH group.

[0322] Option 3-4-2-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group.

[0323] Furthermore, if aperiodic CSI or semi-persistent CSI has already been multiplexed in the PUSCH, then the HARQ ACK information in the UCI is only multiplexed on each PUSCH repeating unit within the PUSCH group, and the PUCCH is no longer transmitted.

[0324] Alternatively, if non-periodic CSI or semi-persistent CSI is not multiplexed in the PUSCH, the HARQ ACK information and CSI report in the UCI are multiplexed on each PUSCH repeating unit in the PUSCH group, and the PUCCH is no longer transmitted.

[0325] In other words, if the first PUSCH repetition unit overlaps in the first part of PUCCH and PUSCH, or if the UCI carried by PUCCH is multiplexed on the first PUSCH repetition unit in the first part of PUSCH to meet the timing requirements, and if CSI is multiplexed in PUSCH, the target behavior includes multiplexing the HARQ ACK information of the UCI carried by PUCCH into the first part of PUSCH and discarding PUCCH.

[0326] If CSI is not reused in PUSCH, the default behavior includes reusing the HARQ ACK information and CSI report of UCI carried by PUCCH into the first part of PUSCH and discarding PUCCH.

[0327] Scheme 3-4-2-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0328] Scheme 3-4-2-2-1: If the PUCCH carries HARQ ACK feedback, the UCI is still transmitted on the PUCCH, while all PUSCH duplicate units in the PUSCH group are discarded.

[0329] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI carried by the PUCCH does not meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the UCI carried by the PUCCH includes HARQ ACK information, the target behavior includes discarding the PUSCH repeating unit in the first part of the PUSCH.

[0330] Option 3-4-2-2-2: If the PUCCH only carries CSI reports, that is, it does not carry HARQ ACK feedback.

[0331] Furthermore, if aperiodic CSI or semi-persistent CSI has already been reused in PUSCH, then UCI is discarded and PUCCH is no longer transmitted.

[0332] If non-periodic CSI or semi-persistent CSI is not reused in the PUSCH, the following two scenarios may be further included:

[0333] If the PUSCH group is not the last PUSCH group, the HARQ ACK information and CSI report in the UCI are multiplexed on each PUSCH repeating unit in the next PUSCH group, and the PUCCH is no longer transmitted.

[0334] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0335] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the timing requirements are not met when the UCI carried by the PUCCH is multiplexed onto the first PUSCH repeating unit in the first part of the PUSCH, and if the UCI carried by the PUCCH includes a CSI report but does not include HARQ ACK information, and further, if the CSI is not multiplexed in the PUSCH and the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, the target behavior includes multiplexing the HARQ ACK information and CSI report in the UCI carried by the PUCCH into the second part of the PUSCH.

[0336] If CSI is not reused in the PUSCH, and the last PUSCH repeating unit in the first part of the PUSCH is not the last PUSCH repeating unit in the PUSCH, the target behavior includes sending PUCCH after the PUSCH repeating transmission.

[0337] The difference between Scheme 3-4-2 and Scheme 3-4-1 is that Scheme 3-4-2 determines which UCI content is reused in PUSCH based on whether CSI is reused in PUSCH.

[0338] Scheme 3-5-1: If the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group.

[0339] Scheme 3-5-1-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the PUSCH group.

[0340] In other words, if the first PUSCH repeating unit in the first part of PUCCH overlaps with the first PUSCH repeating unit, or if the UCI carried by PUCCH satisfies the timing requirements on the first PUSCH repeating unit in the first part of PUSCH, the target behavior includes multiplexing the UCI carried by PUCCH into the first part of PUSCH.

[0341] Scheme 3-5-1-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0342] If the UCI in the PUCCH only contains a CSI report and no HARQ ACK information, the UCI is discarded, the PUCCH is not sent, and the PUSCH is sent as usual.

[0343] If the UCI in the PUCCH contains HARQ ACK information, all duplicate PUSCH units in the PUSCH group will be discarded, and the PUCCH will be sent as usual.

[0344] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI multiplexing carried by the PUCCH does not meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the UCI carried by the PUCCH includes a CSI report but does not include HARQ ACK information, the target behavior is to discard the PUCCH. If the UCI carried by the PUCCH includes HARQ ACK information, the target behavior is to discard the PUSCH repeating unit in the first part of the PUSCH.

[0345] Scheme 3-5-1 prioritizes UCI multiplexing on the first overlapping part. If direct multiplexing is not possible, the HARQ ACK message is considered to have higher priority, and PUSCH is discarded directly, while CSI has lower priority and PUCCH can be discarded.

[0346] Scheme 3-5-2: If the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group.

[0347] Scheme 3-5-2-1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, the following two cases may be further included.

[0348] If aperiodic CSI or semi-persistent CSI has already been multiplexed in the PUSCH, then the HARQ ACK information in the UCI will only be multiplexed on each PUSCH repeating unit in the PUSCH group, and the PUCCH will no longer be transmitted.

[0349] If a non-periodic CSI or semi-persistent CSI is not multiplexed in the PUSCH, the HARQ ACK information and CSI report in the UCI are multiplexed on each PUSCH repeating unit in the PUSCH group, and the PUCCH is no longer transmitted.

[0350] In other words, if the first PUSCH repeating unit in the first part of PUCCH overlaps with the first PUSCH repeating unit in the first part of PUSCH, or if the UCI carried by PUCCH is multiplexed on the first PUSCH repeating unit in the first part of PUSCH to meet the timing requirements, and if CSI is multiplexed in PUSCH, the target behavior includes multiplexing the HARQ ACK information in the UCI carried by PUCCH into the first part of PUSCH.

[0351] If the CSI is not reused in the PUSCH, the target behavior includes reusing the UCIHARQ ACK information and CSI report carried by the PUCCH into the second part of the PUSCH and discarding the PUCCH.

[0352] Scheme 3-5-2-2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if UCI multiplexing on the first PUSCH repeating unit of the PUSCH group does not meet the timing requirements, the following two situations may be further included.

[0353] If the UCI in the PUCCH only contains a CSI report and no HARQ ACK information, the UCI is discarded, the PUCCH is not sent, and the PUSCH is sent as usual.

[0354] If the UCI in the PUCCH contains HARQ ACK information, all duplicate PUSCH units in the PUSCH group will be discarded, and the PUCCH will be sent as usual.

[0355] In other words, if the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI carried by the PUCCH does not meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the UCI carried by the PUCCH includes the CSI report but does not include HARQ ACK information, the target behavior is to discard the PUCCH.

[0356] If the UCI carried by the PUCCH includes HARQ ACK information, the target behavior includes discarding the PUSCH duplicate unit in the first part of the PUSCH.

[0357] Scheme 3-5-2 prioritizes UCI multiplexing on the first overlapping portion. If direct multiplexing is not possible, HARQ ACK is considered to have higher priority, and PUSCH is discarded directly, while CSI has lower priority and PUSCH can be discarded. The difference from Scheme 5 below is that it determines which UCI content to multiplex onto PUSCH based on whether CSI is reused in PUSCH.

[0358] Scheme 3-6: If the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group.

[0359] If the UCI in the PUCCH only contains a CSI report and no HARQ ACK information, the UCI is discarded, the PUCCH is not sent, and the PUSCH is sent as usual.

[0360] If the UCI in the PUCCH contains HARQ ACK information, all duplicate PUSCH units in the PUSCH group will be discarded, and the PUCCH will be sent as usual.

[0361] In other words, when there is overlap between PUCCH and PUSCH repetitions and the UCI carried by the PUCCH includes a CSI report but does not include HARQ ACK information, the target behavior includes discarding the PUCCH. When there is overlap between PUCCH and PUSCH repetitions and the UCI carried by the PUCCH includes HARQ ACK information, the target behavior includes discarding the PUSCH repetition unit in the first part of the PUSCH.

[0362] For schemes 3-6, UCI multiplexing on PUSCH is not considered, and HARQ ACK is considered to have high priority, so PUSCH is directly discarded, while CSI has low priority and PUCCH can be discarded.

[0363] In some embodiments, whether HARQ feedback is disabled is related to whether the code sequence function is enabled. For example, HARQ feedback is disabled when the code sequence function is enabled, or when using code sequences for PUSCH transmission.

[0364] Option 3-7-1: When HARQ feedback is disabled, if the PUCCH overlaps with a PUSCH repetition unit within a PUSCH group, and the PUCCH only contains CSI, then the UCI is discarded, and the PUCCH is no longer sent, or the PUCCH is postponed until after the PUSCH transmission.

[0365] In other words, if the UCI carried by the PUCCH overlaps with the first PUSCH repeat unit in the first part of the PUSCH when HARQ feedback is disabled, and the UCI carried by the PUCCH includes a CSI report, the target behavior is to discard the PUCCH or send the PUCCH after the PUSCH repeat transmission.

[0366] Option 3-7-2: When HARQ feedback is disabled, if the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group, the PUCCH will only contain CSI.

[0367] If a non-periodic CSI or semi-persistent CSI has already been reused in the PUSCH, discard the UCI and do not send the PUCCH again.

[0368] If non-periodic CSI or semi-persistent CSI is not reused in the PUSCH, the following two scenarios may be further included.

[0369] If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI will be multiplexed on each PUSCH repeating unit in the PUSCH group, and the PUCCH will no longer be transmitted.

[0370] If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group, the PUCCH will no longer be transmitted.

[0371] In other words, with HARQ feedback disabled, if the UCI carried by the PUCCH overlaps with the first PUSCH repeating unit in the first part of the PUSCH, and the UCI carried by the PUCCH includes a CSI report, the following two cases can be included:

[0372] Case 1: When CSI is reused in PUSCH, the target behavior includes discarding PUSCH.

[0373] Case 2: If the UCI carried by the PUCCH overlaps with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI carried by the PUCCH is multiplexed on the first PUSCH repeating unit in the first part of the PUSCH to meet the timing requirements, the default behavior includes multiplexing the UCI carried by the PUCCH into the first part of the PUSCH.

[0374] If the UCI carried by the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the timing requirement is not met when the UCI carried by the PUCCH is multiplexed on the first PUSCH repeating unit in the first part of the PUSCH, the target behavior includes discarding the PUCCH.

[0375] For scheme 3-7-2, if HARQ feedback is disabled, CSI is reused if the timing requirements are met, and discarded if they are not.

[0376] Option 3-7-3: When HARQ feedback is disabled, if the PUCCH overlaps with a repeating PUSCH unit within a PUSCH group, the PUCCH will only contain CSI.

[0377] If a non-periodic CSI or semi-persistent CSI has already been reused in the PUSCH, discard the UCI and do not send the PUCCH again.

[0378] In other words, if HARQ feedback is disabled, and there is overlap between PUCCH and PUSCH, and the UCI carried by PUCCH includes a CSI report, and if CSI is reused in PUSCH, the target behavior is to discard PUCCH.

[0379] If non-periodic CSI or semi-persistent CSI is not reused in the PUSCH, the following two scenarios may be further included.

[0380] Case 1: If the PUCCH overlaps with the first PUSCH repeating unit in the PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the PUSCH group, then the UCI will be multiplexed on every PUSCH repeating unit in the PUSCH group, and the PUCCH will no longer be transmitted.

[0381] Case 2: If the PUCCH overlaps with a non-first PUSCH repeating unit within the PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the PUSCH group.

[0382] If the PUSCH group is not the last PUSCH group, the CSI report in the UCI is multiplexed on each PUSCH repeating unit in the next PUSCH group, and the PUCCH is no longer transmitted.

[0383] If the PUSCH group is the last PUSCH group in the PUSCH series, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0384] In other words, if HARQ feedback is disabled, and there is overlap between PUCCH and PUSCH, and the UCI carried by PUCCH includes CSI reports, and if CSI is not reused in PUSCH, the following two scenarios are possible:

[0385] Case 1: If the first PUSCH repeating unit overlaps in the first part of PUCCH and PUSCH, or if the UCI carried by PUCCH is multiplexed on the first PUSCH repeating unit in the first part of PUSCH to meet the timing requirements, and if the last PUSCH repeating unit in the first part of PUSCH is not the last PUSCH repeating unit in PUSCH, the target behavior includes multiplexing the UCI carried by PUCCH into the first part of PUSCH.

[0386] Case 2: If the PUCCH does not overlap with the first PUSCH repeating unit in the first part of the PUSCH, or if the UCI multiplexing carried by the PUCCH does not meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH, and if the last PUSCH repeating unit in the first part of the PUSCH is the last PUSCH repeating unit in the PUSCH, the target behavior includes sending the PUCCH after the PUSCH repeating transmission.

[0387] For scheme 3-7-3, if the CSI meets the timing requirements, it is reused in the first part; if it does not meet the requirements, it is reused in the second part; if it still fails, it is discarded or the transmission is postponed.

[0388] Schemes 3-1 to 3-7 above all assume that UCI is multiplexed within a single PUSCH group, meaning that the number of PUSCH repeating units X in the first or second part of the PUSCH is equal to the number of PUSCH repeating units M in the PUSCH group. Scheme 3-8 below, however, assumes that X can be a multiple of M.

[0389] Scheme 3-8: This scheme needs to be combined with other schemes involving user multiplexing. Based on the code sequence length (configured for each terminal or configured for each PUSCH transmission), whether redundancy version cycle is enabled, whether frequency hopping is enabled, and one or more of the number of configured PUSCH groups, it is necessary to determine how many PUSCH repeating units of PUSCH groups the UCI is multiplexed on (that is, to determine which PUSCH repeating units of PUSCH the UCI is multiplexed on).

[0390] For example, if the maximum configurable code sequence length is Y, then when a UE is configured with a code sequence length of M, the UE will perform UCI multiplexing in Y / M PUSCH groups.

[0391] For example, when redundancy version cyclic is enabled and the code sequence length is 2, if UCI multiplexing is involved, the UCI is multiplexed onto the PUSCH repeating unit of two PUSCH groups. When redundancy version cyclic is disabled or the code sequence length is 4, the UCI is multiplexed onto the PUSCH repeating unit of one PUSCH group.

[0392] For example, when the maximum configurable code sequence length is 4, the UE with a code sequence length of 2 performs redundant version cycling on the PUSCH repeating unit of two PUSCH groups across each PUSCH, and the UE with a code sequence length of 4 performs redundant version cycling on the PUSCH repeating unit of one PUSCH group across each PUSCH.

[0393] For example, when the code sequence length is 4, if UCI multiplexing is involved, the UCI is multiplexed onto the PUSCH repeating unit of one PUSCH group. When the code sequence length is 2, if UCI multiplexing is involved, the UCI is multiplexed onto the PUSCH repeating units of two PUSCH groups. If the PUSCH group overlapping with the PUCCH is the Nth PUSCH group, and if N is odd, then the PUSCH repeating units of the two PUSCH groups are the PUSCH repeating units of the Nth and (N+1th)th PUSCH groups, or the PUSCH repeating units of the (N+2th)th and (N+3rd)th PUSCH groups. These two can be determined based on whether timing requirements are met.

[0394] If N is even, then the repeating units of the two PUSCH groups are the repeating units of the (N-1)th and Nth PUSCH groups, or the repeating units of the (N+1)th and (N+2)th PUSCH groups. These two can be determined based on whether the timing requirements are met.

[0395] For example, combining scheme 3-8 with scheme 3-2-1 results in the following scheme:

[0396] Scheme 3-2-1 & Scheme 3-8: If a PUSCH repeating unit overlaps with the Nth PUSCH group of PUSCH and the code sequence length is 4.

[0397] If the PUCCH overlaps with the first PUSCH repeating unit in the Nth PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the Nth PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the Nth PUSCH group.

[0398] If the PUCCH overlaps with a non-first PUSCH repeating unit within the Nth PUSCH group, or if the timing requirements are not met when the UCI is multiplexed on the first PUSCH repeating unit of the Nth PUSCH group.

[0399] If the last PUSCH repeating unit of the Nth PUSCH group is not the last PUSCH repeating unit of the PUSCH group, that is, if the Nth PUSCH group is not the last PUSCH group, then UCI is multiplexed on each PUSCH repeating unit in the (N+1)th PUSCH group.

[0400] If the last PUSCH repeat unit of the Nth PUSCH group is the last PUSCH repeat unit of PUSCH, that is, if the Nth PUSCH group is the last PUSCH group, then the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0401] For example, if the code sequence length is 2, and if N is odd.

[0402] If the PUCCH overlaps with the first PUSCH repeating unit in the Nth PUSCH group, or if the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit in the Nth PUSCH group, then the UCI is multiplexed on each PUSCH repeating unit in the Nth and N+1th PUSCH groups.

[0403] If the PUCCH overlaps with a non-first PUSCH repeating unit within the Nth PUSCH group, or if UCI multiplexing on the first PUSCH repeating unit of the Nth PUSCH group does not meet timing requirements. Furthermore, if there are at least three more PUSCH groups following the Nth PUSCH group, then UCI is multiplexed on each PUSCH repeating unit within the (N+2)th and (N+3)th PUSCH groups.

[0404] If there are fewer than 3 PUSCH groups after the Nth PUSCH group, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0405] For example, if the code sequence length is 2, and if N is even.

[0406] If the timing requirements can be met by multiplexing the UCI on the first PUSCH repeating unit of the N-1th PUSCH group, then the UCI can be multiplexed on each PUSCH repeating unit of the N-1th and Nth PUSCH groups.

[0407] If the timing requirements are not met by UCI multiplexing on the first PUSCH repetition unit of the N-1th PUSCH group, further, the following two cases can be included:

[0408] If there are at least two more PUSCH groups after the Nth PUSCH group, then UCI reuses each PUSCH repeating unit in the N+1 and N+2th PUSCH groups.

[0409] If there are fewer than two PUSCH groups after the Nth PUSCH group, the PUCCH will be discarded or postponed until after the PUSCH transmission.

[0410] In some implementations, schemes 3-1 to 3-8 above can be applied when the priority of PUSCH is equal to the priority of PUCCH.

[0411] Based on the above schemes 1 to 3-8, it is possible to avoid the destruction of code sequence orthogonality by UCI multiplexing when PUSCH is transmitted using application code sequences and when non-repeating PUCCH and PUSCH overlap in the time domain.

[0412] The solutions shown in Schemes 1 to 3-8 above are merely exemplary and do not constitute a limitation on the technical solutions of the embodiments of this disclosure. Schemes 1 to 3-8 can be arbitrarily combined, and any combination of Schemes 1 to 3-8 should also fall within the protection scope of the embodiments of this disclosure.

[0413] In some embodiments, when PUSCH transmission is performed using application code sequences and repeated PUCCH and PUSCH overlap in the time domain, it is also necessary to avoid the destruction of code sequence orthogonality by UCI multiplexing.

[0414] In a repeatedly transmitted PUCCH, only one of HARQ ACK, SR, and CSI report will be included, without multiplexing of multiple types, unlike a non-repeating PUCCH. When a PUSCH transmission with applied code sequences overlaps with a repeated PUCCH in a certain time domain resource, the processing method can include one or more of the following. That is, when the transmission conditions include the overlap of PUSCH and repeated PUCCH in the time domain resource, the target behavior includes at least one of the following:

[0415] Discard the PUSCH repeating units in the first part of the PUSCH, where the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length;

[0416] Discard any PUCCH that overlaps with PUSCH.

[0417] As an example, discarding the repeating units of PUSCH in the first part of PUSCH includes:

[0418] In response to the satisfaction of a first condition, the PUSCH repeating unit in the first part of the PUSCH is discarded, the first condition including at least one of the following:

[0419] The UCI carried by the repeated PUCCH includes HARQ ACK information;

[0420] The repeated PUCCH carries a CSI report in the UCI;

[0421] The number of PUCCH repeating units that overlap with PUSCH in a repeating PUCCH is greater than N, where N is a positive integer.

[0422] Here, N can be a predefined value, a value configured on the network side, a value related to the number of PUCCH repetitions or the number of PUSCH repetition units in the PUSCH, or the number of PUCCH repetitions multiplied by a value C between 0 and 1. Here, C can be a predefined value or a value configured on the network side. For example, when C is 0.5, it means that when 50% of the PUCCH repetition units overlap with the PUSCH repetitions, the first condition is that the number of PUCCH repetition units overlapping with the PUSCH in the repeated PUCCH is greater than N.

[0423] As an example, discarding PUCCHs that overlap with PUSCHs includes: in response to the number of PUCCH repeating units that overlap with PUSCHs in a repeating PUCCH being less than N, discarding PUCCH repeating units that overlap with PUSCHs, where N is a positive integer.

[0424] In some embodiments, where the target behavior includes discarding a PUCCH (including discarding a PUCCH that overlaps with a PUSCH), the method further includes:

[0425] If the UCI carried by the PUCCH includes HARQ ACK information, determine at least one of the following:

[0426] The HARQ process corresponding to the HARQ ACK message is in an idle state;

[0427] The HARQ process corresponding to the HARQ ACK message is deactivated.

[0428] The HARQ ACK message was successfully received.

[0429] This avoids the situation where the access network device (network side) continuously occupies the HARQ process because it does not receive the HARQ ACK.

[0430] For PUSCH repetitions of the application code sequence, if aperiodic CSI reports are to be multiplexed on the PUSCH, then the aperiodic CSI reports need to be multiplexed on all PUSCH repetitions within the code sequence.

[0431] In related technologies, there are two scenarios for PUSCH multiplexing CSI reports: First, the CSI report is sent at the first transmission timing associated with both the first sounding reference signal (SRS) resource set and the second SRS resource set; second, the CSI report is sent only at the first transmission timing. Regardless of the scenario, for code sequence-based PUSCH transmission, it is necessary to ensure that the CSI reports multiplexed by all PUSCH repeating units within a PUSCH group are identical; otherwise, orthogonality will be compromised.

[0432] Based on this, when the transmission conditions include PUSCH multiplexing CSI reports, the target behavior is performed based on the transmission conditions, including:

[0433] In response to the CSI report being sent on the first PUSCH repeating unit in a PUSCH, the CSI report is multiplexed onto the PUSCH repeating unit in the first PUSCH group, where the number of PUSCH repeating units in the PUSCH group is equal to the code sequence length; or,

[0434] In response to the fulfillment of the second condition, the following actions are performed: multiplexing the CSI report to the PUSCH repeating unit of the PUSCH group where the first transmission timing is associated with the first SRS resource set, and multiplexing the CSI report to the PUSCH repeating unit of the PUSCH group where the first transmission timing is associated with the second SRS resource set; or...

[0435] In response to the failure to meet the second condition, the CSI report is reused on the PUSCH repeating unit in the first PUSCH group of the PUSCH; here, the second condition includes at least one of the following:

[0436] CSI reports are sent at the first transmission time associated with the first SRS resource set and at the first transmission time associated with the second SRS resource set;

[0437] The default high-level parameters are enabled.

[0438] PUSCH does not reuse UCI reports other than CSI reports.

[0439] The preset higher-layer parameters include the Aperiodic Channel State Information Trigger State (CSI-AperiodicTriggerState). The preset higher-layer parameters being enabled include the Aperiodic Channel State Information Multiplexing Mode (ap-CSI-MultiplexingMod) within CSI-AperiodicTriggerState being enabled.

[0440] The above execution of multiplexing CSI reports to the PUSCH repeating unit of the PUSCH group where the first transmission timing is associated with the first SRS resource set, and multiplexing CSI reports to the PUSCH repeating unit of the PUSCH group where the first transmission timing is associated with the second SRS resource set, includes:

[0441] If the first transmission timing associated with the first SRS resource set and the first transmission timing associated with the second SRS resource set are within the same PUSCH group, then the CSI report multiplexing on all PUSCH repeating units within that PUSCH group. Alternatively,

[0442] If the first transmission timing associated with the first SRS resource set and the first transmission timing associated with the second SRS resource set are not in the same PUSCH group, the CSI report multiplexes the PUSCH repeating units in the two PUSCH groups containing these two transmission timings.

[0443] In some embodiments, for PUSCH transmission of application code sequences, if frequency hopping is to be used, it needs to be performed at intervals of one or more PUSCH groups; otherwise, frequency hopping needs to be disabled. In related technologies, there are two types of frequency hopping: intra-slot frequency hopping and inter-slot frequency hopping. If frequency hopping is performed in PUSCH transmission of application code sequences, the orthogonality of the code sequences will be disrupted. To avoid disrupting the orthogonality of code sequences in PUSCH transmission of application code sequences, based on this, when the transmission conditions include whether frequency hopping is enabled, a target behavior is performed based on the transmission conditions, including: in response to determining that frequency hopping is enabled, performing frequency hopping at intervals of one or more PUSCH groups.

[0444] In other words, there are two possible solutions:

[0445] Option 1: Frequency hopping is disabled when the code sequence function is enabled or when the application code sequence is used for PUSCH transmission.

[0446] Code sequence function enabling is for semi-static code sequence function enabling, such as configuring code sequence function enabling through RRC parameters. In this case, all PUSCH transmissions of the terminal in the serving cell will use code sequence and frequency hopping will be disabled. Applicable code sequence PUSCH transmission is dynamic, targeting a single PUSCH transmission using code sequence. For example, it can be implicitly enabled through code sequence index or code sequence length, meaning that code sequence function is only enabled and frequency hopping is disabled in that specific PUSCH transmission. The other schemes described below also address these two code sequence configuration scenarios.

[0447] Option 2: When the code sequence function is enabled or when the application code sequence is used for PUSCH transmission, frequency hopping can be indicated based on the parameters configured on the network side, with an interval of one or more PUSCH groups, that is, frequency hopping across one or more PUSCH groups.

[0448] As can be seen from the above description of PUSCH, PUSCH can include multiple PUSCH groups, and each PUSCH group includes M PUSCH repeating units, where M is the code sequence length.

[0449] When frequency hopping and code sequence functionality are enabled, and PUSCH is not scheduled via RAR uplink grant or DCI format 0_0 (whose CRC is scrambled by the Temporary Cell Radio Network Temporary Identifier (TC-RNTI)), the starting RB (resource block) on the nth repetition is given by the following formula:

[0450] Here, n is the nth PUSCH repetition in the PUSCH transmission of the application code sequence, P is the number of PUSCH repetition units or time slots between frequency hopping intervals, and RB start Indicates the starting RB position within the uplink bandwidth part (BWP). offset It is the frequency offset between two frequency transitions (in resource blocks). Here, the value of P can be obtained as follows:

[0451] In some implementations, P can be the code sequence length M;

[0452] In some implementations, P can be the code sequence length M multiplied by the number of TBoMS slots N;

[0453] In some implementations, P can be the code sequence length M multiplied by the number of PUSCH groups S;

[0454] In some implementations, P can be the product of the number of TBoMS slots N, the code sequence length M, and the number of PUSCH groups S.

[0455] In related technologies, frequency hopping can be performed across multiple slots when configuring demodulation reference signal (DMRS) bundling. However, the formula above gives the frequency domain position of the nth slot in the radio frame, which does not care which slot of a PUSCH transmission the frequency hopping slot is. However, in PUSCH transmission using code sequences, it is necessary to ensure the alignment of the code sequence boundaries, that is, the frequency hopping position needs to be at the boundary of the code sequence.

[0456] For example, in some implementations, existing RRC parameters can be reused to determine whether frequency hopping should be performed. For instance, if the frequency hopping configuration in PUSCH-Config is 'interSlot' and the PUSCH transmission is an application code sequence PUSCH transmission, then frequency hopping is performed across one or more PUSCH groups; otherwise, frequency hopping is not performed.

[0457] Here are some examples of obtaining the number S of PUSCH groups:

[0458] For example, a new RRC parameter can be defined, configured with a value N, indicating that frequency hopping can span N PUSCH groups. The value of N can be one or more from {0, 1, 2, 4, 5, 8, 10, 16}, corresponding to the number of repetitions. For instance, when N is 16, combined with an OCC length of 2, it indicates that frequency hopping is used every 32 repetitions, corresponding to the maximum configurable number of repetitions of 32. This can implicitly indicate that frequency hopping is not used. In some implementations, this RRC parameter N can indicate both the number of PUSCH groups spanned by frequency hopping and the number of PUSCH groups spanned by redundant version cycles or UCI multiplexing.

[0459] For example, the network side may configure the code sequence length to be used by the terminal. This can be done explicitly via RRC, or configured via RRC parameters and then indicated by the TDRA field in the DCI. The terminal can implicitly know how many PUSCH groups to use for frequency hopping based on the code sequence length. If the maximum configurable code sequence length is Y, then when a terminal is configured with a code sequence length of M, the terminal will hop frequencies across every Y / M segments. For example, when the maximum configurable code sequence length is 4, a terminal with a code sequence length of 2 will hop frequencies at intervals of two PUSCH groups, while a terminal with a code sequence length of 4 will hop frequencies at intervals of one PUSCH group. This is done to ensure that the frequency hopping patterns of terminals with a code sequence length of 2 and terminals with a code sequence length of 4 are consistent, allowing them to reuse each other.

[0460] In some embodiments, as shown in FIG12, this disclosure also provides a communication method applied to an access network device, wherein the access network device may be the access network device 20 shown in FIG3 above, and the method may include the following steps:

[0461] S201, Receive PUSCH.

[0462] Here, PUSCH comprises multiple PUSCH repeating units, and PUSCH is transmitted as an application code sequence. For a description of the PUSCH repeating unit, please refer to the corresponding description in step S101 above; it will not be repeated here.

[0463] In some embodiments, the code sequence includes at least one of the following: OCC sequence, NOMA sequence, DFT sequence, Walsh sequence, Zadoff-Chu sequence, and Hadamard sequence.

[0464] In some embodiments, the code sequence is obtained based on configuration information, which is carried in at least one of the following:

[0465] RRC signaling, MAC CE, DCI.

[0466] In some embodiments, the configuration information includes at least one of the following:

[0467] The code sequence index, code sequence length, code sequence enable indicator, multiple of code sequence length, number of PUSCH groups, redundancy version cycle enable indicator, redundancy version indicator, and frequency hopping enable indicator are specified. Here, the number of PUSCH repeating units in a PUSCH group is equal to the code sequence length. For a description of the PUSCH groups, please refer to the corresponding description in the above embodiments; it will not be repeated here.

[0468] In some embodiments, the application code sequence includes at least one of the following:

[0469] Each element in the code sequence is applied to a PUSCH repeating unit;

[0470] Each element in the code sequence is multiplied by a PUSCH repeat unit;

[0471] The number of elements in a code sequence is equal to the length of the code sequence;

[0472] The number of PUSCH repeating units in a PUSCH is a multiple of the code sequence length;

[0473] The code sequence is applied to one or more PUSCH groups in the PUSCH, where the number of PUSCH repeating units in the PUSCH group is the code sequence length.

[0474] Each element in the code sequence is applied sequentially to each PUSCH repeating unit in a PUSCH group within a PUSCH.

[0475] In some embodiments, the access network device determines the target behavior based on transmission conditions, where the target behavior is the behavior performed by the terminal, and the transmission conditions include at least one of the following:

[0476] Whether to enable redundant version cycling, whether PUSCH overlaps with duplicate PUCCH in the time domain, whether PUSCH overlaps with non-duplicate PUCCH in the time domain, whether PUSCH multiplexes Channel State Information (CSI) reports, and whether to enable frequency hopping.

[0477] As an example, when transmission conditions include whether redundant version loops are enabled, the target behavior is determined based on the transmission conditions, including:

[0478] In response to the transmission condition enabling redundant version cycling, it is determined that the redundant versions of every X PUSCH repeating units in the PUSCH are identical. Here, the redundant versions of every X PUSCH repeating units are allocated sequentially and cyclically from the redundant version set, where X is one of the following: the code sequence length, a multiple of the code sequence length; or...

[0479] In response to transmission conditions including disabling redundant version loops, it is determined that the redundant versions of all PUSCH repeating units in the PUSCH are identical.

[0480] As another example, when transmission conditions include the overlap of PUSCH and non-repeating PUCCH in the temporal domain, the target behavior is determined based on the transmission conditions, including:

[0481] The target behavior is determined based on at least one of the following, wherein at least one includes:

[0482] Priority configuration of PUSCH and PUCCH;

[0483] The contents of the uplink control information (UCI) carried by the PUCCH;

[0484] Does the UCI multiplexing carried by the PUCCH meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH? Here, the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, and at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length.

[0485] Does the UCI carried by PUCCH overlap with the first PUSCH repeating unit in the first part of PUSCH?

[0486] Is the last PUSCH repeating unit in the first part of PUSCH the last PUSCH repeating unit in PUSCH?

[0487] Whether to disable HARQ feedback for Hybrid Automatic Repeat Request;

[0488] Whether to reuse CSI in PUSCH;

[0489] Does PUSCH include UL-SCH?

[0490] In some embodiments, the priority configuration of PUSCH and PUCCH includes one of the following:

[0491] PUSCH has a higher priority than PUCCH.

[0492] The priority of PUSCH is equal to the priority of PUCCH;

[0493] PUSCH has a lower priority than PUCCH.

[0494] Neither PUSCH nor PUCCH has a priority configured.

[0495] In some embodiments, the UCI carried by the PUCCH includes at least one of the following:

[0496] HARQ confirms ACK information, CSI report, and scheduling request (SR).

[0497] When the transmission conditions include the overlap of PUSCH and non-repeating PUCCH in the time domain, the target behavior includes at least one of the following:

[0498] Discard the PUCCH;

[0499] Discard the PUSCH repeating units in the first part of the PUSCH. Here, the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, and at least one of the X PUSCH repeating units overlaps with the PUCCH. X is one of the following: code sequence length, multiple of code sequence length.

[0500] Multiplex the UCI carried by PUCCH into the first part of PUSCH;

[0501] The UCI carried by the PUCCH is multiplexed into the second part of the PUSCH. Here, the second part of the PUSCH is X PUSCH repeating units after the first part of the PUSCH.

[0502] Send PUCCH after PUSCH repeat transmission;

[0503] Discard the SR in the UCI carried by the PUCCH;

[0504] Discard the CSI in the UCI carried by the PUCCH.

[0505] In some embodiments, multiplexing the UCI carried by the PUCCH into the first part of the PUSCH includes at least one of the following:

[0506] Reuse all of the UCI content into the first part of PUSCH;

[0507] Reuse the CSI report from UCI into the first part of PUSCH;

[0508] The HARQ ACK information in the UCI is multiplexed into the first part of the PUSCH;

[0509] The CSI report and HARQ ACK information from UCI are reused in the first part of PUSCH;

[0510] Multiplexing the UCI carried by the PUCCH into the second part of the PUSCH includes at least one of the following:

[0511] Reuse all of the UCI content into the second part of PUSCH;

[0512] Reuse the CSI report from UCI into Part 2 of PUSCH;

[0513] The HARQ ACK information in the UCI is reused in the second part of the PUSCH;

[0514] The CSI report and HARQ ACK information from UCI are reused in the second part of PUSCH.

[0515] As another example, when the transmission conditions include the overlap of PUSCH and repeated PUCCH in the time domain, the target behavior includes at least one of the following:

[0516] Discard the PUSCH repeating units in the first part of the PUSCH, where the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length;

[0517] Discard any PUCCH that overlaps with PUSCH.

[0518] In some embodiments, discarding the PUSCH repeating unit in the first part of the PUSCH includes:

[0519] In response to the satisfaction of a first condition, the PUSCH repeating unit in the first part of the PUSCH is discarded, the first condition including at least one of the following:

[0520] The UCI carried by the repeated PUCCH includes HARQ ACK information;

[0521] The repeated PUCCH carries a CSI report in the UCI;

[0522] The number of PUCCH repeating units that overlap with PUSCH in a repeating PUCCH is greater than N, where N is a positive integer.

[0523] In some embodiments, discarding a PUCCH that overlaps with a PUSCH includes:

[0524] If the number of PUCCH repeating units overlapping with PUSCH in a repeating PUCCH is less than N, discard the PUCCH repeating units overlapping with PUSCH, where N is a positive integer.

[0525] As another example, when the transmission conditions include PUSCH multiplexing CSI reports, the target behavior is determined based on the transmission conditions, including:

[0526] In response to the CSI report being sent on the first PUSCH repeating unit in a PUSCH, the determined target behavior includes multiplexing the CSI report to the PUSCH repeating unit in the first PUSCH group; or...

[0527] In response to the satisfaction of the second condition, the target behavior is determined to include multiplexing the CSI report to the PUSCH repeating unit of the PUSCH group where the first transmission timing is associated with the first SRS resource set, and multiplexing the CSI report to the PUSCH repeating unit of the PUSCH group where the first transmission timing is associated with the second SRS resource set; or,

[0528] In response to the failure to meet the second condition, the target behavior is determined to include reusing the CSI report onto the PUSCH repeating unit in the first PUSCH group of PUSCH; here, the second condition includes at least one of the following:

[0529] CSI reports are sent at the first transmission time associated with the first SRS resource set and at the first transmission time associated with the second SRS resource set;

[0530] The default high-level parameters are enabled.

[0531] PUSCH does not reuse UCI reports other than CSI reports.

[0532] In some embodiments, the number of PUSCH groups is configured, or determined based on at least one of the following: code sequence length, whether redundant version cycling is enabled, and whether frequency hopping is enabled.

[0533] As another example, when transmission conditions include whether frequency hopping is enabled, the target behavior is determined based on the transmission conditions, including:

[0534] In response to determining that frequency hopping is enabled, the target behavior is determined to include frequency hopping at intervals of one or more PUSCH groups.

[0535] The foregoing primarily describes the solution provided in this disclosure from the perspective of interaction between various nodes. Each node, such as a terminal or access network device, includes corresponding hardware structures and / or software modules to perform the aforementioned functions. Those skilled in the art should readily recognize that, based on the algorithmic steps of the examples described in conjunction with the embodiments disclosed herein, this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0536] This disclosure embodiment can divide the terminal or access network device into functional modules according to the above method embodiment. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or software. The module division in this disclosure embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each functional module according to each function.

[0537] Figure 13 is a block diagram of a communication device according to an embodiment of the present disclosure. As shown in Figure 13, the communication device 30 includes an acquisition unit 301 and a transmission unit 302.

[0538] The communication device 30 can be the terminal described above or a chip within the terminal. When the communication device 30 is used to implement the functions of the terminal in the above embodiments, each unit is specifically used to implement the following functions.

[0539] Acquisition unit 301 is used to acquire code sequences;

[0540] The sending unit 302 is used to transmit PUSCH using the application code sequence. Here, PUSCH contains multiple PUSCH repeating units.

[0541] In some embodiments, the acquisition unit 301 is specifically used to acquire a code sequence based on configuration information, wherein the configuration information is carried in at least one of the following: RRC signaling, MAC CE, and DCI.

[0542] In some embodiments, the transmitting unit 302 is further configured to perform a target behavior based on transmission conditions, wherein the transmission conditions include at least one of the following: whether to enable redundant version cycling, whether the PUSCH overlaps with the repeated PUCCH in the time domain resources, whether the PUSCH overlaps with the non-repeating PUCCH in the time domain resources, whether to report the PUSCH multiplexing channel state information (CSI), and whether to enable frequency hopping.

[0543] In some embodiments, when the transmission condition includes whether redundant version cycling is enabled, the transmitting unit 302 is specifically configured to, in response to the transmission condition being that redundant version cycling is enabled, perform the following action: Maintain the same redundant version for every X PUSCH repeating units in the PUSCH. Here, the redundant version for every X PUSCH repeating units is allocated sequentially and cyclically from the redundant version set, where X is one of the following: the code sequence length, a multiple of the code sequence length; or...

[0544] In response to transmission conditions including disabling redundant version loops, the redundant versions of all PUSCH repeating units in the PUSCH are kept identical.

[0545] In some embodiments, when the transmission conditions include the overlap of PUSCH and non-repeating PUCCH in the time domain resources, the transmitting unit 302 is specifically configured to perform a target action based on at least one of the following, wherein at least one includes:

[0546] Priority configuration of PUSCH and PUCCH;

[0547] The contents of the uplink control information (UCI) carried by the PUCCH;

[0548] Does the UCI multiplexing carried by the PUCCH meet the timing requirements on the first PUSCH repeating unit in the first part of the PUSCH? Here, the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, and at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length.

[0549] Does the UCI carried by PUCCH overlap with the first PUSCH repeating unit in the first part of PUSCH?

[0550] Is the last PUSCH repeating unit in the first part of PUSCH the last PUSCH repeating unit in PUSCH?

[0551] Whether to disable HARQ feedback for Hybrid Automatic Repeat Request;

[0552] Whether to reuse CSI in PUSCH;

[0553] Does the PUSCH include the uplink shared channel UL-SCH?

[0554] In some embodiments, when the transmission conditions include the overlap of PUSCH and non-repeating PUCCH in the time domain resources, the transmitting unit 302 is specifically used for at least one of the following:

[0555] Discard the PUCCH;

[0556] Discard the PUSCH repeating units in the first part of the PUSCH. Here, the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, and at least one of the X PUSCH repeating units overlaps with the PUCCH. X is one of the following: code sequence length, multiple of code sequence length.

[0557] Multiplex the UCI carried by PUCCH into the first part of PUSCH;

[0558] The UCI carried by the PUCCH is multiplexed into the second part of the PUSCH. Here, the second part of the PUSCH is X PUSCH repeating units after the first part of the PUSCH.

[0559] Send PUCCH after PUSCH repeat transmission;

[0560] Discard the SR in the UCI carried by the PUCCH;

[0561] Discard the CSI in the UCI carried by the PUCCH.

[0562] In some embodiments, the sending unit 302 is further configured to determine at least one of the following if the UCI carried by the PUCCH includes HARQ ACK information:

[0563] The HARQ process corresponding to the HARQ ACK message is in an idle state;

[0564] The HARQ process corresponding to the HARQ ACK message is deactivated.

[0565] The HARQ ACK message was successfully received.

[0566] In some embodiments, when the transmission conditions include the overlap of PUSCH and repeated PUCCH in the time domain resources, the transmitting unit 302 is specifically used for at least one of the following: discarding the repeated PUSCH units in the first part of the PUSCH, where the first part of the PUSCH includes X repeated PUSCH units in the PUSCH, at least one of the X repeated PUSCH units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length;

[0567] Discard any PUCCH that overlaps with PUSCH.

[0568] In some embodiments, when the transmission conditions include PUSCH multiplexing CSI reports, the sending unit 302 is specifically configured to, in response to the transmission of a CSI report on the first PUSCH repeating unit in the PUSCH, perform the multiplexing of the CSI report onto the PUSCH repeating unit in the first PUSCH group; or...

[0569] In response to the satisfaction of the second condition, the following actions are performed: multiplexing the CSI report to the PUSCH repeating unit in the PUSCH group where the first transmission timing is associated with the first SRS resource set, and multiplexing the CSI report to the PUSCH repeating unit in the PUSCH group where the first transmission timing is associated with the second SRS resource set; or...

[0570] In response to the failure to meet the second condition, the CSI report is reused on the PUSCH repeating unit in the first PUSCH group of the PUSCH; here, the second condition includes at least one of the following:

[0571] CSI reports are sent at the first transmission time associated with the first SRS resource set and at the first transmission time associated with the second SRS resource set;

[0572] The default high-level parameters are enabled.

[0573] PUSCH does not reuse UCI reports other than CSI reports.

[0574] In some embodiments, when the transmission conditions include whether frequency hopping is enabled, the transmitting unit 302 is specifically configured to perform frequency hopping at intervals of one or more PUSCH groups in response to determining that frequency hopping is enabled.

[0575] In some embodiments, the sending unit 302 is further configured to determine at least one of the following based on the terminal's capability information or the network-side configuration information:

[0576] Enable redundant version looping;

[0577] The number of PUSCH repeating units applied in each redundant version of the redundant version cycle;

[0578] The number of PUSCH groups applied in each redundant version cycle, where the number of PUSCH repeating units in a PUSCH group is the code sequence length.

[0579] Enable frequency hopping;

[0580] The number of PUSCH repetition units between frequency hopping intervals;

[0581] The number of PUSCH groups between frequency hopping intervals.

[0582] Figure 14 is a block diagram of another communication device provided according to an embodiment of the present disclosure. As shown in Figure 14, the communication device 40 includes a receiving unit 401.

[0583] The communication device 40 can be the access network device described above or a chip within the access network device. When the communication device 40 is used to implement the functions of the access network device in the above embodiments, each unit is specifically used to implement the following functions.

[0584] The receiving unit 401 is used to receive PUSCH, where PUSCH contains multiple PUSCH repeating units and PUSCH is transmitted as an application code sequence.

[0585] The units in Figure 13 or Figure 14 can also be called modules; for example, the transmitting unit can be called a transmitting module. Additionally, in the embodiments shown in Figure 13 or Figure 14, the names of the units may not be those shown in the figures; for example, the transmitting unit can also be called a communication unit, and the receiving unit can also be called a communication unit.

[0586] If the units in Figure 13 or Figure 14 are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this disclosure, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this disclosure. Storage media for storing computer software products include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0587] In the case where the communication device 30 or communication device 40 implements the functions of the integrated module in hardware, a block diagram of another communication device is also provided according to embodiments of this disclosure. As shown in FIG15, the communication device 50 includes: a processor 502, a communication interface 503, and a bus 504. In some embodiments, the communication device 50 may further include a memory 501.

[0588] Processor 502 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. Processor 502 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with this disclosure. Processor 502 may also be a combination that implements computational functions, such as a combination of one or more microprocessors, a digital signal processor (DSP), and a microprocessor.

[0589] Communication interface 503 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0590] The memory 501 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0591] In some embodiments, the memory 501 may exist independently of the processor 502. The memory 501 may be connected to the processor 502 via a bus 504 and is used to store instructions or program code. When the processor 502 calls and executes the instructions or program code stored in the memory 501, it can implement the communication method provided in the embodiments of this disclosure.

[0592] In another possible implementation, the memory 501 can also be integrated with the processor 502.

[0593] Bus 504 can be an extended industry standard architecture (EISA) bus, etc. Bus 504 can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in Figure 15, but this does not mean that there is only one bus or one type of bus.

[0594] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the terminal or access network device can be divided into different functional modules to complete all or part of the functions described above.

[0595] This disclosure also provides a computer-readable storage medium, including a non-transitory computer-readable storage medium on which computer instructions are stored. All or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware. The program can be stored in the computer-readable storage medium, and when executed, it can include the processes of the above method embodiments. The computer-readable storage medium can also be an external storage device for the terminal or access network device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal or access network device. Further, the computer-readable storage medium can include both internal storage units and external storage devices of the terminal or access network device. The computer-readable storage medium is used to store the computer program and other programs and data required by the terminal or access network device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0596] This disclosure also provides a computer program product comprising a computer program that, when run on a computer, causes the computer to perform any of the communication methods provided in the above embodiments.

[0597] Although this disclosure has been described herein in conjunction with various embodiments, those skilled in the art will understand and implement other variations of the disclosed embodiments by reviewing the accompanying drawings, the disclosure, and the appended claims in carrying out the claimed disclosure. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce a good effect.

[0598] Although this disclosure has been described in conjunction with specific features and embodiments, it will be apparent that various modifications and combinations can be made therein without departing from the spirit and scope of this disclosure. Accordingly, this specification and drawings are merely exemplary illustrations of the disclosure as defined by the appended claims and are to be considered as covering any and all modifications, variations, combinations, or equivalents within the scope of this disclosure. It is obvious that those skilled in the art can make various alterations and modifications to this disclosure without departing from its spirit and scope. Thus, this disclosure is also intended to include any such modifications and modifications that fall within the scope of the claims of this disclosure and their equivalents.

[0599] The above are merely specific embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A communication method, wherein, The method includes: Obtain the code sequence; The code sequence is used for uplink physical shared channel (PUSCH) transmission, wherein the PUSCH contains multiple PUSCH repeating units.

2. The method of claim 1, wherein, The code sequence includes at least one of the following: orthogonal covering code (OCC) sequence, nonorthogonal multiple access (NOMA) sequence, discrete Fourier transform (DFT) sequence, Walsh sequence, Zadoff-Chu sequence, and Hadamard sequence.

3. The method of claim 1 or 2, wherein, The acquisition code sequence includes: The code sequence is obtained based on configuration information, wherein the configuration information is carried in at least one of the following: Radio Resource Control (RRC) signaling, Media Access Control (MAC) Control Unit (CE), and Downlink Control Information (DCI).

4. The method of claim 3, wherein, The configuration information includes at least one of the following: Code sequence index, code sequence length, code sequence enable indicator, multiple of code sequence length, number of PUSCH groups, redundancy version cycle enable indicator, redundancy version indicator, frequency hopping enable indicator; the number of PUSCH repeating units contained in the PUSCH group is the code sequence length.

5. The method of any one of claims 1 to 4, wherein, The application of the code sequence includes at least one of the following: Each element in the code sequence is applied to one of the PUSCH repeating units; Each element in the code sequence is multiplied by one of the PUSCH repeating units; The number of elements in the code sequence is equal to the length of the code sequence; The number of PUSCH repeating units in the PUSCH is a multiple of the code sequence length; The code sequence is applied to one or more PUSCH groups in the PUSCH, and the number of PUSCH repeating units contained in the PUSCH group is the code sequence length. Each element in the code sequence is applied sequentially to each PUSCH repeating unit in a PUSCH group within the PUSCH.

6. The method of any one of claims 1 to 5, wherein, The method further includes: Based on transmission conditions, the target behavior is executed, wherein the transmission conditions include at least one of the following: Whether to enable redundant version cycling, whether the PUSCH overlaps with the repeated PUCCH in the time domain, whether the PUSCH overlaps with the non-repeating PUCCH in the time domain, whether the PUSCH multiplexes the Channel State Information (CSI) report, and whether to enable frequency hopping.

7. The method of claim 6, wherein, When the transmission conditions include whether redundant version looping is enabled, the execution of the target behavior based on the transmission conditions includes: In response to the transmission condition enabling the redundancy version cycle, the redundancy version of every X PUSCH repeating units in the PUSCH is kept identical. The redundancy versions of each X PUSCH repeating unit are allocated sequentially and cyclically from the redundancy version set, where X is one of the following: the code sequence length, a multiple of the code sequence length; or... In response to the transmission condition including disabling the redundant version cycle, the redundant version of all PUSCH repeating units in the PUSCH is kept identical.

8. The method of claim 6, wherein, When the transmission conditions include the PUSCH and the non-repeating PUCCH overlapping in the time domain, the execution of the target behavior based on the transmission conditions includes: The target behavior is performed based on at least one of the following, wherein the at least one includes: The priority configuration of the PUSCH and the PUCCH; The content contained in the uplink control information (UCI) carried by the PUCCH; Whether the UCI multiplexing carried by the PUCCH on the first PUSCH repeating unit in the first part of the PUSCH meets the timing requirements; the first part of the PUSCH includes X PUSCH repeating units in the PUSCH, and at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length; Does the UCI carried by the PUCCH overlap with the first PUSCH repeating unit in the first part of the PUSCH? Whether the last PUSCH repeating unit in the first part of the PUSCH is the last PUSCH repeating unit in the PUSCH; Whether to disable HARQ feedback for Hybrid Automatic Repeat Request; Whether CSI is reused in the PUSCH; Does the PUSCH include the uplink shared channel UL-SCH? 9. The method of claim 8, wherein, The priority configuration of the PUSCH and the PUCCH includes one of the following: The priority of the PUSCH is higher than the priority of the PUCCH; The priority of the PUSCH is equal to the priority of the PUCCH; The priority of the PUSCH is lower than that of the PUCCH.

10. The method of claim 8 or 9, wherein, The UCI carried by the PUCCH includes at least one of the following: HARQ confirms ACK information, CSI report, and scheduling request (SR).

11. The method of any one of claims 6 to 10, wherein, When the transmission conditions include the PUSCH and the non-repeating PUCCH overlapping in the time domain, the target behavior includes at least one of the following: Discard the PUCCH; Discard the PUSCH repeating units in the first part of the PUSCH, the first part of the PUSCH including X PUSCH repeating units in the PUSCH, at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length; The UCI carried by the PUCCH is multiplexed into the first part of the PUSCH; The UCI carried by the PUCCH is multiplexed into the second part of the PUSCH, and the second part of the PUSCH is X PUSCH repeating units after the first part of the PUSCH. The PUCCH is sent after the PUSCH is repeatedly transmitted; Discard the SR in the UCI carried by the PUCCH; Discard the CSI in the UCI carried by the PUCCH.

12. The method of claim 11, wherein, The multiplexing of the UCI carried by the PUCCH into the first part of the PUSCH includes at least one of the following: The entire contents of the UCI are reused in the first part of the PUSCH; The CSI report from the UCI is reused in the first part of the PUSCH; The HARQ ACK information in the UCI is multiplexed into the first part of the PUSCH; The CSI report and HARQ ACK information from the UCI are reused in the first part of the PUSCH; The multiplexing of the UCI carried by the PUCCH into the second part of the PUSCH includes at least one of the following: The entire contents of the UCI are reused in the second part of the PUSCH; The CSI report from the UCI is reused in the second part of the PUSCH; The HARQ ACK information in the UCI is reused in the second part of the PUSCH; The CSI report and HARQ ACK information from the UCI are reused in the second part of the PUSCH.

13. The method of any one of claims 6 to 12, wherein, When the transmission conditions include the PUSCH overlapping with a repeated PUCCH in the time domain, the target behavior includes at least one of the following: Discard the PUSCH repeating units in the first part of the PUSCH, the first part of the PUSCH including X PUSCH repeating units in the PUSCH, at least one of the X PUSCH repeating units overlaps with the PUCCH; X is one of the following: code sequence length, multiple of code sequence length; Discard any PUCCH that overlaps with the PUSCH.

14. The method of claim 11 or 13, wherein, If the target behavior includes discarding the PUCCH, the method further includes: If the UCI carried by the PUCCH includes HARQ ACK information, then at least one of the following is determined: The HARQ process corresponding to the HARQ ACK message is in an idle state; The HARQ process corresponding to the HARQ ACK message is disabled; The HARQ ACK message was successfully received.

15. The method of claim 13 or 14, wherein, The discarding of the PUSCH repeating unit in the first part of the PUSCH includes: In response to the satisfaction of a first condition, the PUSCH repeating unit in the first portion of the PUSCH is discarded, the first condition including at least one of the following: The repeated PUCCH carries UCI information including HARQ ACK information; The repeated PUCCH carries a CSI report in the UCI. The number of PUCCH repeating units that overlap with the PUSCH in the repeating PUCCH is greater than N, where N is a positive integer.

16. The method of any one of claims 13-15, wherein, The discarding of PUCCHs that overlap with the PUSCH includes: In response to the fact that the number of PUCCH repeating units overlapping with the PUSCH in the repeating PUCCH is less than N, the PUCCH repeating units overlapping with the PUSCH are discarded, where N is a positive integer.

17. The method of any one of claims 6 to 16, wherein, When the transmission conditions include the PUSCH multiplexing CSI report, the execution of the target behavior based on the transmission conditions includes: In response to the CSI report being sent on the first PUSCH repeating unit in the PUSCH, the CSI report is multiplexed onto the PUSCH repeating units in the first PUSCH group of the PUSCH, the number of PUSCH repeating units in the PUSCH group being equal to the code sequence length; or, In response to the fulfillment of the second condition, the following actions are performed: multiplexing the CSI report to the PUSCH repeating unit of the PUSCH group where the first transmission opportunity is associated with the first SRS resource set, and multiplexing the CSI report to the PUSCH repeating unit of the PUSCH group where the first transmission opportunity is associated with the second SRS resource set; or... In response to the failure to meet the second condition, the CSI report is reused on the PUSCH repeating unit in the first PUSCH group of the PUSCH; the second condition includes at least one of the following: The CSI report is sent at the first transmission time associated with the first SRS resource set and at the first transmission time associated with the second SRS resource set; The default high-level parameters are enabled. The PUSCH does not reuse UCIs other than the CSI report.

18. The method of any one of claims 4, 5, 7, 8, 11, or 13, wherein, The multiple of the code sequence length is equal to the code sequence length multiplied by the number of PUSCH groups, the number of PUSCH groups being configured, or determined based on at least one of the following: code sequence length, whether redundant version cycling is enabled, and whether frequency hopping is enabled.

19. The method of any one of claims 6-18, wherein, When the transmission conditions include whether frequency hopping is enabled, the execution of the target behavior based on the transmission conditions includes: In response to determining that frequency hopping is enabled, frequency hopping is performed at intervals of one or more PUSCH groups; the number of PUSCH repeating units contained in the PUSCH group is equal to the code sequence length.

20. The method of any one of claims 6-19, wherein, The method further includes: Based on the terminal's capability information or the network-side configuration information, determine at least one of the following: Should the redundant version loop be enabled? The number of PUSCH repeating units applied in each redundant version of the redundant version cycle. The number of PUSCH groups applied in each redundant version cycle, wherein the number of PUSCH repeating units contained in the PUSCH group is the code sequence length. Whether to enable frequency hopping; The number of PUSCH repetition units between frequency hopping intervals; The number of PUSCH groups between frequency hopping intervals.

21. A communication method, wherein, The method includes: Receive PUSCH, which contains multiple PUSCH repeat units. PUSCH is transmitted as an application code sequence.

22. A communications device, wherein include: Memory and processor; Memory and processor are coupled; The memory is used to store instructions that can be executed by the processor; When the processor executes the instructions, it performs the method as described in any one of claims 1 to 21.

23. A computer readable storage medium, wherein, The computer-readable storage medium includes a non-transitory computer-readable storage medium on which computer instructions are stored, which, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 21.

24. A computer program product, wherein, The computer program product comprises computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 21.

Images