Terminal device, base station, and communication method

Abstract

The embodiments of the present disclosure relate to a method, an apparatus, and a computer-readable medium for PUSCH repetition. According to the embodiments of the present disclosure, a terminal device determines a physical uplink shared channel (PUSCH) repetition opportunity slot based on a first skipping rule. Then, the terminal device determines a PUSCH repetition actual slot from the set of PUSCH repetition opportunity slots based on a second skipping rule. Then, the terminal device transmits data in the determined PUSCH repetition actual slot. In this way, an enhanced PUSCH enhancement solution is provided, thus improving network coverage and enhancing the robustness of uplink transmission.

Description

[Technical field]

[0001] FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to a method, apparatus, and computer storage medium for physical uplink shared channel (PUSCH) repetition. [Background technology]

[0002] In 3GPP meetings, there have been discussions on enhancing support for the introduction of multi-transmission and reception points (multi-TRPs). For example, it has been proposed to use multi-TRPs and / or multi-panels based on the Release 16 reliability characteristics to identify and specify characteristics that improve the reliability and robustness of physical channels other than the physical downlink shared channel (PDSCH), such as the physical downlink control channel (PDCCH), the physical uplink shared channel (PUSCH) and / or the physical uplink control channel (PUCCH).

[0003] In order to enhance the coverage of New Radio networks, one of the most effective ways to enhance uplink coverage is repetition, since the transmission power can be accumulated in the time domain by the user equipment (UE). Repetition in PUSCH needs further study. Summary of the Invention [Problem to be solved by the invention]

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

[0005] In a first aspect, a communication method is provided, the method including: determining, in a terminal device, a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a first skipping rule, determining an actual PUSCH repetition slot from the set of PUSCH repetition opportunity slots based on a second skipping rule, and transmitting data in the determined actual PUSCH repetition slot.

[0006] In a second aspect, a communication method is provided, the method including: determining, in a terminal device, a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a counting rule for counting PUSCH repetition opportunity slots, determining an actual PUSCH repetition slot from the set of PUSCH repetition opportunity slots based on a skipping rule, and transmitting data in the determined actual PUSCH repetition slot.

[0007] In a third aspect, a terminal device is provided, the terminal device comprising a processor and a memory coupled to the processor, the memory storing instructions that, when executed by the processor, cause the terminal device to perform the methods of the first and second aspects of the present disclosure.

[0008] In a fourth aspect, there is provided a computer readable medium having stored thereon instructions which, when executed on at least one processor, cause the at least one processor to perform a method according to the first or second aspect of the present disclosure.

[0009] Other features of the present disclosure will become readily apparent from the following description. [Brief description of the drawings]

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

[0011] [Figure 1] FIG. 1 is a schematic diagram of a communication environment in which embodiments of the present disclosure may be implemented.

[0012] [Diagram 2] FIG. 2 illustrates a signaling flow of a process for PUSCH repetition in accordance with some embodiments of the present disclosure.

[0013] [Diagram 3] FIG. 2 illustrates a signaling flow of a process for PUSCH repetition in accordance with some embodiments of the present disclosure.

[0014] [Figure 4] FIG. 2 illustrates an exemplary communication method implemented in a terminal device according to some embodiments of the present disclosure.

[0015] [Diagram 5] FIG. 2 illustrates an example communication method implemented in a network device, according to some embodiments of the present disclosure.

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

[0017] In the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

[0020] As used herein, the term "terminal device" refers to any device having wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, in-vehicle devices for V2X communication, etc., where the "X" in V2X represents a pedestrian, vehicle, or infrastructure / network, or an image capture device such as a digital camera, a gaming device, a music storage and playback device, or an Internet appliance that allows wireless or wired Internet access and browsing, etc.

[0021] The term "terminal device" can be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. Also, the term "network device" refers to a device that can provide or host a cell or coverage in which a terminal device can communicate. Examples of network devices include, but are not limited to, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNB), a Transmission Reception Point (TRP), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a femto node, a pico node, or other low power node.

[0022] In one embodiment, the terminal device can be connected to a first network device and a second network device. One of the first network device and the second network device may be a master node and the other may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB and the second RAT device is a gNB. Information about the different RATs can be transmitted from at least one of the first network device and the second network device to the terminal device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device. In one embodiment, information about the configuration of the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of the terminal device configured by the second network device may be transmitted from the second network device directly to the terminal device or via the first network device.

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

[0024] As used herein, the singular forms "a," "an," and "said" include the plural unless the context clearly indicates otherwise. The term "comprises" and variations thereof should be understood as open-ended terms meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment." The term "another embodiment" should be understood as "at least one other embodiment." Terms such as "first," "second," and the like can refer to different or the same object. The following may include other explicit and implicit definitions.

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

[0026] As mentioned above, in order to enhance the coverage of New Radio networks, one of the most effective ways to enhance uplink coverage is repetition, since the transmission power can be accumulated in the time domain by the UE. In the current (rel-16) NR, there are two types of PUSCH repetition: Type A and Type B. Type A is slot-based PUSCH repetition, i.e., retransmission is performed on a slot-by-slot basis. Type B is minislot-based retransmission or symbol-based retransmission.

[0027] It is necessary to study an enhanced mechanism for PUSCH repetition type A. In one aspect, it is considered to maximize the maximum number of repetitions of PUSCH to one number. In another aspect, it is also considered to increase the number of repetitions counted based on the slots available for uplink transmission.

[0028] For PUSCH repetition type A, when transmitting a PUSCH scrambled with C-RNTI, MCS-C-RNTI, or CS-RNTI with CRC NDI=1 and scheduled with DCI format 0_1 ​​or 0_2 in the PDCCH, the number of repetitions K may be determined as follows: - If numberOfRepetitions-r16 exists in the resource allocation table, the number of repetitions K is equal to numberOfRepetitions-r16. - if the UE is configured with pusch-AggregationFactor, the number of iterations K is equal to pusch-AggregationFactor, otherwise K is equal to 1.

[0029] For PUSCH repetition type A, if K>1, the same symbol allocation is applied over K consecutive slots and PUSCH is restricted to a single transmission layer. The UE shall repeat a transmission block (TB) over K consecutive slots applying the same symbol allocation in each slot. Determine the redundancy version applied to the nth transmission opportunity of a TB based on Table 6.1.2.1-2 below, where n=0,1,…K-1. TIFF0007647898000001.tif55139

[0030] For PUSCH repetition type A, a PUSCH transmission in a slot of a multi-slot PUSCH transmission may be omitted according to the conditions of clause 9, clause 11.1 and clause 11.2A of [6, TS38.213].

[0031] For example, in a time division duplexing (TDD) system, if the current slot is for uplink transmission and K is set to 8, there will be 8 consecutive slots for transmitting PUSCH repetitions. However, among the 8 consecutive slots, one or more slots may be configured by the system for downlink transmission. In this case, the slot is unavailable for uplink transmission, and the slot is omitted.

[0032] Moreover, considering that there is more downlink traffic in the network, the slots for uplink transmission are usually less than those for downlink transmission. In such a case, even though a certain number of consecutive slots (e.g., K=8 consecutive slots) is set, finally only two slots are available for uplink transmission, and the remaining six slots are for downlink transmission. Therefore, the uplink transmission can only be transmitted twice. Therefore, in practice, only two uplink retransmissions are performed, and the network coverage may not be good enough.

[0033] At the same time, the inventors of the present disclosure have noticed that there may be several solutions, such as: One simple solution is to set the number K to a higher value, for example, to set K to 16. As a result, if K is set to 8, there may be more (for example, 4) uplink transmission repetitions than two slots out of eight slots are available for uplink transmission. That is, the higher the number K, the greater the actual number of retransmissions.

[0034] Furthermore, the inventors of the present disclosure have realized that K=4 may be directly set, where 4 represents four available slots for uplink transmission, not necessarily consecutive slots, in which case four slots can be reserved for uplink repeated transmission.

[0035] At the same time, the inventors of the present disclosure have noticed that there are at least the following problems with PUSCH repetition.

[0036] First, there are many omitted rules in the current NR specification. It is unclear how to define the available slots for PUSCH repetitions. It is necessary to clarify which rules apply to the available slots and which rules do not apply to the available slots.

[0037] Furthermore, the network and the UE should have a consistent understanding of the actual number of repetitions and transmission slots. Since the UE may miss the dynamic indication, only static configuration (e.g., sent from the network device via RRC) can be used by the UE to determine the availability of slots. However, some of the omission rules are based on dynamic indications. Specifically, in some examples, there are some omission rules based on dynamic indications. In such a case, the network device and the terminal device may have different understandings of the actual number of repetitions and transmission slots. For example, if there is a dynamic indication for omission, the network device may transmit DCI format 2_4 for the serving cell to cancel PUSCH transmission. However, due to some reason (e.g., poor network quality), the terminal device could not receive DCI format 2_4. In such a case, the network device understands that at least one slot is omitted, but the terminal device that does not receive DCI format 2_4 does not perform the omission. As a result, the network device and the terminal device may have different understandings of the actual number and therefore the end of PUSCH repetitions.

[0038] Also, it is unclear whether the second omission rule is applied to the available slots, and the inventors believe that the second omission rule should be applied after the first omission rule that determines the available slots. Therefore, the omission rules can be applied in a combined manner, i.e., there is no hierarchical scheme for applying different types of omission rules.

[0039] In order to solve at least part of the above problem, a solution for PUSCH repetition is provided. According to an embodiment of the present disclosure, the terminal device transmits data in the determined PUSCH repetition opportunity slot. Thus, the terminal device determines a set of PUSCH repetition opportunity slots based on a first skip rule. Then, the terminal device further determines a PUSCH repetition actual slot from the set of PUSCH repetition opportunity slots based on a second skip rule. Thus, the terminal device transmits data in the determined PUSCH repetition actual slot. Thus, the definition of the slot available for PUSCH repetition (i.e., the number of repetitions K) is clear based on the first skip rule. In addition, the available slot can be determined by a second skip rule applied after the first skip rule. As a result, an enhanced PUSCH enhancement solution is provided, thus improving the network coverage and enhancing the robustness of uplink transmission.

[0040] 1 is a schematic diagram of a communication system in which embodiments of the present disclosure may be implemented. The communication system 100, which is part of a communication network, comprises terminal devices 110-1, 110-2, ..., 110-N, which may be collectively referred to as "terminal devices 110." The number N may be any suitable integer.

[0041] The communication system 100 further comprises network device 120-1, network device 120-2, ..., network device 120-M, which may be collectively referred to as "network device 120". In some embodiments, the network device may be a gNB. Alternatively, the network device may be an IAB. The number M may be any suitable integer. In the communication system 100, the network device 120 and the terminal device 110 may communicate data and control information with each other. For purposes of illustration only, the network device 120-1 may be considered as a source network device, and the network device 120-2 may be considered as a target network device. The number of terminal devices 110 and network devices 120 shown in FIG. 1 is shown for purposes of illustration only and does not imply any limitation.

[0042] Communications in the communication system 100 may be achieved according to any suitable communication protocol, including, but not limited to, cellular communication protocols such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local area network communication protocols such as the Institute for Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol now known or developed in the future. Additionally, communications may be achieved according to any suitable communication protocol, including, but not limited to, code division multiple access (CDMA) protocols. access ), frequency division multiple access (FDMA) access ), time divided multiple access (TDMA) access), frequency divided duplexer (FDD), time divided duplexer (TDD), multiple-input multiple-output (MIMO), orthogonal frequency divided multiple access (OFDMA), and / or any other technology now known or developed in the future may be utilized.

[0043] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Now, reference is made to Fig. 2, which illustrates a signaling flow 200 for PUSCH repetition according to an exemplary embodiment of the present disclosure. For illustrative purposes, the signaling flow 200 will be described with reference to Fig. 1. For illustrative purposes only, the signaling flow 200 may involve a terminal device 110 and a network device 120.

[0044] In some embodiments, the terms "transmission opportunity," "transmission," and "repetition" may be used interchangeably. The terms "DCI," "DCI format," and "PDCCH" may be used interchangeably.

[0045] As shown in FIG. 2, the terminal device 110 determines a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a first skipping rule (210). In some embodiments, the first skipping rule may be received in an RRC message from the network device 120. In such an embodiment, the first skipping rule is that for a set of symbols of a slot indicated to the terminal device 110 as downlink, the terminal device 110 does not transmit a PUSCH if the PUSCH overlaps (even partially overlaps) with the set of symbols of the slot. In some other embodiments, the first skipping rule may be that for a set of symbols of a slot indicated to the terminal device 110 by ssb-PositionsInBurst, the terminal device 110 does not transmit a PUSCH in the slot if, for reception of an SS / PBCH block, the transmission would overlap with any symbol of the set of symbols of the slot.

[0046] In some embodiments, since there are many conditions for omission, these conditions may be divided into two types. One type may be called static type, which includes types that are set via RRC messages. For example, clause 11.1 of TS 38.213 includes many such rules. The other type may be called dynamic type, which may include omission rules that are set via DCI. The omission rules may be set via MAC-CE. For example, clauses 9 and 11.2A defined in TS 38.213 include such rules. Some more specific examples of static rules and dynamic rules are detailed below.

[0047] 2, after determining the set of PUSCH repetition opportunity slots, the terminal device 110 determines a PUSCH repetition actual slot from the set of PUSCH repetition opportunity slots based on a second skipping rule (220). Thus, the terminal device 110 transmits data in the determined PUSCH repetition actual slot (230).

[0048] Thereby, the terminal device 110 may apply the skipping rule in two stages for the configuration of the extension type (for example, type A-1 may be regarded as an extension type for type A). Then, based on the type A-1 configuration of, for example, K repetitions, the terminal device 110 may apply the first skipping rule to determine K PUSCH opportunity slots. Then, the terminal device 110 may apply the second skipping rule to determine whether to cancel the PUSCH transmission in the n-th PUSCH opportunity slot. Thus, the definition of the slot available for the PUSCH repetition is clear based on the first skipping rule. Furthermore, the second skipping rule for determining the available slot is applied after the first skipping rule. In this way, an enhanced PUSCH enhancement solution is provided, thus improving the network coverage and enhancing the robustness of the uplink transmission.

[0049] It should be understood that although the above method is shown for slot-based retransmission, it is also applicable to minislot-based retransmission and symbol-based retransmission. That is, PUSCH repetitions of type A and type B in current NR, or other types of PUSCH repetitions that may be defined in the future, may utilize the above method. The scope of protection of the present disclosure is not limited in this respect.

[0050] In some embodiments, the terminal device 110 may receive DCI or MAC-CE from the network device 120 indicating a second skipping rule. In such an embodiment, the second skipping rule may include overlapping for PUCCH and / or PUSCH transmissions with different priority indices. For example, as defined in clause 9 of TS 38.213, when the terminal device 110 determines overlapping for PUCCH and / or PUSCH transmissions with different priority indices, the terminal device 110 first resolves overlapping for PUCCH and / or PUSCH transmissions with smaller priority indices, as described in clause 9.2.5 of TS 38.213. Then, when a first PUCCH transmission with a larger priority index scheduled by a DCI format in the PDCCH reception overlaps in time with a second PUSCH or second PUCCH transmission with a smaller priority index, the terminal device 110 cancels the second PUSCH or second PUCCH transmission before the first symbol that overlaps with the first PUCCH transmission. When a transmission of a first PUSCH having a higher priority index scheduled by a DCI format in a PDCCH reception overlaps in time with a transmission of a second PUCCH having a lower priority index, the terminal device 110 cancels the transmission of the second PUCCH before the first symbol that overlaps with the first PSCCH transmission.

[0051] Alternatively, the second omission rule may be to cancel PUSCH transmission when the terminal device 110 detects DCI format 2_4 for the serving cell. In such an example, as defined in clause 11.2A of TS38.213, the terminal device 110 that detects DCI format 2_4 for the serving cell may respectively: - if applicabilityforCI is set in the terminal device 110, the transmission is a PUSCH with priority 0; - T CI A group of symbols from N symbols in DCI format 2_4BI has at least one bit value "1" in its corresponding set and contains a symbol of a (repetition of) PUSCH transmission or an SRS transmission; and - B CI if a group of PRBs from the PRBs has a corresponding bit value of "1" in the bit set corresponding to the symbol group in DCI format 2_4 and includes a PRB of a (repetition of) PUSCH transmission or an SRS transmission, Cancel the PUSCH transmission on the serving cell, or the actual repetition of the PUSCH transmission (if the PUSCH transmission has repetition type B as defined in clauses 9 and 9.2.5 or clause 6.1 of TS 38.214), or the SRS transmission. Where: - The cancellation of a (repetition of) a PUSCH transmission includes all symbols starting from the oldest symbol of the (repetition of) a PUSCH transmission within the group of symbols with a corresponding bit value "1" in DCI format 2_4.

[0052] In some embodiments, terminal device 110 may receive a message from network device 120 that includes the second predetermined number. In such embodiments, the second predetermined number may indicate a limit (e.g., an upper limit) of a number of PUSCH repetition opportunity slots, where the set of PUSCH repetition opportunity slots is determined from the number of PUSCH repetition opportunity slots. Thus, terminal device 110 may determine the set of PUSCH repetition opportunity slots based on a first skipping rule, the first predetermined number, and the second predetermined number.

[0053] For example, for PUSCH repetition type A-1, the second predetermined number may be M set together with the number of repetitions K, where K' is the number of PUSCH repetition opportunities in M ​​consecutive slots. The terminal device 110 may repeat TB over MIN(K,K') PUSCH repetition opportunity slots, with the same symbol allocation being applied in each slot. As a result, excessive repetition can be avoided.

[0054] In some embodiments, terminal device 110 may receive a message from network device 120 to configure terminal device 110 to be in a PUSCH repetition mode (e.g., enhanced type A-1), where the PUSCH repetition mode is utilized to transmit PUSCH transmissions scheduled by predetermined downlink control information in a physical downlink control channel transmission. For example, the predetermined downlink control information may be DCI format 0_1 ​​or 0_2 in the PDCCH.

[0055] In some embodiments, the PUSCH repetition mode may be utilized to transmit a PUSCH transmission scheduled with a predetermined downlink control information in a physical downlink control channel transmission having a cyclic redundancy check (CRC) scrambled with a cell-radio network temporary identifier (C-RNTI), a modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI), or a configured scheduling-radio network temporary identifier (CS-RNTI) with a new data indicator (NDI). Different PUSCH repetition modes may be configured for different predetermined downlink control information in a physical downlink control channel transmission.

[0056] In some embodiments, the MAC-CE may indicate to terminal device 110 to switch between different types. For example, the MAC-CE may indicate to terminal device 110 to switch between Type A and Type A-1, or between Type B and Type B-1 (an extension of Type B). In some other embodiments, a combined encoding / interpretation of new or existing bit fields in the DCI indicates an uplink grant to dynamically utilize Type A or Type A-1.

[0057] In some embodiments, the number of actual repeated transmissions by the uplink control information (UCI) / MAC CE may be reported to the network device 120 via a PUSCH, so that the network device 120 can know the actual repeated transmissions.

[0058] In some example embodiments, network device 120 may indicate the actual number of PUSCH transmissions and / or an indication of continue or stop of repetitions to terminal device 110 via DCI / MAC CE. In some embodiments, the indication may include the number of remaining repetitions. Upon receiving the indication, terminal device 110 may adjust the repetition scheme based on the remaining number of repetitions. It should be appreciated that due to the dynamic DCI indication, the actual number of repetitions at terminal device 110 may be more than the RRC configured number.

[0059] In some embodiments, for PUSCH repetition type A-1, if K>1, the same symbol allocation is applied over K PUSCH repetition opportunities consecutive slots, and PUSCH is limited to a single transmission layer. According to the conditions of clause 11.1 of [6, TS38.213], if a PUSCH transmission in a slot is not omitted, the slot is a PUSCH overlapping opportunity slot. The terminal device 110 should repeat a TB over K PUSCH repetition opportunities consecutive slots in which the same symbol allocation is applied in each slot. Based on Table 6.1.2.1-2, determine the redundancy version applied to the nth transmission opportunity of the TB, where n=0,1,...K-1. For PUSCH repetition type A and type A-1, PUSCH transmission in a slot of a multi-slot PUSCH transmission is omitted according to the conditions of clauses 9, 11.1 and 11.2A of [6, TS38.213].

[0060] Clauses 9 and 11.2A have been provided above as examples of dynamic types. In the following, we refer to clause 11.1 of TS 38.213 and provide some examples of static rules.

[0061] For example, according to the TDD frame structure, the slots for downlink transmission may be predetermined in a more static manner, i.e., according to the TDD frame structure, the terminal device 110 may be configured to use some frames as downlink frames and some frames for uplink transmission, so that the terminal device 110 knows in advance which frames are configured by the system to carry out uplink transmission.

[0062] In some embodiments, in accordance with Clause 11.1, terminal device 110 considers symbols in slots indicated as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to be available for reception, and considers symbols in slots indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to be available for transmission.

[0063] For a set of symbols of a slot indicated to the terminal device 110 as downlink by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if a PUSCH, PUCCH, PRACH or SRS overlaps (even partially overlaps) with the set of symbols of the slot, the terminal device 110 does not transmit the PUSCH, PUCCH, PRACH or SRS.

[0064] For operation on a single carrier in an unpaired spectrum, for a set of symbols in a slot indicated to the terminal device 110 by ssb-PositionsInBurst in SIB1 or ssb-PositionsInBurst in ServingCellConfigCommon, for reception of an SS / PBCH block, the terminal device 110 does not transmit PUSCH, PUCCH, PRACH in the slot if the transmission overlaps with any symbol in the set of symbols, and the terminal device 110 does not transmit SRS in the set of symbols in the slot.

[0065] In some embodiments, if the terminal device 110 is not configured to monitor the PDCCH for DCI format 2_0, for a set of symbols in a slot indicated as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the terminal device 110, - if the terminal device 110 receives a corresponding indication in the DCI format, the terminal device 110 receives a PDSCH or a CSI-RS in the set of symbols of the slot; - If the terminal device 110 receives a corresponding indication by a DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR, the terminal device 110 transmits a PUSCH, a PUCCH, a PRACH, or an SRS within the set of symbols of the slot.

[0066] In some embodiments, for operation on a single carrier in an unpaired spectrum, if terminal device 110 is configured by higher layers to transmit SRS, PUCCH, PUSCH, or PRACH in a set of symbols of a slot and terminal device 110 detects a DCI format that indicates terminal device 110 to receive CSI-RS or PDSCH in a subset of symbols from the set of symbols, terminal device 110 cancels PUCCH, PUSCH, or PUSCH actual repetitions determined from clauses 9 and 9.2.5 or clause 6.1 of [6, TS 38.214], or PRACH transmissions in the remaining symbols from the set of symbols and cancels SRS transmissions in the remaining symbols from the subset of symbols.

[0067] In some embodiments, for a set of slot symbols indicated to the terminal device 110 as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the terminal device 110, and if DCI format 2_0 is detected by the terminal device 110 that provides a slot format using a slot format value other than 255: - if the SFI-index field value in the DCI format 2_0 indicates that the set of symbols of the slot is flexible, and the terminal device 110 detects a DCI format, a RAR UL grant, a fallbackRAR UL grant, or a successRAR that indicates to the terminal device 110 to transmit a PUSCH, a PUCCH, a PRACH, or an SRS in the set of symbols of the slot, the terminal device 110 transmits a PUSCH, a PUCCH, a PRACH, or an SRS in the set of symbols of the slot; - if the SFI-index field value in the DCI format 2_0 indicates that the set of symbols of the slot is flexible, and the terminal device 110 does not detect a DCI format indicating to the terminal device 110 to receive a PDSCH or a CSI-RS, or the terminal device 110 does not detect a DCI format, a RAR UL, a fallbackRAR UL grant, or a successRAR grant indicating to the terminal device 110 to transmit a PUSCH, a PUCCH, a PRACH, or an SRS in the set of symbols of the slot, the terminal device 110 does not transmit or receive in the set of symbols of the slot; - If the terminal device 110 is configured by a higher layer to transmit a PUCCH, a PUSCH, or a PRACH within the set of symbols of the slot, the terminal device 110 transmits a PUCCH, a PUSCH, or a PRACH within the slot only if the SFI-index field value in DCI format 2_0 indicates the set of symbols of the slot as being uplink.

[0068] In some embodiments, if the terminal device 110 is configured by a higher layer to transmit an SRS, a PUCCH, a PUSCH, or a PRACH within a set of symbols of a slot, and the terminal device 110 detects a DCI format 2_0 having a slot format value other than 255 that indicates the slot format of a subset of symbols from the set of symbols as downlink or flexible, or detects a DCI format that indicates the terminal device 110 to receive a CSI-RS or a PDSCH within a subset of symbols from the set of symbols, - The terminal device 110 cancels PUCCH, PUSCH, or PUSCH actual repetitions determined from clauses 9 and 9.2.5 or clause 6.1 of [6, TS 38.214], or PRACH transmissions in the remaining symbols from the set of symbols and cancels SRS transmissions in the remaining symbols from the subset of symbols.

[0069] For a set of symbols of a slot indicated as flexible by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated (if provided), or if tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated are not provided to the terminal device 110 and if the terminal device 110 has not detected DCI format 2_0 that provides the slot format of the slot, - If the terminal device 110 is configured by a higher layer to transmit an SRS, a PUCCH, a PUSCH, or a PRACH in a set of symbols of a slot and EnableConfiguredUL-r16 is not provided to the terminal device 110, the terminal device 110 - Do not transmit a PUCCH or a PUSCH or a PRACH in the slot and do not transmit an SRS in a symbol from the set of symbols in the slot.

[0070] The inventors of the present application also noticed that due to the existence of various skipping rules (e.g., dynamic rules such as DCI format 2_4), the actual transmission of PUSCH repetitions may differ from the available slots for uplink transmission, i.e., the available number of repetitions cannot be reached during the actual transmission.

[0071] In one example, the network device 120 (e.g., a base station) may configure the terminal device 110 to perform eight PUSCH repetitions, and then two slots are canceled due to detection of DCI format 2_4 to cancel the PUSCH transmission or the actual repetition of the PUSCH transmission. Then, the coverage is not as good as the eight repeated PUSCH transmissions because the number of actually received transmissions is six.

[0072] To solve at least part of the above problem, a solution regarding PUSCH repetition is provided. In some embodiments of the present disclosure, the terminal device 110 determines a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a counting rule for counting PUSCH repetition opportunity slots. Then, the terminal device 110 determines a PUSCH repetition actual slot from the set of PUSCH repetition opportunity slots based on an omission rule. Thus, the terminal device 110 transmits data in the determined PUSCH repetition actual slot. In this way, the coverage for uplink transmission of the network can be improved by ensuring that the actual number of repetition transmissions is fixed, e.g., a predetermined number.

[0073] 3 shows a signaling flow 300 illustrating a process for PUSCH repetition in accordance with some embodiments of the present disclosure. For purposes of illustration, the signaling flow 300 is described with reference to FIG. 1. The signaling flow 300 may involve the terminal device 110 and the network device 120 as shown in FIG.

[0074] In signaling flow 300, terminal device 110 determines 310 a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a counting rule for counting PUSCH repetition opportunity slots.

[0075] In some embodiments, for example, the terminal device 110 may determine M consecutive slots based on a set number of repetitions K, where M is the smallest integer for which there are K counted PUSCHs in the M consecutive slots according to the counting rule. Then, the terminal device 110 applies the skipping rule over the M consecutive slots.

[0076] In such an embodiment, if it is determined based on the omission rules for omitting PUSCH transmissions that a PUSCH transmission in one of a plurality of consecutive slots is not omitted, the terminal device 110 may count the slot as one of the set of PUSCH repetition opportunity slots.

[0077] For example, if a PUSCH in a slot is omitted based only on uplink, downlink and flexible RRC (static) configuration, it is not counted. Otherwise, it is counted. This means that PUSCH missing due to DCI (dynamic) indication is also counted this way. Thus, the number of consecutive slots M is fixed and the actual transmission is variable.

[0078] Alternatively, if the PUSCH in a slot is omitted based on the uplink, downlink, and flexible RRC (static) configuration or DCI (dynamic) indication, it is not counted. Otherwise, it is counted. This makes the number of consecutive slots M variable and the actual transmission fixed. Furthermore, in such an embodiment, if the terminal device 110 determines that a PUSCH transmission in one of the consecutive slots is omitted because it failed to detect downlink control information providing slot format information, the terminal device 110 may count the slot as one of the number of counted PUSCH repetition opportunity slots. The set of symbols of the slot is flexible for transmission. Thus, if the terminal device 110 fails to detect a DCI indication already transmitted by the network device 120, the failure to receive a DCI indication (e.g., including a slot format indication (SFI) index field) or the failure to decode the DCI instructing the terminal device 110 to utilize the set of symbols of the slot as the uplink is counted as one PUSCH repetition transmission, even if the PUSCH repetition transmission was not actually performed because the DCI indication was not received. Thus, a failure on the terminal device 110 side will not result in extra resources being allocated for this failure.

[0079] In some embodiments, if a PUSCH transmission in one of the plurality of consecutive slots is omitted and it is determined that a portion of the symbols in the PUSCH transmission for that slot have already been transmitted, the slot may be counted as one of the set of PUSCH repetition opportunity slots. Alternatively, if a PUSCH transmission in one of the plurality of consecutive slots is omitted and it is determined that the number of transmitted symbols for that slot exceeds a threshold, the slot may be counted as one of the set of PUSCH repetition opportunity slots.

[0080] Then, the terminal device 110 determines a PUSCH repetition actual slot from the set of PUSCH repetition opportunity slots based on the skipping rule (320). Thus, the terminal device 110 transmits data in the determined PUSCH repetition actual slot (330).

[0081] In some embodiments, for PUSCH repetition type A-2, if K>1, the same symbol allocation is applied to M consecutive slots, the PUSCH is restricted to a single transmission layer, and PUSCH transmission in a slot of a multi-slot PUSCH transmission is omitted, subject to the conditions of Clauses 9, 11.1, and 11.2A of [6, TS38.213]. M is the smallest integer for which there are K counted PUSCHs in M ​​consecutive slots according to the counting rules.

[0082] In some embodiments, the terminal device 110 should repeat the TB over M PUSCH repetition opportunities consecutive slots with the same symbol allocation applied in each slot. Determine the redundancy version to be applied to the nth transmission opportunity of the TB based on Table 6.1.2.1-2, where n=0, 1, ...M-1.

[0083] 4 is a flow chart of an example method 400 according to an embodiment of the present disclosure. For illustrative purposes only, the method 400 may be implemented in a terminal device 110 such as that shown in FIG.

[0084] In block 410, the terminal device 110 determines (210) a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a first skipping rule. In block 420, the terminal device 110 determines a PUSCH repetition actual slot from the set of PUSCH repetition opportunity slots based on a second skipping rule. In block 430, the terminal device 110 transmits data in the determined PUSCH repetition actual slot.

[0085] In some embodiments, a radio resource control message is received from the network device, the radio resource control message including the first skipping rule.

[0086] In some embodiments, the method further includes receiving downlink control information or a medium access control-control element (MAC-CE) from the network device indicating the second omission rule.

[0087] In some embodiments, the method further includes receiving from the network device a message including a second predetermined number indicating a limit on a number of PUSCH repetition opportunity slots, the set of PUSCH repetition opportunity slots being determined from the number of PUSCH repetition opportunity slots. Determining the set of PUSCH repetition opportunity slots includes determining the set of PUSCH repetition opportunity slots based on the first skipping rule, the first predetermined number, and the second predetermined number.

[0088] In some embodiments, the method further includes receiving a message from the network device to configure the terminal device to be in a PUSCH repetition mode, the PUSCH repetition mode being utilized to transmit PUSCH transmissions scheduled by predetermined downlink control information within a physical downlink control channel transmission.

[0089] In some embodiments, the PUSCH repetition mode is utilized to transmit a PUSCH transmission scheduled with the predetermined downlink control information within a physical downlink control channel transmission having a cyclic redundancy check (CRC) scrambled with at least one of a cell-radio network temporary identifier (C-RNTI), a modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI), and a configured scheduling-radio network temporary identifier (CS-RNTI) with a new data indicator (NDI).

[0090] In some embodiments, the message includes a first predetermined number.

[0091] 5 is a flow chart of an example method 500 according to an embodiment of the present disclosure. For illustrative purposes only, the method 500 may be implemented in a terminal device 110 such as that shown in FIG.

[0092] At block 510, terminal device 110 determines a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a counting rule for counting PUSCH repetition opportunity slots.

[0093] In some embodiments, determining the set of PUSCH repetition opportunity slots includes, pursuant to a determination that a PUSCH transmission in one slot of the plurality of consecutive slots is not omitted based on another omission rule for omitting PUSCH transmission, counting the slot as one of the set of PUSCH repetition opportunity slots.

[0094] In some embodiments, determining the set of PUSCH repetition opportunity slots includes, pursuant to a determination that a PUSCH transmission in one slot of the plurality of consecutive slots is omitted due to failure to detect downlink control information providing slot format information, counting the slot as one of a number of counted PUSCH repetition opportunity slots, wherein a set of symbols of the slot is flexible for transmission.

[0095] In some embodiments, determining the set of PUSCH repetition opportunity slots includes counting a slot as one of the set of PUSCH repetition opportunity slots pursuant to determining that a PUSCH transmission in one slot of the plurality of consecutive slots has been omitted and that a portion of the symbols in the PUSCH transmission for the slot have already been transmitted.

[0096] In some embodiments, determining the set of PUSCH repetition opportunity slots includes counting a slot as one of the set of PUSCH repetition opportunity slots pursuant to a determination that a PUSCH transmission in one slot of the plurality of consecutive slots is omitted and a number of transmitted symbols for the slot exceeds a threshold.

[0097] At block 520, terminal device 110 determines a PUSCH repetition actual slot from the set of PUSCH repetition opportunity slots based on a skipping rule. At block 530, terminal device 110 transmits data in the determined PUSCH repetition actual slot.

[0098] In some embodiments, the method further includes receiving a message from the network device to configure the terminal device to be in a PUSCH repetition mode, the PUSCH repetition mode being utilized to transmit PUSCH transmissions scheduled by predetermined downlink control information within a physical downlink control channel transmission.

[0099] In some embodiments, the PUSCH repetition mode is utilized to transmit a PUSCH transmission scheduled with the predetermined downlink control information within a physical downlink control channel transmission having a cyclic redundancy check (CRC) scrambled with at least one of a cell-radio network temporary identifier (C-RNTI), a modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI), or a configured scheduling-radio network temporary identifier (CS-RNTI) with a new data indicator (NDI).

[0100] In some embodiments, a terminal device (e.g., terminal device 110) includes circuitry configured to determine a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a first skipping rule, determine an actual PUSCH repetition slot from the set of PUSCH repetition opportunity slots based on a second skipping rule, and transmit data in the determined actual PUSCH repetition slot.

[0101] In some embodiments, the circuitry is further configured to receive a radio resource control message from the network device, the radio resource control message including the first omission rule.

[0102] In some embodiments, the circuitry is further configured to receive downlink control information or a medium access control-control element (MAC-CE) from the network device indicating the second omission rule.

[0103] In some embodiments, the circuitry is further configured to receive from the network device a message including a second predetermined number indicating a limit on a number of PUSCH repetition opportunity slots, the set of PUSCH repetition opportunity slots being determined from the number of PUSCH repetition opportunity slots, and determining the set of PUSCH repetition opportunity slots includes determining the set of PUSCH repetition opportunity slots based on the first skipping rule, the first predetermined number, and the second predetermined number.

[0104] In some embodiments, the circuitry is further configured to receive a message from the network device to configure the terminal device to be in a PUSCH repetition mode, the PUSCH repetition mode being utilized to transmit PUSCH transmissions scheduled by predetermined downlink control information within a physical downlink control channel transmission.

[0105] In some embodiments, the PUSCH repetition mode is utilized to transmit a PUSCH transmission scheduled with the predetermined downlink control information within a physical downlink control channel transmission having a cyclic redundancy check (CRC) scrambled with at least one of a cell-radio network temporary identifier (C-RNTI), a modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI), and a configured scheduling-radio network temporary identifier (CS-RNTI) with a new data indicator (NDI).

[0106] In some embodiments, the message includes the first predetermined number.

[0107] In some embodiments, a terminal device (e.g., terminal device 110) includes circuitry configured to: determine, at the terminal device, a set of physical uplink shared channel (PUSCH) repetition opportunity slots based on a counting rule for counting PUSCH repetition opportunity slots; determine an actual PUSCH repetition slot from the set of PUSCH repetition opportunity slots based on a skipping rule; and transmit data in the determined actual PUSCH repetition slot.

[0108] In some embodiments, determining the set of PUSCH repetition opportunity slots includes, pursuant to a determination that a PUSCH transmission in one slot of the plurality of consecutive slots is not omitted based on another omission rule for omitting PUSCH transmission, counting the slot as one of the set of PUSCH repetition opportunity slots.

[0109] In some embodiments, determining the set of PUSCH repetition opportunity slots includes, pursuant to a determination that a PUSCH transmission in one slot of the plurality of consecutive slots is omitted due to failure to detect downlink control information providing slot format information, counting the slot as one of a number of counted PUSCH repetition opportunity slots, wherein a set of symbols of the slot is flexible for transmission.

[0110] In some embodiments, determining the set of PUSCH repetition opportunity slots includes counting a slot as one of the set of PUSCH repetition opportunity slots pursuant to determining that a PUSCH transmission in one slot of the plurality of consecutive slots has been omitted and that a portion of the symbols in the PUSCH transmission for the slot have already been transmitted.

[0111] In some embodiments, determining the set of PUSCH repetition opportunity slots includes counting a slot as one of the set of PUSCH repetition opportunity slots pursuant to a determination that a PUSCH transmission in one slot of the plurality of consecutive slots is omitted and a number of transmitted symbols for the slot exceeds a threshold.

[0112] In some embodiments, the circuitry is further configured to receive a message from the network device to configure the terminal device to be in a PUSCH repetition mode, the PUSCH repetition mode being utilized to transmit PUSCH transmissions scheduled by predetermined downlink control information within a physical downlink control channel transmission.

[0113] In some embodiments, the PUSCH repetition mode is utilized to transmit a PUSCH transmission scheduled with the predetermined downlink control information within a physical downlink control channel transmission having a cyclic redundancy check (CRC) scrambled with at least one of a cell-radio network temporary identifier (C-RNTI), a modulation and coding scheme-cell-radio network temporary identifier (MCS-C-RNTI), or a configured scheduling-radio network temporary identifier (CS-RNTI) with a new data indicator (NDI).

[0114] Fig. 6 is a schematic block diagram of an apparatus 600 suitable for implementing embodiments of the present disclosure. The apparatus 600 may be considered as another exemplary implementation of the network apparatus 120 or the terminal apparatus 110 shown in Fig. 1. Thus, the apparatus 600 may be implemented in the network apparatus 120 or the terminal apparatus 110, or as at least a part thereof.

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

[0116] It is assumed that the program 630 includes program instructions that, when executed by the associated processor 610, enable the device 600 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 1-5. The embodiments herein may be implemented by computer software executable by the processor 610 of the device 600, or by hardware, or by a combination of software and hardware. The processor 610 may be configured to implement various embodiments of the present disclosure. Furthermore, the combination of the processor 610 and the memory 620 may form a processing means 850 suitable for implementing various embodiments of the present disclosure.

[0117] The memory 620 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed and removable memories. Although only one memory 620 is shown in the device 600, there may be several physically different memory modules in the device 600. The processor 610 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 600 may have multiple processors, for example application specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

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

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

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

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

[0122] It should be noted that although operations have been described in a particular order, it should not be understood that such operations need to be performed in the particular order shown, or in any sequential order, or that all of the operations described must be performed in order to achieve desired results. In some cases, multitasking or parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to certain embodiments. Some features described in the context of individual embodiments may be realized in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented in multiple embodiments separately or in any suitable subcombination.

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

Claims

1. means for receiving at least one of a tdd-UL-DL-ConfigurationCommon, a tdd-UL-DL-ConfigurationDedicated, or a ssb-PositionsInBurst from a base station; A means for determining a set of slots to which a repetition count is applied for a physical uplink shared channel (PUSCH) transmission, the means comprising: Among a plurality of slots, a first slot in which at least one of the symbols allocated for the PUSCH transmission overlaps with a downlink symbol indicated by the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated, or with a symbol of an SS / PBCH block provided by the ssb-PositionsInBurst, is not counted in the set of slots; A second slot, in which at least one of the symbols allocated for the PUSCH transmission among the plurality of slots does not overlap with a downlink symbol indicated by the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated, or a symbol of an SS / PBCH block provided by the ssb-PositionsInBurst, is counted into the set of slots; means for performing the PUSCH transmission in the set of slots, the PUSCH transmission being conditionally omitted in the second slot; A terminal device including:

2. The at least one of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, or ssb-PositionsInBurst is received in a radio resource control message. The terminal device according to claim 1 .

3. means for receiving information for setting the number of repetitions from the base station; The terminal device of claim 1 further comprising:

4. The number of repetitions is for the PUSCH transmission scheduled by downlink control information DCI format 0_1 ​​or 0_2 The terminal device according to claim 3.

5. A means for transmitting at least one of a tdd-UL-DL-ConfigurationCommon, a tdd-UL-DL-ConfigurationDedicated, or an ssb-PositionsInBurst to a terminal device, A set of slots to which a repetition count is applied for a physical uplink shared channel (PUSCH) transmission is determined by the terminal device; Among a plurality of slots, a first slot in which at least one of the symbols allocated for the PUSCH transmission overlaps with a downlink symbol indicated by the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated, or with a symbol of an SS / PBCH block provided by the ssb-PositionsInBurst, is not counted in the set of slots; A second slot, in which at least one of the symbols allocated for the PUSCH transmission among the plurality of slots does not overlap with a downlink symbol indicated by the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated, or a symbol of an SS / PBCH block provided by the ssb-PositionsInBurst, is counted into the set of slots; A means for receiving the PUSCH transmission from the terminal device, wherein the PUSCH transmission is omitted in the second slot according to a condition; A base station including:

6. The at least one of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, or ssb-PositionsInBurst is transmitted in a radio resource control message. The base station according to claim 5.

7. means for receiving information from a network device that sets the number of iterations; The base station of claim 5 further comprising:

8. The number of repetitions is for the PUSCH transmission scheduled by downlink control information DCI format 0_1 ​​or 0_2 The base station according to claim 7.

9. A communication method executed in a terminal device, comprising: receiving at least one of a tdd-UL-DL-ConfigurationCommon, a tdd-UL-DL-ConfigurationDedicated, or a ssb-PositionsInBurst from a base station; determining a set of slots to which a repetition count is applied for a physical uplink shared channel (PUSCH) transmission, Among a plurality of slots, a first slot in which at least one of the symbols allocated for the PUSCH transmission overlaps with a downlink symbol indicated by the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated, or with a symbol of an SS / PBCH block provided by the ssb-PositionsInBurst, is not counted in the set of slots; A second slot in which at least one of the symbols allocated for the PUSCH transmission among the plurality of slots does not overlap with a downlink symbol indicated by the tdd-UL-DL-ConfigurationCommon or the tdd-UL-DL-ConfigurationDedicated, or a symbol of an SS / PBCH block provided by the ssb-PositionsInBurst is counted into the set of slots; performing the PUSCH transmission in the set of slots, conditionally omitting the PUSCH transmission in the second slot; A communication method including:

10. The at least one of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, or ssb-PositionsInBurst is received in a radio resource control message. The communication method according to claim 9.

11. receiving information from the base station that sets the number of repetitions; The communication method of claim 9 further comprising:

12. The number of repetitions is for the PUSCH transmission scheduled by downlink control information DCI format 0_1 ​​or 0_2 The communication method according to claim 11.

Images