Transmission opportunity determination in sub-band full duplex operation

Abstract

Example embodiments of the present disclosure provide a solution for transmission opportunity (TO) determination in sub-band full duplex (SBFD) operations. In an example method, a terminal device receives scheduling information indicating a TO across at least one SBFD symbol and at least one non-SBFD symbol in a time slot. Based on determining that the TO is valid, the terminal device selects a time domain resource for at least a portion of the TO such that the at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol. The terminal device then transmits or receives data on at least a portion of the TO according to the selection. In this manner, UE and network behavior determined for time domain resource allocation for transmissions / repetitions across SBFD and non-SBFD symbols is defined without such transmissions being allowed.

Description

Technical Field

[0001] The exemplary embodiments of this disclosure generally relate to the field of communications, and particularly to terminal devices, network devices, methods, apparatuses, and computer-readable media for determining transmission timing in subband full-duplex (SBFD) operation. Background Technology

[0002] 3GPP has agreed to initiate the Rel-18 study project (RP-213591) on the evolution of duplex operation in New Radio (NR). Specifically, in unpaired wideband NR cells, downlink (DL) and uplink (UL) transmissions are permitted on different physical resource blocks (PRBs) / subbands, a process known as Subband Full-Duplex (SBFD). In SBFD operation, two symbol types exist for both DL and UL transmissions: SBFD symbols and non-SBFD symbols. During the SBFD symbol period, both non-overlapping (multiple) DL subbands and (multiple) UL subbands are present, while during the non-SBFD symbol period, the entire frequency band is used for either DL or UL.

[0003] 3GPP also agreed to investigate whether time slots can be composed of both SBFD and non-SBFD symbols. The behavior of UEs and networks towards such time slot types has not yet been studied. Summary of the Invention

[0004] Typically, the example embodiments of this disclosure provide a solution for TO determination in SBFD operations.

[0005] In a first aspect, a terminal device is provided. The terminal device includes: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: receive scheduling information from a network device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmit or receive data on the at least portion of the selected TO.

[0006] In a second aspect, a network device is provided. The network device includes: at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: send scheduling information to a terminal device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmit or receive data on the at least a portion of the selected TO.

[0007] In a third aspect, a method is provided. The method includes: receiving scheduling information from a network device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; selecting time domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmitting or receiving data on the at least portion of the TO selected.

[0008] In a fourth aspect, a method is provided. The method includes: sending scheduling information to a terminal device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; selecting time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmitting or receiving data on the at least portion of the TO selected.

[0009] In a fifth aspect, an apparatus is provided. The apparatus includes: components for receiving scheduling information from a network device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; components for selecting time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and components for transmitting or receiving data on at least a portion of the TO selected according to the selection.

[0010] In a sixth aspect, an apparatus is provided. The apparatus includes: components for transmitting scheduling information to a terminal device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; components for selecting time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and components for transmitting or receiving data on the at least portion of the TO selected according to the selection.

[0011] In a seventh aspect, a non-transitory computer-readable medium is provided, comprising program instructions. When executed by an apparatus, the program instructions cause the apparatus to perform at least the following: receiving scheduling information from a network device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; based on determining that the TO is valid, selecting time domain resources for at least a portion of the TO such that at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmitting or receiving data on the at least portion of the TO selected.

[0012] In an eighth aspect, a non-transitory computer-readable medium is provided, comprising program instructions. When executed by a device, the program instructions cause the device to perform at least the following: sending scheduling information to a terminal device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; selecting time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmitting or receiving data on the at least portion of the TO selected.

[0013] In a ninth aspect, a computer program is provided, including instructions that, when executed by an apparatus, cause the apparatus to at least: receive scheduling information from a network device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; based on determining that the TO is valid, select time domain resources for at least a portion of the TO such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmit or receive data on the at least portion of the TO according to the selection.

[0014] In a tenth aspect, a computer program is provided, including instructions that, when executed by a device, cause the device to at least: send scheduling information to a terminal device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; and transmit or receive data on the at least portion of the TO according to the selection.

[0015] In an eleventh aspect, a terminal device is provided. The terminal device includes: a receiving circuitry configured to receive scheduling information from a network device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; a selection circuitry configured to select time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least portion does not span the at least one SBFD symbol and the at least one non-SBFD symbol; and a transmitting / receiving circuitry configured to transmit or receive data on at least a portion of the selected TO.

[0016] In a twelfth aspect, a network device is provided. The network device includes: a transmitting circuit system configured to transmit scheduling information to a terminal device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; a selection circuit system configured to select time domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least portion does not span the at least one SBFD symbol and the at least one non-SBFD symbol; and a transmitting / receiving circuit system configured to transmit or receive data on the at least portion of the selected TO.

[0017] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

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

[0019] Figure 1A An example communication network in which embodiments of this disclosure may be implemented is shown.

[0020] Figure 1B An example of Physical Uplink Shared Channel (PUSCH) repetition type A in Rel-15 is shown;

[0021] Figure 1C The bit selection for PUSCH repeat type A with redundant version (RV) cycles is shown;

[0022] Figure 1D An example of PUSCH repeat type A in Rel-17 is shown;

[0023] Figure 1E The power spectral density gain supplied by multi-slot transport block processing (TBoMS) is shown for the same transport block size (TBS) compared to a single-slot PUSCH.

[0024] Figure 1F An example of time-domain resource allocation for TBoMS is shown;

[0025] Figure 1G The bit selection for a single TBoMS transmission is shown;

[0026] Figure 1H An example of TBoMS repetition is shown;

[0027] Figure 1I This demonstrates frequency and time resource allocation using SBFD compared to traditional FDD and TDD;

[0028] Figure 1J Examples of SBFD and non-SBFD time slots are shown;

[0029] Figure 1K This illustrates the types of co-channel interference in SBFD deployments;

[0030] Figure 1L Examples of SBFD and non-SBFD symbols in special time slots are shown;

[0031] Figure 1M An example of PUSCH repetition in SBFD starting from the full UL time slot is shown;

[0032] Figure 2 Examples of process flows according to some exemplary embodiments of this disclosure are shown;

[0033] Figure 3 An example of UL transmission timing in a hybrid time slot is shown;

[0034] Figure 4 Another example of a process flow according to some exemplary embodiments of this disclosure is shown;

[0035] Figure 5 A flowchart is shown illustrating an example method implemented at a terminal device according to some embodiments of the present disclosure;

[0036] Figure 6 Another flowchart is shown, illustrating an example method implemented at a network device according to some embodiments of this disclosure;

[0037] Figure 7 A simplified block diagram of a device suitable for implementing some example embodiments of this disclosure is shown; and

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

[0039] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

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

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

[0042] References to "an embodiment," "an embodiment," "an exemplary embodiment," etc., in this disclosure indicate that the described embodiments may include specific features, structures, or characteristics, but not every embodiment includes that specific feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a specific feature, structure, or characteristic is described in connection with an embodiment, it should be understood that, whether explicitly described or not, incorporating other embodiments to affect such feature, structure, or characteristic is within the knowledge of those skilled in the art.

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

[0044] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that, when used herein, the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” specify the presence of the stated features, elements, and / or components, 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 the following: ” and “at least one of ” and similar wording, where the list of two or more elements is connected by “and” or “or”, means at least any one element, or at least any two or more elements, or at least all elements.

[0045] As used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions and (c) (Multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or a portion of (multiple) microprocessors) that require software (e.g., firmware) to operate, but may not exist when operation does not require software.

[0046] This definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers only the implementation of hardware circuitry or a processor (or multiple processors) or portions thereof and their accompanying software and / or firmware. The term "circuit system" also covers, for example, if applicable to a particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, cellular network device, or other computing or networking device.

[0047] As used herein, the terms “network,” “communication network,” or “data network” refer to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Wi-Fi, and so on. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocols, including but not limited to fourth-generation (4G), 4.5G, future fifth-generation (5G), the IEEE 802.11 communication protocol, and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that this disclosure can utilize. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0048] As used herein, the term "network device" refers to a node in a communication network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS), access point (AP), or transmit and receive point (TRP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NRNB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a WiFi device, a repeater, or a low-power node (such as a femtosecond, picosecond, etc.). In the following description, the terms "terminal device," "AP device," "AP," and "access point" are used interchangeably.

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

[0050] For illustrative purposes, the principles and exemplary embodiments of this disclosure will be referenced below. Figures 1A to 8 The embodiments described herein are provided to enable those skilled in the art to understand the inventive concept of this disclosure and to implement the solutions presented herein, and are not intended to limit the scope of the application in any way.

[0051] Figure 1A Examples of application scenarios 100 in which some exemplary embodiments of this disclosure may be implemented are shown. Application scenario 100 (which is part of a communication network) includes terminal devices and network devices.

[0052] In the description of the currently disclosed exemplary embodiments, network environment 100 may also be referred to as communication system 100 (e.g., part of a communication network). For illustrative purposes only, the aspects of the exemplary embodiments will be described in the context of one or more terminal devices and network devices communicating with each other. However, it should be understood that the description herein can be applied to other types of devices or other similar devices that are referenced using other terms.

[0053] like Figure 1AAs shown, the communication network 100 may include a network device 110 (which may also be referred to as a gNB or BS). The communication network 100 may also include a terminal device 120 (which may also be referred to as a user equipment 120 or UE 120). Although only one network device 110 and one terminal device 120 are present in the diagram... Figure 1A The number of network devices and terminal devices is not limited, although it is shown in the diagram. In other words, there can be one or more network devices 110 and one or more terminal devices 120 in the network.

[0054] Network device 110 can provide services to terminal device 120, and network device 110 and terminal device 120 can transmit data and control information to each other. In some embodiments, network device 110 and terminal device 120 can communicate with a direct link / channel.

[0055] In communication system 100, the link from network device 110 to terminal device 120 is called the downlink (DL), and the link from terminal device 120 to network device 110 is called the uplink (UL). In the downlink, network device 110 is a transmitting (TX) device (or transmitter), and terminal device 120 is a receiving (RX) device (or receiver). In the uplink, terminal device 120 is a transmitting (TX) device (or transmitter), and network device 110 is an RX device (or receiver). It should be understood that network device 110 can provide one or more serving cells. Figure 1A As shown, network device 110 provides a serving cell 102, and a terminal device resides on serving cell 102. In some embodiments, network device 110 is capable of providing multiple serving cells, and terminal device 120 can hand over from a source cell to a target cell between serving cells during its mobility. It should be understood that... Figure 1A The number of serving cells shown is for illustrative purposes and does not imply any limitation.

[0056] Communication in network environment 100 can be implemented according to any suitable communication protocol, including but not limited to wireless network communication protocols such as fourth-generation (4G) and fifth-generation (5G), wireless local area network communication protocols (such as IEEE 802.11), and / or any other protocol currently known or to be developed in the future. Furthermore, communication can 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 Multiple Access (OFDM), Discrete Fourier Transform Spread Spectrum Orthogonal Frequency Division Multiplexing (DFT-s-OFDM), and / or any other technology currently known or to be developed in the future.

[0057] It should be understood that the number of devices as well as their connection relationships and types shown Figure 1A are for illustrative purposes and do not imply any limitations. The communication system 100 may include any suitable number of devices suitable for implementing embodiments of the present disclosure.

[0058] Rel-15 introduced the slot aggregation feature for the Physical Uplink Shared Channel (PUSCH), which is also referred to as PUSCH repetition type A. In this feature, the transmission of the transport block is repeated over multiple slots. The following key design aspects of PUSCH repetition type A in Rel-15 can be noted: • Resource allocation: The same resource allocation is applied across PUSCH repetitions. o Time domain: Each repetition is in one slot. Only the single start and length of the PUSCH within the slot are indicated, i.e., a single Start and Length Indicator Value (SLIV). The same start and length indicated by a single SLIV are applied across all PUSCH repetitions. In Rel-15, the number of repetitions for PUSCH repetition type A is semi-statically configured in the RRC, and the number of repetitions is counted according to consecutive physical slots, as Figure 1B shown in Figure 1B FIG. shows an example of PUSCH repetition type A with 4 repetitions in Rel-15, S = 5 and L = 7, assuming the DDSUU (10D:XG:2U) TDD mode. If the number of available symbols in the slot is not sufficient (<l), the PUSCH repetition is not transmitted in the slot. o Frequency domain: The PUSCH repetitions have the same frequency domain resource allocation (i.e., the same number of Physical Resource Blocks (PRBs), and if frequency hopping is not enabled, the positions of these PRBs in the frequency domain may be the same). • Transport Block Size (TBS) determination: Ninfo for PUSCH repetition type A is calculated based on the number of REs determined in the slot. • Rate matching: The same or different redundant versions (RVs) of the coded bits in the cyclic buffer can be applied for each PUSCH repetition. The RV for the first repetition can be indicated by scheduling the DCI for the dynamic grant or pre-configured for the configured grant. If different RVs are applied, the RVs are cycled from the configured RV sequence, following the indicated RV for the first repetition. There are four RVs, and each RV provides information about the bits encoded starting from the beginning of the cyclic buffer. The UE should map to the PUSCH transmission associated with the RV, as Figure 1C shown in Figure 1CThe bit selection for PUSCH repeat type A with RV cycle is shown.

[0059] Rel-16 allows for dynamic indication of the number of repetitions for PUSCH repetition type A by associating the number of repetitions with each row of the Time Domain Resource Assignment (TDRA) table. Furthermore, Rel-16 introduces PUSCH repetition type B for Ultra-Reliable Low Latency (URLLC) applications. In this feature, a single SLIV is used to determine back-to-back nominal repetitions of equal length, and each nominal repetition is capable of spanning a slot boundary. If each nominal repetition spans a slot boundary or is an invalid symbol, it is then split into multiple actual repetitions. PUSCH repetitions in PUSCH repetition type B also have the same frequency domain resource allocation. It should be noted that this type of PUSCH repetition is added solely for completeness.

[0060] Rel-17 further improves PUSCH repetition type A by allowing the number of repetitions to be counted based on available time slots, such as Figure 1D As shown, Figure 1D An example of PUSCH repeat type A with 4 repetitions is shown in Rel-17, with S=5 and L=7, assuming the DDSUU (10D:2G:2U) TDD pattern. Rel-17 also increases the maximum number of repetitions for PUSCH repeat type A from 16 to 32.

[0061] Rel-17 Coverage Enhancement WI specifies a feature called Transport Block Processing via Multi-Slot (TBoMS). This feature allows a single transport block (TB) to be mapped onto multiple slots, meaning that resource allocation for a single PUSCH transport can span multiple slots. This differs from PUSCH repetition.

[0062] Figure 1E The power spectral density gain supplied by multi-slot transport block processing (TBoMS) is shown for the same transport block size (TBS) compared to a single-slot PUSCH. Figure 1E As shown, a key advantage of TBoMS is its ability to reduce the number of PRBs required to transmit the same Transport Block Size (TBS) compared to when TBs are transmitted in a single timeslot. This helps improve the Energy Per Resource Element (EPRE), thus increasing coverage.

[0063] Some key design aspects of TBoMS can be summarized as follows: • Resource allocation: o Time Domain: A new column has been added to the TDRA table to indicate the number of time slots allocated for TBoMS. ). It is counted based on available time slots (following the Rel-17 rule for counting based on available time slots for PUSCH repetition type A). Therefore, non-contiguous time slots can be used for TBoMS in TDD. The same start symbol (S) and length (L) of the resources allocated in each time slot for TBoMS (similar to repetition type A) are used. Figure 1F As shown, Figure 1F It shows the target for having An example of time-domain resource allocation for TBoMS. o Frequency domain: The same number of PRBs across time slots are allocated for TBoMS transmission (similar to repetition type A). • TBS determines: N for TBoMS Info Scaling is based on the number of REs determined in the first time slot allocated for TBoMS. Calculated, of which This is the number of time slots allocated for TBoMS. In other words, the TBS for TBoMS is calculated based on the total resources allocated for TBoMS across multiple time slots. • Rate matching: o Only a single redundant version is used for a single TBoMS (i.e., no RV loop within a single TBoMS). Bit selection and bit interleaving from the circular buffer are performed in time slots. For bit selection within a time slot, the index of the starting encoded bit in the circular buffer is a continuous index from the position of the last bit selected from the previously allocated time slot, regardless of whether UCI multiplexing occurred in a previously allocated time slot. Figure 1G As shown, Figure 1G It shows the target for having =3 bits selected for a single TBoMS transmission. o TBoMS transmission is limited to only one encoded block. • Repetition of a single TBoMS: Repetition of a single TBoMS is supported. The column in the TDRA table that indicates the number of repetitions for Rel-17 PUSCH repetition type A (i.e., numberOfRepetitions-r17) is also used to indicate the number of repetitions (Nrep) for a single TBoMS. o UE determines the repetition used for TBoMS There are 10 available time slots, each with the same S and L, but TBS will be calculated using the resources of a single TBoMS (i.e., per TBoMS). Scaling). Figure 1HIt shows having and Examples of TBoMS repetition. Redundant versions (RVs) are repeated across TBoMS. The traditional Rel-15 / 16 RV sequence and RV index indicator are reused.

[0064] Rel-18 is a research project on duplex evolution, including Subband Non-Overlapping Full-Duplex (SBFD). 3GPP 5G NR currently supports two duplex modes: FDD for paired frequency bands and TDD for unpaired frequency bands. In TDD, time-domain resources are split between the downlink and uplink. The allocation of limited duration for the uplink in TDD results in reduced coverage, increased latency, and decreased capacity.

[0065] As a result, 3GPP has agreed to initiate the Rel-18 research project (RP-213591) on the evolution of duplex operation in NR, which addresses the aforementioned challenges. One of the goals of this research project is to allow simultaneous DL and UL transmissions on different Physical Resource Blocks (PRBs) / subbands within unpaired broadband NR cells, such as... Figure 1I As shown, Figure 1I This demonstrates the use of SBFD for frequency-time resource allocation compared to conventional FDD and TDD. In this disclosure, it is also referred to as Subband Non-overlapping Full-Duplex (SBFD). In other sources, this duplex scheme is also known as Cross-Split-Duplex (xDD) or Flexible Split-Duplex (FDU).

[0066] The following are some of the most relevant objectives of this disclosure from the research project (RP-213591) described in the research project description.

[0067] The following is an example of the definition of an SBFD time slot. Figure 1J Examples of SBFD and non-SBFD time slots are shown. From the above description of SBFD operation, it can be observed that, as Figure 1J As shown, both DL and UL transmissions have two timeslot types: • SBFD time slot, during which both non-overlapping DL subbands and (multiple) UL subbands exist; and • Non-SBFD time slots: During non-SBFD time slots, the entire frequency band is used for DL ​​or UL (i.e., conventional / full DL / UL time slots).

[0068] Several SBFD operating modes have been studied, including whether the time and frequency positions of the subbands for SBFD operation are known to the SBFD-aware UE. However, it was agreed at the 3GPP RAN1#110 meeting that operating modes where the time and frequency positions of the subbands for SBFD operation are known to the SBFD-aware UE are prioritized. This means that SBFD slots should be known to the (SBFD-aware) UE in some way.

[0069] It should be noted that cross-link interference (CLI) exists on the SBFD time slot. This is explained in Nokia's Tdoc (R1-2207267) for the RAN1#110 meeting, and... Figure 1K As shown, SBFD introduces a new type of CLI: co-channel subband CLI. This interference can be better classified as: 1. gNB self-interference. 2. CLI between UEs on the same channel within the cell. 3. Inter-UE CLI on the same channel subband between UEs within a small interval. 4. gNB to gNB co-channel subband CLI. In addition to these new CLI types, in cases of different frequency domain allocations in adjacent cells, the system may also suffer from intra-channel CLI, i.e. CLI transmitted from overlapping frequency resources: 5. CLI in the same channel subband between gNB and gNB. 6. CLI on the same channel between UEs.

[0070] For SBFD operation, one design aspect to consider is whether a time slot can consist of both SBFD and non-SBFD symbols. Another design aspect for SBFD operation could be whether transmission can span across SBFD and non-SBFD symbols, including: a) Transmissions spanning multiple time slots, each time slot consisting of symbols of the same symbol type, and the symbol type may differ from one time slot to another from multiple time slots (e.g., PUSCH repeat or TBoMS); and b) Transmission of SBFD symbols and non-SBFD symbols across a time slot (e.g., a single PUSCH or PUSCH repetition). In this regard, the following can be observed: • Given that one of the main motivations for introducing SBFD operation is for UL coverage enhancement (supplying more UL resources), and PUSCH repeat / TBoMS is a fundamental feature that will be used when coverage is insufficient, scenarios in which PUSCH repeat / TBoMS spans SBFD and non-SBFD time slots should be supported. • Furthermore, it is easy to observe that, at least for (traditional) special time slots (consisting of DL, gaps, and UL symbols), time slots composed of both SBFD and non-SBFD symbols should be supported, such as... Figure 1L As shown in the image.

[0071] Although it is easy to see from the above observations that time slots can consist of both SBFD and non-SBFD symbols, 3GPP Radio Access Network (RAN) Working Group (WG) 1 (i.e., RAN1) is still discussing whether transmissions within a time slot can span both SBFD and non-SBFD symbols. In fact, as discussed in R1-2301411, the focus is primarily on current hardware implementations. Specifically, • From the NW's perspective, switching between SBFD and non-SBFD symbols may require a transition protection period to switch panels, tuning filters, and adjust timing, which may interrupt transmission or reception (the NW may use one panel for UL reception in an SBFD symbol and two panels in a UL symbol). • From the UE's perspective, an SBFD-aware UE may need to retune the filters and adjust the UL sampling rate from SBFD to UL-SB. For other examples of switching from DL to SBFD, an SBFD-aware UE may adjust the filtering between DL and SBFD symbols, which interrupts DL reception.

[0072] Therefore, two possibilities can be considered by RAN1: RAN1 can specify that the transmission cannot cross SBFD and non-SBFD symbols within the time slot, or let NW depend on the capabilities of NW and UE to configure whether the transmission can cross SBFD and non-SBFD symbols within the time slot.

[0073] However, regardless of which method is ultimately adopted, in cases where transmission cannot span SBFD and non-SBFD symbols within a time slot, the UE behavior determined by the TDRA for transmission / repetition across SBFD and non-SBFD symbols within a time slot should be defined (which is not currently available and will be proposed in this invention).

[0074] This is especially important in cases with repeated PUSCH or PDSCH, given that repeated PUSCH / PDSCH follow the same resource allocation as the one used for the first repeat, as summarized above. Therefore, consider as... Figure 1M The example shown, Figure 1M The illustration shows a PUSCH repetition with S=0 and L=14 in an SBFD starting from a full UL timeslot. If a PUSCH transmission with repetition is scheduled throughout the entire timeslot (14 symbols), the UE behavior determined by the TDRA for repetitions in timeslots consisting of both SBFD and non-SBFD symbols (hereinafter referred to as mixed timeslots) is unclear and needs to be defined / determined by the UE. Furthermore, whether a mixed timeslot is counted as an available timeslot should be specified when PUSCH repetitions are counted according to available timeslots (as summarized in the Rel-17 features above). Embodiments of this disclosure are provided in view of the above analysis and discussion.

[0075] In general, embodiments of this disclosure propose a solution for TDRA determination in cases where the Transmission Timing (TO) spans SBFD and non-SBFD symbols within a time slot. TO can refer to candidate PUSCH / PDSCH repetition within a time slot or candidate PUSCH transmission within a time slot used for TBoMS, or any RRC configuration resource for PUSCH / PDSCH transmission. In some embodiments, terminal device 120 receives scheduling information from network device 110 indicating that TO spans at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol within a time slot. Terminal device 120 can determine whether TO is valid. Herein, a TO for UL transmission is valid when all resource elements (REs) in TO are uplink REs and available for UL transmission; or similarly, a TO for DL ​​transmission is valid when all resource elements (REs) in TO are downlink REs and available for DL ​​transmission. If TO is valid, terminal device 120 selects time-domain resources for at least a portion of TO such that the at least portion does not span at least one SBFD symbol and at least one non-SBFD symbol, and transmits or receives data on the selected at least portion of TO. In some embodiments, network device 110 may send scheduling information to terminal device 120 instructing TO to span at least one SBFD symbol and non-SBFD symbol in a time slot, select time-domain resources, and perform transmission or reception accordingly, so that both parties operate on the same resources.

[0076] Figure 2 Examples of process flows according to some exemplary embodiments of the present disclosure are shown. For ease of understanding, process flow 400 will be referenced. Figure 1A It is described. It should be understood that although process flow 200 has been described with reference to communication network 100 in Figure 1, process flow 200 can also be applied to other similar communication scenarios.

[0077] like Figure 2As shown, network device 110 sends (201) scheduling information to terminal device 120, which indicates the transmission timing (TO) across at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot. Correspondingly, terminal device 120 receives (202) the scheduling information.

[0078] In some embodiments, TO can be a UL or DL ​​transmission timing (e.g., for PUSCH or PDSCH). In some embodiments, TO can be used for data duplication, or authorized resources configured by TBoMS or RRC. The time slots scheduled on TO can consist of both SBFD and (multiple) non-SBFD symbols, and can be referred to as hybrid time slots.

[0079] Figure 3 An example of a TO in a hybrid time slot is shown, which consists of SBFD symbols, non-SBFD symbols, and (optionally) gap symbols. As shown, SBFD symbols may include both uplink (UL) and downlink (DL) frequency resources, and non-SBFD symbols may include either UL or DL ​​frequency resources. Multiple gap symbols (if any) may include guard time resources.

[0080] It is worth noting that in some embodiments, no special treatment is proposed for the TO portion of the gap symbol. Therefore, for simplicity, only SBFD symbols and non-SBFD symbols are mentioned below, which means that gap symbols (if any) can be included in either SBFD or non-SBFD symbols. Thus, both network device 110 and terminal device 120 can use any gap symbol in the time slot that includes protection time resources as either an SBFD or non-SBFD symbol.

[0081] Upon receiving the scheduling information (202), terminal device 120 determines (204) that the TO is valid. Based on the determination that the TO is valid, terminal device 120 selects (206) at least a portion of the time-domain resources for the TO, such that the at least portion does not span at least one SBFD symbol and at least one non-SBFD symbol. Correspondingly, network device 110 also determines (203) that the TO is valid, and based on the determination that the TO is valid, selects (205) at least a portion of the time-domain resources for the TO, such that the at least portion does not span at least one SBFD symbol and at least one non-SBFD symbol. By doing so, terminal device 120 and network device 110 can align the time resources used for data transmission or reception.

[0082] Network device 110 transmits (207) data on at least a portion of the selected TO. Correspondingly, terminal device 120 receives (208) data on at least a portion of the selected TO.

[0083] Alternatively or otherwise, terminal device 120 transmits (210) data on at least a portion of the selected TO. Correspondingly, network device 110 receives (209) data on at least a portion of the selected TO.

[0084] Figure 4 Another example of a process flow according to some example embodiments of this disclosure is shown. Figure 4 In this context, gNB410 can be an example implementation of network device 110, and the UE can be... Figure 1A Example implementation of terminal devices in [the context].

[0085] At step 401, gNB 410 may indicate to UE 420, and UE 420 may receive a configuration set via radio resource control messages or downlink control information (DCI).

[0086] In some embodiments, UE 420 may be indicated, for example, a frequency band. Alternatively or additionally, UE 420 may indicate the number of time slots / symbols and the location of these time slots / symbols in a radio frame, wherein the frequency band is divided into multiple sub-bands, and at least one sub-band is used for DL ​​transmission, and at least one sub-band is used for UL transmission, i.e., sub-band full-duplex (SBFD) time slots / symbols. UE 420 may indicate the number of time slots / symbols and the location of these time slots / symbols in a radio frame, wherein the entire frequency band is used for DL ​​transmission or UL transmission, i.e., non-SBFD time slots / symbols. Alternatively or additionally, UE 420 may indicate the number and location of (if any) gap symbols in a particular time slot.

[0087] At step 402, gNB 410 may indicate to UE 420, and UE 420 may receive (e.g., via RRC) an indication that transmission across SBFD and non-SBFD symbols within a time slot is not permitted. Note that this step is not required if the specification hardcodes that transmission across SBFD and non-SBFD symbols within a time slot is not permitted. Furthermore, the order of steps 401 and 402 may be interchanged or combined; for clarity, they are separated herein.

[0088] At step 403, gNB 410 may send scheduling information to UE 420, which indicates the transmission timing (TO). This time slot may include both SBFD symbols and (multiple) non-SBFD symbols. Figure 3As shown, TO can span at least one of the SBFD symbols and at least one of the non-SBFD symbols(s) in a mixed time slot. In some embodiments, TO can be a UL or DL ​​transmission timing (e.g., for PUSCH or PDSCH). In some embodiments, TO can be used for data duplication, or authorized resources configured by TBoMS or RRC.

[0089] At step 404, UE 420 may also determine the resources in TO used for (multiple) actual transmissions and the number to be accumulated to the total number of repetitions (in the case that TO is used for PUSCH repetitions and when counting based on available time slots is enabled by gNB410).

[0090] At step 405, UE 420, based on the result of step 404, sends or receives data on the identified resources in TO used for (multiple) actual transmissions.

[0091] At step 404, UE 420 may first determine whether the TO is valid, and then apply different methods. In some embodiments, a TO for UL transmission may be determined to be valid when all REs in the TO are UL REs and can be used for UL transmission; or a TO for DL ​​transmission may be determined to be valid when all REs in the TO are DL REs and can be used for DL ​​transmission. Otherwise, the TO may be determined to be invalid.

[0092] When UE 420 determines that a TO is valid, it can select time-domain resources for at least a portion of the TO such that the at least portion does not span at least one SBFD symbol and at least one non-SBFD symbol. In some embodiments, UE 420 can determine that the TO is valid and transmit (e.g., rate-matched) or receive data only on the portion of the TO in either an SBFD symbol or a non-SBFD symbol. The at least portion of the TO can be a first portion of the TO in at least one SBFD symbol, or a second portion of the TO in at least one non-SBFD symbol. Therefore, UE 420 can transmit or receive data on one portion of the first portion or the second portion of the TO, and disable the transmission or reception of data on the other portion of the first portion or the second portion of the TO.

[0093] In some embodiments, which portion of the first and second parts of the TO is used for transmission or reception can be determined based on a pre-configured configuration. This pre-configured configuration can be hard-coded in the specification or configured by the gNB 410, for example, via RRC configuration. In some embodiments, the specification can be hard-coded to specify that the UE 420 always transmits or receives data only on the portion of the TO in the SBFD symbol. Alternatively, the specification can be hard-coded to specify that the UE 420 always transmits or receives data only on the portion of the TO outside the SBFD symbol.

[0094] In some embodiments, which portion of the first part and the second part of the TO is used for transmission or reception can be determined based on its length (e.g., the longer one). UE 420 may first determine the longer portion of the TO (with a higher symbol number) between the first part of the TO in an SBFD symbol and the second part of the TO in a non-SBFD symbol. Then, UE 420 may transmit or receive data only on the determined longer portion of the TO.

[0095] In some embodiments, when TO is used for data repeats (e.g., PUSCH repeats) with a number of repeats counted according to the available time slots, UE 420 may count the repeats for the data repeats with respect to that time slot.

[0096] The above describes a method in which UE 420 transmits or receives data only on a portion of TO, such that TO does not cross SBFD symbols and non-SBFD symbols. Alternatively or additionally, UE 420 may transmit or receive data on two separate portions of TO, wherein each portion of TO does not cross SBFD symbols and non-SBFD symbols.

[0097] In some embodiments, the TO is considered a nominal TO, referred to as the first TO. The UE 420 may determine that the nominal TO is split into two valid actual TOs, referred to as the second TO and the third TO. The nominal TO here can be understood as a nominal existence, i.e., the actual TO is determined based on the nominal TO. One actual TO occupies the portion of the nominal TO in an SBFD symbol, and one actual TO occupies the portion of the nominal TO in a non-SBFD symbol. The UE 420 then transmits (e.g., rate-matched) or receives data on these two actual TOs. Alternatively or additionally, if the TO is used for PUSCH repetition and counting based on available time slots is enabled, the time slot is counted as two repetitions.

[0098] In some embodiments, when the nominal TO is used for data repetition (e.g., for PUSCH), two actual TOs can be considered as two repetitions, and different redundancy versions (RVs) can be used for rate matching. When the number of repetitions is counted based on the available time slots, the UE 420 can count two repetitions for data repetition with respect to that time slot due to two data transmissions.

[0099] In some embodiments, when a nominal TO is used for Transport Block Processing (TBoMS) across multiple time slots, two actual TOs are treated as two transmission attempts for the same transport block (TB). The two actual TOs can use the same RV for rate matching, and data is rate matched consecutively across the two TOs (similar to what is done for TBoMS across time slots).

[0100] When selecting time resources for a TO, UE 420 can determine whether a portion of the TO (e.g., within an SBFD symbol) overlaps with any other UL or DL ​​transmission (regardless of whether the TO is prioritized). If an overlap exists, UE 420 can transmit or receive data only on the portion of the TO that does not overlap with other UL or DL ​​transmissions. Otherwise, the above-described embodiment is applied, i.e., the non-overlapping portion is included in at least a portion of the selected TO such that it satisfies the constraint regarding not crossing SBFD symbols and non-SBFD symbols.

[0101] The embodiments for valid TOs have been described above. When UE 420 determines that a TO is invalid, it does not transmit or receive data on that TO. In some embodiments, it may transmit or receive data on an invalid TO. In cases where the TO is used for data repetitions with a repetition number counted according to the available time slots, UE 420 may skip counting according to that time slot.

[0102] Although the discussion of steps 404 and 405 is from the perspective of UE 420, it should be understood that the same actions also apply to network device 110. Therefore, for the sake of brevity, the details from the perspective of network device 110 are omitted.

[0103] In view of the above, embodiments of this disclosure define the behavior of terminal devices and network devices for transmissions spanning SBFD and non-SBFD symbols determined by the TDRA when transmissions cannot cross SBFD and non-SBFD symbols within a time slot (whether not supported by hardware implementation, by network configuration, or fixed by specification). In some embodiments, repeated PUSCH or PDSCH are also enhanced for this situation.

[0104] Figure 5A flowchart of an example method 500 implemented at a terminal device according to some other embodiments of the present disclosure is shown. For ease of understanding, method 500 will be referenced. Figure 1A It is described from the perspective of terminal device 120.

[0105] At block 510, terminal device 120 receives scheduling information from network device 110, which indicates the transmission timing (TO) across at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot. In some embodiments, the at least one SBFD symbol may include both uplink (UL) frequency resources and downlink (DL) frequency resources. The at least one non-SBFD symbol may include either UL frequency resources or DL ​​frequency resources. In some embodiments, the time slot may include one or more gap symbols, which may include guard time resources. Terminal device 120 may consider the one or more gap symbols as either SBFD symbols(s) or non-SBFD symbols(s).

[0106] At block 520, based on determining that TO is valid, terminal device 120 selects at least a portion of the time-domain resources for TO such that the at least portion does not span at least one SBFD symbol and at least one non-SBFD symbol.

[0107] At block 530, terminal device 120 sends or receives data on at least a portion of the selected TO.

[0108] In some embodiments, at least a portion of TO may be a first portion of TO in at least one SBFD symbol, or a second portion of TO in at least one non-SBFD symbol. Terminal device 120 may transmit or receive data on one portion of the first portion or the second portion of TO, and disable the transmission or reception of data on the other portion of the first portion or the second portion of TO.

[0109] In some embodiments, one of the first portion and the second portion of the TO is determined based on a pre-configured configuration. This pre-configured configuration may be hard-coded in a specification or configured by network device 110, for example, via RRC configuration. Alternatively or additionally, one of the first portion and the second portion of the TO may have more symbols than the other portion.

[0110] In some embodiments, where TO can be used for data repetitions having a number of repetitions counted according to the available time slots, the terminal device 120 can count the time slot as a repetition for the data repetition.

[0111] In some embodiments, TO is a first TO, and the terminal device can perform selection by splitting the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol, and can send or receive data on the second TO and on the third TO.

[0112] In some embodiments, when TO is used for data duplication, the second TO and the third TO may use different redundancy versions (RVs) for rate matching. Alternatively or additionally, when the number of duplications is calculated based on the available time slots, the terminal device 120 may count the time slot as two duplications for data duplication.

[0113] In some embodiments, when the TO is used for multi-slot transport block processing (TBoMS), the second TO and the third TO may have the same RV for rate matching.

[0114] In some embodiments, terminal device 120 may determine whether the TO overlaps with any other UL or DL ​​transmission. Based on the determination that the TO overlaps with other UL or DL ​​transmissions, terminal device 120 may transmit or receive data on the non-overlapping portion of the TO that does not overlap with other UL or DL ​​transmissions. This non-overlapping portion may be included in at least a portion of the selected TO.

[0115] In some embodiments, based on determining that a TO is invalid, the terminal device 120 may disable the transmission or reception of data on the TO that is determined to be invalid. Alternatively or additionally, if the TO is used for data repetitions with a number of repetitions counted according to the available time slots, the terminal device 120 may skip counting according to that time slot.

[0116] Figure 6 Another flowchart of an example method implemented at a network device according to some embodiments of the present disclosure is shown. For ease of understanding, method 600 will refer to Figure 1A It is described from the perspective of network device 110.

[0117] At block 610, network device 110 sends scheduling information to terminal device 120, indicating the transmission timing (TO) across at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot. In some embodiments, the at least one SBFD symbol may include both uplink (UL) frequency resources and downlink (DL) frequency resources. The at least one non-SBFD symbol may include either UL frequency resources or DL ​​frequency resources. In some embodiments, a time slot may include one or more gap symbols, which may include guard time resources. Terminal device 120 may consider the one or more gap symbols as either SBFD symbols(s) or non-SBFD symbols(s).

[0118] At block 620, based on the determination that TO is valid, network device 110 selects time-domain resources for at least a portion of the TO such that the at least portion does not span at least one SBFD symbol and at least one non-SBFD symbol.

[0119] At block 630, network device 110 sends or receives data on at least a portion of the selected TO.

[0120] In some embodiments, at least a portion of TO may be a first portion of TO in at least one SBFD symbol, or a second portion of TO in at least one non-SBFD symbol. Network device 110 may transmit or receive data on one portion of the first portion or the second portion of TO, and disable the transmission or reception of data on the other portion of the first portion or the second portion of TO.

[0121] In some embodiments, one of the first portion and the second portion of the TO is determined based on a pre-configured configuration. The pre-configured configuration may be hard-coded in a specification or configured by network device 110, for example, via RRC configuration. Alternatively or additionally, one of the first portion and the second portion of the TO may have more symbols than the other portion.

[0122] In some embodiments, where TO can be used for data repetitions having a number of repetitions counted according to the available time slots, network device 110 can count the time slot as a repetition for the data repetition.

[0123] In some embodiments, TO is a first TO, and the terminal device can perform selection by splitting the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol, and can send or receive data on the second TO and on the third TO.

[0124] In some embodiments, when TO is used for data duplication, the second TO and the third TO may use different redundancy versions (RVs) for rate matching. Alternatively or additionally, when the number of duplications is counted according to the available time slots, the network device 110 may count the time slot as two duplications for data duplication.

[0125] In some embodiments, when the TO is used for multi-slot transport block processing (TBoMS), the second TO and the third TO may have the same RV for rate matching.

[0126] In some embodiments, network device 110 can determine whether the TO overlaps with any other UL or DL ​​transmission. Based on the determination that the TO overlaps with other UL or DL ​​transmissions, network device 110 can transmit or receive data on the non-overlapping portions of the TO that do not overlap with other UL or DL ​​transmissions. The non-overlapping portions can be included in at least a portion of the TO selected.

[0127] In some embodiments, network device 110 may disable the transmission or reception of data on a TO that is determined to be invalid. Alternatively or additionally, if the TO is used for data repetitions with a number of repetitions counted according to the available time slots, network device 110 may skip counting according to the time slots.

[0128] In some embodiments, the apparatus capable of performing method 500 (e.g., terminal device 120) may include components for performing the corresponding steps of method 500. These components may be implemented in any suitable form. For example, the components may be implemented as a circuit system or a software module.

[0129] In some example embodiments, the apparatus includes: components for receiving scheduling information from a network device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; components for selecting time domain resources for at least a portion of the TO based on determining that the TO is valid, such that at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol; and components for transmitting or receiving data on at least a portion of the selected TO.

[0130] In some embodiments, at least a portion of the TO is a first portion of the TO in at least one SBFD symbol, or a second portion of the TO in at least one non-SBFD symbol, and the component for transmitting or receiving data on at least a portion of the selected TO may include: a component for transmitting or receiving data on one portion of the first portion or the second portion of the TO, and a component for disabling the transmission or reception of data on the other portion of the first portion or the second portion of the TO.

[0131] In some embodiments, one of the first portion of TO and the second portion of TO may be determined based on a pre-configured configuration.

[0132] In some embodiments, one of the first part and the second part of TO may have more symbols than the other part.

[0133] In some embodiments, when TO is used for data repetitions having a number of repetitions counted according to available time slots, the apparatus may include components for counting the time slot as a repetition for the data repetition.

[0134] In some embodiments, the TO may be a first TO, and the components for selecting time-domain resources for at least a portion of the TO may include: components for splitting the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol, and the components for transmitting or receiving data on at least a portion of the selected TO may include: components for transmitting or receiving data on the second TO and for transmitting or receiving data on the third TO.

[0135] In some embodiments, when TO is used for data duplication, the second TO and the third TO may use different redundant versions (RV) for rate matching.

[0136] In some embodiments, the apparatus may further include a component for counting the time slot as two repetitions for data repetition, provided that the number of repetitions is counted based on the available time slots.

[0137] In some embodiments, when the TO is used for multi-slot transport block processing (TBoMS), the second TO and the third TO have the same RV for rate matching.

[0138] In some embodiments, at least one SBFD symbol may include both uplink (UL) frequency resources and downlink (DL) frequency resources; and at least one non-SBFD symbol may include either UL frequency resources or DL ​​frequency resources.

[0139] In some embodiments, the apparatus may include a component for treating any gap symbol in a time slot that includes a protected time resource as an SBFD symbol or a non-SBFD symbol.

[0140] In some embodiments, the apparatus may include: a component for determining whether the TO overlaps with any other UL or DL ​​transmission; and a component for transmitting or receiving data on a non-overlapping portion of the TO that does not overlap with other UL or DL ​​transmissions based on the determination that the TO overlaps with other UL or DL ​​transmissions, wherein the non-overlapping portion is included in at least a portion of the TO selected.

[0141] In some embodiments, the apparatus may include components for disabling the transmission or reception of data on a TO based on the determination that the TO is invalid.

[0142] In some embodiments, the apparatus may include a component for skipping counting based on the available time slots in the case of data repetitions having a number of repetitions counted according to the available time slots.

[0143] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 500. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

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

[0145] In some exemplary embodiments, the apparatus includes: components for sending scheduling information to a terminal device, the scheduling information indicating a transmission timing (TO) spanning at least one sub-band full-duplex (SBFD) symbol and at least one non-SBFD symbol in a time slot; components for selecting time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol; and components for transmitting or receiving data on at least a portion of the selected TO.

[0146] In some embodiments, at least a portion of the TO is a first portion of the TO in at least one SBFD symbol, or a second portion of the TO in at least one non-SBFD symbol, and the component for transmitting or receiving data on at least a portion of the selected TO may include: a component for transmitting or receiving data on one portion of the first portion or the second portion of the TO, and a component for disabling the transmission or reception of data on the other portion of the first portion or the second portion of the TO.

[0147] In some embodiments, one of the first portion of TO and the second portion of TO may be determined based on a pre-configured configuration.

[0148] In some embodiments, one of the first part and the second part of TO may have more symbols than the other part.

[0149] In some embodiments, when TO is used for data repetitions having a number of repetitions counted according to available time slots, the apparatus may include components for counting the time slot as a repetition for the data repetition.

[0150] In some embodiments, the TO may be a first TO, and the components for selecting time-domain resources for at least a portion of the TO may include: components for splitting the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol, and the components for transmitting or receiving data on at least a portion of the selected TO may include: components for transmitting or receiving data on the second TO and for transmitting or receiving data on the third TO.

[0151] In some embodiments, when TO is used for data duplication, the second TO and the third TO may use different redundant versions (RV) for rate matching.

[0152] In some embodiments, the apparatus may further include a component for counting the time slot as two repetitions for data repetition, provided that the number of repetitions is counted based on the available time slots.

[0153] In some embodiments, when the TO is used for Transport Block Processing via Multi-Time Slots (TBoMS), the second TO and the third TO have the same RV for rate matching.

[0154] In some embodiments, at least one SBFD symbol may include both uplink (UL) frequency resources and downlink (DL) frequency resources; and at least one non-SBFD symbol may include either UL frequency resources or DL ​​frequency resources.

[0155] In some embodiments, the apparatus may include components for treating any gap symbol in a time slot that includes a protected time resource as either an SBFD symbol or a non-SBFD symbol.

[0156] In some embodiments, the apparatus may include components for determining whether the TO overlaps with any other UL or DL ​​transmission; and components for transmitting or receiving data on a non-overlapping portion of the TO that does not overlap with other UL or DL ​​transmissions based on the determination that the TO overlaps with other UL or DL ​​transmissions, wherein the non-overlapping portion is included in at least a portion of the TO selected.

[0157] In some embodiments, the apparatus may include components for disabling the transmission or reception of data on a TO based on the determination that the TO is invalid.

[0158] In some embodiments, the apparatus may include a component for skipping counting based on the available time slots in the case of data repetitions having a number of repetitions counted according to the available time slots.

[0159] In some embodiments, the apparatus further includes components for performing other steps in some embodiments of method 600. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause execution of the apparatus together with the at least one processor.

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

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

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

[0163] Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not persist during power outages.

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

[0165] Embodiments of this disclosure can be implemented via program 730, enabling device 700 to execute any process of this disclosure, as referenced. Figure 4 and Figure 5The embodiments of this disclosure can also be implemented in hardware or by a combination of software and hardware.

[0166] In some embodiments, program 730 may be tangibly contained in a computer-readable medium, which may be included in device 700 (such as in memory 720) or in other storage devices accessible by device 700. Device 700 may load program 730 from the computer-readable medium into RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc.

[0167] Figure 8 A block diagram of an example of a computer-readable medium 600 according to some exemplary embodiments of the present disclosure is shown. A program 730 is stored on the computer-readable medium 600. It should be noted that, although... Figure 8 The computer-readable medium 800 is depicted in the form of a CD or DVD, but the computer-readable medium 800 may also be any other form suitable for carrying or storing the program 730.

[0168] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown or described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic circuitry, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0169] This disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions (such as instructions included in a program module) that are executed in a device on a target real or virtual processor to perform the functions described above. Figure 5 or Figure 6 The method described is 500 or 600. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can be executed on a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.

[0170] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may 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.

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

[0172] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media include electrical connections having one or more lines, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. As used herein, the term "non-transient" is a limitation of the medium itself (i.e., tangible, not signaling), not a limitation of the persistence of data storage (e.g., RAM and ROM).

[0173] Furthermore, although the operations are described in a specific order, this should not be construed as requiring that these operations be performed in the specific or sequential order shown, or that all of the operations shown be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the foregoing discussion, these details should not be considered as limiting the scope of this disclosure, but rather as descriptions of the features of particular embodiments. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination.

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

Claims

1. A terminal device, comprising: At least one processor; as well as At least one memory stores instructions that, when executed by the at least one processor, cause the terminal device to at least: Receive scheduling information from network devices, the scheduling information indicating the timing of transmission TO across at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in a time slot; Based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Sending or receiving data on at least a portion of the selected TO.

2. The terminal device of claim 1, wherein the at least portion of the TO is a first portion of the TO in the at least one SBFD symbol, or a second portion of the TO in the at least one non-SBFD symbol, and the terminal device is such that: Sending or receiving data on a portion of the first part or the second part of the TO; and Disable the transmission or reception of data on the first portion of the TO or another portion of the second portion of the TO.

3. The terminal device according to claim 2, wherein one of the first portion of the TO and the second portion of the TO is determined based on a pre-configured configuration.

4. The terminal device according to claim 2 or 3, wherein one of the first portion of the TO and the second portion of the TO has more symbols than the other portion.

5. The terminal device according to any one of claims 2 to 4, wherein, in the case where the TO is used for data repetition having a repetition number counted according to available time slots, the terminal device is further configured to: The time slot is counted as a repetition for the data repetition.

6. The terminal device according to claim 1, wherein the TO is a first TO, and the terminal device is configured such that: The selection is performed by splitting the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol; and Sending or receiving data on the second TO and sending or receiving data on the third TO.

7. The terminal device according to claim 6, wherein when the TO is used for data duplication, the second TO and the third TO use different redundancy versions RV for rate matching.

8. The terminal device according to claim 7, wherein the terminal device is further configured to: If the number of repetitions is counted based on the available time slots, the time slot is counted as two repetitions for the data repetition.

9. The terminal device according to claim 6, wherein when the TO is used for Multi-Time Slot Transport Block Processing (TBoMS), the second TO and the third TO have the same RV for rate matching.

10. The terminal device according to any one of claims 1 to 9, wherein: The at least one SBFD symbol includes both uplink UL frequency resources and downlink DL frequency resources; and The at least one non-SBFD symbol includes a UL frequency resource or a DL frequency resource.

11. The terminal device of claim 10, wherein the terminal device is configured to: treat any gap symbol in the time slot that includes a protected time resource as an SBFD symbol or a non-SBFD symbol.

12. The terminal device according to any one of claims 1 to 11, wherein the terminal device is further configured to: Determine whether the TO overlaps with any other UL or DL ​​transmission; and Based on determining that the TO overlaps with the other UL or DL ​​transmissions, data is transmitted or received on the non-overlapping portion of the TO that does not overlap with the other UL or DL ​​transmissions, wherein the non-overlapping portion is included in the at least part of the TO selected.

13. The terminal device according to any one of claims 1 to 12, wherein the terminal device is further configured to: Based on the determination that the TO is invalid, the transmission or reception of data on the TO is disabled.

14. The terminal device according to claim 13, wherein the terminal device is further configured to: In the case where the TO is used for data repetition with a number of repetitions counted according to the available time slots, counting according to the time slots is skipped.

15. A network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the network device to at least: Send scheduling information to the terminal device, the scheduling information indicating the transmission timing TO of at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in the time slot; Based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Sending or receiving data on at least a portion of the selected TO.

16. The network device of claim 15, wherein the at least portion of the TO is a first portion of the TO in the at least one SBFD symbol, or a second portion of the TO in the at least one non-SBFD symbol, and the network device is such that: Sending or receiving data on a portion of the first part or the second part of the TO; and Disable the transmission or reception of data on the first portion of the TO or another portion of the second portion of the TO.

17. The network device of claim 16, wherein one of the first portion of the TO and the second portion of the TO is determined based on a pre-configured configuration.

18. The network device of claim 16 or 17, wherein one of the first portion of the TO and the second portion of the TO has more symbols than the other portion.

19. The network device according to any one of claims 15 to 18, wherein, in the case where the TO is used for data repetition having a repetition number counted according to available time slots, the network device is further configured to: The time slot is counted as a repetition for the data repetition.

20. The network device of claim 15, wherein the TO is a first TO, and the network device is configured such that: The selection is performed by splitting the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol; and Sending or receiving data on the second TO and sending or receiving data on the third TO.

21. The network device of claim 20, wherein, in the case of data duplication by the TO, the second TO and the third TO use different redundancy versions RV for rate matching.

22. The network device of claim 21, wherein the network device is further configured to: If the number of repetitions is counted based on the available time slots, the time slot is counted as two repetitions for the data repetition.

23. The network device of claim 20, wherein when the TO is used for Multi-Time Slot Transport Block Processing (TBoMS), the second TO and the third TO have the same RV for rate matching.

24. The network device according to any one of claims 15 to 23, wherein The at least one SBFD symbol includes both uplink UL frequency resources and downlink DL frequency resources; and The at least one non-SBFD symbol includes a UL frequency resource or a DL frequency resource.

25. The network device of claim 24, wherein the network device is configured to: treat any slot symbol in the time slot that includes a protected time resource as an SBFD symbol or a non-SBFD symbol.

26. The network device according to any one of claims 15 to 25, wherein the network device is further configured to: Determine whether the TO overlaps with any other UL or DL ​​transmission; and Based on determining that the TO overlaps with the other UL or DL ​​transmissions, data is transmitted or received on the non-overlapping portion of the TO that does not overlap with the other UL or DL ​​transmissions, wherein the non-overlapping portion is included in the at least part of the TO selected.

27. The network device according to any one of claims 15 to 26, wherein the network device is further configured to: Based on the determination that the TO is invalid, the transmission or reception of data on the TO is disabled.

28. The network device of claim 27, wherein the network device is further configured to: In the case where the TO is used for data repetition with a number of repetitions counted according to the available time slots, counting according to the time slots is skipped.

29. A method comprising: Receive scheduling information from network devices, the scheduling information indicating the timing of transmission TO across at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in a time slot; Based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Sending or receiving data on at least a portion of the selected TO.

30. A method comprising: Send scheduling information to the terminal device, the scheduling information indicating the transmission timing TO of at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in the time slot; Based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Sending or receiving data on at least a portion of the selected TO.

31. An apparatus comprising: A component for receiving scheduling information from a network device, the scheduling information indicating the timing of transmission TO across at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in a time slot; A component for selecting time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Components for transmitting or receiving data on at least a portion of the selected TO.

32. An apparatus comprising: A component for sending scheduling information to a terminal device, the scheduling information indicating the timing of transmission TO across at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in a time slot; A component for selecting time-domain resources for at least a portion of the TO based on determining that the TO is valid, such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Components for transmitting or receiving data on at least a portion of the selected TO.

33. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the following: Receive scheduling information from network devices, the scheduling information indicating the timing of transmission TO across at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in a time slot; Based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Sending or receiving data on at least a portion of the selected TO.

34. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the following: Send scheduling information to the terminal device, the scheduling information indicating the transmission timing TO of at least one sub-band full-duplex SBFD symbol and at least one non-SBFD symbol in the time slot; Based on determining that the TO is valid, select time-domain resources for at least a portion of the TO such that the at least a portion does not span the at least one SBFD symbol and at least one non-SBFD symbol; as well as Sending or receiving data on at least a portion of the selected TO.

Images