Repetition of uplink transmissions

Abstract

The embodiment of the invention relates to a repetition method of uplink transmission. A terminal device receives, from a network device, scheduling information that schedules an uplink transmission to be transmitted by the terminal device using a repetition type; determining, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, where the first set of resources is located in a first number of slots having a first slot type, and the second set of resources is located in a second number of slots having a second slot type; and the second set of resources is located in a second number of time slots having a second time slot type; and transmitting the plurality of repetitions to the network device. The solution enables enhanced coverage improvement of uplink transmissions.

Description

Technical Field

[0001] Various example embodiments relate to the field of telecommunications, and in particular to methods, devices, apparatus, and computer-readable storage media for repetition of uplink transmissions. Background Art

[0002] In the field of communications, there is an ongoing evolution to provide efficient and reliable solutions for utilizing wireless communication networks. To meet the increased demand for wireless data services since the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. The new communication systems can support various types of service applications for terminal devices.

[0003] 3GPP Rel-15 introduced a timeslot aggregation feature for the Physical Uplink Shared Channel (PUSCH), also known as PUSCH repetition type A. Rel-16 allows the number of repetitions for PUSCH repetition type A to be dynamically indicated by associating the repetition number with each row of the Time Domain Resource Allocation (TDRA) table. Rel-17 further improves PUSCH repetition type A by allowing the number of repetitions on available timeslots to be counted. In addition, Rel-17 Coverage Enhancement WI specifies a feature called Transport Block Handling Over Multiple Slots (TBoMS). This feature allows a single transport block (TB) to be mapped over multiple timeslots. Summary of the Invention

[0004] In general, example embodiments of the present disclosure provide a solution for uplink transmission repetition.

[0005] In a first aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: receive scheduling information from a network device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; determine, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, wherein the first set of resources is located in a first number of time slots having a first time slot type and the second set of resources is located in a second number of time slots having a second time slot type; and send the plurality of repetitions of the uplink transmission to the network device.

[0006] In a second aspect, a network device is provided. The network device comprises: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: send scheduling information to a terminal device, the scheduling information scheduling an uplink transmission to be sent by the terminal device using a repetition type; and receive, from the terminal device, a plurality of repetitions of the uplink transmission comprising a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

[0007] In a third aspect, a method is provided. The method includes: receiving, at a terminal device, scheduling information from a network device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; determining, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, wherein the first set of resources is located in a first number of time slots having a first time slot type and the second set of resources is located in a second number of time slots having a second time slot type; and sending the plurality of repetitions of the uplink transmission to the network device.

[0008] In a fourth aspect, a method is provided. The method comprises: sending, at a network device, scheduling information to a terminal device, the scheduling information scheduling an uplink transmission to be sent by the terminal device using a repetition type; and receiving, from the terminal device, a plurality of repetitions of the uplink transmission comprising a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

[0009] In a fifth aspect, an apparatus is provided. The apparatus includes: means for receiving, at a terminal device, scheduling information from a network device, the scheduling information scheduling an uplink transmission to be sent by the terminal device using a repetition type; means for determining, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, wherein the first set of resources is located in a first number of time slots having a first time slot type and the second set of resources is located in a second number of time slots having a second time slot type; and means for sending the plurality of repetitions of the uplink transmission to the network device.

[0010] In a sixth aspect, an apparatus is provided. The apparatus comprises means for sending, at a network device, scheduling information to a terminal device, the scheduling information scheduling an uplink transmission to be sent by the terminal device using a repetition type; and means for receiving, from the terminal device, a plurality of repetitions of the uplink transmission comprising a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, the medium comprising program instructions for causing an apparatus to at least execute the method according to any one of the third to fourth aspects above.

[0012] In an eighth aspect, a non-transitory computer-readable medium is provided, the medium including program instructions stored thereon, the program instructions being used to at least execute the method according to any one of the third to fourth aspects above.

[0013] In a ninth aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to at least: receive scheduling information from a network device, the scheduling information scheduling uplink transmissions to be sent by a terminal device using a repetition type; determine a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions based on the repetition type, wherein the first set of resources is located in a first number of time slots having a first time slot type and the second set of resources is located in a second number of time slots having a second time slot type; and send the plurality of repetitions of the uplink transmission to the network device.

[0014] In a tenth aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to at least: send scheduling information to a terminal device, the scheduling information scheduling an uplink transmission to be sent by the terminal device using a repetition type; and receive from the terminal device a plurality of repetitions of the uplink transmission comprising a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

[0015] In an eleventh aspect, a terminal device is provided. The terminal device includes: a receiving circuit system configured to receive scheduling information from a network device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; a determining circuit system configured to determine, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, wherein the first set of resources is located in a first number of time slots having a first time slot type and the second set of resources is located in a second number of time slots having a second time slot type; and a transmitting circuit system configured to transmit the plurality of repetitions of the uplink transmission to the network device.

[0016] In a twelfth aspect, a network device is provided. The network device comprises: a transmit circuit system configured to transmit scheduling information to a terminal device, the scheduling information scheduling an uplink transmission to be transmitted by the terminal device using a repetition type; and a receive circuit system configured to receive a plurality of repetitions of the uplink transmission from the terminal device, comprising a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

[0017] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0019] Figure 1A An example communication system is shown in which embodiments of the present disclosure may be implemented;

[0020] Figure 1B shows a schematic diagram illustrating SBFD time slots and non-SBFD time slots;

[0021] Figure 1C shows a schematic diagram illustrating frequency-time resource partitioning using SBFD compared to FDD and TDD;

[0022] Figure 1D and Figure 1E shows a schematic diagram illustrating the types of co-channel interference in SBFD deployment;

[0023] Figure 1Fshows a schematic diagram illustrating the power spectral density gain provided by TBoMS compared to a single-slot PUSCH for the same TBS;

[0024] Figure 2 A schematic diagram illustrating a communication process between a terminal device and a network device according to some embodiments of the present disclosure is shown;

[0025] Figure 3 shows a schematic diagram illustrating a repetitive type of SBFD operation according to the present disclosure;

[0026] Figure 4 A schematic diagram illustrating a communication process between a terminal device and a network device according to some other embodiments of the present disclosure is shown;

[0027] Figure 5 A schematic diagram illustrating methods implemented at a terminal device according to some other embodiments of the present disclosure is shown;

[0028] Figure 6 A schematic diagram illustrating a method implemented at a network device according to some other embodiments of the present disclosure is shown;

[0029] Figure 7 shows a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure; and

[0030] Figure 8 A block diagram illustrating an example computer-readable medium according to some embodiments of the present disclosure is shown;

[0031] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0032] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described only for illustrative purposes and to help those skilled in the art understand and implement the present disclosure, and do not imply any limitation on the scope of the present disclosure. The present disclosure described herein can be implemented in various other ways in addition to the ways described below.

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

[0034] In this disclosure, references to "one embodiment," "an embodiment," and "an example embodiment" indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, those skilled in the art recognize that it is within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

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

[0036] As used herein, the term "comprising", "including", "having", "including" and / or "comprising" specify the existence of the feature, element and / or component when used in this article, but does not exclude the existence or addition of one or more other features, elements, components and / or their combination. As used herein, "at least one of the following: <list of two or more elements>" and "at least one of the following <list of two or more elements>" and similar wording (wherein the list of two or more elements is connected by "and" or "or") mean at least any one element in these elements or at least any two or more elements in these elements or at least all elements in these elements.

[0037] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0038] (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuitry)

[0039] present); and

[0040] (b) a combination of hardware circuitry and software such as (if applicable):

[0041] (i) a combination of analog and / or digital hardware circuit(s) with software / firmware, and

[0042] (ii) any portion of hardware processor(s) with software (including digital signal processor(s), software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions); and

[0043] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), that require software (e.g., firmware) to operate, but in which case the software may not be present when not required for operation.

[0044] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0045] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), New Radio (NR), Wideband Code Division Multiplexing (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network equipment in the communication network can be performed according to any suitable intergenerational communication protocol, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems. Due to the rapid development of communication, there will certainly be future types of communication technologies and systems that can be used to implement the present disclosure. The scope of the present disclosure should not be considered to be limited to the above-mentioned systems.

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

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

[0048] 3GPP Rel-15 introduced the time slot aggregation feature for the Physical Uplink Shared Channel (PUSCH), also known as PUSCH repetition type A. In this feature, the transmission of a transport block is repeated over multiple time slots. The key design aspects of PUSCH repetition type A in Rel-15 include:

[0049] Resource allocation: The same resource allocation is applied across PUSCH repetitions. For the time domain: Each repetition is in a time slot. Only the single start and length of the PUSCH within the time slot are indicated, i.e., a single Start and Length Indicator Value (SLIV). The same start and length indicated by a single SLIV are applied across all PUSCH repetitions. In Rel-15, the repetition count for PUSCH repetition type A is semi-statically configured in RRC (Radio Resource Control), and the repetition count is counted over consecutive physical time slots. If the number of available symbols in a time slot is insufficient (<L), the PUSCH repetition is not transmitted in that time slot. For the frequency domain: PUSCH repetitions have the same frequency domain resource allocation (i.e., the same number of Physical Resource Blocks (PRBs) in the frequency domain and the same positions of these PRBs).

[0050] Transport Block Size (TBS) determination: The unquantized intermediate variable (NInfo) used to calculate the TBS for PUSCH repetition type A is calculated based on the number of REs determined in a time slot.

[0051] Rate Matching: The same or different redundancy versions (RVs) of the coded bits in the circular buffer can be applied to each PUSCH repetition. The RV for the first repetition can be indicated by the scheduling DCI (Downlink Control Information) for dynamic grants or pre-configured for configuration grants. If different RVs are applied, the RVs will be cycled from the configured RV sequence, following the indicated RV for the first repetition. There are four RVs, each of which provides information about the starting coded bits of the circular buffer that the UE should map to the PUSCH transmission associated with the RV.

[0052] Rel-16 allows the number of repetitions for PUSCH repetition type A to be dynamically indicated by associating the repetition number with each row of the time domain resource allocation (TDRA) table. In addition, Rel-16 also introduces PUSCH repetition type B for ultra-reliable low latency (URLLC) applications. In this feature, a single SLIV is used to determine multiple back-to-back nominal repetitions of the same length, and each nominal repetition can cross a slot boundary. Then, if each nominal repetition crosses a slot boundary or an invalid symbol, it is divided into multiple actual repetitions. PUSCH repetitions in PUSCH repetition type B also have the same frequency domain resource allocation.

[0053] Rel-17 further improves PUSCH repetition type A by allowing the number of repetitions on available time slots to be counted (i.e., only the number of repetitions on time slots that can be used for repeated transmissions is counted). Rel-17 also increases the maximum number of repetitions of PUSCH repetition type A from 16 to 32.

[0054] Rel-17 Coverage Enhancement WI specifies a feature called Transport Block Management Over Multiple Slots (TBoMS). This feature allows a single transport block (TB) to be mapped across multiple slots, meaning that the resource allocation for a single PUSCH transmission can span multiple slots. This is different from PUSCH repetition.

[0055] Some key design aspects of TBoMS can be summarized as follows:

[0056] Resource Allocation: For time domain: A new column is added in the TDRA table to indicate the number of time slots allocated for TBoMS (N slot ). N slotCounting over available slots (following the Rel-17 rule for counting over available slots for PUSCH repetition type A). Therefore, non-contiguous slots can be used for TBoMS in TDD (time division duplex). The resources in each slot allocated for TBoMS have the same starting symbol (S) and length (L) (similar to repetition type A). In the frequency domain: the same number of PRBs are allocated across the slots of TBoMS transmissions (similar to repetition type A).

[0057] TBS confirms: NInfo for TBoMS is based on N slot The scaled number of REs determined in the first time slot allocated to the TBoMS is calculated, where N slot is the number of time slots allocated for the TBoMS. In other words, the TBS for the TBoMS is calculated based on the total resources allocated for the TBoMS across multiple time slots.

[0058] Rate matching: Only a single redundancy version is used for a single TBoMS (i.e., there is no RV cycle within a single TBoMS). Bit selection and bit interleaving from the circular buffer are performed for each time slot. For bit selection within a time slot, the index of the starting coded bit in the circular buffer is a continuous index starting from the position of the last bit selected in the previously allocated time slot, regardless of whether UCI (uplink control information) multiplexing occurred in the previously allocated slot. TBoMS transmission is limited to one code block.

[0059] Repetition for a single TBoMS: Repetition for a single TBoMS is supported. The column in the TDRA table that indicates the number of repetitions for Rel-17 PUSCH repetition type A (ie, numberOfRepetitions-r17) is also used to indicate the number of repetitions for a single TBoMS (N rep ). UE repeatedly determines N for TBoMS rep *N slot Available time slots, the S&L on each time slot is the same, but the TBS will be calculated by the resources of a single TBoMS (i.e., by N slot Scaling). Redundancy versions (RVs) are cycled repeatedly across TBoMSs. The legacy Rel-15 / 16 RV sequences and RV index indicators are reused.

[0060] Rel-18 duplex evolution study items, including sub-band non-overlapping full duplex (SBFD). 3GPP 5G NR currently supports two duplex modes: FDD (frequency division duplex) for paired bands and TDD for unpaired bands. In TDD, time domain resources are split between downlink and uplink. Allocating a limited duration for the uplink in TDD results in reduced coverage, increased latency, and decreased capacity.

[0061] Inspired by this, 3GPP has agreed to initiate a Rel-18 study project (RP-213591) on the evolution of duplex operation in NR to address the above challenges. One of the goals of this study project is to allow simultaneous DL (downlink) transmission and UL (uplink) transmission on different physical resource blocks (PRBs) / subbands within unpaired wideband NR cells. This can be called sub-band non-overlapping full duplex (SBFD). In other sources, this duplex scheme is also called cross-division duplex (xDD) scheme (see, for example, this article) or flexible division duplex (FDU).

[0062] Some of the objectives of the research project (RP-213591) are as follows:

[0063]

[0064]

[0065] According to the above description of SBFD operation, there are two types of time slots for both DL and UL transmissions: SBFD time slots and non-SBFD time slots. Several SBFD operation modes have been studied, including whether or not SBFD-aware UEs are aware of the time and frequency locations of the subbands for SBFD operation. However, at the 3GPP RAN1#110 meeting, it was agreed to prioritize at least the operation mode in which the time and frequency locations of the subbands for SBFD operation are known to SBFD-aware UEs. This means that SBFD time slots must be known to (SBFD-aware) UEs in one way or another.

[0066] For cross-link interference (CLI) in SBFD timeslots, a new type of CLI, co-channel inter-subband CLI, was introduced in RAN1#110 meeting. This interference can be better categorized into: 1) gNB self-interference; 2) intra-cell UE-to-UE co-channel inter-subband CLI; 3) inter-cell UE-to-UE co-channel inter-subband CLI; and 4) gNB-to-gNB co-channel inter-subband CLI.

[0067] In addition to these new CLI types, in case the frequency domains in adjacent cells are partitioned differently, the system can also be affected by co-channel intra-sub-band CLI, i.e. CLI from transmissions on overlapping frequency resources: 5) gNB to gNB cell co-channel intra-sub-band CLI; 6) UE to UE cell co-channel intra-sub-band CLI.

[0068] In the case of dynamic TDD, flexible slots and static slots are equivalent to SBFD slots and non-SBFD slots, respectively. However, in dynamic TDD, there is no subband splitting, and the gNB can freely schedule DL or UL transmissions on the flexible slots. Therefore, in the case of dynamic TDD, the CLI is the gNB-to-gNB co-channel interference and the UE-to-UE co-channel interference.

[0069] At the RAN1#111 meeting, the following agreements were reached:

[0070]

[0071]

[0072] From the above description of CLI types, it can be seen that UL transmissions in SBFD timeslots (e.g., especially PUSCH) will be affected by at least gNB self-interference (1), gNB-to-gNB co-channel inter-subband CLI (4), and gNB-to-gNB inter-cell co-channel intra-subband CLI (5). This significantly affects the coverage of UL transmissions in SBFD timeslots. UL transmissions in non-SBFD timeslots are not affected by these interferences, at least when the frame structure is aligned across cells. Therefore, enhancements are needed to improve the coverage of PUSCH transmissions in SBFD timeslots (compared to non-SBFD timeslots), especially when the UE is in coverage deficit.

[0073] Using TBoMS with repetition can help improve the coverage of PUSCH transmission. However, the current TBoMS repetition framework has several limitations when used for SBFD operation, namely

[0074] TBoMS repetition does not allow for different numbers of PRBs and frequency allocations across repetitions. Therefore, it cannot take advantage of the fact that non-SBFD timeslots have larger bandwidth and better coverage (lower CLI) compared to SBFD timeslots to increase the number of PRBs used for repetitions on SBFD timeslots. This is critical in SBFD operation because the bandwidth of the UL subband in an SBFD timeslot is limited and shared by many SBFD-aware UEs in the cell. Furthermore, coexistence with other cells can lead to intra-subband co-channel CLI scenarios, where some DL transmissions from other cells can occur in the UL subband of the current cell using SBFD. In this case, assuming scheduling information is exchanged between gNBs, the current gNB can avoid this interference by allocating UL transmissions that do not overlap with DL transmissions from other cells, resulting in a smaller number of PRBs that can be used for UL transmissions in the SBFD timeslot compared to non-SBFD timeslots.

[0075] TBoMS repetition always considers the same number of timeslots for each repetition. Therefore, it cannot take advantage of the fact that non-SBFD timeslots have lower CLI than SBFD timeslots to minimize the number of timeslots for TBoMS on non-SBFD timeslots (and improve latency).

[0076] Several technical solutions have addressed resource determination for Rel-17 TBoMS features. Specifically, when a TBoMS is scheduled across both SBFD and non-SBFD time slots, the issue of determining available time slots for the TBoMS has been raised. These technical solutions address the issues involved in enabling TBoMS to operate in SBFD. However, no solution has been identified that defines a new recurrence type for SBFD operation.

[0077] Therefore, a new PUSCH repetition type is needed for use with SBFD operation that takes into account the advantages of TBoMS in resolving coverage deficiencies caused by CLI in SBFD time slots, while also utilizing the characteristics of SBFD operation with respect to bandwidth and CLI differences between SBFD time slots and non-SBFD time slots. As described above, it can be seen that coverage deficiencies caused by CLI in time slots of a first time slot type (e.g., SBFD) are not resolved, and the characteristics of operation associated with the first time slot type with respect to bandwidth and CLI differences between time slots of different types (e.g., SBFD time slots and non-SBFD time slots) are not utilized.

[0078] In view of the above, the embodiments of the present disclosure provide a solution for repetition of uplink transmission. This solution enables enhanced coverage improvement of uplink transmission. The principles and embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. First, refer to Figure 1A , which illustrates an example communication system 100 in which embodiments of the present disclosure may be implemented. System 100 includes a terminal device 110 and a network device 120. As long as the terminal device 110 is located within a corresponding cell, the terminal device 110 can connect and communicate with the network device 120 in either UL or DL. In the communication system, UL refers to a link in the direction from the terminal device 110 to the network device 120, and DL refers to a link in the direction from the network device 120 to the terminal device 110. The network device 120 may send scheduling information for scheduling uplink transmissions to the terminal device 110, and the terminal device 110 may send multiple repetitions of uplink transmissions to the network device 120.

[0079] It should be understood that the number of network devices 120 and terminal devices 110 is for illustration purposes only and does not imply any limitation. The system 100 may include any suitable number of network devices 120 and terminal devices 110 suitable for implementing the embodiments of the present disclosure.

[0080] Communications in the communication system 100 may be implemented according to any suitable communication protocol(s), including but not limited to first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G) cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or to be developed in the future. Furthermore, communications may utilize any suitable wireless communication technology, including but not limited to code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology currently known or to be developed in the future.

[0081] Based on the above discussion, some contents will be further described below with reference to the accompanying drawings. Figure 1B A schematic diagram illustrating SBFD and non-SBFD time slots is shown. During a SBFD time slot, non-overlapping DL subbands and (multiple) UL subbands are both present, and during a non-SBFD time slot, the entire frequency band is used for DL ​​or UL (i.e., legacy / full DL / UL time slots). Figure 1C A schematic diagram illustrating frequency-time resource partitioning using SBFD compared to FDD and TDD is shown.

[0082] Figure 1D and Figure 1E A schematic diagram illustrating the types of co-channel interference in SBFD deployment is shown. Referring to the above, gNB self-interference (1), intra-cell UE-to-UE co-channel sub-band CLI (2), inter-cell UE-to-UE co-channel sub-band CLI (3) and gNB-to-gNB co-channel sub-band CLI (4), as shown in FIG. Figure 1D As shown. The intra-channel sub-band CLI (5) between gNB and gNB cells and the intra-channel sub-band CLI (6) between UE and UE cells are as follows. Figure 1E shown.

[0083] Figure 1F A schematic diagram illustrating the power spectral density gain provided by TBoMS compared to a single-slot PUSCH for the same TBS is shown. Figure 1F A major advantage of TBoMS is that it can reduce the number of PRBs required to transmit the same transport block size (TBS) compared to when the TB is transmitted in a single time slot. This helps improve the energy per resource element (EPRE). Therefore, it improves coverage.

[0084] Figure 21 is a schematic diagram illustrating a communication process 200 between a terminal device 110 and a network device 120 according to some embodiments of the present disclosure. Figure 2 As shown, network device 120 may send (210) scheduling information 205 to terminal device 110, the scheduling information scheduling uplink transmissions to be sent by terminal device 110 using a repetition type. On the terminal device 110 side, terminal device 110 may receive (220) scheduling information 205 from network device 120. Terminal device 110 may determine (230) a first set of resources for a first repetition in a plurality of repetitions 215 of uplink transmissions, and a second set of resources for a second repetition in the plurality of repetitions based on the repetition type. The first set of resources is located in a first number of time slots having a first time slot type, and the second set of resources is located in a second number of time slots having a second time slot type. Terminal device 110 may send (240) the plurality of repetitions 215 of the uplink transmissions to network device 120. On the network device 120 side, network device 120 may receive (250) the plurality of repetitions 215 from terminal device 110.

[0085] In this way, uplink cell coverage is improved overall and latency is reduced. In addition, uplink throughput and resource efficiency are both improved.

[0086] In some embodiments, before sending the scheduling information, the network device 120 may send a first indication that the repetition type is applicable to uplink transmission to the terminal device 110. Before receiving the scheduling information, the terminal device 110 may receive the first indication from the network device 120.

[0087] In some embodiments, based on receiving the first indication, the terminal device 110 may determine the repetition type as a default repetition type. For example, as long as the UE (an example of the terminal device 110) receives the first indication, the repetition type is supported by default.

[0088] In some embodiments, the scheduling information may comprise a second indication indicating whether the repetition type is to be used for uplink transmission (at the terminal device 110 ).

[0089] In some embodiments, based on determining that the second indication is configured to indicate that the repetition type is to be used for uplink transmissions, the terminal device 110 may determine that the uplink transmissions are to be sent using the repetition type.

[0090] In some embodiments, the second indication may comprise a column of a time domain resource allocation (TDRA) table. Additionally or alternatively, the second indication may comprise a field in downlink control information (DCI).

[0091] In some embodiments, based on determining that the terminal device 110 is configured with operation associated with the first time slot type, the terminal device 110 may determine the repetition type as a default repetition type. For example, when the UE is configured with SBFD operation, the repetition type is supported by default.

[0092] In some embodiments, to determine the first set of resources and the second set of resources, the terminal device 110 may determine the first set of resources from a first number of time slots, where the first number is greater than 1; and may determine the second set of resources from a second number of time slots, where the second number is equal to 1. In some embodiments, the first number is N slot express.

[0093] In some embodiments, the first number is determined based on the number of consecutive time slots of the first time slot type. slot Always equal to the number of consecutive SBFD slots.

[0094] In some embodiments, where the first time slot is between a plurality of consecutive time slots, the first number is determined based on 1 plus the number of remaining consecutive time slots of the plurality of consecutive time slots having the first time slot type excluding the first time slots used for the plurality of repetitions. For example, in some embodiments, if the repetition first time slot is an SBFD time slot, then N slot Equal to the remaining SBFD time slots in the consecutive SBFD time slot group plus 1 (the first time slot).

[0095] In some embodiments, where the first time slot for the plurality of repetitions has a second time slot type, the first number is determined based on the number of consecutive time slots having the first time slot type. For example, in some embodiments, if the first time slot for the repetition is a non-SBFD time slot, then N slot Equal to the number of consecutive SBFD time slots.

[0096] In some embodiments, the first number is determined based on the number of time slots allocated for transport block multi-slot processing (TBoMS). slot is equal to the number of time slots allocated for TBoMS in the current specification, i.e., the number determined by the column in the TDRA table. In this case, it is up to the gNB (an example of network device 120) to ensure that N slot ≤ the number of consecutive SBFD time slots, and N slot >1.

[0097] In some embodiments, on the terminal device 110 side, the first repetition is configured with a first starting symbol index and a first allocated resource length per time slot; the second repetition is configured with a second starting symbol index and a second allocated resource length. On the network device 120 side, the network device 120 may configure the first starting symbol index and the first allocated resource length per time slot for the first repetition, and configure the second starting symbol index and the second allocated resource length per time slot for the second repetition. In addition, in some embodiments, the first starting symbol index may be the same as the second starting symbol index per time slot; or the first allocated resource length may be the same as the second allocated resource length per time slot. In some other embodiments, the first starting symbol index may be different from the second starting symbol index per time slot; or the first allocated resource length may be different from the second allocated resource length per time slot.

[0098] In some embodiments, on the network device 120 side, the network device 120 may indicate the first starting symbol index and the first allocated resource length via one of a radio resource control (RRC) message or scheduling information, and the network device 120 may indicate the second starting symbol index and the second allocated resource length via the other of the RRC message or scheduling information. In other words, on the terminal device 110 side, the first starting symbol index and the first allocated resource length may be indicated via one of a radio resource control (RRC) message or scheduling information; and the second starting symbol index and the second allocated resource length may be indicated via the other of the RRC message or scheduling information.

[0099] In some embodiments, where the plurality of repeated first time slots have a first time slot type, the terminal device 110 may determine that the number of physical resource blocks (PRBs) used for the second repetition is equal to the number of PRBs used for the first repetition scaled by a factor. For example, in some embodiments, if the repeated first time slot is an SBFD time slot, the number of PRBs used for the single-slot repetition in a non-SBFD time slot is Equal to the number of PRBs used for TBoMS repetition in the SBFD slot scaled by a factor

[0100] In some other embodiments, where the first time slot of the plurality of repetitions has the second time slot type, the terminal device 110 may determine that the number of PRBs used for the first repetition is equal to the number of PRBs used for the second repetition scaled by a factor. For example, in some embodiments, if the first time slot of the repetition is a non-SBFD time slot, the number of PRBs used for the TBoMS repetition in the SBFD time slot is Equal to the number of PRBs used for single slot repetition scaled by a factor

[0101] In some embodiments, the factor may be equal to the first number of time slots of the first time slot type. In some other embodiments, the factor may be indicated via an RRC message or scheduling information on the terminal device 110 side. In other words, the factor may be indicated via an RRC message or scheduling information on the network device 120 side.

[0102] In some embodiments, when multiple repeated first time slots have a first time slot type, the terminal device 110 can determine that the starting resource block (RB) for the second repetition is equal to: the starting RB for the first repetition plus an offset, or a reference RB in the frequency domain plus an offset.

[0103] Alternatively, in some embodiments, where the multiple repeated first time slots have the second time slot type, the terminal device 110 may determine that the starting RB for the first repetition is equal to: the starting RB for the second repetition plus an offset, or a reference RB in the frequency domain plus an offset.

[0104] In some embodiments, the offset may be indicated via an RRC message (by network device 120). In some other embodiments, the offset may be indicated via scheduling information.

[0105] In some embodiments, the reference RB may be the starting RB of the bandwidth for uplink transmission. In some other embodiments, the reference RB may be the starting RB of a subband for uplink transmission that coexists with at least a subband for downlink transmission in a time slot. In some other embodiments, the reference RB may be the value of the starting RB indicated via an RRC message or scheduling information.

[0106] In some embodiments, for the plurality of repetitions, the terminal device 110 may calculate a transport block size (TBS) based on at least one allocated resource per time slot having a first time slot type multiplied by the first number. Additionally or alternatively, in some embodiments, the terminal device 110 may calculate the TBS based on at least one allocated resource per time slot having a second time slot type.

[0107] In some embodiments, the terminal device 110 may determine a first redundancy version (RV) sequence that circulates across a first plurality of repetitions associated with a first time slot type in a plurality of repetitions; and may determine a second RV sequence that circulates across a second plurality of repetitions associated with a second time slot type in a plurality of repetitions. In other words, according to the present disclosure, the first redundancy version (RV) sequence that circulates across the first plurality of repetitions associated with the first time slot type in a plurality of repetitions is a first RV sequence; and the second RV sequence that circulates across the second plurality of repetitions associated with the second time slot type in a plurality of repetitions is a second RV sequence.

[0108] In some embodiments, the time slots having the first time slot type are sub-band non-overlapping full-duplex (SBFD) time slots, and the time slots having the second time slot type are non-SBFD time slots. In some other embodiments, the time slots having the first time slot type are flexible time slots, and the time slots having the second time slot type are static time slots.

[0109] According to some embodiments of the present disclosure, a new repetition type of SBFD operation is proposed. Figure 3 FIG. 1 is a diagram illustrating a repetitive type of SBFD operation according to the present disclosure. Figure 3 , TBoMS is applied across SBFD time slots (in the UL sub-band), as the number of PRBs with lower PRBs (given by ), and single-slot PUSCH transmission is applied to each non-SBFD UL slot as the one with higher PRB number (denoted by Indicates that ). The repetition using TBoMS across SBFD time slots may be referred to as TBoMS repetition (e.g., Figure 3 1st and 3rd repetitions in ), and the other repetitions are called single-slot repetitions (e.g., Figure 3 2nd and 4th repetitions in ).

[0110] Figure 4 A schematic diagram illustrating a communication process 400 between a terminal device 110 and a network device 120 is shown. The terminal device 110 may be a UE, and the network device 120 may be referred to as NW. In step 1, the network device 120 indicates to the terminal device 110 the number of sub-band full duplex (SBFD) time slots / symbols and the positions of the time slots / symbols in a radio frame, and the number of non-SBFD time slots / symbols and the positions of the time slots / symbols in a radio frame. Specifically, the network device 120 indicates and the terminal device 110 receives the following: the frequency band; the number of time slots / symbols in the radio frame (in which the frequency band is split into multiple subbands and at least one subband is used for DL ​​transmission and at least one subband is used for UL transmission, i.e., sub-band full-duplex (SBFD) time slots / symbols) and the positions of the number of time slots / symbols; and the number of time slots / symbols in the radio frame (in which the entire frequency band is used for DL ​​transmission or UL transmission, i.e., non-SBFD time slots / symbols) and the positions of the number of time slots / symbols.

[0111] In some embodiments, the network device 120 may indicate the above via RRC configuration or DCI.

[0112] In step 2 , the network device 120 indicates that a new repetition type (ie, a repetition type in the present disclosure) for PUSCH transmission may be applied at the terminal device 110 .

[0113] Specifically, the network device 120 indicates, and the terminal device 110 receives, an indication (referred to as a first indication) that a new repetition type for PUSCH transmission should be applied at the terminal device 110. In some embodiments, the network device 120 may indicate the first indication via RRC configuration.

[0114] In step 3, network device 120 may schedule PUSCH transmissions with repetitions across SBFD timeslots and non-SBFD timeslots using the new repetition type.

[0115] In some embodiments, the scheduling DCI may convey information about whether the new repetition type should be used at the terminal device 110. Specifically, the network device 120 indicates and the terminal device 110 receives (e.g., via the scheduling DCI) an indication (referred to as the second indication) about whether the new PUSCH repetition type should be used at the terminal device 110 for PUSCH transmission with repetitions, i.e., a dynamic indication.

[0116] In various embodiments, this indication (second indication) can be accomplished using different alternatives (Alt. 1-Alt. 3). In some embodiments, as in Alt. 1, a new column is added to the TDRA table (see 3GPP TS 38.214, Section 6.1.2.1) that indicates whether the new repetition type should be applied to each row of the TDRA table (e.g., associated with bit 0 or 1). In other words, the second indication can include a column of the TDRA table.

[0117] In some other embodiments, such as Alt. 2, a new field is added in the DCI for triggering the applicability of the new repetition type. In other words, the second indication may include a field in the DCI.

[0118] In some other embodiments, such as Alt.3, as long as the UE receives an indication (first indication) in step 2 and / or when the UE is configured with SBFD operation, the new repetition type is supported by default.

[0119] In step 4, the terminal device 110 determines the time domain resources and frequency domain resources, the transport block size and the redundancy version for sending the coded bits of the transport block using the scheduled PUSCH transmission with the new repetition type, where the time domain resources and frequency domain resources across the repetitions may be different depending on whether the repetition is on an SBFD time slot or a non-SBFD time slot.

[0120] Taking the terminal device 110 as an example, the UE may determine time domain resources and frequency domain resources, a transport block size and a redundancy version for sending a transport block via multiple repetitions of a PUSCH.

[0121] For time domain resource determination, repetition in SBFD time slots can use the slot The repetition in non-SBFD slots may use resources from multiple slots (referred to as TBoMS repetition), and the repetition in non-SBFD slots may use resources from a single slot (referred to as single slot repetition).

[0122] The above N slot Can be determined from one of the following alternatives (Alt.1-Alt.3 below) (N slot ≤ the number of consecutive SBFD time slots, and N slot >1):

[0123] Alt.1:N slot Always equal to the number of consecutive SBFD slots.

[0124] Alt.2: In some embodiments, if the first time slot of the repetition is a SBFD time slot, then N slot =N is equal to the remaining SBFD time slots in the group of consecutive SBFD time slots plus 1 (the first time slot). Otherwise, in some embodiments, the first time slot of the repetition is a non-SBFD time slot, N slot Equal to the number of consecutive SBFD time slots.

[0125] Alt.3: In some embodiments, N slot is equal to the number of time slots allocated for TBoMS in the current specification, i.e., the number determined by the column in the TDRA table. In this case, N is ensured by up to gNB (an example of network device 120) slot ≤ the number of consecutive SBFD time slots, and N slot >1.

[0126] Alternatively or additionally, in some embodiments, the same number of time slots (N) for TBoMS repetition within consecutive SBFD time slot groups is slot ) and the same position of these time slots is applied across different groups of consecutive SBFD time slots. For example, TBoMS repetitions are always sent across the first and third time slots in a group of 3 consecutive SBFD time slots.

[0127] In some embodiments, the same starting symbol index (S) and length (L) of allocated resources per slot indicated via scheduling DCI is applied across TBoMS-repeated slots and single-slot-repeated slots.

[0128] Alternatively, in some other embodiments, the above-mentioned S and L may be different between the time slots in the TBoMS repetition and the time slots in the single-slot repetition. For example, the S and L of the time slots in the TBoMS repetition are pre-configured in the RRC, and the scheduling DCI only indicates the S and L of the time slots in the single-slot repetition, or vice versa.

[0129] For frequency domain resource determination, in some embodiments, if the first slot of the repetition is an SBFD slot, the number of PRBs used for single slot repetition in the non-SBFD slot is Equal to the number of PRBs used for TBoMS repetition in the SBFD slot scaled by the factor

[0130] In one example, the factor is equal to the number of time slots used for TBoMS repetitions during consecutive SBFD time slots, ie, This results in the same resources across TBoMS repetitions and single-slot repetitions, which helps simplify TBS determination.

[0131] In some other embodiments, if the first time slot of the repetition is a non-SBFD time slot, the number of PRBs used for TBoMS repetition in the SBFD time slot is Equal to the number of PRBs used for single slot repetition scaled by a factor

[0132] In one example, the factor is equal to 1 divided by the number of time slots used for TBoMS repetition during consecutive SBFD time slots, ie

[0133] The terminal device 110 may also determine a transport block size (TBS). For TBS calculation, in some embodiments, Alt. 1: TBS is based on the resources allocated per SBFD time slot multiplied by N slot In some other embodiments, Alt.2: TBS is calculated based on the resources allocated per non-SBFD time slot. Then the above Alt.1 and Alt.2 will get the same TBS.

[0134] Terminal device 110 may determine a redundancy version. For redundancy version determination, in some embodiments, a conventional RV sequence is used. The RV uses the conventional sequence to cycle across all repetitions, including TBoMS repetitions and single-slot repetitions. In some other embodiments, two RV sequences are configured. The RV uses one sequence (e.g., a new sequence different from the conventional RV sequence) to cycle across TBoMS repetitions, and another sequence (e.g., a conventional sequence) to cycle across single-slot repetitions.

[0135] In step 5, the terminal device 110 may send the coded bits of the transport block via a scheduled PUSCH transmission using the determined time and frequency domain resources, transport block size and redundancy version with the new repetition type.

[0136] Specifically, for example, the UE transmits and the NW (network) receives coded bits of the transport block via scheduled PUSCH transmission using the new repetition type using the determined time and frequency domain resources, transport block size and redundancy version.

[0137] In some embodiments, steps 1 and 2 can be interchanged or combined.

[0138] In some embodiments, as a preliminary step, terminal device 110 may report its ability to support the new repetition type to network device 120 .

[0139] In some embodiments, for a dynamic TDD scenario, SBFD time slots may be replaced with flexible time slots of dynamic TDD, and non-SBFD time slots may be replaced with static time slots of dynamic TDD.

[0140] According to an embodiment of the present disclosure, a terminal device 110 (e.g., a UE) receives an indication from a network (NW) (e.g., via RRC and / or DCI) for the UE to determine the time domain resources and frequency domain resources, the transport block size, and the redundancy version for sending a transport block via multiple repetitions of a PUSCH. Depending on whether the repetition is on an SBFD or non-SBFD time slot, at least the time domain resources (and in some embodiments, also the frequency domain resources) across the repetitions are different. On the UE side, the UE determines the time domain resources and frequency domain resources, the transport block size, and the redundancy version for sending a transport block via multiple repetitions of the PUSCH. In this way, the combination of TBoMS and single-slot PUSCH transmission allows for a narrower PUSCH allocation (in terms of the number of PRBs) in the SBFD time slot, which results in more users being multiplexed in the frequency domain (in the UL subband of the SBFD time slot) and overall improving the UL cell coverage. At the same time, having a single-slot PUSCH transmission in a non-SBFD time slot reduces latency and improves UL throughput and resource efficiency compared to the case where TBoMS is applied.

[0141] Figure 5 FIG. 5 is a schematic diagram illustrating a method 500 implemented at a terminal device according to some other embodiments of the present disclosure. Figure 5As shown, at block 510, terminal device 110 may receive scheduling information from network device 120 that schedules uplink transmissions to be sent by terminal device 110 using a repetition type. At block 520, terminal device 110 may determine, based on the repetition type, a first set of resources for a first repetition in a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition in the plurality of repetitions. The first set of resources is located in a first number of time slots having a first time slot type, and the second set of resources is located in a second number of time slots having a second time slot type. At block 530, terminal device 110 may send the plurality of repetitions of the uplink transmission to network device 120.

[0142] In some embodiments, prior to receiving the scheduling information, the terminal device 110 may receive a first indication from the network device 120 that the repetition type is applicable for uplink transmissions.

[0143] In some embodiments, based on receiving the first indication, the terminal device 110 may determine the repetition type as a default repetition type.

[0144] In some embodiments, the scheduling information may include a second indication indicating whether the repetition type is to be used for uplink transmission.

[0145] In some embodiments, based on determining that the second indication is configured to indicate that the repetition type is to be used for uplink transmissions, the terminal device 110 may determine that the uplink transmissions are to be sent using the repetition type.

[0146] In some embodiments, the second indication may include at least one of: a column of a time domain resource allocation (TDRA) table; or a field in downlink control information (DCI).

[0147] In some embodiments, based on determining that the terminal device 110 is configured for operation associated with the first time slot type, the terminal device 110 may determine the repetition type to be a default repetition type.

[0148] In some embodiments, to determine the first set of resources and the second set of resources, the terminal device 110 may determine the first set of resources from a first number of time slots, where the first number is greater than 1; and determine the second set of resources from a second number of time slots, where the second number is equal to 1.

[0149] In some embodiments, the first number can be determined based on one of the following: the number of multiple consecutive time slots having a first time slot type; in the case where the first time slot is located between multiple consecutive time slots, 1 plus the number of remaining consecutive time slots in the multiple consecutive time slots having the first time slot type excluding the first time slot used for multiple repetitions; in the case where the first time slot used for multiple repetitions has a second time slot type, the number of multiple consecutive time slots having the first time slot type; or the number of time slots allocated for multi-slot transport block processing (TBoMS).

[0150] In some embodiments, the first repetition is configured with a first starting symbol index and a first allocated resource length per time slot, and the second repetition is configured with a second starting symbol index and a second allocated resource length per time slot. In this case, the first starting symbol index is the same as the second starting symbol index per time slot. Alternatively or additionally, the first allocated resource length is the same as the second allocated resource length per time slot.

[0151] In some embodiments, the first repetition is configured with a first starting symbol index and a first allocated resource length per time slot, and the second repetition is configured with a second starting symbol index and a second allocated resource length per time slot. In this case, the first starting symbol index is different from the second starting symbol index per time slot. Alternatively or additionally, the first allocated resource length is different from the second allocated resource length per time slot.

[0152] In some embodiments, the first starting symbol index and the first allocated resource length may be indicated via one of a radio resource control (RRC) message or scheduling information; and the second starting symbol index and the second allocated resource length may be indicated via the other of the RRC message or scheduling information.

[0153] In some embodiments, when the multiple repeated first time slots have a first time slot type, the terminal device 110 can determine that the number of physical resource blocks (PRBs) used for the second repetition is equal to the number of PRBs used for the first repetition scaled by a factor; or when the multiple repeated first time slots have a second time slot type, the terminal device 110 can determine that the number of PRBs used for the first repetition is equal to the number of PRBs used for the second repetition scaled by a factor.

[0154] In some embodiments, the factor is equal to the first number of time slots having the first time slot type; or the factor is indicated via an RRC message or scheduling information.

[0155] In some embodiments, when multiple repeated first time slots have a first time slot type, the terminal device 110 can determine that the starting resource block (RB) for the second repetition is equal to: the starting RB for the first repetition plus an offset, or the reference RB in the frequency domain plus an offset; or, when multiple repeated first time slots have a second time slot type, the terminal device 110 can determine that the starting RB for the first repetition is equal to: the starting RB for the second repetition plus an offset, or the reference RB in the frequency domain plus an offset.

[0156] In some embodiments, the offset may be indicated via an RRC message or scheduling information.

[0157] In some embodiments, the reference RB is one of: the starting RB of the bandwidth of the uplink transmission; the starting RB of the subband of the uplink transmission that coexists with at least the subband of the downlink transmission in the time slot; or the value of the starting RB indicated via an RRC message or scheduling information.

[0158] In some embodiments, for the plurality of repetitions, the terminal device 110 may calculate a transport block size (TBS) based on at least one allocated resource per time slot having a first time slot type multiplied by the first number. In some other embodiments, the terminal device 110 may calculate the TBS based on at least one allocated resource per time slot having a second time slot type.

[0159] In some embodiments, the terminal device 110 can determine a first redundant version (RV) sequence that circulates across a first plurality of repetitions associated with a first time slot type in a plurality of repetitions; and can determine a second RV sequence that circulates across a second plurality of repetitions associated with a second time slot type in a plurality of repetitions.

[0160] In some embodiments, the time slots having the first time slot type are sub-band non-overlapping full duplex (SBFD) time slots or flexible time slots; and the time slots having the second time slot type are non-SBFD time slots or static time slots.

[0161] Figure 6 1 is a schematic diagram illustrating a method 600 implemented at a network device 120 according to some other embodiments of the present disclosure. Figure 6 As shown, at block 610, network device 120 may send scheduling information to terminal device 110 that schedules uplink transmissions to be sent by terminal device 110 using a repetition type. At block 620, network device 120 may receive a plurality of repetitions of the uplink transmission including a first repetition and a second repetition from terminal device 110. A first set of resources for the first repetition is located in a first number of slots having a first slot type, and a second set of resources for the second repetition is located in a second number of slots having a second slot type.

[0162] In some embodiments, before sending the scheduling information, the network device 120 may send a first indication to the terminal device 110 that the repetition type is applicable to uplink transmission.

[0163] In some embodiments, the scheduling information comprises a second indication for indicating whether the repetition type is to be used for uplink transmission at the terminal device 110 .

[0164] In some embodiments, the second indication comprises at least one of: a column of a time domain resource allocation (TDRA) table; or a field in downlink control information (DCI).

[0165] In some embodiments, the first number is greater than 1. Additionally or alternatively, the second number is equal to one.

[0166] In some embodiments, the first number is determined based on one of: the number of multiple consecutive time slots having a first time slot type; in the case where the first time slot is located between multiple consecutive time slots, 1 plus the number of remaining consecutive time slots in the multiple consecutive time slots having the first time slot type excluding the first time slot used for multiple repetitions; in the case where the first time slot used for multiple repetitions has a second time slot type, the number of multiple consecutive time slots having the first time slot type; or the number of time slots allocated for multi-slot transport block processing (TBoMS).

[0167] In some embodiments, network device 120 may configure a first starting symbol index and a first allocated resource length per time slot for the first repetition; and configure a second starting symbol index and a second allocated resource length per time slot for the second repetition. In this case, the first starting symbol index is the same as the second starting symbol index per time slot. Alternatively or additionally, the first allocated resource length is the same as the second allocated resource length per time slot.

[0168] In some embodiments, network device 120 may configure a first starting symbol index and a first allocated resource length per time slot for the first repetition, and a second starting symbol index and a second allocated resource length per time slot for the second repetition. In this case, the first starting symbol index differs from the second starting symbol index per time slot. Alternatively or additionally, the first allocated resource length differs from the second allocated resource length per time slot.

[0169] In some embodiments, the network device 120 may indicate the first starting symbol index and the first allocated resource length via one of a radio resource control (RRC) message or scheduling information; and indicate the second starting symbol index and the second allocated resource length via the other of the RRC message or scheduling information.

[0170] In some embodiments, where the first time slot of the plurality of repetitions has a first time slot type, the number of physical resource blocks (PRBs) used for the second repetition is equal to the number of PRBs used for the first repetition scaled by a factor. In some embodiments, where the first time slot of the plurality of repetitions has a second time slot type, the number of PRBs used for the first repetition is equal to the number of PRBs used for the second repetition scaled by a factor.

[0171] In some embodiments, the factor is equal to the first number of time slots having the first time slot type.In some embodiments, the network device 120 indicates the factor via an RRC message or scheduling information.

[0172] In some embodiments, when the first time slots of the plurality of repetitions have a first time slot type, the network device 120 may determine a starting resource block (RB) for the second repetition to be equal to: the starting RB for the first repetition plus an offset, or a reference RB in the frequency domain plus an offset. In some embodiments, when the first time slots of the plurality of repetitions have a second time slot type, the network device 120 may determine a starting RB for the first repetition to be equal to: the starting RB for the second repetition plus an offset, or a reference RB in the frequency domain plus an offset.

[0173] In some embodiments, network device 120 may indicate the offset via an RRC message or scheduling information.

[0174] In some embodiments, the reference RB is one of: the starting RB of the bandwidth of the uplink transmission; the starting RB of the subband of the uplink transmission that coexists with at least the subband of the downlink transmission in the time slot; or the value of the starting RB indicated via an RRC message or scheduling information.

[0175] In some embodiments, a transport block size (TBS) for the plurality of repetitions may be calculated based on at least one allocated resource per time slot having a first time slot type multiplied by a first number. In some embodiments, the TBS may be calculated based on at least one allocated resource per time slot having a second time slot type.

[0176] In some embodiments, a first redundant version (RV) sequence that circulates across a first plurality of repetitions associated with a first time slot type in a plurality of repetitions is a first RV sequence; and a second RV sequence that circulates across a second plurality of repetitions associated with a second time slot type in a plurality of repetitions is a second RV sequence.

[0177] In some embodiments, the time slots having the first time slot type are sub-band non-overlapping full duplex (SBFD) time slots or flexible time slots; and the time slots having the second time slot type are non-SBFD time slots or static time slots.

[0178] In some embodiments, an apparatus capable of performing any of the steps of method 500 (e.g., terminal device 110) may include a component for performing the corresponding steps of method 500. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module.

[0179] In some embodiments, the apparatus includes a component for receiving scheduling information from a network device 120, the scheduling information scheduling an uplink transmission to be sent by a terminal device 110 using a repetition type; a component for determining a first set of resources for a first repetition of a plurality of repetitions for the uplink transmission, and a second set of resources for a second repetition of the plurality of repetitions based on the repetition type, wherein the first set of resources is located in a first number of time slots having a first time slot type and the second set of resources is located in a second number of time slots having a second time slot type; and a component for sending the plurality of repetitions of the uplink transmission to the network device 120.

[0180] In some embodiments, the apparatus further comprises means for receiving a first indication from the network device 120 that the repetition type is applicable for uplink transmissions prior to receiving the scheduling information.

[0181] In some embodiments, the apparatus further comprises means for determining the repetition type as a default repetition type based on receiving the first indication.

[0182] In some embodiments, the scheduling information includes a second indication indicating whether the repetition type is to be used for uplink transmission.

[0183] In some embodiments, the apparatus further comprises means for determining that the uplink transmission is to be sent using the repetition type based on determining that the second indication is configured to indicate that the repetition type is to be used for the uplink transmission.

[0184] In some embodiments, the second indication comprises at least one of: a column of a time domain resource allocation (TDRA) table; or a field in downlink control information (DCI).

[0185] In some embodiments, the apparatus further comprises means for determining the repetition type to be a default repetition type based on determining that the terminal device 110 is configured with an operation associated with the first time slot type.

[0186] In some embodiments, the means for determining the first set of resources and the second set of resources comprises: means for determining the first set of resources from a first number of time slots, wherein the first number is greater than 1; and means for determining the second set of resources from a second number of time slots, wherein the second number is equal to 1.

[0187] In some embodiments, the first number is determined based on one of: the number of multiple consecutive time slots having a first time slot type; in the case where the first time slot is located between multiple consecutive time slots, 1 plus the number of remaining consecutive time slots in the multiple consecutive time slots having the first time slot type excluding the first time slot used for multiple repetitions; in the case where the first time slot used for multiple repetitions has a second time slot type, the number of multiple consecutive time slots having the first time slot type; or the number of time slots allocated for multi-slot transport block processing (TBoMS).

[0188] In some embodiments, the first repetition is configured with a first starting symbol index and a first allocated resource length per time slot; the second repetition is configured with a second starting symbol index and a second allocated resource length per time slot; and at least one of the following: the first starting symbol index is the same as the second starting symbol index per time slot; or the first allocated resource length is the same as the second allocated resource length per time slot.

[0189] In some embodiments, the first repetition is configured with a first starting symbol index and a first allocated resource length per time slot; the second repetition is configured with a second starting symbol index and a second allocated resource length per time slot; and at least one of the following: the first starting symbol index is different from the second starting symbol index per time slot; or the first allocated resource length is different from the second allocated resource length per time slot.

[0190] In some embodiments, the first starting symbol index and the first allocated resource length are indicated via one of a radio resource control (RRC) message or scheduling information; and the second starting symbol index and the second allocated resource length are indicated via the other of the RRC message or scheduling information.

[0191] In some embodiments, the apparatus further comprises means for determining, when the first time slots of the plurality of repetitions have a first time slot type, that the number of physical resource blocks (PRBs) used for the second repetition is equal to the number of PRBs used for the first repetition scaled by a factor, or, when the first time slots of the plurality of repetitions have a second time slot type, determining that the number of PRBs used for the first repetition is equal to the number of PRBs used for the second repetition scaled by a factor.

[0192] In some embodiments, the factor is equal to the first number of time slots having the first time slot type; or the factor is indicated via an RRC message or scheduling information.

[0193] In some embodiments, the device also includes a component for one of the following: in a case where the first time slot of multiple repetitions has a first time slot type, determining that the starting resource block (RB) for the second repetition is equal to: the starting RB for the first repetition plus an offset, or the reference RB in the frequency domain plus an offset; or in a case where the first time slot of multiple repetitions has a second time slot type, determining that the starting RB for the first repetition is equal to: the starting RB for the second repetition plus an offset, or the reference RB in the frequency domain plus an offset.

[0194] In some embodiments, the offset is indicated via an RRC message or scheduling information.

[0195] In some embodiments, the reference RB is one of: the starting RB of the bandwidth of the uplink transmission; the starting RB of the subband of the uplink transmission that coexists with at least the subband of the downlink transmission in the time slot; or the value of the starting RB indicated via an RRC message or scheduling information.

[0196] In some embodiments, the apparatus further comprises one of: a component for calculating a transport block size (TBS) for a plurality of repetitions based on at least one allocated resource per time slot having a first time slot type multiplied by a first number; or a component for calculating the TBS based on at least one allocated resource per time slot having a second time slot type.

[0197] In some embodiments, the apparatus further comprises means for determining a first redundant version (RV) sequence that circulates across a first plurality of repetitions associated with the first time slot type in the plurality of repetitions; and means for determining a second RV sequence that circulates across a second plurality of repetitions associated with the second time slot type in the plurality of repetitions.

[0198] In some embodiments, the time slots having the first time slot type are sub-band non-overlapping full duplex (SBFD) time slots or flexible time slots; and the time slots having the second time slot type are non-SBFD time slots or static time slots.

[0199] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 500. In some embodiments, the means comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause execution of the apparatus.

[0200] In some embodiments, an apparatus capable of performing any of the steps of method 600 (e.g., network device 120) may include components for performing the corresponding steps of method 600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0201] In some embodiments, the apparatus includes: a component for sending scheduling information to the terminal device 110, the scheduling information scheduling an uplink transmission to be sent by the terminal device 110 using a repetition type; and a component for receiving multiple repetitions of the uplink transmission including a first repetition and a second repetition from the terminal device 110, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

[0202] In some embodiments, the apparatus further comprises means for sending a first indication to the terminal device 110 that the repetition type is applicable for uplink transmission prior to sending the scheduling information.

[0203] In some embodiments, the scheduling information comprises a second indication for indicating whether the repetition type is to be used for uplink transmission at the terminal device 110 .

[0204] In some embodiments, the second indication comprises at least one of: a column of a time domain resource allocation (TDRA) table; or a field in downlink control information (DCI).

[0205] In some embodiments, at least one of the following: the first number is greater than 1; or the second number is equal to 1.

[0206] In some embodiments, the first number is determined based on one of: the number of multiple consecutive time slots having a first time slot type; in the case where the first time slot is located between multiple consecutive time slots, 1 plus the number of remaining consecutive time slots in the multiple consecutive time slots having the first time slot type excluding the first time slot used for multiple repetitions; in the case where the first time slot used for multiple repetitions has a second time slot type, the number of multiple consecutive time slots having the first time slot type; or the number of time slots allocated for multi-slot transport block processing (TBoMS).

[0207] In some embodiments, the device also includes a component for configuring a first starting symbol index and a first allocated resource length for the first repetition on a per-time slot basis; a component for configuring a second starting symbol index and a second allocated resource length for the second repetition on a per-time slot basis; and at least one of the following: the first starting symbol index is the same as the second starting symbol index on a per-time slot basis; or the first allocated resource length is the same as the second allocated resource length on a per-time slot basis.

[0208] In some embodiments, the apparatus further comprises a component for configuring a first starting symbol index and a first allocated resource length for the first repetition on a per-time slot basis; a component for configuring a second starting symbol index and a second allocated resource length for the second repetition on a per-time slot basis; and at least one of the following: the first starting symbol index is different from the second starting symbol index on a per-time slot basis; or the first allocated resource length is different from the second allocated resource length on a per-time slot basis.

[0209] In some embodiments, the apparatus further comprises means for indicating a first starting symbol index and a first allocated resource length via one of a radio resource control (RRC) message or scheduling information; and means for indicating a second starting symbol index and a second allocated resource length via the other of the RRC message or scheduling information.

[0210] In some embodiments, at least one of the following: in the case where the first time slot of the multiple repetitions has a first time slot type, the number of physical resource blocks (PRBs) used for the second repetition is equal to the number of PRBs used for the first repetition scaled by a factor; or in the case where the first time slot of the multiple repetitions has a second time slot type, the number of PRBs used for the first repetition is equal to the number of PRBs used for the second repetition scaled by a factor.

[0211] In some embodiments, the factor is equal to a first number of time slots having a first time slot type; or the apparatus further comprises means for indicating the factor via an RRC message or scheduling information.

[0212] In some embodiments, the device also includes a component for one of the following: in a case where the first time slot of multiple repetitions has a first time slot type, determining that the starting resource block (RB) for the second repetition is equal to: the starting RB for the first repetition plus an offset, or the reference RB in the frequency domain plus an offset; or in a case where the first time slot of multiple repetitions has a second time slot type, determining that the starting RB for the first repetition is equal to: the starting RB for the second repetition plus an offset, or the reference RB in the frequency domain plus an offset.

[0213] In some embodiments, the apparatus further comprises means for indicating the offset via an RRC message or scheduling information.

[0214] In some embodiments, the reference RB is one of: the starting RB of the bandwidth of the uplink transmission; the starting RB of the subband of the uplink transmission that coexists with at least the subband of the downlink transmission in the time slot; or the value of the starting RB indicated via an RRC message or scheduling information.

[0215] In some embodiments, at least one of the following is applied: a transport block size (TBS) for multiple repetitions is calculated based on at least one allocated resource per time slot having a first time slot type multiplied by a first number; or the TBS is calculated based on at least one allocated resource per time slot having a second time slot type.

[0216] In some embodiments, a first redundant version (RV) sequence that circulates across a first plurality of repetitions associated with a first time slot type in a plurality of repetitions is a first RV sequence; and a second RV sequence that circulates across a second plurality of repetitions associated with a second time slot type in a plurality of repetitions is a second RV sequence.

[0217] In some embodiments, the time slots having the first time slot type are sub-band non-overlapping full duplex (SBFD) time slots or flexible time slots; and the time slots having the second time slot type are non-SBFD time slots or static time slots.

[0218] In some embodiments, the apparatus further comprises means for performing other steps of some embodiments of method 600. In some embodiments, the apparatus comprises at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause execution of the apparatus.

[0219] Figure 7 is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1A The terminal device 110 or the network device 120 is shown. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0220] The communication module 740 is used for two-way communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements.

[0221] Processor 710 can be of any type suitable for the local technology network and, as non-limiting examples, can include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 can have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock synchronized with a main processor.

[0222] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist during power outages.

[0223] Computer program 730 includes computer executable instructions that are executed by associated processor 710. Program 730 may be stored in ROM 820. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 820.

[0224] The embodiment of the present disclosure can be implemented by means of a program 730, so that the device 700 can execute the reference Figures 2 to 6 The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0225] In some embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (such as in the memory 720) or in other storage devices accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium into the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 in the form of a CD or DVD is shown. The computer readable medium has a program 730 stored thereon.

[0226] In general, various embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0227] 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, which are executed in a device on a target real or virtual processor to perform the above referenced Figure 2-Figure 6 Method 500 or method 600 is described. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. The machine-executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0228] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the function / operation specified in the flow chart and / or block diagram to be realized. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0229] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0230] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media will include electrical connections with one or more wires, portable computer floppy disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disc read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. The term "non-transient" as used herein is a restriction on the medium itself (i.e., tangible, rather than signal), rather than a restriction on data storage persistence (e.g., RAM versus ROM).

[0231] In addition, although operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in sequence or performing all of the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

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

Claims

1. A terminal device, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least: receiving scheduling information from a network device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; determining, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, wherein the first set of resources is located in a first number of slots having a first slot type and the second set of resources is located in a second number of slots having a second slot type; as well as The multiple repetitions of the uplink transmission are sent to the network device.

2. The terminal device according to claim 1, wherein the terminal device is further configured to: Prior to receiving the scheduling information, a first indication is received from the network device that the repetition type is applicable to the uplink transmission.

3. The terminal device according to claim 2, wherein the terminal device is further configured to: Based on receiving the first indication, the repetition type is determined to be a default repetition type.

4. The terminal device according to claim 1 or 2, wherein: The scheduling information includes a second indication for indicating whether the repetition type is to be used for the uplink transmission.

5. The terminal device according to claim 4, wherein the terminal device is further configured to: Based on determining that the second indication is configured to indicate that the repetition type is to be used for the uplink transmission, determining that the uplink transmission is to be sent using the repetition type.

6. The terminal device according to claim 4 or 5, wherein the second indication comprises at least one of the following: a column of a Time Domain Resource Allocation (TDRA) table; or Field in Downlink Control Information (DCI).

7. The terminal device according to claim 1 or 2, wherein the terminal device is further configured to: Based on determining that the terminal device is configured with operations associated with the first time slot type, the repetition type is determined to be a default repetition type.

8. The terminal device according to any one of claims 1 to 7, wherein the terminal device is caused to determine the first set of resources and the second set of resources by: determining the first set of resources from the first number of time slots, wherein the first number is greater than one; and The second set of resources is determined from the second number of time slots, wherein the second number is equal to one.

9. The terminal device according to claim 8, wherein the first number is determined based on one of the following: the number of a plurality of consecutive time slots of the first time slot type; in a case where the first time slot is located between the plurality of consecutive time slots, 1 plus the number of remaining consecutive time slots in the plurality of consecutive time slots of the first time slot type excluding first time slots used for the plurality of repetitions; the number of a plurality of consecutive time slots of the first time slot type if the first time slots used for the plurality of repetitions are of the second time slot type; or The number of timeslots allocated for transport block multislot processing (TBoMS).

10. The terminal device according to any one of claims 1 to 9, wherein: The first repetition is configured with a first starting symbol index and a first allocated resource length per time slot; The second repetition is configured with a second starting symbol index and a second allocated resource length per time slot; and At least one of the following is provided: the first starting symbol index is the same as the second starting symbol index per time slot; or the first allocated resource length is the same as the second allocated resource length per time slot.

11. The terminal device according to any one of claims 1 to 9, wherein: The first repetition is configured with a first starting symbol index and a first allocated resource length per time slot; The second repetition is configured with a second starting symbol index and a second allocated resource length per time slot; and At least one of the following items is provided: the first starting symbol index is different from the second starting symbol index per time slot; or the first allocated resource length is different from the second allocated resource length per time slot.

12. The terminal device according to claim 10 or 11, wherein: The first starting symbol index and the first allocated resource length are indicated via one of a radio resource control (RRC) message or the scheduling information; and The second starting symbol index and the second allocated resource length are indicated via the other of the RRC message or the scheduling information.

13. The terminal device according to any one of claims 1 to 12, wherein the terminal device is further configured to: In a case where the first time slots of the plurality of repetitions have the first time slot type, determining the number of physical resource blocks (PRBs) used for the second repetition to be equal to the number of the PRBs used for the first repetition scaled by a factor; or In a case where a first time slot of the plurality of repetitions has the second time slot type, the number of the PRBs used for the first repetition is determined to be equal to the number of the PRBs used for the second repetition scaled by a factor.

14. The terminal device according to claim 13, wherein: the factor being equal to the first number of time slots having the first time slot type; or The factor is indicated via an RRC message or the scheduling information.

15. The terminal device according to any one of claims 1 to 14, wherein the terminal device is further configured to do at least one of the following: In a case where the first time slots of the plurality of repetitions have the first time slot type, determining a starting resource block (RB) for the second repetition to be equal to: a starting RB for the first repetition plus an offset, or a reference RB in the frequency domain plus the offset; or In a case where the first time slots of the plurality of repetitions have the second time slot type, the starting RB for the first repetition is determined to be equal to: the starting RB for the second repetition plus the offset, or the reference RB in the frequency domain plus the offset.

16. The terminal device according to claim 15, wherein the offset is indicated via an RRC message or the scheduling information.

17. The terminal device according to claim 15 or 16, wherein the reference RB is one of the following: A starting RB of the bandwidth of the uplink transmission; a starting RB of a subband for uplink transmission that coexists with at least a subband for downlink transmission in a timeslot; or The value of the starting RB indicated by the RRC message or the scheduling information.

18. The terminal device according to any one of claims 1 to 17, wherein the terminal device is further configured to do at least one of the following: for the plurality of repetitions, calculating a transport block size (TBS) based on at least one allocated resource per time slot of the first time slot type multiplied by the first number; or The TBS is calculated based on at least one allocated resource per time slot having the second time slot type.

19. The terminal device according to any one of claims 1 to 18, wherein the terminal device is further configured to: determining a first redundancy version (RV) sequence that circulates across a first plurality of repetitions of the plurality of repetitions associated with the first slot type; and A second RV sequence is determined that cycles across a second plurality of repetitions of the plurality of repetitions associated with the second slot type.

20. The terminal device according to any one of claims 1 to 19, wherein: The time slot of the first time slot type is a sub-band full duplex (SBFD) time slot or a flexible time slot; and The timeslot having the second timeslot type is a non-SBFD timeslot or a static timeslot.

21. A network device comprising: at least one processor; as well as at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: sending scheduling information to the terminal device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; and Multiple repetitions of the uplink transmission are received from the terminal device, including a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

22. The network device of claim 21 , wherein the network device is further configured to: Prior to sending the scheduling information, a first indication is sent to the terminal device that the repetition type is applicable to the uplink transmission.

23. The network device according to claim 21 or 22, wherein: The scheduling information comprises a second indication for indicating whether the repetition type is to be used for the uplink transmission at the terminal device.

24. The network device according to claim 23, wherein the second indication comprises at least one of the following: a column of a Time Domain Resource Allocation (TDRA) table; or Field in Downlink Control Information (DCI).

25. The network device according to any one of claims 21 to 24, wherein at least one of the following: The first number is greater than 1; or The second number is equal to 1.

26. The network device of claim 25, wherein the first number is determined based on one of: the number of a plurality of consecutive time slots of the first time slot type; in a case where the first time slot is located between the plurality of consecutive time slots, 1 plus the number of remaining consecutive time slots in the plurality of consecutive time slots of the first time slot type excluding first time slots used for the plurality of repetitions; the number of a plurality of consecutive time slots of the first time slot type if the first time slots used for the plurality of repetitions are of the second time slot type; or The number of timeslots allocated for transport block multislot processing (TBoMS).

27. The network device according to any one of claims 21 to 26, wherein: configuring a first starting symbol index and a first allocated resource length for each time slot for the first repetition; configuring a second starting symbol index and a second allocated resource length for the second repetition per time slot; and At least one of the following is provided: the first starting symbol index is the same as the second starting symbol index per time slot; or the first allocated resource length is the same as the second allocated resource length per time slot.

28. The network device according to any one of claims 21 to 26, wherein the network device is further configured to: configuring a first starting symbol index and a first allocated resource length for each time slot for the first repetition; configuring a second starting symbol index and a second allocated resource length for the second repetition per time slot; and At least one of the following items is provided: the first starting symbol index is different from the second starting symbol index per time slot; or the first allocated resource length is different from the second allocated resource length per time slot.

29. The network device according to claim 27 or 28, wherein: The network device is caused to indicate the first starting symbol index and the first allocated resource length via one of a radio resource control (RRC) message or the scheduling information; and The network device is caused to indicate the second starting symbol index and the second allocated resource length via the other of the RRC message or the scheduling information.

30. The network device according to any one of claims 21 to 29, wherein at least one of the following: Where the plurality of repeated first time slots have the first time slot type, the number of physical resource blocks (PRBs) used for the second repetition is equal to the number of PRBs used for the first repetition scaled by a factor; or In case that the first time slots of the plurality of repetitions have the second time slot type, the number of PRBs used for the first repetition is equal to the number of PRBs used for the second repetition scaled by a factor.

31. The network device according to claim 30, wherein: the factor being equal to the first number of time slots having the first time slot type; or The network device indicates the factor via an RRC message or the scheduling information.

32. The network device according to claims 21 to 31, wherein at least one of the following is applied: In a case where the first time slots of the plurality of repetitions have the first time slot type, determining a starting resource block (RB) for the second repetition to be equal to: a starting RB for the first repetition plus an offset, or a reference RB in the frequency domain plus the offset; or In a case where the first time slots of the plurality of repetitions have the second time slot type, the starting RB for the first repetition is determined to be equal to: the starting RB for the second repetition plus the offset, or the reference RB in the frequency domain plus the offset.

33. The network device of claim 32, wherein the network device is further caused to: The offset is indicated via an RRC message or the scheduling information.

34. The network device according to claim 32 or 33, wherein the reference RB is one of the following: A starting RB of the bandwidth of the uplink transmission; a starting RB of a subband for uplink transmission that coexists with at least a subband for downlink transmission in a timeslot; or The value of the starting RB indicated by the RRC message or the scheduling information.

35. The network device according to any one of claims 21 to 34, wherein at least one of the following is applied: A transport block size (TBS) for the plurality of repetitions is calculated based on at least one allocated resource per timeslot of the first timeslot type multiplied by the first number; or The TBS is calculated based on at least one allocated resource per time slot having the second time slot type.

36. The network device according to any one of claims 21 to 35, wherein: a first redundancy version (RV) sequence that circulates across a first plurality of repetitions associated with the first slot type in the plurality of repetitions being a first RV sequence; as well as A second RV sequence that cycles across a second plurality of repetitions associated with the second slot type in the plurality of repetitions is a second RV sequence.

37. The network device according to any one of claims 21 to 36, wherein: The time slot of the first time slot type is a sub-band full duplex (SBFD) time slot or a flexible time slot; and The timeslot having the second timeslot type is a non-SBFD timeslot or a static timeslot.

38. A method comprising: receiving, at a terminal device, scheduling information from a network device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; determining, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, wherein the first set of resources is located in a first number of slots having a first slot type and the second set of resources is located in a second number of slots having a second slot type; as well as The multiple repetitions of the uplink transmission are sent to the network device.

39. A method comprising: sending, at a network device, scheduling information to a terminal device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; as well as Multiple repetitions of the uplink transmission are received from the terminal device, including a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type, and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

40. An apparatus comprising: means for receiving, at a terminal device, scheduling information from a network device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; means for determining, based on the repetition type, a first set of resources for a first repetition of a plurality of repetitions of the uplink transmission and a second set of resources for a second repetition of the plurality of repetitions, wherein the first set of resources is located in a first number of slots having a first slot type and the second set of resources is located in a second number of slots having a second slot type; as well as Means for sending the plurality of repetitions of the uplink transmission to the network device.

41. An apparatus comprising: means for sending, at a network device, scheduling information to a terminal device, the scheduling information scheduling uplink transmissions to be sent by the terminal device using a repetition type; as well as means for receiving from the terminal device a plurality of repetitions of the uplink transmission comprising a first repetition and a second repetition, wherein a first set of resources for the first repetition is located in a first number of time slots having a first time slot type and a second set of resources for the second repetition is located in a second number of time slots having a second time slot type.

42. A non-transitory computer-readable medium comprising program instructions, which, when executed by an apparatus, cause the apparatus to at least perform the method according to any one of claims 38 to 39.

Images