Determining transmission opportunities in subband full-duplex operation

Abstract

Embodiments of this disclosure provide a solution for determining a Transmit Opportunity (TO) in subband full-duplex (SBFD) operation. In one embodiment, a terminal device receives scheduling information indicating a TO that spans at least one SBFD symbol and at least one non-SBFD symbol within a slot. Based on the determination that the TO is valid, the terminal device selects time-domain resources for at least a portion of the TO such that 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. Thus, when transmission / repetition spanning SBFD and non-SBFD symbols is not permitted, UE and network operations for determining time-domain resource allocation are defined.

Description

[Technical Field]

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

[0002] 3GPP® has agreed to initiate Rel-18 (RP-213591) on the evolution of duplex operation in new radio (NR). Specifically, downlink (DL) and uplink (UL) transmissions are permitted in different physical resource blocks (PRBs) / subbands within an asymmetric broadband NR cell, known as subband full-duplex (SBFD). In SBFD operation, there are two symbol types for both DL and UL transmissions: SBFD symbols where non-overlapping DL and UL subbands coexist, and non-SBFD symbols where the entire band is used for either DL or UL.

[0003] 3GPP® also agreed to consider the possibility of a single slot containing both SBFD and non-SBFD symbols. The behavior of UEs and networks in this type of slot has not yet been investigated. [Overview of the project]

[0004] In general, the embodiments described herein provide solutions for determining the time of operation (TO) in SBFD operation.

[0005] In a first embodiment, a terminal device is provided. The terminal device comprises at least one processor and at least one memory which stores instructions that, when executed by the at least one processor, cause the terminal device to perform at least: receive scheduling information from a network device indicating a transmit opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; select time-domain resources for at least a portion of the transmit opportunity (TO) such that at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol, based on a determination that the transmit opportunity (TO) is valid; and transmit or receive data on at least a portion of the TO according to the selection.

[0006] In a second embodiment, a network device is provided. The network device comprises at least one processor and at least one memory containing instructions that, when executed by at least one processor, cause the network device to transmit to a terminal device scheduling information indicating a transmit opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; select time-domain resources for at least a portion of the TO, based on a determination that the transmit opportunity (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 transmit or receive data on at least a portion of the TO, based on the selection.

[0007] In a third embodiment, a method is provided. This method includes receiving scheduling information from a network device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; selecting time-domain resources for at least a portion of the TO, based on a determination that the TO is valid, such that at least a portion of the TO does not span at least one SBFD symbol and at least one non-SBFD symbol; and transmitting or receiving data in at least a portion of the TO in accordance with the selection.

[0008] In a fourth embodiment, a method is provided. This method includes transmitting scheduling information to a terminal device indicating that a transmission opportunity (TO) spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; selecting time-domain resources for at least a portion of the TO, based on a determination 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 transmitting or receiving data on at least a portion of the TO in accordance with the selection.

[0009] In a fifth embodiment, the apparatus is provided. The apparatus includes means for receiving scheduling information from a network device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; means for selecting time-domain resources for at least a portion of the TO, based on a determination 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 means for transmitting or receiving data in at least a portion of the TO, based on the selection.

[0010] In a sixth embodiment, the apparatus is provided. The apparatus includes means for transmitting scheduling information to a terminal device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; means for selecting time-domain resources for at least a portion of the transmit opportunity (TO) based on a determination 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 means for transmitting or receiving data in at least a portion of the TO according to the selection.

[0011] In a seventh embodiment, a non-temporary computer-readable storage medium is provided which includes a program instruction. When executed by the device, the program instruction causes the device to at least: receive scheduling information from a network device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; select time-domain resources for at least a portion of the TO, based on a determination 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 transmit or receive data on at least a portion of the TO in accordance with the selection.

[0012] In an eighth embodiment, a non-temporary computer-readable storage medium is provided which includes a program instruction. When executed by the device, the program instruction causes the device to at least transmit scheduling information to a terminal device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; select time-domain resources for at least a portion of the TO, based on a determination 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 transmit or receive data on at least a portion of the TO in accordance with the selection.

[0013] In a ninth embodiment, a computer program is provided which, when executed by the device, causes the device to perform at least: receive scheduling information from a network device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; select time-domain resources for at least a portion of the TO, based on a determination 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 transmit or receive data on at least a portion of the TO in accordance with the selection.

[0014] In a tenth embodiment, a computer program is provided which, when executed by the device, causes the device to perform at least: transmit scheduling information to a terminal device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; select time-domain resources for at least a portion of the TO, based on a determination that the transmit opportunity (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 transmit or receive data on at least a portion of the TO, based on the selection.

[0015] In an eleventh embodiment, a terminal device is provided. The terminal device comprises: a receiving circuit configured to receive scheduling information from a network device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; a selecting circuit configured to select time-domain resources for at least a portion of the TO, based on a determination 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 a transmitting / receiving circuit configured to transmit or receive data on at least a portion of the TO according to the selection.

[0016] In a twelfth embodiment, a network device is provided. The network device comprises: a transmit circuit configured to transmit to a terminal device scheduling information indicating a transmit opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; a select circuit configured to select time-domain resources for at least a portion of the TO, based on a determination 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 a transmit / receive circuit configured to transmit or receive data on at least a portion of the TO according to the selection.

[0017] It should be understood that this abstract does not identify any important or essential features of the embodiments described herein, nor is it intended to limit the scope of this specification. Other features of this specification will be readily apparent through the following description. [Brief explanation of the drawing]

[0018] Several embodiments will be described with reference to the attached drawings. [Figure 1A] Figure 1A shows an example of a communication network in which embodiments of the present disclosure may be implemented. [Figure 1B] Figure 1B shows an example of repeating type A for a physical uplink shared channel (PUSCH) in Rel-15. [Figure 1C] Figure 1C shows the bit selection for PUSCH iteration type A with redundant version (RV) cycling. [Figure 1D] Figure 1D shows an example of PUSCH repeat type A in Rel-17. [Figure 1E] Figure 1E shows the power spectral density gain achieved by multi-slot transport block processing (TBoMS) compared to single-slot push for the same transport block size (TBS). [Figure 1F]FIG. 1F shows an example of time domain resource allocation of TBoMS. [Figure 1G] FIG. 1G shows bit selection in a single TBoMS transmission. [Figure 1H] FIG. 1H shows an example of TBoMS repetition. [Figure 1I] FIG. 1I shows frequency-time resource division by SBFD compared with conventional FDD and TDD. [Figure 1J] FIG. 1J shows examples of SBFD slots and non-SBFD slots. [Figure 1K] FIG. 1K shows the types of co-channel interference in SBFD deployment. [Figure 1L] FIG. 1L shows examples of SBFD symbols and non-SBFD symbols in special slots. [Figure 1M] FIG. 1M shows an example of PUSCH repetition in SBFD starting from a complete UL slot. [Figure 2] FIG. 2 shows an example of a process flow according to some embodiments of the present disclosure. [Figure 3] FIG. 3 shows an example of an opportunity for UL transmission in a mixed slot. [Figure 4] FIG. 4 shows another example of a process flow according to some embodiments of the present disclosure. [Figure 5] FIG. 5 is a flowchart showing an example of a method implemented in a terminal device according to an example embodiment of the present disclosure. [Figure 6] FIG. 6 is another flowchart showing an example of a method implemented in a network device according to an embodiment of the present disclosure. [Figure 7] FIG. 7 shows a simplified block diagram of a device suitable for implementing some embodiments of the present disclosure. [Figure 8] FIG. 8 is a block diagram showing an example of a computer-readable medium according to some embodiments of the present disclosure. Throughout the drawings, the same or similar reference numerals denote the same or similar components.

MODE FOR CARRYING OUT THE INVENTION

[0019] The principles of this specification will be described with reference to several examples. These examples are not intended to limit the scope of this specification, but are provided solely for illustrative purposes to help those skilled in the art understand and implement this specification. The disclosures described herein can be implemented in various ways other than those described below.

[0020] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meanings as those generally understood by a person of ordinary skill in the art to which this disclosure belongs.

[0021] In this specification, descriptions such as "one embodiment," "embodiment," and "exemplary embodiment" indicate that the described embodiment may include a particular function, structure, or feature, but not all embodiments are required to include such a particular function, structure, or feature. Furthermore, these expressions do not necessarily refer to the same embodiment. Also, if a particular function, structure, or characteristic is described in relation to an embodiment, it is within the knowledge of those skilled in the art that such function, structure, or characteristic will be affected in relation to other embodiments, whether or not it is explicitly stated.

[0022] While terms such as "first" and "second" may be used to describe various elements, these elements are not limited by these terms. These terms are simply used to distinguish elements. For example, it is possible to refer to the first element as the second element, and similarly, the second element as the first element, without departing from the scope of the examples. In this specification, the term "and / or" encompasses any combination of one or more of the terms described.

[0023] The terms used herein are intended solely to describe specific embodiments and are not intended to limit the exemplary embodiments. In this specification, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context clearly indicates otherwise. Furthermore, in this specification, the terms “equip,” “equip,” “have,” “possess,” “include,” and / or “include” identify the presence of the described features, elements, and / or components, but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. In this specification, “at least one of the following: <list of two or more elements>” and “at least one of the following: <list of two or more elements>” and similar expressions, where lists of two or more elements are linked by “and” or “or,” means at least one of the elements, at least two or more elements, or at least all of the elements.

[0024] In this application, the term "circuit" is defined as follows: (a) Hardware-only circuit implementation (such as implementation using only analog and / or digital circuits), (b) A combination of hardware circuits and software, for example (where applicable), (i) A combination of analog and / or digital hardware circuits and software / firmware, (ii) A configuration in which a part of the hardware processor, software (including a digital signal processor), software, and memory work together to enable devices such as mobile phones and servers to perform various functions. (c) Hardware circuits and / or processors (e.g., microprocessors or parts of microprocessors) that require software (e.g., firmware) for operation, where the software may not be present if it is not necessary for operation. This may refer to one, more than, or all of the above.

[0025] This definition of "circuit" applies to all uses of this term in this application, i.e., all uses in all claims. For example, as used in this application, the term "circuit" includes not only a mere hardware circuit or processor (or multiple processors), but also a part of a hardware circuit or processor and its associated software and / or firmware implementation. The term "circuit" also includes, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network, or other computing system, where applicable to a particular claim element.

[0026] In this specification, the terms “Network,” “Communication Network,” or “Data Network” refer to Long-Term Evolution (LTE), LTE-Advanced (LTE-A), Broadband Code Division Multiple Access (WCDMA®), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), Wireless Fidelity (Wi-Fi®), and others. Furthermore, communication between terminal devices and network devices / elements within a communication network may be performed in accordance with any appropriate generation of communication protocol, including but not limited to fourth-generation (4G), 4.5G, future fifth-generation (5G), IEEE 802.11 communication protocol, and / or other protocols currently known or to be developed in the future. Embodiments of this disclosure are applicable to a variety of communication systems, and given the rapid development of communication technology, there will naturally be future communication technologies and systems to which this disclosure will be embodied. The scope of this disclosure is not limited to the aforementioned systems.

[0027] In this specification, “Network device” refers to a node on a communication network from which terminal devices access the network and receive services. Network devices may include, for example, base stations (BS), access points (AP), transceiver points (TRP), node B (NodeB or NB), evolved node B (eNodeB or eNB), NR node B (also called gNB), remote radio units (RRU), radio headers (RH), remote radio heads (RRH), WiFi® devices, repeaters, and low-power nodes such as femto and pico, depending on the terminology and technology applied. In the following description, the terms “Network device,” “AP device,” “AP,” and “Access point” may be used interchangeably.

[0028] The term "terminal equipment" refers to any terminal device capable of wireless communication. While these are merely examples, terminal equipment may also be called communication equipment, user equipment (UE), subscriber station (SS), mobile subscriber station, mobile station (MS), station (STA) or station equipment, or access terminal (AT). Terminal equipment includes mobile phones, mobile phone terminals, smartphones, VoIP phones, wireless local loop phones, tablet devices, wearable devices, PDAs, portable computers, desktop computers, image capture devices such as digital cameras, game consoles, music storage and playback devices, in-vehicle wireless terminals, wireless endpoints, mobile stations, laptop computers (LEE), laptop computers (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches and other wearables, 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, and devices operating on commercial and / or industrial wireless networks. In the following explanation, the terms "station," "station device," "STA," "terminal device," "communication device," "terminal," "user device," and "UE" may be used interchangeably.

[0029] For illustrative purposes, the principles and embodiments of this disclosure will be described below with reference to Figures 1A to 8. However, it should be noted that these embodiments are intended to enable those skilled in the art to understand the inventive concept of this disclosure and to implement the solutions proposed herein, and are not intended to limit the scope of this application in any way.

[0030] Figure 1A shows an example of an application scenario 100 in which several embodiments of this disclosure may be implemented. Application scenario 100, which is part of a communication network, includes terminal equipment and network equipment.

[0031] In describing the embodiments of this disclosure, the network environment 100 may also be referred to as the communication system 100 (e.g., part of a communication network). For convenience of explanation, various aspects of the exemplary embodiments are described in the context of one or more terminal devices and network devices communicating with each other. However, it should be noted that the descriptions herein are also applicable to other types of devices or other similar devices referred to using other terms.

[0032] As shown in Figure 1A, the communication network 100 may include network devices 110 (also called gNB or BS). The communication network 100 may further include terminal devices 120 (also called user equipment 120 or UE120). Although only one network device 110 and one terminal device 120 are shown in Figure 1A, the number of network devices and terminal devices is not limited. That is, there may be one or more network devices 110 and one or more terminal devices 120 in the network.

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

[0034] In the communication system 100, the link from the network device 110 to the terminal device 120 is called a downlink (DL), and the link from the terminal device 120 to the network device 110 is called an uplink (UL). In a downlink, the network device 110 is a transmitting (TX) device (or transmitter), and the terminal device 120 is a receiving (RX) device (or receiver). In an uplink, the terminal device 120 is a transmitting (TX) device (or transmitter), and the network device 110 is a receiving (RX) device (or receiver). It should be understood that the network device 110 may provide one or more service cells. As shown in Figure 1A, the network device 110 provides one service cell 102, and the terminal device 120 camps in the service cell 102. In some embodiments, the network device 110 may provide multiple service cells, and the terminal device 120 may switch between service cells from source to target during its movement. Please understand that the number of serving cells shown in Figure 1A is illustrative for illustrative purposes only and does not imply any limitations.

[0035] Communication in network environment 100 is implemented according to an appropriate communication protocol, which includes, but is not limited to, fourth-generation (4G) and fifth-generation (5G) cellular communication protocols, wireless local area network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or other protocols currently known or to be developed in the future. Furthermore, communication may utilize an appropriate wireless communication technology, which includes, but is not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiplexing (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and other technologies currently known or to be developed in the future.

[0036] The number, connections, and types of devices shown in Figure 1A are illustrative for illustrative purposes only and do not imply any limitations. The communication system 100 may include any number of devices suitable for carrying out the embodiments described herein.

[0037] Rel-15 introduces a slot aggregation feature for physical uplink shared channels (PUSCH), also known as PUSCH repetition type A. This feature allows the transmission of a transport block to be repeated across multiple slots. The main design features of PUSCH repetition type A in Rel-15 are as follows: • Resource allocation: The same resource allocation is applied throughout the entire PUSCH loop. Time Domain: Each repeat resides within a slot. Only a single start position and length of the PUSCH within the slot are indicated, i.e., a single start position and length indicator (SLIV). The start position and length indicated by this single SLIV apply to all PUSCH repeats. In Rel-15, the number of repeats for PUSCH repeat type A is semi-statically set in RRC, and the number of repeats is counted in consecutive physical slots. Figure 1B shows an example of PUSCH repeat type A in Rel-15 (4 repeats, S=5, L=7) assuming a DDSUU(10D:2G:2U)TDD pattern. If there are insufficient symbols available in a slot (less than L), no PUSCH repetitions will be sent in that slot. Frequency Domain: A PUSCH iteration has the same resource allocation in the frequency domain (i.e., the same number of physical resource blocks (PRBs), and the same location of these PRBs in the frequency domain if frequency hopping is not enabled). • Determination of Transport Block Size (TBS): The NInfo for a PUSCH repeater type A is calculated based on the number of REs determined within the slot. • Rate Matching: For each PUSCH iteration, the same or different redundant versions (RVs) can be applied to the encoded bits in the circular buffer. The RV for the first iteration is indicated by the scheduling DCI in the case of a dynamic grant, and is pre-set in the case of a set grant. When applying a different RV, the RVs are cycled from the set RV sequence, following the RV indicated for the first iteration. There are four RVs, each providing information about the starting encoded bits from the circular buffer that the UE should associate with the PUSCH transmission. Figure 1C shows the bit selection for PUSCH iteration type A with RV cycling.

[0038] In Rel-16, the number of repetitions for PUSCH repetition type A can be dynamically specified by associating the number of repetitions 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, and each nominal repetition can cross slot boundaries. Subsequently, if a nominal repetition crosses a slot boundary or invalid symbol, each nominal repetition is split into multiple actual repetitions. PUSCH repetitions in PUSCH repetition type B also have the same frequency domain resource allocation. Note that this type of PUSCH repetition was added solely to ensure integrity.

[0039] Rel-17 further improves PUSCH repetition type A by allowing the number of repetitions to be counted only in slots available for repeated transmission, as shown in Figure 1D. As shown in Figure 1D, it is only done in slots where repeated transmission is possible. Figure 1D shows an example of PUSCH repetition type A in Rel-17, assuming 4 repetitions, S=5, L=7, and a DDSUU(10D:2G:2U)TDD pattern. Rel-17 also increases the maximum number of repetitions for PUSCH repetition type A from 16 to 32.

[0040] The Rel-17 coverage enhancement WI defines a feature called multi-slot transport block processing (TBoMS). This feature allows a single transport block (TB) to be mapped across multiple slots, meaning that resource allocation for a single PUSCH transmission can span multiple slots. This is different from PUSCH repetition.

[0041] Figure 1E shows the power spectral density gain of multi-slot transport block processing (TBoMS) compared to single-slot push for the same transport block size (TBS). As Figure 1E shows, the main advantage of TBoMS is that, when transmitting the same transport block size (TBS), it reduces the number of PRBs required compared to transmitting the TB in a single slot. This increases the energy per resource element (EPRE). As a result, coverage is improved.

[0042] The main design elements of TBoMS can be summarized as follows: • Resource allocation Time domain: A new column is added to the TDRA table to indicate the number of slots allocated for TBoMS (N slot ). N slotThe number of available slots is counted based on the number of available slots (following the Rel-17 rule for counting available slots in PUSCH repeat type A). Therefore, non-contiguous slots can be used for TBoMS in TDD. The resource for each slot allocated for TBoMS is set to the same start symbol (S) and length (L) as in repeat type A. Figure 1F shows N slot This shows an example of TBoMS time-domain resource allocation using =2. Frequency domain: For TBoMS transmission, the same number of PRBs are allocated across the entire slot (similar to repeating type A). TBS decision: TBoMS's N Info This is based on the number of REs determined in the slot initially assigned to TBoMS, N slot It is scaled and calculated as follows: Here, N slot This is the total number of slots allocated to the TBoMS. In other words, the TBS of the TBoMS is calculated based on the total amount of resources allocated to the TBoMS across multiple slots. • Rate matching Use only one redundant version for a single TBoMS (i.e., do not switch RVs within a single TBoMS). Bit selection and bit interleaving from the circular buffer are performed on a slot-by-slot basis. In bit selection within a slot, the index of the start encoded bit in the circular buffer is a contiguous index from the position of the last selected bit in the previous assigned slot, regardless of whether UCI multiplexing was performed in the previous assigned slot. Figure 1G shows a single TBoMS transmission (N slot The bit selection in =3) is illustrated as an example. TBoMS transmissions are limited to one code block only. • Iteration of a single TBoMS Iteration of a single TBoMS is supported. The column in the TDRA table indicating the number of repetitions for Rel-17PUSCH repetition type A (i.e., numberOfRepetitions-r17) is a single TBoMS(Nrep It is also used to indicate the number of repetitions of (1). The UE secures N rep *N slot slots for TBoMS repetition. S and L of each slot are the same, but the TBS is calculated with the resources of a single TBoMS (i.e., scaled by N slot ). FIG. 1H shows an example of TBoMS repetition with N slot = 2 and N rep = 2. The redundant version (RV) circulates among TBoMS repetitions. The legacy Rel-15 / 16 RV sequence and RV index notification are reused.

[0043] The Rel-18 research item includes the evolution of multiplexing methods, sub-band non-overlapping full-duplex (SBFD). 3GPP (registered trademark) 5G NR currently supports two multiplexing modes: FDD for paired bands and TDD for unpaired bands. In TDD, time-domain resources are divided between the downlink and the uplink. If the time frames allocated to the uplink in TDD are limited, it will lead to a decrease in coverage, an increase in delay, and a decrease in capacity.

[0044] Based on this problem, 3GPP (registered trademark) agreed to initiate a Rel-18 research item (RP-213591) on the evolution of multiplexing methods in NR to solve the above problems. One of the objectives of this research item is to enable simultaneous transmission of DL and UL using different physical resource blocks (PRBs) / sub-bands within an asymmetric wideband NR cell, as shown in FIG. 1I, which shows the frequency-time resource division by SBFD compared with conventional FDD and TDD. In this specification, this is also referred to as sub-band non-overlapping full-duplex (SBFD). In other documents, this multiplexing method is also referred to as cross-divided multiplexing (xD) or flexible divided multiplexing (FDU).

[0045] The following is part of the most important objectives in the description of the research item (RP-213591) related to the present disclosure.

Table 1

[0046] The following shows an example of an SBFD slot definition. Figure 1J shows examples of SBFD and non-SBFD slots. From the above explanation of SBFD operation, it can be seen that there are two types of slots for both DL and UL transmission, as shown in Figure 1J. That is, • SBFD slots for periods in which non-overlapping DL subbands and UL subbands (multiple possible) exist simultaneously, and • Non-SBFD slots where the entire bandwidth is used for either DL or UL (i.e., conventional / full DL / UL slots), That is the case.

[0047] Regarding SBFD operating modes, several forms have been considered, including whether or not the SBFD-enabled UE recognizes the time and frequency position of the subband. However, at the 3GPP® RAN1#110 meeting, it was agreed that an operating mode in which the SBFD-enabled UE recognizes the time and frequency position of the subband should be prioritized. This means that the (SBFD-enabled) UE should recognize the SBFD slot in some way.

[0048] It should be noted that cross-link interference (CLI) exists in SBFD slots. As described in Nokia's technical document for the RAN1#110 conference (R1-2207267) and shown in Figure 1K, SBFD introduces a new type of CLI, namely, same-channel subband CLI. This interference can be appropriately classified as follows: 1. gNB self-interference 2. Intra-cell UE-to-UE co-channel inter-subband CLI 3. Inter-cell UE-to-UE co-channel inter-subband CLI 4. Inter-channel subband CLI between gNBs (gNB-to-gNB co-channel inter-subband CLI) In addition to these new CLI types, if the frequency domain is divided differently between adjacent cells, the system may also be affected by inter-subband interference (CLI) within the same frequency band. This is CLI caused by transmissions using overlapping frequency resources. 5. gNB-to-gNB inter-cell co-channel intra-subband CLI 6. UE-to-UE inter-cell co-channel intra-subband CLI

[0049] One design aspect to consider in SBFD operation is whether a slot can consist of both SBFD and non-SBFD symbols. Another design aspect of SBFD operation is whether a transmission can span both SBFD and non-SBFD symbols. This includes: a) A transmission that spans multiple slots, where each slot consists of the same symbol type, and the symbol types may differ between the multiple slots (e.g., a PUSCH repetition or TBoMS). b) Transmissions that span SBFD and non-SBFD symbols within a single slot (e.g., a single PUSCH or repeated PUSCH). In this regard, the following can be observed: One of the main motivations for introducing SBFD operations is to enhance UL coverage (providing more UL resources), while PUSCH iteration / TBoMS is a basic function used when coverage is insufficient. Therefore, PUSCH iteration / TBoMS should support scenarios that span both SBFD and non-SBFD slots. Furthermore, as shown in Figure 1L, it is clear that special (legacy) slots consisting of DL, gap, and UL symbols should support slots consisting of at least both SBFD and non-SBFD symbols.

[0050] From the observations above, it is clear that a slot consists of both SBFD and non-SBFD symbols, but the 3GPP® Radio Access Network (RAN) Working Group (WG) 1, i.e., RAN1, is still debating whether transmissions within a slot span both SBFD and non-SBFD symbols. Indeed, as discussed in R1-2301411, the concerns lie primarily in the current hardware implementation. Specifically, these are as follows: From a network perspective, switching between SBFD and non-SBFD symbols may require a transition guard period to allow for panel switching, filter adjustments, and timing adjustments. This can interfere with transmission or reception (the network may use one panel for UL reception with SBFD symbols and two panels for UL symbols). From the UE's perspective, SBFD-compatible UEs will need to readjust their filters and change the UL sampling rate from SBFD to UL-SB. In the case of switching from DL to SBFD, an SBFD-compatible UE may adjust DL filtering between DL and SBFD symbols, potentially interrupting DL reception.

[0051] Therefore, RAN1 considers two possibilities: either prohibit transmissions from spanning SBFD and non-SBFD symbols within a slot, or allow the network to configure transmissions to span SBFD and non-SBFD symbols within a slot, depending on the capabilities of the network and UE.

[0052] However, regardless of which approach is ultimately adopted, if a transmission within a slot does not span SBFD and non-SBFD symbols, then the UE behavior for TDRA determination for transmissions / repetitions that span SBFD and non-SBFD symbols within a slot should be defined (this is not currently available and is proposed in this invention).

[0053] This is extremely important in the case of PUSCH or PDSCH with repetitions, because, as mentioned above, PUSCH / PDSCH repetitions follow the same resource allocation as assigned to the first repetition. Therefore, consider the example shown in Figure 1M, which illustrates a PUSCH repetition in SBFD with S=0, L=14, starting from a full UL slot. In a PUSCH transmission with repetitions scheduled across all slots (14 symbols), the UE's behavior for TDRA determination for repetitions in slots containing a mix of SBFD and non-SBFD symbols (hereinafter referred to as mixed slots) is unclear and needs to be defined / determined by the UE. Furthermore, in the case of PUSCH repetitions counted in available slots (the Rel-17 function mentioned above), it should be specified whether or not mixed slots are counted as available slots. Embodiments of this specification are provided based on the above analysis and considerations.

[0054] In general, embodiments of the present disclosure propose a solution for TDRA determination when a Transmit Opportunity (TO) spans both SBFD and non-SBFD symbols in a slot. A TO may point to a candidate PUSCH / PDSCH repetition in a slot, or a candidate PUSCH transmission in a slot for TBoMS, or any RRC configuration resource for a PUSCH / PDSCH transmission. In some embodiments, terminal device 120 receives scheduling information from network device 110 indicating a TO that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot. Terminal device 120 may determine whether the TO is valid, where a TO for UL transmission is valid if all resource elements (REs) in the TO are uplink REs and available for UL transmission, and similarly, a TO for DL ​​transmission is valid if all resource elements (REs) in the TO are downlink REs and available for DL ​​transmission. If a TO is valid, the terminal device 120 selects time-domain resources for at least a portion of the TO such that at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol, and transmits or receives data on at least a portion of the TO according to that selection. In some embodiments, the network device 110 transmits scheduling information to the terminal device 120 indicating a TO that spans at least one SBFD symbol and a non-SBFD symbol in a slot, selects time-domain resources, and performs the corresponding transmit or receive so that both sides operate on the same resources.

[0055] Figure 2 shows an example of a process flow according to some embodiments of this disclosure. For ease of understanding, process flow 400 is described with reference to Figure 1A. Process flow 200 is described with reference to the communication network 100 in Figure 1A, but it should be noted that this process flow 200 is equally applicable to other similar communication scenarios.

[0056] As shown in Figure 2, the network device 110 transmits scheduling information to the terminal device 120 indicating a Transmit Opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in the slot (201). Thus, the terminal device 120 receives the scheduling information (202).

[0057] In some embodiments, the TO may be a transmission opportunity for UL or DL ​​(e.g., for PUSCH or PDSCH). In some embodiments, the TO may be for data repetition, TBoMS, or RRC configuration grant resources. The slot in which the TO is scheduled may contain both SBFD and non-SBFD symbols and may be called a mixed slot.

[0058] Figure 3 shows an example of a TO in a mixed slot, which consists of SBFD symbols, non-SBFD symbols, and (optionally) gap symbols. As shown in the figure, SBFD symbols contain both uplink (UL) frequency resources and downlink (DL) frequency resources, while non-SBFD symbols contain either UL or DL ​​frequency resources. Gap symbols (if present) contain guard time resources.

[0059] It is worth noting that in some embodiments, no special processing is proposed for the TO portion within the gap symbol; therefore, for simplicity, only SBFD symbols and non-SBFD symbols will be referred to below, meaning that a gap symbol (if any) may be contained within either an SBFD symbol or a non-SBFD symbol. Thus, both the network device 110 and the terminal device 120 can treat a gap symbol containing a guard time resource in a slot as either an SBFD symbol or a non-SBFD symbol.

[0060] Upon receiving scheduling information (202), the terminal device 120 determines that the TO is valid (204). Based on this determination, the terminal device 120 selects time domain resources for at least a portion of the TO such that at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol (206). Correspondingly, the network device 110 also determines that the TO is valid (203). Based on this determination, the network device 110 selects time domain resources for at least a portion of the TO such that at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol (205). This allows the terminal device 120 and the network device 110 to coordinate time resources for data transmission or reception.

[0061] Network device 110 transmits data in at least a portion of the TO according to the selection (207). Correspondingly, terminal device 120 receives data in at least a portion of the TO according to the selection (208).

[0062] Alternatively, or additionally, terminal device 120 transmits data in at least a portion of the TO, according to selection (210). Correspondingly, network device 110 receives data in at least a portion of the TO, according to selection (209).

[0063] Figure 4 shows another example of a process flow according to some embodiments of the present disclosure. In Figure 4, gNB410 is an embodiment of the network device 110, and UE is an embodiment of the terminal device in Figure 1A.

[0064] In step 401, the gNB410 notifies the UE420, and the UE420 receives the set of settings via a radio resource control message or downlink control information (DCI).

[0065] In some embodiments, the UE420 may be notified of, for example, the frequency band. Alternatively, or additionally, the UE420 may be notified that the frequency band is divided into multiple subbands, with at least one subband used for DL ​​transmission and at least one subband used for UL transmission, i.e., the subband full-duplex (SBFD) slots / symbols and their locations within the radio frame. The UE420 may be notified of the number of slots / symbols whose entire frequency band is used for DL ​​or UL transmission, i.e., non-SBFD slots / symbols and their locations within the radio frame. Alternatively, or additionally, the UE420 may be notified of the number and locations of gap symbols (if any) present in special slots.

[0066] In step 402, gNB410 may notify UE420 that transmissions spanning SBFD and non-SBFD symbols within a slot are not permitted, and UE420 receives this notification (e.g., via RRC). Note that this step is unnecessary if the specification hardcodes that transmissions spanning SBFD and non-SBFD symbols within a slot are not permitted. Furthermore, the order of steps 401 and 402 is interchangeable or can be combined, but they are separated here for clarity.

[0067] In step 403, the gNB410 sends scheduling information to the UE420 indicating a Transmit Occasion (TO). A slot may consist of SBFD symbols and non-SBFD symbols. As shown in Figure 3, a TO spans at least one of the SBFD and non-SBFD symbols of a mixed slot. In some embodiments, the TO is a Transmit Occasion for UL or DL ​​(e.g., for PUSCH or PDSCH). In some embodiments, the TO is for data repetition, TBoMS, or RRC setting grant resources.

[0068] In step 404, the UE420 further determines the resources for the actual transmission within the TO and the number of repetitions to be accumulated in the total number of repetitions (if the TO is for PUSCH repetitions and counts the available slots enabled by the gNB410).

[0069] In step 405, UE420 sends or receives data in the determined resource for the actual transmission within TO, according to the result of step 404.

[0070] In step 404, UE420 first determines whether the TO is valid and then applies a different approach. In some embodiments, a TO for UL transmission is determined to be valid if all REs within the TO are UL REs and available for UL transmission, and a TO for DL ​​transmission is determined to be valid if all REs within the TO are DL REs and available for DL ​​transmission. Otherwise, the TO is determined to be invalid.

[0071] Based on its determination that a TO is valid, the UE420 may select time-domain resources for at least a portion of the TO such that at least a portion does not span at least one SBFD symbol and at least one non-SBFD symbol. In some embodiments, the UE420 determines that a TO is a valid TO and transmits (e.g., rate-matches) or receives data only in the portion of the TO that is in an SBFD symbol or a non-SBFD symbol. At least a portion of the TO is either 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. Thus, the UE420 can transmit or receive data in either the first or second portion of the TO and disable data transmission or reception in the other first or second portion of the TO.

[0072] In some embodiments, whether the first or second portion of the TO is used for transmission or reception is determined based on a pre-configured setting. This pre-configured setting is either hardcoded in the specification or set by the gNB410 (e.g., via the RRC setting). In some embodiments, the specification may be hardcoded to ensure that the UE420 always transmits or receives data only in the TO portion within an SBFD symbol. Alternatively, the specification may be hardcoded to ensure that the UE420 always transmits or receives data only in the TO portion within a non-SBFD symbol.

[0073] In some embodiments, the choice of which of the first and second parts of a TO to use for transmission or reception may be determined based on its length, for example, the longer one. The UE420 first determines which part of the TO is longer (has more symbols) between the first part of the TO in an SBFD symbol and the second part of the TO in a non-SBFD symbol. The UE420 then transmits or receives data only in the determined longer part of the TO.

[0074] In some embodiments, if the TO is a data repetition by the number of repetitions counted in the available slots (e.g., a PUSCH repetition), the UE420 counts the slot as one data repetition.

[0075] The above describes a method in which the UE420 transmits or receives data in only a portion of the TO so that the TO does not span between SBFD and non-SBFD symbols. Alternatively, or additionally, the UE420 can transmit or receive data in two separate portions of the TO, each portion not spanning between SBFD and non-SBFD symbols.

[0076] In some embodiments, a TO is considered a nominal TO (e.g., the first TO), and the UE420 determines that the nominal TO is divided into two valid actual TOs (e.g., the second TO and the third TO). Here, "nominal" means nominally existing, and the actual TOs are determined based on the nominal TO. One actual TO takes the SBFD symbol portion of the nominal TO, and the other actual TO takes the non-SBFD symbol portion of the nominal TO. The UE420 then transmits (e.g., rate-matches) or receives data with the two actual TOs. Alternatively, or additionally, if a TO is for PUSCH repetition and the count of available slots is valid, that slot is counted as two repetitions.

[0077] In some embodiments, if a nominal TO is for data repetition (e.g., for PUSCH), the two actual TOs may be considered two repetitions and use different redundant versions (RVs) for rate matching. When counting the number of repetitions in an available slot, the UE420 counts that slot as two repetitions of data repetition because there are two data transmissions.

[0078] In some embodiments, if a nominal TO is for transport block processing (TBoMS) spanning multiple slots, the two actual TOs are considered two attempts for the same transport block (TB). The two actual TOs use the same RV for rate matching, and the data is rate-matched sequentially across the two TOs (similar to TBoMS across slots).

[0079] When selecting a time resource for a TO, the UE420 determines whether any portion of the TO (e.g., within an SBFD symbol) overlaps with other UL or DL ​​transmissions (regardless of whether the TO takes precedence). If there is overlap, the UE420 transmits or receives data only in the portion of the TO that does not overlap with other UL or DL ​​transmissions. Otherwise, the non-overlapping portion is included in at least a portion of the TO, according to the selection, so as the above embodiment applies, i.e., satisfying the constraint that it does not span both SBFD and non-SBFD symbols.

[0080] The above describes examples of valid TOs. Based on the UE420's determination that a TO is invalid, it will not send or receive data through that TO. In some embodiments, data may be sent or received through an invalid TO. In the case of a TO for data repetition that counts the number of repetitions in an available slot, the UE420 may skip the count in that slot.

[0081] The explanations for steps 404 and 405 are given from the perspective of UE420, but it should be understood that similar operations are also applicable to network device 110. Therefore, for the sake of brevity, details from the perspective of network device 110 are omitted.

[0082] From this perspective, embodiments of this specification define the behavior of terminal and network devices in TDRA decisions for transmissions / repetitions that span SBFD and non-SBFD symbols when a transmission cannot span SBFD and non-SBFD symbols within a slot (whether or not it is not supported by the hardware implementation, not configured on the network, or not fixed by the specification). In some embodiments, this case is further enhanced for PUSCH or PDSCH with repetitions.

[0083] Figure 5 shows a flowchart of an exemplary method 500 implemented in a terminal device according to another embodiment of the present disclosure. For ease of understanding, method 500 will be described with reference to Figure 1A, in view of the terminal device 120.

[0084] In block 510, terminal device 120 receives scheduling information from network device 110 indicating a Transmit Opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot. In some embodiments, at least one SBFD symbol may include both uplink (UL) frequency resources and downlink (DL) frequency resources. At least one non-SBFD symbol may include either UL frequency resources or DL ​​frequency resources. In some embodiments, the slot may consist of one or more gap symbols containing guard time resources. Terminal device 120 may consider one or more gap symbols as either SBFD symbols or non-SBFD symbols.

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

[0086] In block 530, the terminal device 120 transmits or receives data in at least a portion of the TO according to the selection.

[0087] In some embodiments, at least a portion of the TO may be either a first portion of the TO within at least one SBFD symbol, or a second portion of the TO within at least one non-SBFD symbol. The terminal device 120 may transmit or receive data in either the first or second portion of the TO, and invalidate the transmission or reception of data in the other first or second portion of the TO.

[0088] In some embodiments, either the first or second part of the TO is determined based on a pre-configured configuration. The pre-configured configuration is hardcoded in the specification or configured by the network device 110, for example, via RRC settings. Alternatively or additionally, either the first or second part of the TO may have more symbols than the other.

[0089] In some embodiments, if the TO is for data repetition by the number of repetitions counted in the available slots, the terminal device 120 counts the slot as one data repetition.

[0090] In some embodiments, the TO is a first TO, and the terminal device may divide the first TO into a second TO with at least one SBFD symbol and a third TO with at least one non-SBFD symbol, and send or receive data in the second TO and send or receive data in the third TO.

[0091] In some embodiments, if the TO is for data repetition, the second and third TOs use different redundant versions (RVs) for rate matching. Alternatively or additionally, if the number of repetitions is counted in an available slot, the terminal device 120 counts that slot as two repetitions of data repetition.

[0092] In some embodiments, if the TO is for transport block processing (TBoMS) spanning multiple slots, the second and third TOs may have the same RV for rate matching.

[0093] In some embodiments, the terminal device 120 determines whether the TO overlaps with other UL or DL ​​transmissions. Based on the determination that the TO overlaps with other UL or DL ​​transmissions, the terminal device 120 transmits or receives data in the non-overlapping portion of the TO that does not overlap with other UL or DL ​​transmissions. The non-overlapping portion may, depending on the choice, be included in at least a part of the TO.

[0094] In some embodiments, the terminal device 120 may disable the transmission or reception of data in a TO based on a determination that the TO is invalid. Alternatively or additionally, if the TO is for data repetition where the number of repetitions is counted in an available slot, the terminal device 120 may skip the count in that slot.

[0095] Figure 6 is a flowchart showing examples of other methods implemented in a network device according to some embodiments of the present disclosure. For ease of understanding, method 600 will be described in terms of network device 110 with reference to Figure 1A.

[0096] In block 610, the network device 110 transmits scheduling information to the terminal device 120 indicating a Transmit Opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol within a slot. In some embodiments, at least one SBFD symbol may include both uplink (UL) frequency resources and downlink (DL) frequency resources. At least one non-SBFD symbol may include either UL frequency resources or DL ​​frequency resources. In some embodiments, the slot may consist of one or more gap symbols containing guard time resources. The terminal device 120 may consider one or more gap symbols as either SBFD symbols or non-SBFD symbols.

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

[0098] In block 630, the network device 110 transmits or receives data in at least a portion of the TO, according to the selection.

[0099] In some embodiments, at least a portion of the TO may be either a first portion of the TO within at least one SBFD symbol, or a second portion of the TO within at least one non-SBFD symbol. The network device 110 may transmit or receive data from either the first or second portion of the TO, and disable data transmission or reception from the other portion of the TO.

[0100] In some embodiments, either the first or second part of the TO is determined based on a pre-configured setting. The pre-configured setting is hardcoded in the specification or configured by the network device 110 (e.g., via RRC settings). Alternatively or additionally, either the first or second part of the TO may have more symbols than the other.

[0101] In some embodiments, if the TO is for data repetition based on the number of repetitions counted in the available slots, the network device 110 counts the slot as one repetition of the data repetition.

[0102] In some embodiments, the TO is a first TO, and the terminal device makes a selection by dividing the first TO into a second TO with at least one SBFD symbol and a third TO with at least one non-SBFD symbol, transmitting or receiving data in the second TO and transmitting or receiving data in the third TO.

[0103] In some embodiments, if the TO is for data repetition, the second and third TOs use different redundant versions (RVs) for rate matching. Alternatively or additionally, if the number of repetitions is counted in an available slot, the network device 110 counts that slot as two repetitions of data repetition.

[0104] In some embodiments, if the TO is for transport block processing (TBoMS) spanning multiple slots, the second and third TOs may have the same RV for rate matching.

[0105] In some embodiments, the network device 110 determines whether the TO overlaps with other UL or DL ​​transmissions. Based on the determination that the TO overlaps with other UL or DL ​​transmissions, the network device 110 transmits or receives data using the non-overlapping portion of the TO that does not overlap with other UL or DL ​​transmissions. The non-overlapping portion may, depending on the choice, be included in at least a portion of the TO.

[0106] In some embodiments, the network device 110 may disable the transmission or reception of data in a TO based on a determination that the TO is invalid. Alternatively or additionally, if the TO is for data repetition where the number of repetitions is counted in an available slot, the network device 110 may skip the count in that slot.

[0107] In some embodiments, an apparatus capable of performing Method 500 (e.g., terminal device 120) may include means for performing each step of Method 500. These means can be implemented in any suitable form. For example, these means can be implemented as a circuit or a software module.

[0108] In some embodiments, the device includes means for receiving scheduling information from a network device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; means for selecting time-domain resources for at least a portion of the TO, based on a determination 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 means for transmitting or receiving data in at least a portion of the TO according to the selection.

[0109] In some embodiments, at least a portion of the TO is either 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. Means for transmitting or receiving data in at least a portion of the TO based on selection may include means for transmitting or receiving data in either the first or second portion of the TO, and means for disabling data transmission or reception in the other of the first or second portion of the TO.

[0110] In some embodiments, either the first or second part of the TO is determined based on a pre-configured setting.

[0111] In some embodiments, either the first part of the TO or the second part of the TO may have more symbols than the other.

[0112] In some embodiments, if the TO is for data repetition by the number of repetitions counted in the available slots, the device may include means for counting the slots as one repetition of the data repetition.

[0113] In some embodiments, the TO is a first TO, and means for selecting time-domain resources for at least a portion of the TO include means for dividing 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 means for transmitting or receiving data in at least a portion of the TO according to the selection include means for transmitting or receiving data in the second TO and means for transmitting or receiving data in the third TO.

[0114] In some embodiments, if the TO is for data repetition, the second and third TOs use different redundant versions (RVs) for rate matching.

[0115] In some embodiments, the device may further include means for counting an available slot as two repetitions of data repetitions if the number of repetitions in that slot is counted.

[0116] In some embodiments, if the TO is for transport block processing (TBoMS) spanning multiple slots, the second TO and the third TO have the same RV for rate matching.

[0117] In some embodiments, at least one SBFD symbol includes both uplink (UL) frequency resources and downlink (DL) frequency resources, and at least one non-SBFD symbol includes either an UL frequency resource or a DL frequency resource.

[0118] In some embodiments, the device includes means for treating any gap symbol containing guard time resources within a slot as either an SBFD symbol or a non-SBFD symbol.

[0119] In some embodiments, the apparatus includes means for determining whether a TO overlaps with other UL or DL ​​transmissions, and means for transmitting or receiving data in the 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, according to the choice, the non-overlapping portion is included in at least a part of the TO.

[0120] In some embodiments, the device may include means for disabling the transmission or reception of data at a TO based on a determination that the TO is invalid.

[0121] In some embodiments, the device includes means for skipping the count in a slot when the TO is for data repetition where the number of repetitions is counted in an available slot.

[0122] 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, wherein the at least one memory and the computer program code are configured to cause the at least one processor to perform the operation of the apparatus.

[0123] In some embodiments, an apparatus capable of performing Method 600 (e.g., a network device 110) may include means for performing each step of Method 600. These means can be implemented in any suitable form. For example, these means can be implemented as a circuit or a software module.

[0124] In some embodiments, the apparatus includes means for transmitting scheduling information to a terminal device indicating a transmit opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot; means for selecting time-domain resources for at least a portion of the TO, based on a determination 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 means for transmitting or receiving data in at least a portion of the TO according to the selection.

[0125] In some embodiments, at least a portion of the TO is either 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. Means for transmitting or receiving data in at least a portion of the TO, as selected, may include means for transmitting or receiving data in either the first or second portion of the TO, and means for disabling data transmission or reception in the other portion of the TO.

[0126] In some embodiments, either the first or second part of the TO is determined based on a pre-configured setting.

[0127] In some embodiments, either the first part of the TO or the second part of the TO may have more symbols than the other.

[0128] In some embodiments, if the TO is for data repetition by the number of repetitions counted in the available slots, the device may include means for counting the slots as one repetition of the data repetition.

[0129] In some embodiments, the TO is a first TO, and means for selecting time-domain resources for at least a portion of the TO include means for dividing 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 means for transmitting or receiving data in at least a portion of the TO according to the selection include means for transmitting or receiving data in the second TO and means for transmitting or receiving data in the third TO.

[0130] In some embodiments, if the TO is for data repetition, the second and third TOs use different redundant versions (RVs) for rate matching.

[0131] In some embodiments, the device may further include means for counting an available slot as two repetitions of data repetitions if the number of repetitions in that slot is counted.

[0132] In some embodiments, if the TO is for transport block processing (TBoMS) spanning multiple slots, the second TO and the third TO have the same RV for rate matching.

[0133] In some embodiments, at least one SBFD symbol includes both uplink (UL) frequency resources and downlink (DL) frequency resources, and at least one non-SBFD symbol includes either an UL frequency resource or a DL frequency resource.

[0134] In some embodiments, the device includes means for treating any gap symbol containing guard time resources within a slot as either an SBFD symbol or a non-SBFD symbol.

[0135] In some embodiments, the apparatus includes means for determining whether a TO overlaps with other UL or DL ​​transmissions, and means for transmitting or receiving data in the 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, according to the choice, the non-overlapping portion is included in at least a portion of the TO.

[0136] In some embodiments, the device may include means for disabling the transmission or reception of data at a TO based on a determination that the TO is invalid.

[0137] In some embodiments, the device includes means for skipping the count in a slot when the TO is for data repetition where the number of repetitions is counted in an available slot.

[0138] 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, wherein the at least one memory and the computer program code are configured to cause the at least one processor to perform the operation of the apparatus.

[0139] Figure 7 shows a simplified block diagram of a device 700 suitable for implementing some embodiments of the present disclosure. The device 700 is provided for implementing, for example, a communication device such as the network device 110 or terminal device 120 shown in Figure 1A. As shown in the figure, the device 700 comprises one or more processors 710, one or more memories 720 connected to the processors 710, and one or more communication modules 740 connected to the processors 710.

[0140] The communication module 740 is for bidirectional 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.

[0141] The processor 710 is any type suitable for a local technology network and may include, but is not limited to, one or more of the following, as examples: a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), or a processor based on a multi-core processor architecture. The device 700 may have multiple processors, such as application-specific integrated circuit chips that are time-dependent to a clock that synchronizes the main processor.

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

[0143] The computer program 730 contains computer executable instructions that are executed by the associated processor 710. The program 730 may be stored in the ROM 724. The processor 710 performs any appropriate operations and processes by loading the program 730 into the RAM 722.

[0144] Embodiments of the present disclosure are implemented by program 730, enabling the device 700 to perform any of the processes of the disclosure described with reference to Figures 4 and 5. Embodiments of the present disclosure may also be implemented by hardware, or by a combination of software and hardware.

[0145] In some embodiments, the program 730 may be tangibly stored in a computer-readable medium built into the device 700 (for example, in the memory 720) or in another storage device accessible to the device 700. The device 700 can load the program 730 from the computer-readable medium into the RAM 722 and execute it. The computer-readable medium may include any type of tangible non-volatile storage device, such as ROM, EPROM, flash® memory, hard disk, CD, DVD, etc.

[0146] Figure 8 is a block diagram showing an example of a computer-readable medium 600 according to some embodiments of the present disclosure. The computer-readable medium 800 stores a program 730. Note that although the computer-readable medium 800 is shown in the form of a CD or DVD in Figure 8, it may be in other forms suitable for transporting or holding the program 730.

[0147] In general, various embodiments of this disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some features may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Various aspects of the embodiments of this disclosure are described using block diagrams, flowcharts, or other graphic representations, but it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented, in non-limiting examples, in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or a combination thereof.

[0148] Furthermore, this disclosure provides at least one computer program product physically recorded on a non-temporary computer-readable storage medium. This computer program product includes computer-executable instructions contained in a program module, which are executed on a device on a target real or virtual processor to perform the methods 500 or 600 described above with reference to Figure 5 or 6. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The functionality of the program modules is combined or divided among the program modules as needed in various embodiments. The machine-executable instructions for the program modules are executed in local or distributed devices. In distributed devices, the program modules are located on both local and remote storage media.

[0149] Program code for carrying out the methods of this disclosure is written in any combination of one or more programming languages. These program codes are provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and are executed by the processor or controller to implement the functions / operations specified in the flowcharts and / or block diagrams. The program code may run entirely on the machine, partially on the machine, run as a standalone software package, partially on the machine and partially on a remote machine, or run entirely on a remote machine or server.

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

[0151] Computer-readable media may be computer-readable signal media or computer-readable storage media. Computer-readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, and semiconductor systems, apparatus, devices, or appropriate combinations thereof. More specific examples of computer-readable storage media include electrical connections with one or more wires, portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash® memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or appropriate combinations thereof. The term "non-temporary" as used herein refers to a limitation on the medium itself (i.e., a tangible medium rather than a signal medium), not on the persistence of data storage (e.g., RAM vs. ROM).

[0152] Furthermore, even if operations are shown in a specific order, this should not be interpreted as meaning that the operations must be performed in that specific order or sequential order, or that all illustrated operations must be performed, in order to obtain the desired result. In certain situations, multitasking or parallel processing may be advantageous. Similarly, the above description includes some specific implementation details, which should not be interpreted as limitations on the scope of this disclosure, but rather as descriptions of features specific to 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 individually or in any suitable partial combination in multiple embodiments.

[0153] While this disclosure is described in a language specific to structural features and / or methodological actions, the disclosure as defined in the attached claims is not necessarily limited to the specific functions or actions described above. Rather, the specific functions or actions described above are disclosed as exemplary 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 receives at least, Receiving scheduling information from a network device indicating a transmit opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol within a slot, Based on the determination that the TO is valid, time domain resources for at least a portion of the TO are selected such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol. In accordance with the above selection, to transmit or receive data in at least a portion of the TO, At least one memory to store instructions to execute, A terminal device equipped with the following features.

2. At least a portion of the TO is either 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 terminal device is Transmitting or receiving data in either the first part of the TO or the second part of the TO, Disabling the transmission or reception of data in the first part of the TO, or the other of the second part of the TO, The terminal device according to claim 1, which is configured to perform the following:

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

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

5. If the TO is a data repetition counted by the number of repetitions in the available slots, the terminal device further: The aforementioned slot is counted as one repetition of the aforementioned data. A terminal device according to any one of claims 2 to 4, wherein the device is configured to do so.

6. The aforementioned TO is the first TO, and the terminal device is The selection is performed by dividing the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol. Sending or receiving data in the second TO, and sending or receiving data in the third TO, The terminal device according to claim 1, which is configured to perform the following:

7. The terminal device according to claim 6, wherein if the TO is for data repetition, the second TO and the third TO use different redundant versions (RV) for rate matching.

8. The aforementioned terminal device further, If the number of repetitions is counted in an available slot, the slot is counted as two repetitions of the data. The terminal device according to claim 7, wherein the device is configured to be such as.

9. The terminal device according to claim 6, wherein, if the TO is for transport block processing (TBoMS) spanning multiple slots, the second TO and the third TO have the same RV for rate matching.

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

11. The terminal device according to claim 10, wherein the terminal device is configured to treat any gap symbol containing a guard time resource in the slot as an SBFD symbol or a non-SBFD symbol.

12. The aforementioned terminal device further, The determination of whether the aforementioned TO overlaps with other UL or DL ​​transmissions, Based on the determination that the TO overlaps with the other UL or DL ​​transmission, the transmission or reception of data in the non-overlapping portion of the TO that does not overlap with the other UL or DL ​​transmission, wherein, according to the selection, the non-overlapping portion is included in at least a part of the TO. A terminal device according to any one of claims 1 to 11, which is configured to perform the following:

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

14. The aforementioned terminal device further, If the aforementioned TO is for data repetition based on the number of repetitions counted in the available slots, the count in the aforementioned slot is skipped. The terminal device according to claim 13, wherein the device is configured to be such as.

15. Network device, At least one processor, When executed by the at least one processor, the network device will have at least, To transmit scheduling information to a terminal device indicating a transmission opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in the slot, Based on the determination that the TO is valid, time domain resources for at least a portion of the TO are selected such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol. In accordance with the above selection, to transmit or receive data in at least a portion of the TO, At least one memory to store instructions to execute, A network device equipped with the following features.

16. At least a portion of the TO is either 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 network device is Transmitting or receiving data in either the first part of the TO or the second part of the TO, Disabling the transmission or reception of data in the first part of the TO, or the other of the second part of the TO, The network device according to claim 15, which is configured to perform the following.

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

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

19. If the TO is a data repetition counted by the number of repetitions in the available slots, the network device further: The aforementioned slot is counted as one repetition of the aforementioned data. A network device according to any one of claims 15 to 18, wherein the network device is configured to be such as.

20. If the TO is the first TO, the network device is The selection is performed by dividing the first TO into a second TO in at least one SBFD symbol and a third TO in at least one non-SBFD symbol. Sending or receiving data in the second TO, and sending or receiving data in the third TO, The network device according to claim 15, which is configured to perform the following.

21. The network device according to claim 20, wherein if the TO is for data repetition, the second TO and the third TO use different redundant versions (RV) for rate matching.

22. The aforementioned network device further, If the number of repetitions is counted in an available slot, the slot is counted as two repetitions of the data. The network device according to claim 21, wherein the network device is configured to be such as.

23. The network device according to claim 20, wherein if the TO is for transport block processing (TBoMS) spanning multiple slots, the second TO and the third TO have the same RV for rate matching.

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

25. The network device according to claim 24, wherein the network device is configured to treat any gap symbol containing a guard time resource in the slot as either an SBFD symbol or a non-SBFD symbol.

26. The aforementioned network device further, The determination of whether the aforementioned TO overlaps with other UL or DL ​​transmissions, Based on the determination that the TO overlaps with the other UL or DL ​​transmission, the transmission or reception of data is performed using the non-overlapping portion of the TO that does not overlap with the other UL or DL ​​transmission, wherein the non-overlapping portion is included in at least a part of the TO according to the selection. A network device according to any one of claims 15 to 25, which is configured to perform the following.

27. The aforementioned network device further, Based on the determination that the TO is invalid, the transmission or reception of data in the TO is disabled. A network device according to any one of claims 15 to 26, wherein the network device is configured to be such as described above.

28. The aforementioned network device further, If the aforementioned TO is for repeating data by the number of repetitions counted in the available slots, the count in the slots is skipped. The network device according to claim 27, wherein the network device is configured to be such as.

29. Receiving scheduling information from a network device indicating a transmit opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol within a slot, Based on the determination that the TO is valid, time domain resources for at least a portion of the TO are selected such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol. In accordance with the above selection, to transmit or receive data in at least a portion of the TO, Methods that include...

30. To transmit scheduling information to a terminal device indicating a transmission opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in the slot, Based on the determination that the TO is valid, time domain resources for at least a portion of the TO are selected such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol. In accordance with the above selection, to transmit or receive data in at least a portion of the TO, Methods that include...

31. It is a device, Means for receiving scheduling information from a network device indicating a transmission opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot, Means for selecting time-domain resources for at least a portion of the TO, based on the determination 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, In accordance with the above selection, means for transmitting or receiving data in at least a portion of the TO, A device equipped with the following features.

32. It is a device, Means for transmitting scheduling information to a terminal device indicating a transmission opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in a slot, Means for selecting time-domain resources for at least a portion of the TO, based on the determination 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, In accordance with the above selection, means for transmitting or receiving data in at least a portion of the TO, A device equipped with the following features.

33. A non-temporary computer-readable medium, which, when executed by a device, provides to the device at least: Receiving scheduling information from a network device indicating a transmit opportunity (TO) spanning at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol within a slot, Based on the determination that the TO is valid, time domain resources for at least a portion of the TO are selected such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol. In accordance with the above selection, to transmit or receive data in at least a portion of the TO, A non-temporary computer-readable medium containing program instructions that cause something to be executed.

34. A non-temporary computer-readable medium, which, when executed by a device, provides to the device at least: To transmit scheduling information to a terminal device indicating a transmission opportunity (TO) that spans at least one subband full-duplex (SBFD) symbol and at least one non-SBFD symbol in the slot, Based on the determination that the TO is valid, time domain resources for at least a portion of the TO are selected such that the at least portion does not span the at least one SBFD symbol and at least one non-SBFD symbol. In accordance with the above selection, to transmit or receive data in at least a portion of the TO, A non-temporary computer-readable medium containing program instructions that cause something to be executed.

Images