Repeated uplink transmissions

Abstract

An embodiment of the present disclosure relates to a method for repeating uplink transmissions, wherein a terminal device receives, from a network device, schedule information for scheduling uplink transmissions to be transmitted by the terminal device using a repetition type, and determines, based on the repetition type, a first resource set for a first repetition in multiple repetitions of the uplink transmissions and a second resource set for a second repetition in the multiple repetitions, wherein the first resource set is arranged in a first number of slots having a first slot type and the second resource set is arranged in a second number of slots having a second slot type, and transmits the multiple repetitions to the network device. This solution enables improved coverage of the uplink transmissions.

Description

[Technical Field]

[0001] Various embodiments relate to the field of telecommunications, and more particularly to methods, apparatus, devices, and computer-readable storage media relating to repetition of uplink transmissions. [Background technology]

[0002] The communications field is constantly evolving to provide solutions for efficient and reliable use of wireless communication networks. To meet the increased demand for wireless data traffic since the introduction of the fourth-generation (4G) communications system, improved fifth-generation (5G) or pre-5G communications systems have been developed. The new communications systems can support a variety of service applications for terminal devices.

[0003] 3GPP Rel-15 introduced the slot aggregation feature (also known as PUSCH repetition type A) for the Physical Uplink Shared Channel (PUSCH). Rel-16 allowed for dynamic signaling of the repetition count for PUSCH repetition type A by associating a repetition count with each row in the Time Domain Resource Allocation (TDRA) table. Rel-17 further improved PUSCH repetition type A by allowing the repetition count to be counted over available slots. Additionally, the Rel-17 Coverage Enhancement WI specifies a feature called Transmission Block Processing over Multiple Slots (TBoMS), which allows a single transmission block (TB) to be mapped across multiple slots. Summary of the Invention

[0004] Generally, embodiments of the present disclosure provide a solution to repetitive uplink transmissions.

[0005] In a first aspect, a terminal device is provided, comprising: at least one processor; and at least one memory having stored thereon instructions that, when executed by the at least one processor, cause the terminal device to at least: receive, from a network device, schedule information that schedules uplink transmissions to be transmitted by the terminal device using a recurrence type; determine, based on the recurrence type, a first resource set corresponding to a first recurrence in a plurality of recurrences of the uplink transmission and a second resource set corresponding to a second recurrence in the plurality of recurrences, where the first resource set is disposed in a first number of slots having the first slot type and the second resource set is disposed in a second number of slots having the second slot type; and transmit the plurality of recurrences of the uplink transmission to the network device.

[0006] In a second aspect, a network device is provided, the network device comprising: at least one processor; and at least one memory having stored thereon instructions that, when executed by the at least one processor, cause the network device to at least: transmit, to a terminal device, schedule information that schedules uplink transmissions transmitted by the terminal device using a repetition type; and receive, from the terminal device, multiple repetitions of the uplink transmission, including a first repetition and a second repetition, wherein a first resource set for the first repetition is disposed in a first number of slots having a first slot type and a second resource set for the second repetition is disposed in a second number of slots having a second slot type.

[0007] In a third aspect, a method is provided, including: receiving, in a terminal device, from a network device, schedule information that schedules uplink transmissions to be transmitted by the terminal device using a recurrence type; determining, based on the recurrence type, a first resource set for a first recurrence in a plurality of recurrences of the uplink transmission and a second resource set for a second recurrence in the plurality of recurrences, where the first resource set is disposed in a first number of slots having the first slot type and the second resource set is disposed in a second number of slots having the second slot type; and transmitting the plurality of recurrences of the uplink transmission to the network device.

[0008] In a fourth aspect, a method is provided, including: transmitting, in a network device, to a terminal device, schedule information that schedules uplink transmissions to be transmitted by the terminal device using a repetition type; and receiving, from the terminal device, multiple repetitions of the uplink transmission, including a first repetition and a second repetition, where a first resource set of the first repetition is arranged in a first number of slots having a first slot type and a second resource set of the second repetition is arranged in a second number of slots having a second slot type.

[0009] In a fifth aspect, an apparatus is provided, comprising: means, in a terminal device, for receiving, from a network device, schedule information that schedules uplink transmissions to be transmitted by the terminal device using a recurrence type; means for determining, based on the recurrence type, a first resource set for a first recurrence in multiple recurrences of the uplink transmission and a second resource set for a second recurrence in the multiple recurrences, where the first resource set is arranged in a first number of slots having the first slot type and the second resource set is arranged in a second number of slots having the second slot type; and means for transmitting the multiple recurrences of the uplink transmission to the network device.

[0010] In a sixth aspect, an apparatus is provided, comprising: means for transmitting, in a network device, to a terminal device, schedule information that schedules uplink transmissions transmitted by the terminal device using a repetition type; and means for receiving, from the terminal device, multiple repetitions of the uplink transmission, including a first repetition and a second repetition, where a first resource set of the first repetition is arranged in a first number of slots having a first slot type and a second resource set of the second repetition is arranged in a second number of slots having a second slot type.

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

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

[0013] In a ninth aspect, a computer program is provided that, when executed by an apparatus, causes the apparatus to at least: receive, from a network apparatus, schedule information for scheduling an uplink transmission to be transmitted by a terminal device using a repetition type; determine, based on the repetition type, a first resource set for a first repetition in a plurality of repetitions of the uplink transmission and a second resource set for a second repetition in the plurality of repetitions, wherein the first resource set is arranged in a first number of slots having the first slot type and the second resource set is arranged in a second number of slots having the second slot type; and transmit the plurality of repetitions of the uplink transmission.

[0014] In a tenth aspect, a computer program is provided that includes instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: transmitting, to a terminal device, schedule information that schedules uplink transmissions to be transmitted by the terminal device using a repetition type; and receiving, from the terminal device, multiple repetitions of the uplink transmissions, including a first repetition and a second repetition, wherein a first resource set of the first repetition is arranged in a first number of slots having a first slot type, and a second resource set of the second repetition is arranged in a second number of slots having a second slot type.

[0015] In an eleventh aspect, a terminal device is provided, the terminal device comprising: a receiving circuit configured to receive, from a network device, schedule information scheduling an uplink transmission to be transmitted by the terminal device using a repetition type, a determining circuit configured to determine, based on the repetition type, a first resource set for a first repetition in multiple repetitions of the uplink transmission and a second resource set for a second repetition in the multiple repetitions, where the first resource set is arranged in a first number of slots having a first slot type and the second resource set is arranged in a second number of slots having a second slot type, and a transmitting circuit configured to transmit the multiple repetitions of the uplink transmission to the network device.

[0016] In a twelfth aspect, a network device is provided, comprising: a transmitting circuit configured to transmit, to a terminal device, schedule information scheduling uplink transmissions transmitted by the terminal device using a repetition type; and a receiving circuit configured to receive, from the terminal device, multiple repetitions of the uplink transmission, including a first repetition and a second repetition, wherein a first resource set of the first repetition is arranged in a first number of slots having a first slot type and a second resource set of the second repetition is arranged in a second number of slots having a second slot type.

[0017] It should be noted that the summary does not identify important or essential features of the embodiments of the present specification, nor is it intended to be used to limit the scope of the present specification. Other features of the present specification will be readily apparent from the following description. [Brief explanation of the drawings]

[0018] Some embodiments will now be described with reference to the accompanying drawings. [Figure 1A] FIG. 1A illustrates an example of a communication system in which embodiments of the present disclosure may be implemented. [Figure 1B] FIG. 1B is a schematic diagram showing SBFD and non-SBFD slots. [Figure 1C] Figure 1C is a schematic diagram showing frequency-time resource division with SBFD compared to FDD and TDD. [Figure 1D] FIG. 1D is a schematic diagram illustrating types of co-channel interference in an SBFD deployment. [Figure 1E] FIG. 1E is a schematic diagram illustrating types of co-channel interference in an SBFD deployment. [Figure 1F] FIG. 1F is a schematic diagram illustrating the power spectral density gain with TBoMS compared to single-slot PUSCH in the same TBS. [Figure 2] FIG. 2 is a schematic diagram illustrating a communication process between a terminal device and a network device according to some embodiments of the present disclosure. [Figure 3] FIG. 3 is a schematic diagram illustrating the iteration types for SBFD operation according to the present disclosure. [Figure 4] FIG. 4 is a schematic diagram illustrating a communication process between a terminal device and a network device according to another embodiment of the present disclosure. [Figure 5] FIG. 5 is a schematic diagram illustrating a method implemented in a terminal device according to some other embodiments of the present disclosure. [Figure 6] FIG. 6 is a schematic diagram illustrating a method implemented in a network device according to another embodiment of the present disclosure. [Figure 7] FIG. 7 shows a simplified block diagram of an apparatus suitable for practicing embodiments of the present disclosure. [Figure 8] 8 is a block diagram illustrating an example of a computer-readable medium according to some embodiments of the present disclosure. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0019] The principles of the present specification will be explained with reference to some examples. It should be understood that these examples are not intended to limit the scope of the present specification, but are merely provided for illustrative purposes and to assist those skilled in the art in understanding and practicing the present specification. The disclosure described herein can be implemented in various ways other than those described below.

[0020] Unless otherwise defined, in the following description and claims, 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 specification belongs.

[0021] References herein to "one embodiment," "embodiment," "exemplary embodiment," and the like indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need to include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one skilled in the art to affect that feature, structure, or characteristic in connection with other embodiments, whether or not explicitly stated.

[0022] Although terms such as "first" and "second" may be used to describe various elements, these elements are not limited by these terms. These terms are merely used to distinguish between elements. For example, calling a first element a second element, and similarly calling a second element a first element, would not depart from the scope of the embodiments. As used herein, the term "and / or" encompasses any combination of one or more of the listed terms.

[0023] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural unless the context clearly dictates otherwise. Furthermore, the terms "comprises," "comprising," "has," "having," "includes," and / or "comprising" as used herein identify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, "at least one of: " and "at least any of: " and similar expressions, when a list of two or more elements is joined by "and," mean at least any element, at least two or more elements, or at least all elements.

[0024] In this application, the term "circuit" means (a) hardware-only circuit implementation (e.g., implementation using only analog and / or digital circuitry); (b) A combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) A configuration in which a portion of a hardware processor and software (including a digital signal processor), software, and memory work together to cause a device such as a mobile phone or server to perform various functions; (c) hardware circuitry and / or processors (e.g., microprocessors or portions of microprocessors) that require software (e.g., firmware) to operate, but the software may be absent if not necessary for operation; It may refer to any one or more, or all of the above.

[0025] This definition of circuit applies to all uses of the term in this application, i.e., in all claims. By way of further example, the term circuit as used herein encompasses a simple hardware circuit or processor (or processors), or a portion of a hardware circuit or processor and its associated software and / or firmware implementation. The term circuit also encompasses, for example, baseband or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular networks, and other computing systems, where applicable to particular claim elements.

[0026] As used herein, the term "communication network" refers to a network conforming to an appropriate communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), or Narrowband Internet of Things (NB-IoT). Furthermore, communications between terminal devices and network devices in a communication network may be performed using, but are 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 other protocols currently known or developed in the future. Embodiments of the present disclosure are applicable to various communication systems. Given the rapid development of communication technologies, future communication technologies and systems may also exist in which the present disclosure may be embodied. The scope of the present disclosure should not be construed as being limited to only the aforementioned systems.

[0027] In this specification, the term "network device" refers to a node in a communication network through which a terminal device accesses the network and receives services from it. A network device may refer to, for example, a base station (BS) or an access point (AP). Examples of network devices include a Node B (Node B or NB), an evolved Node B (eNode B or eNB), an NR Node B (also known as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a repeater, and a low-power node such as a femto or pico node.

[0028] The term "terminal equipment" refers to any terminal device capable of wireless communication. By way of example only, terminal equipment may also be referred to as communications equipment, user equipment (UE), subscriber station (SS), mobile subscriber station, mobile station (MS), or access terminal (AT). Terminal equipment may include mobile phones, smartphones, VoIP phones, wireless local loop phones, tablets, wearable devices, PDAs, portable computers, desktop computers, digital cameras and other imaging devices, gaming consoles, music storage and playback devices, automotive wireless terminals, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches and 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 industrial and / or automated processing chain environments), consumer electronics devices, and devices operating on commercial and / or industrial wireless networks. In the following description, the terms "terminal equipment", "communications device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0029] 3GPP Rel-15 introduced a slot aggregation feature (also called PUSCH repetition type A) for the Physical Uplink Shared Channel (PUSCH), which repeats the transmission of a transport block over multiple slots. The key design elements of PUSCH repetition type A in Rel-15 are as follows:

[0030] For resource allocation, the same resource allocation is applied across repetitions of the PUSCH. In the time domain, each repetition is placed within 1 slot. Within a slot, the single start and length of the PUSCH are indicated by a single Start-Length Indicator (SLIV). The same start and length indicated by this single SLIV are applied across all repetitions of the PUSCH. In Rel-15, the number of repetitions of PUSCH repetition type A is semi-statically set by RRC (Radio Resource Control), and the number of repetitions is counted on consecutive physical slots. If the number of available symbols within a slot is insufficient (<L), no PUSCH repetition is transmitted in that slot. In the frequency domain, PUSCH repetitions have the same resource allocation in the frequency domain (i.e., the same number of Physical Resource Blocks (PRBs) and the same positions of these PRBs in the frequency domain).

[0031] For the determination of the Transport Block Size (TBS), the unquantized intermediate variable (NInfo) for TBS calculation of PUSCH repetition type A is calculated based on the number of REs determined within a slot.

[0032] For rate matching, the same or different redundancy versions (RVs) can be applied to the coded bits in the cyclic buffer for each PUSCH repetition. The RV for the first repetition is indicated by the scheduling DCI (Downlink Control Information) in the case of a dynamic grant, and is pre-set in the case of a configured grant. When applying different RVs, the RVs are cycled from the configured RV sequence following the RV indicated for the first repetition. Four RVs exist, and information regarding the starting coded bits from the cyclic buffer that the UE associates with PUSCH transmission is provided for each of them.

[0033] Rel-16 allows for dynamic specification of the repetition number for PUSCH repetition type A by associating a repetition number with each row in the time-domain resource allocation (TDRA) table. Furthermore, Rel-16 also introduces PUSCH repetition type B for ultra-reliable low-latency communications (URLLC) applications. This feature uses a single SLIV to determine multiple consecutive nominal repetitions of the same length (back-to-back nominal repetitions), where each nominal repetition may cross a slot boundary. Each nominal repetition is then split into multiple actual repetitions if it crosses a slot boundary or an invalid symbol. PUSCH repetitions in PUSCH repetition type B also have a similar frequency-domain resource allocation.

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

[0035] The Rel-17 Coverage Enhancement WI defines a feature called Transport Block Processing over Multiple Slots (TBoMS), which allows a single Transport Block (TB) to be mapped to multiple slots, i.e., the resource allocation for a single PUSCH transmission can span multiple slots. This is different from PUSCH repetition.

[0036] The main design elements of TBoMS can be summarized as follows:

[0037] Regarding resource allocation, in the time domain, a new column is added to the TDRA table to indicate the number of slots allocated to TBoMS (N slot ) indicates N slotare counted in available slots (following the Rel-17 rules for available slot counting in PUSCH recurrence type A). Therefore, in TDD (Time Division Duplex), non-consecutive slots can be used for TBoMS. The resources in each slot allocated for TBoMS have the same start symbol (S) and length (L) as in recurrence type A. In the frequency domain, the same number of PRBs are allocated across slots for TBoMS transmission (similar to recurrence type A).

[0038] Regarding the TBS decision, TBoMS's NInfo slot is calculated based on the number of REs determined in the first slot allocated for TBoMS scaled by N slot is the number of slots allocated for TBoMS. That is, the TBS for TBoMS is calculated based on the total resources allocated to TBoMS across multiple slots.

[0039] For rate matching, only a single redundancy version is used for a single TBoMS (i.e., no cycling of RVs within a single TBoMS). Bit selection from the circular buffer and bit interleaving are performed on a slot-by-slot basis. For bit selection within a slot, the index of the starting coded bit in the circular buffer is a consecutive index from the position of the last bit selected in the previously allocated slot. This applies regardless of whether UCI (Uplink Control Information) multiplexing occurred in the previously allocated slot. TBoMS transmission is limited to only one code block.

[0040] For single TBoMS repetitions, single TBoMS repetitions are supported. The column (numberOfRepetitions-r17) in the TDRA table indicating the number of repetitions for PUSCH repetition type A in Rel-17 is rep ) is also used to indicate the number of repetitions of the rep *N slotDetermine the slots for repeating TBoMS. Each slot uses the same S and L, but TBS is calculated with the resources of a single TBoMS (i.e., N slot (scaled by ). The redundancy version (RV) rotates between TBoMS iterations. The legacy Rel-15 / 16 RV sequence and RV index signaling are reused.

[0041] Evolution of duplexing methods in Rel-18 study items, including subband non-overlapping full duplexing (SBFD). 3GPP® 5G NR currently supports two duplexing modes: FDD (Frequency Division Duplex) for paired bands and TDD for unpaired bands. In TDD, time domain resources are divided into downlink and uplink. The limited time slot allocated to the uplink in TDD results in poor coverage, increased latency, and reduced capacity.

[0042] In light of this challenge, 3GPP has agreed to initiate a Rel-18 study item (RP-213591) on the evolution of NR duplexing to address the above challenges. One of the goals of this study item is to enable simultaneous DL (downlink) and UL (uplink) transmissions on different physical resource blocks (PRBs) / subbands within asymmetric wideband NR cells. This is sometimes referred to as subband non-overlapping full duplex (SBFD). In other literature, this duplexing scheme is also referred to as cross-division duplexing (xDD) (see, for example, this) or flexible division duplexing (FDU).

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

[0044] [Table 1]

[0045] From the above description of SBFD operation, there are two slot types for DL ​​and UL transmission: SBFD slots and non-SBFD slots. Several SBFD operation modes have been considered, including whether the time-frequency location of the subband for SBFD operation is known to the SBFD-capable UE. However, the 3GPP® RAN1#110 meeting agreed to prioritize an operation mode in which at least the SBFD-capable UE knows the time-frequency location of the subband for SBFD operation. This means that the SBFD slots are somehow known to the (SBFD-capable) UE.

[0046] Regarding crosslink interference (CLI) in SBFD slots, RAN1#110 meeting introduced a new CLI type, i.e., same-channel inter-subband CLI, which can be classified as follows: 1) gNB self-interference, 2) same-channel inter-subband CLI between UEs in the same cell, 3) same-channel inter-subband CLI between UEs in different cells, and 4) same-channel inter-subband CLI between gNBs.

[0047] In addition to these new CLI types, when adjacent cells have different divisions of the frequency domain, the system may also be affected by co-channel interference (CLI), namely 5) inter-gNB co-channel interference and 6) inter-UE co-channel interference CLI due to transmissions on overlapping frequency resources.

[0048] In dynamic TDD, flexible slots and static slots correspond to SBFD slots and non-SBFD slots, respectively. However, in dynamic TDD, subband division is not performed, and gNBs can freely schedule DL or UL transmissions on flexible slots. Therefore, CLI in dynamic TDD is inter-gNB co-channel interference and inter-UE co-channel interference.

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

[0050] [Table 2]

[0051] From the above discussion of CLI types, we can see that UL transmissions (especially PUSCH) in SBFD slots are affected by at least gNB self-interference (1), inter-gNB same-channel inter-subband CLI (4), and inter-gNB same-channel inter-cell CLI (5). This has a significant impact on the coverage of UL transmissions in SBFD slots. UL transmissions in non-SBFD slots are not affected by these interferences, at least when the frame structure is aligned between cells. Therefore, measures to improve the coverage of PUSCH transmissions in SBFD slots compared to non-SBFD slots are needed, especially when the UE is in an under-coverage state.

[0052] Repeated use of TBoMS can contribute to improving the coverage rate of PUSCH transmission. However, there are several limitations when applying the current TBoMS repetition method to SBFD operation. Specifically, these limitations are as follows:

[0053] TBoMS repetitions do not allow for changes in the number of PRBs or frequency allocation between repetitions. Therefore, it is not possible to increase the number of PRBs by repetitions on SBFD slots, taking advantage of the fact that non-SBFD slots have wider bandwidth and better coverage (lower CLI) than SBFD slots. This is a significant issue in SBFD operation, where the UL subband bandwidth in SBFD slots is limited and shared by many SBFD-capable UEs within a cell. Furthermore, coexistence with other cells can lead to scenarios where co-channel CLI occurs within a subband. In this case, some DL transmissions from other cells may occur within the UL subband of the current cell using SBFD. In this case, assuming that scheduling information is exchanged between gNBs, the current gNB can avoid interference by allocating UL transmissions that do not overlap with DL transmissions from other cells. As a result, the number of PRBs available for UL transmissions in SBFD slots may be reduced compared to non-SBFD slots.

[0054] The TBoMS iteration always considers the same number of slots in each iteration, so the fact that non-SBFD slots have a lower CLI compared to SBFD slots cannot be used to minimize the number of slots for TBoMS (and improve the delay) on non-SBFD slots.

[0055] Several technical solutions have focused on resource determination for the TBoMS feature in Rel-17. In particular, the issue of how to determine available slots for TBoMS when TBoMS is scheduled across SBFD and non-SBFD slots has been raised. The problems discussed in these technical solutions are aimed at making TBoMS work in SBFD operation. No solution has been found that defines a new recurrence type to be used for SBFD operation.

[0056] Therefore, a new PUSCH recurrence type is needed for use in SBFD operation that takes into account the benefits of TBoMS in addressing the lack of coverage due to CLI in SBFD slots, while also leveraging the characteristics of SBFD operation, such as bandwidth and CLI differences between SBFD and non-SBFD slots. As noted above, it does not address the lack of coverage due to CLI in slots of the first slot type (e.g., SBFD), nor does it leverage the operational characteristics associated with the first slot type in terms of bandwidth and CLI differences between slots of different types (e.g., SBFD and non-SBFD slots).

[0057] In view of the above, an embodiment of the present disclosure provides a solution to the repetition of uplink transmissions. This solution enables an enhancement to improve the coverage of uplink transmissions. The principles and embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. First, reference is made to FIG. 1A, which shows an example of a communication system 100 in which an embodiment of the present disclosure can be implemented. The 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 to and communicate with the network device 120 via an uplink or downlink. In the communication system, the uplink refers to a link from the terminal device 110 to the network device 120, and the downlink refers to a link from the network device 120 to the terminal device 110. The network device 120 can transmit schedule information to the terminal device 110 to schedule uplink transmissions, and the terminal device 110 can transmit multiple repetitions of uplink transmissions to the network device 120.

[0058] It should be noted that the number of network devices 120 and terminal devices 110 is for illustrative purposes only and is not intended to imply any limitation. System 100 may include any suitable number of network devices 120 and terminal devices 110 adapted to implement embodiments herein.

[0059] Communications in the communication system 100 may be conducted according to any suitable communication protocol, including, but not limited to, cellular communication protocols such as first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G), wireless local network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or other protocols now known or 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 other technologies now known or developed in the future.

[0060] Based on the above, some contents will be further explained below with reference to the accompanying drawings. Figure 1B is a schematic diagram showing SBFD slots and non-SBFD slots. In SBFD slots, both non-overlapping DL subbands and UL subbands exist. Meanwhile, in non-SBFD slots, the entire band is used for DL ​​or UL (i.e., conventional / full DL / UL slots). Figure 1C is a schematic diagram showing frequency-time resource division with SBFD compared with FDD and TDD.

[0061] Figures 1D and 1E are schematic diagrams illustrating types of co-channel interference in SBFD deployments. Based on the above, Figure 1D shows gNB self-interference (1), intra-cell inter-UE inter-subband co-channel CLI (2), inter-cell inter-UE inter-subband co-channel CLI (3), and inter-gNB inter-subband co-channel CLI (4). Inter-gNB inter-cell inter-subband co-channel CLI (5) and inter-UE inter-cell inter-subband co-channel CLI (6) are shown in Figure 1E.

[0062] Figure 1F is a schematic diagram illustrating the power spectral density gain that TBoMS provides compared to single-slot PUSCH for the same TBS. Referring to Figure 1F, one of the main advantages of TBoMS is that it reduces the number of PRBs required to transmit the same TBS compared to transmitting the TBS in a single slot. This increases the energy per resource element (EPRE), thus improving coverage.

[0063] FIG. 2 is a schematic diagram illustrating a communication process 200 between a terminal device 110 and a network device 120, in accordance with some embodiments of the present disclosure. As shown in FIG. 2, the network device 120 transmits (210) to the terminal device 110 schedule information 205 that schedules uplink transmissions that the terminal device 110 will transmit using a repetition type. At the terminal device 110 side, the terminal device 110 receives (220) the schedule information 205 from the network device 120. The terminal device 110 determines (230) a first resource set for a first repetition in the plurality of repetitions 215 of the uplink transmission and a second resource set for a second repetition in the plurality of repetitions based on the repetition type. The first resource set is arranged in a first number of slots having a first slot type, and the second resource set is arranged in a second number of slots having a second slot type. The terminal device 110 transmits (240) the plurality of repetitions 215 of the uplink transmission to the network device 120. On the network device 120 side, the network device 120 receives 250 multiple repetitions 215 from the end device 110 .

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

[0065] In some embodiments, on the network device 120 side, before transmitting the schedule information, the network device 120 may send a first notification to the terminal device 110 informing that a recurrence type is applicable to the uplink transmission. On the terminal device 110 side, before receiving the schedule information, the terminal device 110 receives the first notification from the network device 120.

[0066] In some embodiments, based on receiving the first notification, terminal device 110 determines the recurrence type as a default recurrence type, e.g., the recurrence type is supported by default as soon as UE (an example of terminal device 110) receives the first notification.

[0067] In some embodiments, the schedule information may include a second indication to indicate whether a recurrence type is to be used (at terminal device 110) for the uplink transmission.

[0068] In some embodiments, based on determining that the second notification is configured to notify the use of a repetition type for the uplink transmission, the terminal device 110 determines to transmit the uplink transmission using a repetition type.

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

[0070] In some embodiments, based on determining that terminal device 110 is configured with operation associated with the first slot type, terminal device 110 determines the repetition type as the default repetition type, e.g., if the UE is configured with SBFD operation, the repetition type is supported by default.

[0071] In some embodiments, to determine the first resource set and the second resource set, terminal device 110 determines the first resource set from a first number of slots, the first number being greater than 1, and determines the second resource set from a second number of slots, the second number being equal to 1. In some embodiments, the first number is equal to N slot It is expressed as:

[0072] In some embodiments, the first number is determined based on the number of consecutive slots having the first slot type. For example, in some embodiments, N slot is always equal to the number of consecutive SBFD slots.

[0073] In some embodiments, if the first slot is among multiple consecutive slots, the first slot is determined based on the number of remaining consecutive slots in the multiple consecutive slots having the first slot type, excluding the first slot for the multiple repetitions, plus one. For example, in one embodiment, if the first slot of a repetition is an SBFD slot, then N slot is equal to the number of remaining SBFD slots in the group of consecutive SBFD slots plus 1 (the first slot).

[0074] In some embodiments, if the first slot in the repetition is of the second slot type, the first slot is determined based on the number of consecutive slots having the first slot type. For example, in some embodiments, if the first slot in the repetition is a non-SBFD slot, N slot is equal to the number of consecutive SBFD slots.

[0075] In some embodiments, the first number is determined based on the number of slots allocated for transmission block processing over multiple slots (TBoMS). For example, in some embodiments, N slotis equal to the number of slots allocated to TBoMS in the current specification, i.e., the number determined by the row in the TDRA table. In this case, Nslot≦number of consecutive SBFD slots, and N slot It is up to the implementation of the gNB (an example of network device 120) to ensure that >1.

[0076] In some embodiments, at the terminal device 110 side, the first repetition is configured with a first starting symbol index and a first length of allocated resources per slot. The second repetition is configured with a second starting symbol index and a second length of allocated resources per slot. At the network device 120 side, the network device 120 can configure the first repetition with the above-mentioned first starting symbol index and first length of allocated resources per slot, and the second repetition with a second starting symbol index and a second length of allocated resources per slot. Furthermore, in some embodiments, the first starting symbol index may be the same as the second starting symbol index for each slot. Alternatively, the first length of allocated resources may be the same as the second length of allocated resources for each slot. In other embodiments, the first starting symbol index may be different from the second starting symbol index for each slot. Alternatively, the first length of allocated resources may be different from the second length of allocated resources for each slot.

[0077] In some embodiments, on the network device 120 side, the network device 120 may report a first starting symbol index and a first length of the assigned resources via either a radio resource control (RRC) message or scheduling information, and the network device 120 may report a second starting symbol index and a second length of the assigned resources 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 length of the assigned resources are reported via either a radio resource control (RRC) message or scheduling information, and the second starting symbol index and the second length of the assigned resources are reported via the other of the RRC message or scheduling information.

[0078] In some embodiments, if the first slot of the multiple repetitions is of the first slot type, terminal device 110 determines that the number of physical resource blocks (PRBs) for the second repetition is equal to the number of PRBs for the first repetition scaled by a factor. For example, in some embodiments, if the first slot of the repetition is an SBFD slot, the number of PRBs used for a single slot repetition in a non-SBFD slot (

number

number

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

number

number

[0080] In some embodiments, the factor may be equal to the first number of slots having the first slot type. In other embodiments, at the terminal device 110 side, the factor may be signaled via an RRC message or schedule information. In other words, at the network device 120 side, the network device 120 may signal the factor via an RRC message or schedule information.

[0081] In some embodiments, if the first slot of the multiple repetitions is of the first slot type, the terminal device 110 determines that the starting resource block (RB) of the second repetition is equal to the starting RB of the first repetition plus an offset, or to a reference RB in the frequency domain plus an offset.

[0082] Alternatively, in some embodiments, if the first slot of the multiple repetitions is of the second slot type, the terminal device 110 may determine that the starting RB of the first repetition is equal to either the starting RB of the second repetition plus an offset, or a reference RB in the frequency domain plus an offset.

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

[0084] In some embodiments, the reference RB may be the starting RB of the bandwidth of the uplink transmission. In other embodiments, the reference RB may be the starting RB of a subband of the uplink transmission that coexists with at least a subband of the downlink transmission in the slot. In yet other embodiments, the reference RB may be the value of the starting RB signaled via an RRC message or schedule information.

[0085] In some embodiments, terminal device 110 calculates a transmission block size (TBS) for multiple iterations based on at least one resource allocated per slot having a first slot type multiplied by a first number. Additionally or alternatively, in some embodiments, terminal device 110 calculates a TBS based on at least one resource allocated per slot having a second slot type.

[0086] In some embodiments, the terminal device 110 determines a first redundancy version (RV) sequence that cycles through a first of the plurality of repetitions associated with a first slot type, and determines a second RV sequence that cycles through a second of the plurality of repetitions associated with a second slot type. In other words, according to the present disclosure, the redundancy version (RV) sequence that cycles through a first of the plurality of repetitions associated with a first slot type is the first RV sequence, and the RV sequence that cycles through a second of the plurality of repetitions associated with a second slot type is the second RV sequence.

[0087] In some embodiments, the slots having the first slot type are subband non-overlapping full duplex (SBFD) slots and the slots having the second slot type are non-SBFD slots, hi other embodiments, the slots having the first slot type are flexible slots and the slots having the second slot type are static slots.

[0088] According to one embodiment of the present disclosure, a new repetition type for SBFD operation is proposed. Figure 3 is a schematic diagram illustrating the repetition type for SBFD operation according to the present disclosure. Referring to Figure 3, TBoMS uses a smaller number of PRBs (

number

number

[0089] 4 is a schematic diagram showing a communication process 400 between a terminal device 110 and a network device 120. The terminal device 110 is a UE, and the network device 120 can be abbreviated as NW. In step 1, the network device 120 notifies the terminal device 110 of the number of subband full duplex (SBFD) slots / symbols and the positions of the slots / symbols in a radio frame, as well as the number of non-SBFD slots / symbols and the positions of the slots / symbols in a radio frame. Specifically, the network device 120 notifies the terminal device 110 of the frequency band, the number of slots / symbols in which the frequency band is divided 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., the subband full duplex (SBFD) slots / symbols, the positions of the number of slots / symbols in the radio frame, and the number of slots / symbols in which the entire frequency band is used for DL ​​transmission or UL transmission, i.e., the non-SBFD slots / symbols, and the positions of the number of slots / symbols in the radio frame, and these are received by the terminal device 110.

[0090] In some embodiments, the network device 120 may signal this via an RRC configuration or DCI.

[0091] In step 2, the network device 120 notifies the terminal device 110 that a new recurrence type (ie, a recurrence type in this specification) for PUSCH transmission is applicable.

[0092] Specifically, network device 120 notifies, and terminal device 110 receives, a notification (referred to as a first notification) that a new recurrence type for PUSCH transmission is applied in terminal device 110. In some embodiments, network device 120 can notify the first notification via an RRC configuration.

[0093] In step 3, the network device 120 may schedule PUSCH transmissions using the new repetition type, including repetition across SBFD and non-SBFD slots.

[0094] In some embodiments, the scheduling DCI conveys information regarding whether a new repetition type should be used by terminal device 110. Specifically, network device 120 receives (e.g., via the scheduling DCI) a notification (referred to as a second notification) regarding whether terminal device 110 should use a new PUSCH repetition type for PUSCH transmission with repetition at terminal device 110. This is a dynamic notification.

[0095] In various embodiments, this notification (second notification) can be performed using different alternatives (Alternative 1 to Alternative 3). In some embodiments, Alternative 1 is to add a new column to the TDRA table (see 3GPP TS38.214, section 6.1.2.1). This column indicates whether a new recurrence type should be applied for each row of the TDRA table (e.g., associated with bit 0 or 1). In other words, the second notification may include a column of the TDRA table.

[0096] In another embodiment, as Alternative 2, a new field is added to the DCI to trigger the applicability of the new recurrence type, i.e. the second notification may include a field in the DCI.

[0097] Furthermore, as another embodiment, in alternative 3, the new recurrence type is supported by default when the UE receives the notification (first notification) in step 2 and / or when the UE is configured for SBFD operation.

[0098] In step 4, the terminal device 110 determines the time-domain and frequency-domain resources, the transport block size, and the redundancy version for transmitting coded bits of the transport block in the scheduled PUSCH transmission using the new repetition type. At this time, the time-domain and frequency-domain resources between repetitions may differ depending on whether the repetition is on an SBFD slot or not.

[0099] For example, if the terminal device 110 is a UE, the UE determines the time domain resource, the frequency domain resource, the transport block size, and the redundancy version for transmitting a transport block via multiple repetitions of the PUSCH.

[0100] In determining the time domain resources, the repetition within the SBFD slot is N slot The repetition in a non-SBFD slot uses the resources of a single slot (called a single-slot repetition).

[0101] The above N slot is determined from one of the following alternatives (Alt.1 to Alt.3 below) (N slot ≤ number of consecutive SBFD slots, N slot ).

[0102] Alternative 1:N slot is always equal to the number of consecutive SBFD slots.

[0103] Alternative 2: In some embodiments, if the first slot of the repetition is an SBFD slot, then N slot is equal to the number of remaining SBFD slots in the consecutive SBFD slots plus 1 (the first slot). Otherwise, in some embodiments, if the first slot of the repeat is a non-SBFD slot, N slot is equal to the number of consecutive SBFD slots.

[0104] Alternative 3: In some embodiments, N slotis equal to the number of slots allocated to TBoMS in the current specification, i.e., the value determined by the row in the TDRA table. In this case, N slot ≦ the number of consecutive SBFD slots, N slot It is the gNB (an implementation example of network device 120) that ensures that >1.

[0105] Alternatively, or additionally, in some embodiments, the number of slots used for TBoMS repetition (N slot and the positions of these slots within a sequence of SBFD slots apply across different sequences of SBFD slots. For example, TBoMS repetitions are always transmitted in the first and third slots of three consecutive SBFD slots.

[0106] In some embodiments, the same starting symbol index (S) and length of allocated resources per slot (L) signaled via the scheduling DCI applies to the TBoMS repeating slots and the single slot repeating slots.

[0107] Alternatively, in other embodiments, the above S and L may be different between TBoMS repeating slots and single-slot repeating slots, for example, S and L for TBoMS repeating slots may be preconfigured by RRC, and the scheduling DCI may only indicate S and L for single-slot repeating slots, or vice versa.

[0108] In frequency domain resource determination, in some embodiments, if the first slot of the repetition is an SBFD slot, the number of PRBs (

number

number

[0109] As an example, this factor may be the number of slots used for repeating TBoMS in consecutive SBFD slots, i.e.

number

[0110] In another embodiment, if the first slot of the repetition is a non-SBFD slot, the number of PRBs (

number

number

[0111] As an example, this factor can be divided by the number of slots used for repeating TBoMS in consecutive SBFD slots, i.e.

number

[0112] Terminal device 110 also determines a transmission block size (TBS). In calculating TBS, in some embodiments, as alternative 1, TBS is calculated as N times the allocated resources per SBFD slot. slot In another embodiment, Alternative 2, the TBS is calculated based on the allocated resources per non-SBFD slot. The above Alternatives 1 and 2 are

number

[0113] The terminal device 110 may determine a redundancy version. In determining the redundancy version, in some embodiments, a legacy RV sequence is used. The legacy sequence is used to rotate the RV in all repetitions, including TBoMS repetitions and single-slot repetitions. In other embodiments, two RV sequences are configured. One sequence (e.g., a new sequence different from the legacy RV sequence) is used to rotate the RV between TBoMS repetitions, and another sequence (e.g., the legacy sequence) is used to rotate the RV between single-slot repetitions.

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

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

[0116] In some embodiments, steps 1 and 2 are interchangeable or integrable.

[0117] In some embodiments, terminal device 110 may report its ability to support new recurrence types to network device 120 as a preliminary step.

[0118] In some embodiments, in a dynamic TDD scenario, SBFD slots may be replaced by dynamic TDD flexible slots and non-SBFD slots may be replaced by dynamic TDD static slots.

[0119] According to an embodiment of the present disclosure, a terminal device 110 (e.g., a UE) receives a notification (e.g., via RRC and / or DCI) from the network (NW) to determine the time and frequency domain resources, transport block size, and redundancy version for transmitting a transport block via multiple PUSCH repetitions. The resources in at least the time domain (and in some embodiments, the frequency domain as well) differ depending on whether the repetitive transmission is performed on an SBFD slot or a non-SBFD slot. On the UE side, the UE determines the time and frequency domain resources, transport block size, and redundancy version and performs the transmission of the transport block via multiple PUSCH repetitions. In this way, the combination of TBoMS and single-slot PUSCH transmission enables a narrower PUSCH allocation (in terms of the number of PRBs) in the SBFD slot, thereby increasing the number of users multiplexed in the frequency domain (UL subband of the SBFD slot) and improving overall UL cell coverage. At the same time, the single-slot PUSCH transmission in a non-SBFD slot reduces latency and improves UL throughput and resource efficiency compared to the case of applying TBoMS.

[0120] FIG. 5 is a schematic diagram illustrating a method 500 implemented in a terminal device in accordance with another embodiment of the present disclosure. As shown in FIG. 5, at block 510, terminal device 110 receives, from network device 120, schedule information that schedules uplink transmissions that terminal device 110 will transmit using a repetition type. At block 520, terminal device 110 determines, based on the repetition type, a first resource set for a first repetition in the multiple repetitions of the uplink transmission and a second resource set for a second repetition in the multiple repetitions. The first resource set is arranged in a first number of slots having a first slot type, and the second resource set is arranged in a second number of slots having a second slot type. At block 530, terminal device 110 transmits the multiple repetitions of the uplink transmission to network device 120.

[0121] In some embodiments, before receiving the schedule information, terminal device 110 receives a first indication from network device 120 that a recurrence type is applicable for the uplink transmission.

[0122] In some embodiments, based on receipt of the first notification, terminal device 110 determines the recurrence type as the default recurrence type.

[0123] In some embodiments, the schedule information may include a second notification to indicate whether a recurrence type is to be used for uplink transmission.

[0124] In some embodiments, if it is determined that the second notification is configured to notify that a repetition type is to be used for the uplink transmission, the terminal device 110 determines to transmit the uplink transmission using the repetition type.

[0125] In some embodiments, the second notification may include at least one of a row in a time domain resource allocation (TDRA) table or a field in downlink control information (DCI).

[0126] In some embodiments, if terminal device 110 determines that it is configured with the operation associated with the first slot type, terminal device 110 determines the recurrence type as the default recurrence type.

[0127] In some embodiments, to determine the first resource set and the second resource set, the terminal device 110 determines the first resource set from a first number of slots, the first number being greater than one, and determines the second resource set from a second number of slots, the second number being equal to one.

[0128] In some embodiments, the first number is determined based on any of the following: a number of consecutive slots having a first slot type; a number of remaining consecutive slots in the consecutive slots having the first slot type plus one, excluding the first slot for the multiple repetitions, if the first slot is located between consecutive slots; a number of consecutive slots having the first slot type, if the first slot in the multiple repetitions is a second slot type; or a number of slots allocated for transmission block processing across multiple slots (TBoMS).

[0129] In some embodiments, the first repetition comprises a first starting symbol index and a first length of allocated resources per slot, and the second repetition comprises a second starting symbol index and a second length of allocated resources per slot, where the first starting symbol index is the same as the second starting symbol index per slot, or the first length of allocated resources is the same as the second length of allocated resources per slot.

[0130] In some embodiments, a first repetition comprises a first starting symbol index and a first length of allocated resources per slot, and a second repetition comprises a second starting symbol index and a second length of allocated resources per slot, where the first starting symbol index per slot is different from the second starting symbol index. Alternatively, or additionally, the first length of allocated resources per slot is different from the second length of allocated resources.

[0131] In some embodiments, the first starting symbol index and the second length of the assigned resources are signaled by one of a Radio Resource Control (RRC) message or scheduling information, and the second starting symbol index and the second length of the assigned resources are signaled by the other of the RRC message or scheduling information.

[0132] In some embodiments, if the first slot of the multiple repetitions is of a first slot type, the terminal device 110 determines that the number of physical resource blocks (PRBs) for the second repetition is equal to the number of PRBs for the first repetition scaled by a factor. Alternatively, if the first slot of the multiple repetitions is of a second slot type, the terminal device 110 may determine that the number of PRBs in the first repetition is equal to the number of PRBs in the second repetition scaled by a factor.

[0133] In some embodiments, the factor is equal to the first number of slots of the first slot type, or the factor is signaled via an RRC message or schedule information.

[0134] In some embodiments, when the first slot of the multiple repetitions is of a first slot type, terminal device 110 determines that the starting resource block (RB) of the second repetition is equal to the starting RB of the first repetition plus an offset or a reference RB in the frequency domain plus an offset. Alternatively, when the first slot of the multiple repetitions is of a second slot type, terminal device 110 determines that the starting RB of the first repetition is equal to the starting RB of the second repetition plus an offset or a reference RB in the frequency domain plus an offset.

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

[0136] In some embodiments, the reference RB is either the starting RB of the bandwidth of the uplink transmission, the starting RB of a subband of the uplink transmission that coexists with at least a subband of the downlink transmission within the slot, or a value of the starting RB notified via an RRC message or schedule information.

[0137] In some embodiments, terminal device 110 calculates a transmission block size (TBS) for multiple iterations based on at least one resource allocated per slot in the first slot type multiplied by a first number, while in other embodiments, terminal device 110 calculates a TBS based on at least one resource allocated per slot in the second slot type.

[0138] In some embodiments, the terminal device 110 determines a first redundancy version (RV) sequence that cycles through a first plurality of repetitions associated with a first slot type among the plurality of repetitions, and determines a second RV sequence that cycles through a second plurality of repetitions associated with a second slot type among the plurality of repetitions.

[0139] In some embodiments, the slots having the first slot type are subband non-overlapping full duplex (SBFD) slots or flexible slots, and the slots having the second slot type are non-SBFD slots or static slots.

[0140] 6 is a schematic diagram illustrating a method 600 implemented in network device 120 in accordance with another embodiment of the present disclosure. As shown in FIG. 6, at block 610, network device 120 may transmit, to terminal device 110, schedule information that schedules uplink transmissions to be transmitted by terminal device 110 using a repetition type. At block 620, network device 120 receives, from terminal device 110, multiple repetitions of the uplink transmission, including a first repetition and a second repetition. A first resource set for the first repetition is located in a first number of slots having a first slot type, and a second resource set for the second repetition is located in a second number of slots having a second slot type.

[0141] In some embodiments, before transmitting the schedule information, network device 120 transmits a first notification to terminal device 110 informing it that a recurrence type is applicable for uplink transmission.

[0142] In some embodiments, the schedule information includes a second indication to indicate whether a recurrence type is used at terminal device 110 for uplink transmission.

[0143] In some embodiments, the second notification includes at least one of a column in a time domain resource allocation (TDRA) table or a field in downlink control information (DCI).

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

[0145] In some embodiments, the first number is determined based on any of the following: a number of consecutive slots having a first slot type; a number of remaining consecutive slots in the consecutive slots having the first slot type, excluding the first slot for the multiple repetitions, plus one, if the first slot is located between the consecutive slots; a number of consecutive slots of the first slot type, if the first slot in the multiple repetitions is a second slot type; or a number of slots allocated for transmission block processing across multiple slots (TBoMS).

[0146] In some embodiments, the network device 120 configures a first repetition with a first starting symbol index and a first length of allocated resources per slot, and a second repetition with a second starting symbol index and a second length of allocated resources per slot, where the first starting symbol index per slot is the same as the second starting symbol index, or where the first length of allocated resources per slot is the same as the second length of allocated resources.

[0147] In some embodiments, the network device 120 may configure a first repetition with a first starting symbol index and a first length of allocated resources per slot, and a second repetition with a second starting symbol index and a second length of allocated resources per slot, where the first starting symbol index per slot is different from the second starting symbol index. Alternatively, or additionally, the first length of allocated resources per slot is different from the second length of allocated resources.

[0148] In some embodiments, the network device 120 may signal a first starting symbol index and a first length of the assigned resources via either a radio resource control (RRC) message or scheduling information, and may signal a second starting symbol index and a second length of the assigned resources via the other of the RRC message or scheduling information.

[0149] In some embodiments, if the first slot of the multiple repetitions is of a first slot type, the number of physical resource blocks (PRBs) in the second repetition is equal to the number of PRBs in the first repetition scaled by a factor. In some embodiments, if the first slot of the multiple repetitions is of a second slot type, the number of PRBs in the first repetition is equal to the number of PRBs in the second repetition scaled by a factor.

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

[0151] In some embodiments, if the first slot of the multiple repetitions is of a first slot type, the network device 120 may determine that the starting resource block (RB) of the second repetition is equal to either the starting RB of the first repetition plus an offset or a reference RB in the frequency domain plus an offset. In some embodiments, if the first slot of the multiple repetitions is of a second slot type, the network device 120 determines that the starting RB of the first repetition is equal to either the starting RB of the second repetition plus an offset or a reference RB in the frequency domain plus an offset.

[0152] In some embodiments, the network device 120 may signal the offset through an RRC message or scheduling information.

[0153] In some embodiments, the reference RB is either the starting RB of the bandwidth of the uplink transmission, the starting RB of a subband of the uplink transmission that coexists with at least a subband of the downlink transmission within the slot, or a value of the starting RB notified via an RRC message or schedule information.

[0154] In some embodiments, a transmission block size (TBS) of the multiple repetitions is calculated based on at least one of the allocated resources per slot in the first slot type multiplied by a first number, and in some embodiments, the TBS is calculated based on at least one of the allocated resources per slot in the second slot type.

[0155] In some embodiments, a redundancy version (RV) sequence applied periodically across a first plurality of repetitions associated with a first slot type among the plurality of repetitions is a first RV sequence, and a RV sequence applied periodically across a second plurality of repetitions associated with a second slot type among the plurality of repetitions is a second RV sequence.

[0156] In some embodiments, slots having a first slot type are subband non-overlapping full duplex (SBFD) slots or flexible slots, and slots having a second slot type are non-SBFD slots or static slots.

[0157] In some embodiments, a device capable of performing any of the methods 500 (e.g., terminal device 110) may comprise means for performing each step of the method 500. The means may be implemented in any suitable form. For example, the means may be implemented as a circuit or a software module.

[0158] In some embodiments, the apparatus comprises: means for receiving, from the network device 120, scheduling information that schedules uplink transmissions that the terminal device 110 transmits using a repetition type; means for determining, based on the repetition type, a first resource set for a first repetition in the multiple repetitions of the uplink transmission and a second resource set for a second repetition in the multiple repetitions, wherein the first resource set is arranged in a first number of slots having the first slot type and the second resource set is arranged in a second number of slots having the second slot type; and means for transmitting the multiple repetitions of the uplink transmission to the network device 120.

[0159] In some embodiments, the apparatus further comprises means for receiving, prior to receiving the schedule information, a first notification from the network device 120 that a recurrence type is applicable to the uplink transmission.

[0160] In some embodiments, the apparatus further comprises means for determining the recurrence type as a default recurrence type based on receiving the first notification.

[0161] In some embodiments, the schedule information includes a second notification to indicate whether a recurrence type is to be used for uplink transmission.

[0162] In some embodiments, the apparatus further comprises means for determining, based on determining that the second notification is configured to notify use of the repetition type for the uplink transmission, to transmit the uplink transmission using the repetition type.

[0163] In some embodiments, the second notification includes at least one of a column in a time domain resource allocation (TDRA) table or a field in downlink control information (DCI).

[0164] In some embodiments, the apparatus further comprises means for determining the recurrence type as a default recurrence type based on determining that the terminal device 110 is configured with an operation associated with the first slot type.

[0165] In some embodiments, the means for determining the first resource set and the second resource set includes means for determining the first resource set from a first number of slots, where the first number of slots is greater than one, and means for determining the second resource set from a second number of slots, where the second number of slots is equal to one.

[0166] In some embodiments, the first number is determined based on any of the following: a number of consecutive slots having a first slot type; a number of remaining consecutive slots in the consecutive slots having the first slot type plus one, excluding the first slot for the multiple repetitions, if the first slot is located between consecutive slots; a number of consecutive slots having the first slot type, if the first slot in the multiple repetitions is a second slot type; or a number of slots allocated for transmission block processing across multiple slots (TBoMS).

[0167] In some embodiments, the first repetition is comprised of a first starting symbol index and a first length of the resources allocated per slot, the second repetition is comprised of a second starting symbol index and a second length of the resources allocated per slot, and at least one of the first starting symbol index is identical to the second starting symbol index per slot and the first length of the resources allocated per slot is identical to the second length of the resources allocated per slot.

[0168] In some embodiments, the first repetition is comprised of a first starting symbol index and a first length of the allocated resources per slot, and the second repetition is comprised of a second starting symbol index and a second length of the allocated resources per slot, and the first starting symbol index per slot is different from the second starting symbol index, or the first length of the allocated resources per slot is different from the second length of the allocated resources.

[0169] In some embodiments, the first starting symbol index and the second length of the allocated resources are signaled via one of a Radio Resource Control (RRC) message or scheduling information, and the second starting symbol index and the second length of the allocated resources are signaled via the other of the RRC message or scheduling information.

[0170] In some embodiments, the apparatus further comprises means for determining, if the first slot of the multiple repetitions is of a first slot type, that the number of physical resource blocks (PRBs) for the second repetition is equal to the number of PRBs for the first repetition scaled by the factor, or, if the first slot of the multiple repetitions is of a second slot type, that the number of PRBs for the first repetition is equal to the number of PRBs for the second repetition scaled by the factor.

[0171] In some embodiments, the factor is equal to the first number of slots of the first slot type, or the factor is signaled via an RRC message or schedule information.

[0172] In some embodiments, the apparatus further comprises either means for determining, when the first slot of the multiple repetitions is of a first slot type, that a starting resource block (RB) of the second repetition is equal to the starting RB of the first repetition plus an offset or a reference RB in the frequency domain plus an offset, or means for determining, when the first slot of the multiple repetitions is of a second slot type, that a starting RB of the first repetition is equal to either the starting RB of the second repetition plus an offset or a reference RB in the frequency domain plus an offset.

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

[0174] In some embodiments, the reference RB is either the starting RB of the bandwidth of the uplink transmission, the starting RB of a subband of the uplink transmission that coexists with at least a subband of the downlink transmission within the slot, or a value of the starting RB notified via an RRC message or schedule information.

[0175] In some embodiments, the apparatus further comprises either means for calculating, for multiple repetitions, a transmission block size (TBS) based on at least one resource allocated for each slot having a first slot type multiplied by a first number, or means for calculating a TBS based on at least one resource allocated for each slot having a second slot type.

[0176] In some embodiments, the apparatus further comprises means for determining a first redundancy version (RV) sequence that cycles through a first plurality of repetitions associated with a first slot type among the plurality of repetitions, and means for determining a second RV sequence that cycles through a second plurality of repetitions associated with a second slot type among the plurality of repetitions.

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

[0178] 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 containing computer program code, the at least one memory and the computer program code configured, by the at least one processor, to cause the apparatus to perform operations.

[0179] In some embodiments, a device capable of performing any of the methods 600 (e.g., network device 120) may comprise means for performing each step of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented as a circuit or a software module.

[0180] In some embodiments, the apparatus comprises: means for transmitting, to the terminal device 110, schedule information that schedules an uplink transmission to be transmitted by the terminal device 110 using a repetition type; and means for receiving, from the terminal device 110, multiple repetitions of the uplink transmission, including a first repetition and a second repetition, wherein a first resource set of the first repetition is arranged in a first number of slots having a first slot type, and a second resource set of the second repetition is arranged in a second number of slots having a second slot type.

[0181] In some embodiments, the apparatus further comprises means for transmitting, prior to transmitting the schedule information, a first notification to terminal device 110 informing that a recurrence type is applicable to uplink transmission.

[0182] In some embodiments, the schedule information includes a second indication to indicate whether a recurrence type is used at terminal device 110 for uplink transmission.

[0183] In some embodiments, the second notification includes at least one of a row in a time domain resource allocation (TDRA) table and a field in downlink control information (DCI).

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

[0185] In some embodiments, the first number is determined based on any of the following: a number of consecutive slots having a first slot type; a number of remaining consecutive slots in the consecutive slots having the first slot type excluding the first slot for the multiple repetitions plus one if the first slot is located between the multiple consecutive slots; a number of consecutive slots of the first slot type if the first slot in the multiple repetitions is a second slot type; or a number of slots allocated for transmission block processing across multiple slots (TBoMS).

[0186] In some embodiments, the apparatus further comprises means for configuring a first repetition with a first starting symbol index and a first length of allocated resources per slot, and means for configuring a second repetition with a second starting symbol index and a second length of allocated resources per slot, wherein the first starting symbol index is identical to the second starting symbol index per slot, or the first length of allocated resources is identical to the second length of allocated resources per slot.

[0187] In some embodiments, the apparatus further comprises means for configuring a first repetition with a first starting symbol index and a first length of allocated resources per slot, and means for configuring a second repetition with a second starting symbol index and a second length of allocated resources per slot, wherein at least one of the first starting symbol index is different from the second starting symbol index per slot or the second length of allocated resources is different from the second length of allocated resources per slot.

[0188] In some embodiments, the apparatus further comprises means for signaling the first starting symbol index and the first length of the assigned resources via one of a Radio Resource Control (RRC) message or scheduling information, and means for signaling the second starting symbol index and the second length of the assigned resources via the other of the RRC message or scheduling information.

[0189] In some embodiments, if the first slot of the multiple repetitions is of a first slot type, the number of physical resource blocks (PRBs) in the second repetition is equal to the number of PRBs in the first repetition scaled by a factor, or if the first slot of the multiple repetitions is of a second slot type, the number of PRBs in the first repetition is equal to the number of PRBs in the second repetition scaled by a factor.

[0190] In some embodiments, the factor is equal to the first number of slots of the first slot type, or the apparatus further comprises means for signaling the factor via an RRC message or schedule information.

[0191] In some embodiments, the apparatus further comprises either means for determining, when the first slot of the multiple repetitions is of a first slot type, that a starting resource block (RB) of the second repetition is equal to the starting RB of the first repetition plus an offset or a reference RB in the frequency domain plus an offset, or means for determining, when the first slot of the multiple repetitions is of a second slot type, that a starting RB of the first repetition is equal to either the starting RB of the second repetition plus an offset or a reference RB in the frequency domain plus an offset.

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

[0193] In some embodiments, the reference RB is either the starting RB of the bandwidth of the uplink transmission, the starting RB of a subband of the uplink transmission that coexists with at least a subband of the downlink transmission within the slot, or a value of the starting RB notified via an RRC message or schedule information.

[0194] In some embodiments, at least one of the following applies: a transmission block size (TBS) of the multiple repetitions is calculated based on at least one resource allocated per slot in the first slot type multiplied by a first number; or the TBS is calculated based on at least one resource allocated per slot in the second slot type.

[0195] In some embodiments, a redundancy version (RV) sequence applied periodically across a first plurality of repetitions associated with a first slot type among the repetitions is a first RV sequence, and a RV sequence applied periodically across a second plurality of repetitions associated with a second slot type among the repetitions is a second RV sequence.

[0196] In some embodiments, slots having a first slot type are subband non-overlapping full duplex (SBFD) slots or flexible slots, and slots having a second slot type are non-SBFD slots or static slots.

[0197] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of method 600. In some embodiments, the means comprises at least one processor and at least one memory containing computer program code, the at least one memory and the computer program code configured by the at least one processor to cause the apparatus to perform operations.

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

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

[0200] Processor 710 may be of any type suitable for a local technology network, including, for example, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a processor based on a multi-core processor architecture, etc. Device 700 may have multiple processors, such as application-specific integrated circuit chips time-slaved to a clock that synchronizes the main processor.

[0201] 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 erasable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), other magnetic and / or optical storage devices, etc. Examples of volatile memories include random access memory (RAM) 722 and other volatile memories that cannot retain data during power-off periods.

[0202] The computer program 730 includes computer-executable instructions that are executed by the associated processor 710. The program 730 may be stored in ROM 820. The processor 710 can load the program 730 into RAM 820 to perform any suitable operations and processes.

[0203] The embodiments of the present disclosure are implemented by a program 730 that enables the device 700 to perform any of the processes disclosed above with reference to Figures 2 to 6. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0204] In some embodiments, the program 730 may be tangibly stored on a computer-readable medium internal to the device 700 (e.g., in memory 720) or other storage accessible by the device 700. The device 700 may load the program 730 from the computer-readable medium into RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile storage device, such as a ROM, an EPROM, a flash memory, a hard disk, a CD, a DVD, etc. Figure 8 shows an example of a computer-readable medium 800 in the form of a CD or DVD. The computer-readable medium has the program 730 stored thereon.

[0205] In general, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic, or any combination thereof. Some features may be implemented in hardware, while other features may be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Although various aspects of embodiments of the present disclosure have been described using block diagrams, flowcharts, or other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented by, by way of non-limiting example, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or combinations thereof.

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

[0207] Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, and executed by the processor or controller to implement the functions / acts specified in the flowcharts and / or block diagrams. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0208] In the context of the present disclosure, computer program code or associated data may be transmitted by any suitable medium to enable a device, apparatus, or processor to perform the various processes and operations as described above. Examples of media include signals, computer-readable media, etc.

[0209] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, devices, or any suitable combination thereof. More specific examples of computer-readable storage media include an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. The term "non-transitory" in this context refers not to the permanence of data storage (e.g., RAM vs. ROM), but to the medium itself (i.e., a tangible object rather than a signal).

[0210] Furthermore, even if operations are shown in a particular order, this should not be interpreted as requiring that the operations be performed in the particular order or sequential order shown, or that all of the operations shown be performed, to achieve desirable results. In certain situations, multitasking or parallel processing may be advantageous. Similarly, while the above discussion includes some specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of functionality specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

[0211] Although the present disclosure has been described in language specifying structural features and / or method acts, the present disclosure, as defined by the appended claims, is not necessarily limited to the specific features and acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A terminal device, at least one processor; When executed by the at least one processor, the terminal device is configured to: receiving, from a network device, schedule information for scheduling uplink transmissions to be transmitted by the terminal device using a recurrence type; determining a first resource set for a first repetition in the plurality of repetitions of the uplink transmission and a second resource set for a second repetition in the plurality of repetitions based on the repetition type, the first resource set being located in a first number of slots having a first slot type and the second resource set being located in a second number of slots having a second slot type; transmitting the plurality of repetitions of the uplink transmission to the network device; at least one memory storing instructions for executing the A terminal device comprising:

2. The terminal device further receiving, prior to receiving the schedule information, a first indication from the network device that the recurrence type is applicable to the uplink transmission; The terminal device of claim 1 , configured to execute:

3. The terminal device further determining the recurrence type as a default recurrence type based on receiving the first notification; The terminal device according to claim 2 .

4. the schedule information includes a second notification for indicating whether the recurrence type is used for the uplink transmission.

3. The terminal device according to claim 1 or 2.

5. The terminal device further determining that the uplink transmission is to be transmitted using the recurrence type based on determining that the second notification is configured to notify that the recurrence type will be used for the uplink transmission; The terminal device according to claim 4, wherein

6. The second notification is a column in a Time Domain Resource Allocation (TDRA) table, or Downlink Control Information (DCI) fields, 6. The terminal device according to claim 4, further comprising at least one of:

7. The terminal device further determining the repetition type as a default repetition type based on determining that the terminal device is configured with an operation associated with the first slot type; 3. The terminal device according to claim 1 or 2, wherein:

8. The terminal device determining the first resource set from the first number of slots, the first number being greater than one; determining the second resource set from the second number of slots, the second number equal to one; The terminal device according to claim 1 , configured to determine the first resource set and the second resource set by:

9. The first number is the number of consecutive slots having the first slot type; if a first slot is between the plurality of consecutive slots, the sum of the number of remaining consecutive slots having the first slot type in the plurality of consecutive slots excluding the first slot of the plurality of repetitions and 1; if the first slot in the plurality of repetitions is the second slot type, the number of the plurality of consecutive slots having the first slot type; or the number of slots allocated to Transport Block Processing over Multiple Slots (TBoMS); The terminal device according to claim 8 , wherein the determination is based on any one of the following:

10. the first repetition is comprised of a first starting symbol index and a first length of allocated resources per slot; the second repetition is comprised of a second starting symbol index and a second length of allocated resources per slot; the first starting symbol index is the same as the second starting symbol index per slot, or the first length of the allocated resources is the same as the second length of the allocated resources per slot.

10. The terminal device according to claim 1.

11. the first repetition is comprised of a first starting symbol index and a first length of allocated resources per slot; the second repetition is comprised of a second starting symbol index and a second length of allocated resources per slot; for each slot, the first starting symbol index is different from the second starting symbol index; or for each slot, the first length of the assigned resources is different from the second length of the assigned resources.

10. The terminal device according to claim 1.

12. the first starting symbol index and the first length of the assigned resource are signaled via one of a Radio Resource Control (RRC) message or the schedule information; the second starting symbol index and the second length of the allocated resource are signaled via the other of the RRC message or the scheduling information. The terminal device according to claim 10 or 11.

13. The terminal device further If a first slot of the multiple repetitions is of the first slot type, determining that the number of physical resource blocks (PRBs) for the second repetition is equal to the number of PRBs for the first repetition scaled by a factor; or if the first slot of the multiple repetitions is the second slot type, determining that the number of PRBs of the first repetition is equal to the number of PRBs of the second repetition scaled by the factor; 13. The terminal device according to claim 1, wherein the terminal device is configured to:

14. the coefficient is equal to the first number of slots having the first slot type, or The coefficient is signaled via an RRC message or the schedule information. The terminal device according to claim 13.

15. The terminal device further If a first slot of the multiple repetitions is the first slot type, determining that the starting resource block (RB) of the second repetition is equal to the starting RB of the first repetition plus an offset, or equal to a reference RB in the frequency domain plus the offset; or If the first slot of the plurality of repetitions is the second slot type, determining that the starting RB of the first repetition is equal to the starting RB of the second repetition plus the offset, or equal to the reference RB in the frequency domain plus the offset; 15. A terminal device according to claim 1, adapted to perform at least one of the following:

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

17. The reference RB is the starting RB of the bandwidth of said uplink transmission; the starting RB of a subband of an uplink transmission that coexists with at least a subband of a downlink transmission within a slot; or The value of the starting RB notified via an RRC message or the scheduling information; 17. The terminal device according to claim 15, wherein the terminal device is one of the following:

18. The terminal device further calculating a transmission block size (TBS) for the plurality of repetitions based on at least one resource allocated per slot of the first slot type multiplied by the first number; or calculating the TBS based on at least one resource allocated for each slot having the second slot type; 18. The terminal device according to claim 1, wherein the terminal device executes at least one of the following:

19. The terminal device further determining a first redundancy version (RV) sequence that cycles through a first plurality of repetitions associated with the first slot type among the plurality of repetitions; determining a second RV sequence that cycles through a second plurality of repetitions of the plurality of repetitions associated with the second slot type; 19. Terminal device according to any one of claims 1 to 18, adapted to execute:

20. the slot having the first slot type is a sub-band full duplex (SBFD) slot or a flexible slot; the slots having the second slot type are non-SBFD slots or static slots; 20. A terminal device according to any one of claims 1 to 19.

21. A network device, at least one processor; When executed by the at least one processor, the network device is configured to: transmitting, to a terminal device, schedule information that schedules uplink transmissions transmitted by the terminal device using a recurrence type; receiving, from the terminal device, multiple repetitions of the uplink transmission, including a first repetition and a second repetition, wherein a first resource set of the first repetition is arranged in a first number of slots having a first slot type and a second resource set of the second repetition is arranged in a second number of slots having a second slot type; at least one memory storing instructions for executing the A network device comprising:

22. The network device further comprises: transmitting, to the terminal device, a first notification that the recurrence type is applicable to the uplink transmission, before transmitting the schedule information; 22. The network device according to claim 21, wherein

23. the schedule information includes a second notification for notifying whether the recurrence type is used for the uplink transmission in the terminal device; 23. A network device according to claim 21 or 22.

24. The second notification is a column in a Time Domain Resource Allocation (TDRA) table, or A field in the Downlink Control Information (DCI), 24. The network device of claim 23, comprising at least one of:

25. the first number is greater than 1, or the second number is equal to 1; 25. A network device according to any one of claims 21 to 24.

26. The first number is the number of consecutive slots having the first slot type; if a first slot is between the plurality of consecutive slots, the number of remaining consecutive slots in the plurality of consecutive slots having the first slot type, excluding the first slot of the plurality of repetitions, plus one; if the first slot in the plurality of repetitions is the second slot type, the number of the plurality of consecutive slots having the first slot type; or the number of slots allocated for Transport Block Processing over Multiple Slots (TBoMS); The network device of claim 25, wherein the determination is based on any of the following:

27. the first repetition is comprised of a first starting symbol index and a first length of allocated resources per slot; the second repetition is comprised of a second starting symbol index and a second length of allocated resources per slot; the first starting symbol index is the same as the second starting symbol index per slot, or the first length of the allocated resources is the same as the second length of the allocated resources per slot; The network device according to claim 21 , wherein at least one of the following conditions is satisfied:

28. The network device further comprises: configuring the first repetition with a first starting symbol index and a first length of allocated resources per slot; configuring the second repetition with a second starting symbol index and a second length of allocated resources per slot; It was like this, At least one of the following is satisfied: for each slot, the first starting symbol index is different from the second starting symbol index; or for each slot, the first length of allocated resources is different from the second length of allocated resources.

27. A network device according to any one of claims 21 to 26.

29. the network device is configured to signal the first starting symbol index and the first length of allocated resources via one of a Radio Resource Control (RRC) message or the schedule information; the network device is configured to signal the second starting symbol index and the second length of the allocated resources via the other of the RRC message or the scheduling information.

29. A network device according to claim 27 or 28.

30. If a first slot of the multiple repetitions is of the first slot type, the number of physical resource blocks (PRBs) in the second repetition is equal to the number of PRBs in the first repetition scaled by a factor; or if the first slot of the multiple repetitions is of the second slot type, the number of PRBs of the first repetition is equal to the number of PRBs of the second repetition scaled by the factor; At least one of the following is satisfied:

30. A network device according to any one of claims 21 to 29.

31. the coefficient is equal to the first number of slots having the first slot type, or The network device notifies the coefficient via an RRC message or the scheduling information.

31. The network device of claim 30.

32. If a first slot of the multiple repetitions is the first slot type, determining that the starting resource block (RB) of the second repetition is equal to the starting RB of the first repetition plus an offset, or a reference RB in the frequency domain plus the offset; or If the first slot of the plurality of repetitions is the second slot type, determining that the starting RB of the first repetition is equal to the starting RB of the second repetition plus the offset, or the reference RB in the frequency domain plus the offset; 32. The network device according to claim 21, wherein at least one of the following applies:

33. The network further comprises: signaling the offset via an RRC message or the scheduling information; 33. The network device of claim 32, wherein

34. The reference RB is the starting RB of the bandwidth of said uplink transmission; the starting RB of a subband of an uplink transmission that coexists with at least a subband of a downlink transmission within a slot; or The value of the starting RB notified via an RRC message or the scheduling information; 34. The network device according to claim 32 or 33, wherein:

35. The transmission block size (TBS) of the plurality of repetitions is calculated based on at least one resource allocated for each slot having the first slot type multiplied by the first number; or the TBS is calculated based on at least one of resources allocated for each slot having the second slot type; 35. A network device according to claim 21, wherein at least one of the following applies:

36. a redundancy version (RV) sequence that cycles across a first plurality of repetitions associated with the first slot type among the plurality of repetitions is a first RV sequence; a second RV sequence that cycles through a second plurality of repetitions associated with the second slot type among the plurality of repetitions; 36. A network device according to any one of claims 21 to 35.

37. the slot having the first slot type is a sub-band full duplex (SBFD) slot or a flexible slot; the slots having the second slot type are non-SBFD slots or static slots; 37. A network device according to any one of claims 21 to 36.

38. receiving, at a terminal device, from a network device, schedule information scheduling uplink transmissions to be transmitted by the terminal device using a recurrence type; determining a first resource set for a first repetition in the plurality of repetitions of the uplink transmission and a second resource set for a second repetition in the plurality of repetitions based on the repetition type, the first resource set being located in a first number of slots having a first slot type and the second resource set being located in a second number of slots having a second slot type; transmitting multiple repetitions of the uplink transmission to the network device; A method comprising:

39. transmitting, in the network device, to a terminal device, schedule information that schedules uplink transmissions transmitted by the terminal device using a recurrence type; receiving, from the terminal device, multiple repetitions of the uplink transmission, including a first repetition and a second repetition, wherein a first resource set of the first repetition is arranged in a first number of slots having a first slot type and a second resource set of the second repetition is arranged in a second number of slots having a second slot type; A method comprising:

40. 1. An apparatus comprising: means for receiving, in a terminal device, from a network device, schedule information for scheduling uplink transmissions transmitted by said terminal device using a recurrence type; means for determining, based on the repetition type, a first resource set for a first repetition in a plurality of repetitions of an uplink transmission and a second resource set for a second repetition in the plurality of repetitions, wherein the first resource set is located in a first number of slots having a first slot type and the second resource set is located in a second number of slots having a second slot type; means for transmitting the plurality of repetitions of the uplink transmission to the network device; An apparatus comprising:

41. 1. An apparatus comprising: means, in the network device, for transmitting, to a terminal device, schedule information for scheduling uplink transmissions transmitted by the terminal device using a recurrence type; means for receiving from the terminal device multiple repetitions of the uplink transmission, including a first repetition and a second repetition, wherein a first resource set of the first repetition is arranged in a first number of slots having a first slot type and a second resource set of the second repetition is arranged in a second number of slots having a second slot type; An apparatus comprising:

42. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method of claim 38 or 39.

Images