Multi-slot scheduling in SBFD

Abstract

Exemplary embodiments of the present disclosure relate to a terminal device, a network device, a method, an apparatus, and a computer-readable storage medium for multi-slot scheduling in the context of SBFD. The terminal device receives a DCI from a network device, the DCI including at least one FDRA field for at least one communication to be dynamically scheduled or activated. The terminal device determines different FDRAs for SBFD and non-SBFD communications based on the at least one FDRA field in the DCI. In this manner, the terminal device can perform communications based on the different FDRAs. In this manner, a larger bandwidth can be utilized in non-SBFD time units, improving the reliability of multi-slot scheduling and increasing resource efficiency.

Description

[Technical Field]

[0001] The exemplary embodiments of this disclosure generally relate to the field of telecommunications, and more particularly to terminal equipment, network equipment, methods, apparatus, and computer-readable storage media for solutions of multi-slot scheduling in the context of subband non-overlapping full-duplex (SBFD). [Background technology]

[0002] In recent years, the Third Generation Partnership Project (3GPP®) has agreed to initiate research on SBFD. SBFD enables simultaneous downlink (DL) and uplink (UL) transmission on different physical resource blocks (PRBs) or subbands within an unpaired broadband new radio (NR) cell.

[0003] Multiple UL or DL ​​transmissions can be scheduled across multiple slots; this is called multi-slot scheduling. In multi-slot scheduling, multiple transmissions may share the same frequency domain resource allocation. When multi-slot scheduling is performed in the context of SBFD, sharing the same frequency domain resource allocation can lead to insufficient utilization of frequency resources and reduced communication efficiency. [Overview of the project]

[0004] In general, exemplary embodiments of this disclosure provide solutions for multi-slot scheduling in the context of SBFD.

[0005] In a first embodiment, a terminal device is provided. The terminal device comprises 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 perform at least one of the following actions: receive downlink control information (DCI) from a network device, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated; determine a first frequency domain resource allocation (FDRA) in a first bandwidth for a first communication and a second FDRA in a second bandwidth for a second communication based on the at least one FDRA field in the DCI; and perform a first communication and a second communication with the network device, respectively, based on the first and second FDRAs, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is either an SBFD communication or a non-SBFD communication.

[0006] In a second embodiment, a network device is provided. The network device comprises at least one processor and at least one memory for storing instructions causing the network device to transmit, and to perform, based on the first and second FDRAs, a first communication and a second communication with the terminal device, respectively, when performed by the at least one processor, the first communication being either an SBFD communication or a non-SBFD communication, and the second communication being either an SBFD communication or a non-SBFD communication.

[0007] In a third embodiment, a method is provided that is performed by a terminal device. The method includes the terminal device receiving downlink control information (DCI) from a network device, which includes at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated; determining a first FDRA in a first bandwidth for a first communication and a second FDRA in a second bandwidth for a second communication based on at least one FDRA field in the DCI; and performing a first communication and a second communication with the network device, respectively, based on the first FDRA and the second FDRA, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is either an SBFD communication or a non-SBFD communication.

[0008] In a fourth embodiment, a method is provided that is performed by a network device. The method includes the network device transmitting downlink control information (DCI) to a terminal device, the DCI comprising at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated, wherein the at least one FDRA field in the DCI is for determining a first FDRA in a first bandwidth for a first communication and a second FDRA in a second bandwidth for a second communication; and performing first and second communications with the terminal device, respectively, based on the first and second FDRAs, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is either an SBFD communication or a non-SBFD communication.

[0009] In a fifth embodiment, the apparatus is provided. The apparatus includes means for receiving downlink control information (DCI) from a network device, which includes at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated at a terminal device; means for determining a first FDRA in a first bandwidth of a first communication and a second FDRA in a second bandwidth of a second communication based on at least one FDRA field in the DCI; and means for performing a first communication and a second communication with the network device, respectively, based on the first FDRA and the second FDRA, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is the other of either an SBFD communication or a non-SBFD communication.

[0010] In a sixth embodiment, the apparatus is provided. The apparatus is a network device, comprising means for transmitting downlink control information (DCI) to a terminal device, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated, wherein at least one FDRA in the DCI is for determining a first FDRA in a first bandwidth for a first communication and a second FDRA in a second bandwidth for a second communication; and means for performing a first communication and a second communication with the terminal device, respectively, based on the first FDRA and the second FDRA, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is the other of either an SBFD communication or a non-SBFD communication.

[0011] In a seventh embodiment, a non-temporary computer-readable medium is provided which includes program instructions for causing an apparatus to perform at least the method of the third or fourth embodiment.

[0012] In the eighth embodiment, a computer program is provided that, when executed by the apparatus, includes instructions causing the apparatus to perform at least the method of the third or fourth embodiment.

[0013] In a ninth embodiment, a terminal device is provided. The terminal device comprises: a receiving circuit configured to receive downlink control information (DCI) from a network device, which includes at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated; a determining circuit configured to determine a first FDRA in a first bandwidth for a first communication and a second FDRA in a second bandwidth for a second communication, based on at least one FDRA field in the DCI; and an executing circuit configured to perform first and second communications with the network device, respectively, based on the first and second FDRAs, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is the other either an SBFD communication or a non-SBFD communication.

[0014] In a tenth embodiment, a network device is provided. The network device comprises a transmitting circuit configured to transmit downlink control information (DCI) to a terminal device, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated, the at least one FDRA field in the DCI being for determining a first FDRA in a first bandwidth for a first communication and a second FDRA in a second bandwidth for a second communication; and an executing circuit configured to perform a first communication and a second communication with the terminal device, respectively, based on the first FDRA and the second FDRA, the first communication being either an SBFD communication or a non-SBFD communication, and the second communication being the other of either an SBFD communication or a non-SBFD communication.

[0015] In the eleventh embodiment, a computer-readable medium is provided which, when executed by the apparatus, contains program instructions causing the apparatus to perform at least the method of the third or fourth embodiment.

[0016] It should be understood that the Summary section is not intended to identify key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent from the following description. [Brief Description of the Drawings]

[0017] Several exemplary embodiments will now be described with reference to the accompanying drawings. [Figure 1A] Figure 1A shows a schematic diagram of FDD. [Figure 1B] Figure 1B shows a schematic diagram of TDD. [Figure 1C] Figure 1C shows a schematic diagram of FDU. [Figure 2A] Figure 2A shows a schematic diagram of common channel interference types in SBFD deployment. [Figure 2B] Figure 2B shows a schematic diagram of common channel interference types in SBFD deployment. [Figure 3A] Figure 3A is a schematic diagram illustrating an example of RA Type 0 of FDRA for PUSCH. [Figure 3B] Figure 3B is a schematic diagram illustrating an example of RA Type 1 of FDRA for PUSCH. [Figure 4] Figure 4 is a diagram illustrating examples of SBFD slots and non-SBFD slots. [Figure 5] Figure 5 is a diagram illustrating an example of a network environment in which some exemplary embodiments of the present disclosure may be implemented. [Figure 6] Figure 6 is a diagram illustrating an example of a process flow in some exemplary embodiments of the present disclosure. [Figure 7] Figure 7 shows a flowchart of a method implemented by a terminal device in some exemplary embodiments of the present disclosure. [Figure 8] Figure 8 shows a flowchart of a method implemented by a network device in some exemplary embodiments of the present disclosure. [Figure 9]Figure 9 shows a simplified block diagram of a device suitable for implementing some exemplary embodiments of the present disclosure. [Figure 10] Figure 10 shows a block diagram of an example of a computer-readable medium in some exemplary embodiments of the present disclosure. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. [Modes for carrying out the invention]

[0018] Next, the principles of this disclosure will be described with reference to several exemplary embodiments. These embodiments are provided for illustrative purposes only and are intended to help those skilled in the art understand and implement this disclosure, and should not be considered to imply any limitation on the scope of this disclosure. The disclosures described herein may be implemented in various other ways than those described below.

[0019] 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 those skilled in the art to which this disclosure belongs.

[0020] References in this disclosure to “one embodiment,” “embodiment,” “exemplary embodiment,” etc., indicate that the described embodiments may include certain features, structures, or characteristics, but not all embodiments are required to include such features, structures, or characteristics. Furthermore, such expressions do not necessarily refer to the same embodiment. In addition, if certain features, structures, or characteristics are described in relation to an embodiment, it is considered within the knowledge of those skilled in the art that such features, structures, or characteristics will be affected in relation to other embodiments, whether or not they are explicitly stated.

[0021] In this specification, terms such as “first” and “second” may be used to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are used merely to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the terms “and / or” include any one or more of the listed terms and all combinations thereof.

[0022] The terms used in this embodiment are for illustrative purposes only and do not limit the exemplary embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural form unless the context clearly indicates otherwise. As used herein, the terms "comprises," "comprising," "has," "having," "includes," and / or "including" identify, but do not exclude, the presence of the described features, elements, and / or components. As used herein, "at least one of the following, <list of two or more elements>" and "at least one of the <list of two or more elements>" and similar expressions mean at least one of the elements, or at least two or more of the elements, or at least all of the elements, when the lists of two or more elements are joined by "and" or "or."

[0023] As used in this application, the term "circuit" means (a) Hardware-only circuit implementation (such as implementation of analog and / or digital circuits only), (b) A combination of hardware circuitry and software, for example (where applicable), (i) combinations of analog and / or digital hardware circuits and software / firmware, (ii) A part that works in cooperation with a hardware processor (one or more) equipped with software (including a digital signal processor), software, and memory (one or more) to enable a device such as a mobile phone or server to perform various functions. (c) Hardware circuits (one or more), such as a microprocessor (one or more) or a part of a microprocessor (one or more), and processors (one or more), which require software (e.g., firmware) for operation, but may not be present when not required for operation. It may refer to one or more of these, or all of them.

[0024] This definition of circuit applies to all uses of the term in this application, including in the claims. As a further example, in the use of this embodiment, the term circuit also includes simply a hardware circuit or processor (or multiple processors), or a part of a hardware circuit or processor and the implementation of the software and / or firmware associated with it (or them). 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 equipment, or other computing or network equipment, where applicable to the elements of a particular claim.

[0025] As used herein, the term “communication network” refers to a network conforming to any appropriate communication standard, such as Long-Term Evolution (LTE), LTE-Advanced (LTE-A), New Radio (NR), Broadband Code Division Multiple Access (WCDMA®), High-Speed ​​Packet Access (HSPA), and Narrowband Internet of Things (NB-IoT). Furthermore, communication between terminal equipment and network equipment in a communication network is any of the first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), and sixth-generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, there will of course be future communication technologies and systems to which this disclosure can be embodied. The scope of this disclosure should not be considered to be limited to the aforementioned systems only.

[0026] As used herein, the term “network equipment” refers to a node in a communications network from which terminal devices access the network and receive services. Network equipment may refer to base stations (BS) or access points (APs), such as Node B (NodeB, or NB), evolved Node B (eNodeB, or eNB), new radio (NR) NB (also known as gNB), remote radio units (RRU), and may vary depending on the terminology and technology applied, including radio headers (RH), remote radio heads (RRH), integrated access backhaul (IAB) nodes, relays, and low-power nodes such as femto and pico.

[0027] The term "terminal equipment" refers to any end device capable of wireless communication. Examples, though not limited to, include communication equipment, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices include, but are not limited to, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture devices such as digital cameras, gaming devices, music storage and playback appliances, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless home equipment (CPEs), Internet of Things (IoT) devices, machine-type communication (MTC) devices, wearables such as watches, 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, and devices operating on commercial and / or industrial wireless networks. In the following description, the terms “terminal devices,” “communication devices,” “terminal,” “user devices,” and “UE” can be used interchangeably.

[0028] 3GPP® 5G NR currently supports two redundancy modes: frequency division duplexing (FDD) for paired bands and time division duplexing (TDD) for non-paired bands. Figures 1A and 1B are schematic diagrams of FDD and TDD, respectively. In TDD, time-domain resources are divided between the downlink and uplink, and limited time is allocated to the uplink, resulting in reduced coverage, increased latency, and reduced capacity.

[0029] Therefore, 3GPP® has agreed to address the above challenges by initiating the Release 18 (R18) research project on the evolution of duplication in NR. One of the objectives of this research project is to enable simultaneous transmission of DL and UL on different physical resource blocks (PRBs) / subbands within an unpaired broadband NR cell, which is sometimes referred to as subband non-overlapping full-duplex (SBFD).

[0030] In the context of this disclosure, the SBFD redundancy scheme may also be referred to as the cross-division redundancy (xDD) scheme or the flexible redundancy (FDU) scheme. Figure 1C shows a schematic diagram of the FDU.

[0031] The following text boxes describe some non-limiting purposes of the R18 research items related to SBFD. However, it should be noted that the exemplary embodiments of this disclosure are not limited to the purposes indicated in the text boxes. [Table 1]

[0032] SBFD may introduce at least one type of cross-link interference (CLI), sometimes referred to as common channel subband CLI. This interference can be classified as follows: (1) gNB self-interference, (2) intracellular UE-to-common channel subband CLI, (3) intercellular UE-to-common channel subband CLI, and (4) inter-gNB common channel subband CLI.

[0033] Figure 2A shows a schematic diagram of common channel interference types in SBFD deployment. It is assumed that gNB201 and gNB202 are in the same frequency domain partitioning, UE203 and UE204 are in the cell of gNB201, and UE205 and UE206 are in the cell of gNB202. Possible types of interference include gNB self-interference, an intra-cell UE-to-UE co-channel inter-subband CLI, an inter-cell UE-to-UE co-channel inter-subband CLI, an inter-cell UE-to-UE co-channel inter-subband CLI, or a gNB-to-gNB co-channel inter-subband CLI.

[0034] In addition to these new CLI types (1) to (4), if different frequency domain partitioning is performed in adjacent cells, the system may also be affected by common channel subband CLI, i.e., CLI due to transmission over overlapping frequency resources, (5) inter-cell co-channel intra-subband CLI between gNBs, and (6) inter-cell co-channel intra-subband CLI between UEs.

[0035] Figure 2B shows another schematic diagram of common channel interference types in SBFD deployment. It is assumed that gNB207 and gNB208 are in different frequency domain partitions, UE209 is in the cell of gNB207, and UE219 is in the cell of gNB208. There may be inter-cell co-channel intra-subband CLIs between gNBs (a gNB-to-gNB inter-cell co-channel intra-subband) or inter-cell co-channel intra-subband CLIs between UEs (a UE-to-UE inter-cell co-channel intra-subband) (a UE-to-UE inter-cell co-channel intra-subband).

[0036] In 5G NR, there are two main types of frequency domain resource allocations (FDRAs) for physical uplink shared channels (PUSCH): RA type 0 and RA type 1. Network equipment (such as gNBs) can configure either type 0 or type 1, or both, to indicate the RA type to be used for PUSCH transmissions scheduled by the scheduling DCI.

[0037] In uplink RA type 0, the resource block allocation information in the scheduling DCI includes a bitmap indicating the resource block group (RBG) to be allocated to the scheduled UE. An RBG is a set of contiguous resource blocks defined by the upper-layer parameter rbg-Size and the size of the bandwidth portion (BWP), which are set in push-Config. Table 1 shows two possible settings for rbg-Size for each range of BWP size. RA type 0 can represent non-contiguous PRBs by using the bitmap. [Table 2]

[0038] Figure 3A shows a schematic diagram 310 of an example of RA type 0 for FDRA for PUSCH. Assume that the BWP size 312 is equal to 20 RBs and the RBG size is equal to 4 RBs. The bitmap 314 included in the scheduling DCI may be "11001" in the example shown in Figure 3A.

[0039] RA type 1 is the starting resource block (RB). start (as shown by) and the length of the contiguously allocated resource block (L RBs The FDRA is shown via (indicated by ). Figure 3B is a schematic diagram showing an example of RA type 0 of PUSCH's FDRA. As shown in Figure 3B, the BWP size 322 is equal to 20 RBs, and RB start 324 and L RBs 326 (equivalent to 10 RBs) can be used to indicate FDRA.

[0040] It should be understood that RA Type 1 can reduce DCI overhead by avoiding the use of bitmaps. Resource block allocation information within the scheduling DCI is used for the scheduled UE, based on the size within the active BWP.

number

number

[0041] The resource allocation field for uplink type 1 is RB start and L RBs This includes the corresponding Resource Indication Value (RIV). start and L RBs Based on this, RIV is given as follows: If, [Math] if, [Math] and if not, [Math] is. Here, L RBs ≧1, and [Math] shall not be exceeded.

[0042] It should be noted that although FIGS. 3A to 3B illustrate the FDRA procedure for PUSCH, the similar FDRA procedure is also applicable to a physical downlink shared channel (PDSCH), and will not be repeated in the present disclosure.

[0043] Several techniques that allow scheduling multiple UL or DL transmissions in multiple slots with a single scheduling DCI have been specified and improved in previous releases of the 3GPP® specifications. For example, there are two techniques that can schedule multiple UL transmissions in multiple slots using a single DCI, which are referred to as PUSCH repetitions and multi-PUSCH scheduling. These techniques have the following common design aspects. A single DCI schedules multiple PUSCHs, and each PUSCH is within a slot. The scheduled PUSCHs have the same frequency domain resource allocation indicated by the single DCI (i.e., the same number of physical resource blocks (PRBs) and the same positions of these PRBs in the frequency domain).

[0044] However, these techniques have the following design differences.

[0045] In a PUSCH iteration, only the single start and length of the PUSCH within a slot is indicated by the scheduling DCI, i.e., the Single Start and Length Indicator Value (SLIV). This single SLIV is used by the UE to determine the time-domain resources of the PUSCH scheduled in each slot, depending on the PUSCH iteration type. (1) For PUSCH iteration type A (introduced / enhanced in Rel-15 / 16), the same start and length indicated by the single SLIV applies to all scheduled PUSCHs. (2) For PUSCH iteration type B (introduced in Rel-16), the single SLIV is used to determine multiple back-to-back nominal iterations of the same length, each nominal iteration may span a slot boundary. Each nominal iteration is then split into multiple actual iterations if it crosses a slot boundary or an invalid symbol. All PUSCH iterations are used to transmit a single transport block using the same Hybrid Auto-Retransmission Request (HARQ) process number as different redundant versions.

[0046] In multi-PUSCH scheduling (introduced / enhanced in Rel-16 / 17), a scheduling DCI can represent multiple SLIVs, with each valid SLIV corresponding to one PUSCH from multiple scheduled PUSCHs. The scheduled PUSCHs are used to send different transport blocks with different HARQ process numbers.

[0047] Similarly, downlink transmissions include PDSCH iteration and multi-PDSCH scheduling. PDSCH iteration is supported in 5G NR (introduced in Rel-15) using a mechanism similar to that described for PUSCH iteration type A. Multi-PDSCH scheduling is supported in 5G NR (introduced in Rel-17) using a mechanism similar to that described for multi-PUSCH scheduling.

[0048] In addition to PUSCH / PDSCH iterations scheduled by DCI (referred to as Dynamic Grants (DGs)), there is also a framework for transmitting iterations without scheduling DCIs, which is called Semi-Persistent Scheduling (SPS) for PDSCH or Configured Grants (CG) for PUSCH. The idea behind SPS / CG scheduling is that transmission opportunities are pre-configured via RRC, and gNB / UEs can transmit data to these opportunities without transmitting / waiting for DCIs. There are also two types of CG PUSCHs: Type 1 CG PUSCHs do not require activation DCIs, while Type 2 CG PUSCHs require DCIs to activate the use of transmission opportunities. For Type 1 CG PUSCHs, the time and frequency resources of the transmission opportunities are indicated by the RRC settings. For Type 2 CG PUSCHs, the time and frequency resources of the transmission opportunities are indicated by activation DCIs.

[0049] Based on the SBFD operation description shown in Figure 1C, it is observed that there are two slot types for both DL and UL transmissions: SBFD slots and non-SBFD slots. Figure 4 shows an illustrative figure of SBFD and non-SBFD slots. As shown in Figure 4, DL transmissions can be performed within non-SBFD slots 432 and SBFD slots 434, and UL transmissions can be performed within SBFD slots 434 and non-SBFD slots 436. In other words, both non-overlapping DL subbands and UL subbands reside within SBFD slot 434, with the entire bandwidth used for DL ​​transmissions in non-SBFD slot 432 and the entire bandwidth used for UL transmissions in non-SBFD slot 436. In some embodiments, non-SBFD slot 432 may also be called a legacy slot or a full DL slot, and non-SBFD slot 436 may also be called a legacy slot or a full UL slot.

[0050] While SBFD slots and non-SBFD slots are illustrated with reference to Figure 4, please note that this disclosure also applies to SBFD minislots and non-SBFD minislots, or SBFD symbols and non-SBFD symbols, or other time units not listed herein.

[0051] In the context of this disclosure, the term "SBFD-aware UE" may be used, and an SBFD-aware UE is at least aware of the operating modes relating to the time and frequency positions of the subbands for SBFD operation. In the context of this disclosure, terms such as SBFD-aware, FDU-aware, SBFD-capable, and FDU-capable may be used interchangeably.

[0052] Based on the explanation of multi-slot scheduling, scheduled PUSCH / PDSCH have the same frequency-domain resource allocation. In the context of SBFD, assigning the same frequency-domain resource allocation to scheduled PUSCH / PDSCH may lead to inefficient use of frequency-domain resources and therefore requires further consideration.

[0053] Exemplary embodiments of this disclosure provide a solution for multi-slot scheduling in the context of SBFD. In particular, terminal equipment can receive DCI from network equipment and determine different FDRAs for SBFD and non-SBFD communications. Thus, terminal equipment can perform communications based on different FDRAs. Consequently, a larger bandwidth can be utilized in non-SBFD time units, the reliability of multi-slot scheduling can be improved, and resource efficiency can be increased. The principles of this disclosure and some exemplary embodiments will be described in detail below with reference to the accompanying drawings.

[0054] Figure 5 shows an example of a network environment 500 in which several exemplary embodiments of the present disclosure may be implemented. The environment 500, which is part of a communication network, includes terminal equipment 510 and network equipment 520.

[0055] The communication environment 500 may include any appropriate number of devices and cells. In the communication environment 500, the network device 520 can provide services to the terminal device 510, and the network device 520 and the terminal device 510 can communicate data and control information with each other. In some embodiments, the network device 520 and the terminal device 510 can communicate via a direct link / channel.

[0056] In system 500, the link from network device 520 to terminal device 510 is called a downlink (DL), and the link from terminal device 510 to network device 520 is called an uplink (UL). In a downlink, network device 520 is a transmitting (TX) device (or transmitter), and terminal device 510 is a receiving (RX) device (or receiver). In an uplink, terminal device 510 is a transmitting TX device (or transmitter), and network device 520 is an RX device (or receiver). It should be understood that network device 520 may provide one or more serving cells. In some embodiments, network device 520 may provide multiple cells.

[0057] Communication in network environment 500 can be carried out in accordance with any suitable communication protocol(s), including but not limited to, cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local network communication protocols such as IEEE 802.11, and / or other protocols 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 duplexing (FDD), time division duplexing (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technologies currently known or to be developed in the future.

[0058] It should be understood that the number of devices (i.e., terminal devices 510 and network devices 520) shown in Figure 5, as well as their connectivity and types, are for illustrative purposes only and do not imply any limitation. For example, environment 500 may include any suitable number of devices adapted to carry out embodiments of this disclosure. For example, while Figure 5 depicts terminal device 510 as a mobile phone, terminal device 510 may be any type of user device.

[0059] Figure 6 shows an example of process flow 600 in some exemplary embodiments of this disclosure. For illustrative purposes, process flow 600 will be described with reference to Figure 5. Process flow 600 includes terminal equipment 510 and network equipment 520. Although process flow 300 has been described in the network environment 500 of Figure 5, it should be understood that this process flow can be similarly applied to other communication scenarios.

[0060] In some exemplary embodiments, alternatively, as shown in Figure 6, the network device 520 may transmit configuration information 612 to the terminal device 510 (610). In some examples, the configuration information is transmitted via RRC messages or RRC signaling.

[0061] In some embodiments, the configuration information 612 may indicate one or more of the following: frequency band, a first number of time units for both uplink and downlink transmissions, a first position of the first number of time units in a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units in a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units in a radio frame, or a resource allocation type. In some embodiments, the time unit may be a slot, a minislot, or a symbol. In some embodiments, the configuration information 612 may indicate: frequency band, The number of slots / minislots / symbols between which the frequency band is divided into multiple subbands, with at least one subband used for DL ​​transmission and at least one other subband used for UL transmission, i.e., the number of SBFD slots / minislots / symbols, and the position of the number of SBFD slots / minislots / symbols within the radio frame. The number of slots / minislots / symbols used for DL ​​or UL transmission across the entire frequency band, i.e., the number of non-SBFD slots / minislots / symbols, and the position of the number of SBFD slots / minislots / symbols within the radio frame, as well as, Resource allocation type, This could demonstrate that.

[0062] In some exemplary embodiments, the resource allocation type may be one or more of RA type 0 or RA type 1. In exemplary embodiments, the configuration information 612 may further indicate trigger information. The trigger information may be used to prompt the terminal device 510 to determine different FDRAs for SBFD and non-SBFD communications.

[0063] On the other end of the communication, terminal device 510 receives configuration information 612 (614). In this disclosure, it is assumed that terminal device 510 is an SBFD-aware UE.

[0064] Additionally or alternatively, the network device 520 may transmit trigger information to the terminal device 510, and the terminal device 510 may receive the trigger information accordingly. In some exemplary embodiments, the trigger information and configuration information 612 may be transmitted in the same RRC message or in different RRC messages. In some exemplary embodiments, the trigger information may be carried in DCI.

[0065] In some embodiments, trigger information may be used to prompt the terminal device 510 to determine different FDRAs for SBFD and non-SBFD communications based on at least one FDRA file in the DCI (an exemplary single FDRA field).

[0066] The network device 520 transmits DCI622 to the terminal device 510. In some embodiments, DCI622 includes at least one FDRA field for at least one communication that is dynamically scheduled or activated.

[0067] In some exemplary embodiments, at least two communications are dynamically scheduled or activated by the DCI622, and these at least two communications include at least one SBFD communication and at least one non-SBFD communication. In some examples, the communications are dynamically scheduled or activated by a single DCI without introducing additional bits.

[0068] In some examples, DCI622 may indicate that part of the communication is scheduled or set in SBFD time units, and other parts of the communication are scheduled or set in non-SBFD time units. The time units may be slots, minislots, or symbols.

[0069] For example, DCI622 may indicate that the first communication is scheduled or configured in an SBFD slot and the second communication is scheduled or configured in a non-SBFD slot. In other embodiments, DCI622 may indicate that the first communication is scheduled or configured in a non-SBFD slot and the second communication is scheduled or configured in an SBFD slot.

[0070] In some examples, with respect to terminal device 510, the first and second communications may be transmissions to network device 520, and with respect to network device 520, the first and second transmissions may be receptions from terminal device 510. In some other embodiments, with respect to terminal device 510, the first and second communications may be receptions from network device 520, and with respect to network device 520, the first and second transmissions may be transmissions to terminal device 510.

[0071] In some embodiments, the first and second communications are push iterations or multi-push scheduling. In some other embodiments, the first and second communications are PDSCH iterations or multi-PDSCH scheduling. In some other embodiments, the first and second communications may be type 1 CG push transmissions, type 2 CG push transmissions, or DG push transmissions.

[0072] In some exemplary embodiments, the number of communications scheduled or configured by the DCI622 may be two or more, and for ease of explanation, two communications (i.e., a first communication and a second communication) are described in the following disclosure.

[0073] In some exemplary embodiments, DCI622 includes at least one FDRA file, for example, DCI622 includes a single FDRA field. In some exemplary embodiments, at least one FDRA is associated with a first bandwidth of a first communication. In some embodiments, the type of the first communication (SBFD or non-SBFD) can be predefined by being preconfigured by the network device 520.

[0074] Additionally or alternatively, the network device 520 may send a notification to the terminal device 510 that indicates the type of first communication associated with at least one FDRA in DCI 622. Thus, the terminal device 510 can receive the notification and know the type of first communication. In some examples, the notification may be sent as an RRC message. For example, the RRC message may be the same as the one that sends the configuration information 612, or it may be different from the one that sends the configuration information 612.

[0075] For example, if the type of first communication is SBFD communication, in other words, if the first communication is scheduled in an SBFD slot (or mini-slot, or symbol), then at least one FDRA field is associated with the UL / DL subband bandwidth used for the SBFD slot (or mini-slot, or symbol). In another example, if the type of first communication is non-SBFD communication, in other words, if the first communication is scheduled in a non-SBFD slot (or mini-slot, or symbol), then at least one FDRA field is associated with the entire UL / DL broadband bandwidth used for the non-SBFD slot (or mini-slot, or symbol).

[0076] In some exemplary embodiments, a rule can be specified to predefine that at least one FDRA field in DCI622 is associated with the bandwidth of a non-SBFD slot (or minislot, or symbol), i.e., the entire UL / DL broadband bandwidth used for the non-SBFD slot (or minislot, or symbol). In some other exemplary embodiments, a rule can be specified to predefine that at least one FDRA field in DCI622 is associated with the bandwidth of an SBFD slot (or minislot, or symbol), i.e., the UL / DL subband bandwidth used for the SBFD slot (or minislot, or symbol).

[0077] On the other end of the communication, terminal device 510 receives DCI622 (624). Thus, terminal device 510 can obtain at least one filed FDRA (such as a single filed FDRA).

[0078] The terminal device 510 determines the first FDRA and the second FDRA based on DCI622 (640). Specifically, the terminal device 510 determines the first FDRA for the first communication in the first bandwidth and the second FDRA for the second communication in the second bandwidth based on at least one FDRA field in DCI622.

[0079] In some exemplary embodiments, terminal device 510 may determine a first FDRA based on at least one FDRA field in DCI622, and terminal device 510 may determine a second FDRA based on the first FDRA or based on a setting from network device 520.

[0080] In some embodiments, the terminal device 510 may determine a first FDRA based on at least one FDRA file in DCI 622 and the resource allocation type indicated by configuration information 612.

[0081] [When the resource allocation type is RA type 0] Terminal device 510 may determine a first FDRA based on an FDRA filed in DCI612 or based on a setting from network device 520. Specifically, terminal device 510 may determine a first set of a first number of RGBs, and then determine the first FDRA based on the first set of a first number of RGBs (which may be called the first RGB size).

[0082] For example, terminal device 510 can determine a first RGB size for a first communication based on an FDRA field such as a bitmap in DCI622. In another example, if network device 520 sets a UL / DL broadband RGB size and the first communication is associated with a UL / DL broadband bandwidth, terminal device 510 can determine a first RGB size for the first communication based on the set UL / DL broadband RGB size. In yet another example, if network device 520 sets a UL / DL subband RGB size and the first communication is associated with a UL / DL subband bandwidth, terminal device 510 can determine a first RGB size for the first communication based on the set UL / DL subband RGB size.

[0083] Terminal device 510 may determine the second FDRA based on the first FDRA or based on settings from network device 520. Specifically, terminal device 510 may determine a second set of a second number of RGBs, and then determine the second FDRA based on the second set of the second number of RGBs (also called the second RGB size).

[0084] In some embodiments, the second RBG size may be determined based on the first RBG size and offset. For example, equation (3) below may be used to determine the second FDRA based on the first FDRA. Subband RGB / Broadband RGB = offset (3)

[0085] In equation (3), the subband RBG and broadband RBG may be in PRB units. For example, if the first communication is SBFD communication and the second communication is not SBFD communication, the second FDRA may be determined by subband RBG / offset. If the first communication is not SBFD communication and the second communication is SBFD communication, the second FDRA may be determined by broadband RBG × offset.

[0086] In this embodiment, the offset is the ratio of the bandwidth of the subband of SBFD communication to the bandwidth of non-SBFD communication, for example, offset = subband bandwidth / broadband bandwidth. In some embodiments, the offset may be set by the network device 520, for example, the network device 520 may set the value of the offset, which is greater than 0 and less than 1.

[0087] In some other examples, if network device 520 has set a UL / DL broadband RGB size and the second communication is associated with the UL / DL broadband bandwidth, terminal device 510 may determine the second RGB size for the second communication based on the set UL / DL broadband RGB size. In other examples, if network device 520 has set a UL / DL subband RGB size and the second communication is associated with the UL / DL subband bandwidth, terminal device 510 may determine the second RGB size for the second communication based on the set UL / DL subband RGB size.

[0088] [When the resource allocation type is RA type 1] Terminal device 510 may determine the first FDRA based on the FDRA filed in DCI612. Specifically, terminal device 510 may determine the first index and first length of the first starting resource block and determine the first FDRA based on the first index and first length of the first starting resource block.

[0089] For example, terminal device 510 may determine the first index and first length of the first initiation resource block based on FDRA fields such as RIV in DCI622. If the first communication relates to UL / DL broadband bandwidth, the first index and first length of the first initiation resource block are, respectively, broadband RB start and broadband L RBSThis can be represented by: When the first communication is associated with the UL / DL subband bandwidth, the first index and first length of the first starting resource block are, respectively, subband RB start and subband L RBS It can be represented by [this].

[0090] Terminal device 510 may determine the second FDRA based on the first FDRA. Specifically, terminal device 510 may determine the second index and second length of the second starting resource block and determine the second FDRA based on the second index and second length of the second starting resource block.

[0091] In some embodiments, the second index of the second starting resource block may be determined based on the first index and offset. For example, the following equation (4) may be used. Subband RB start / Broadband RB start =offset (4)

[0092] For example, if the first communication is SBFD communication and the second communication is not SBFD communication, the second index of the second starting resource block is subband RB. start This can be determined by / offset. If the first communication is non-SBFD communication and the second communication is SBFD communication, the second index of the second starting resource block is broadband RB. start This can be determined by the offset.

[0093] In some other embodiments, the second index of the second starting resource block may be determined based on the first index, the offset, and a further offset set by the network device 520. For example, the following equation (5) may be used. Broadband RB start ×offset=subband RB start +offset2(5)

[0094] In equation (5), offset2 represents a further offset and may be a positive or negative value. For example, if the first communication is SBFD communication and the second communication is not SBFD communication, the second index of the second starting resource block is (subband RB start This can be determined by (+offset2) / offset. If the first communication is non-SBFD communication and the second communication is SBFD communication, the second index of the second starting resource block is broadband RB. start This can be determined by ×offset-offset2.

[0095] Equation (5) is used for illustrative purposes only without limitation, and it should be understood that, for example, further offsets may be represented by offset3, which may be a positive or negative value, and equation (6) may be used. Broadband RB start -offset3=subband RB start / offset (6)

[0096] In some embodiments, the second length may be determined based on the first length and the offset. For example, the following equation (4) may be used. Subband L RBS / Broadband L RBS =offset (7)

[0097] For example, if the first communication is SBFD communication and the second communication is not SBFD communication, the length of the second communication is subband L. RBS This can be determined by / offset. If the first communication is non-SBFD communication and the second communication is SBFD communication, the length of the second is broadband L RBS This can be determined by the offset.

[0098] Thus, the terminal device 510 can determine the first FDRA and the second FDRA based on one or more of at least one FDRA field, resource allocation type, offset, or further offsets in the DCI622.

[0099] In some other exemplary embodiments, if the DCI622 schedules or sets a single transmit / receive on an SBFD slot / minislot / symbol and the FDRA field in the DCI622 is associated with a subband bandwidth or a broadband bandwidth, the terminal device 510 may similarly determine the FDRA for a single transmit / receive on an SBFD slot / minislot / symbol.

[0100] Network device 520 determines the first FDRA and the second FDRA (650). The determination in 650 is the same as the determination in 640, and therefore will not be repeated here.

[0101] Terminal device 510 and network device 520 perform first communication and second communication (660). Specifically, terminal device 510 can perform first communication and second communication based on first FDRA and second FDRA, respectively, and network device 520 performs first communication and second communication based on first FDRA and second FDRA, respectively.

[0102] The order of the first and second communications is determined based on configuration information 612 and DCI 622. Referring to Figure 4, taking UL transmission as an example, if at least one FDRA field in DCI 622 is associated with the bandwidth of the first communication and the type of the first communication is SBFD communication, then terminal equipment 510 can perform the first communication (first transmission) based on the first FDRA during SBFD slot 434, and then perform the second communication (second transmission) based on the second FDRA during non-SBFD slot 436. From the perspective of network equipment 520, network equipment 520 can perform the first communication (first reception) based on the first FDRA during SBFD slot 434, and then perform the second communication (second reception) based on the second FDRA during non-SBFD slot 436.

[0103] Referring to Figure 4, and taking DL transmission as an example, if at least one FDRA field in DCI622 is associated with the bandwidth of the first communication and the type of the first communication is SBFD communication, then terminal device 510 can perform the second communication (second reception) based on the second FDRA during the non-SBFD slot 432, and then perform the first communication (first reception) based on the first FDRA during the SBFD slot 434. From the perspective of network device 520, network device 520 can perform the second communication (second transmission) based on the second FDRA during the non-SBFD slot 432, and then perform the first communication (first transmission) based on the first FDRA during the SBFD slot 434.

[0104] According to an exemplary embodiment with reference to Figure 6, when communication is dynamically scheduled or activated by DCI, terminal equipment 510 can determine different FDRAs for SBFD communication and non-SBFD communication. Thus, the exemplary embodiment provides a solution for showing greater physical resources for PUSCH / PDSCH iterations in non-SBFD slots / minislots / symbols compared to PUSCH / PDSCH iterations in SBFD slots / minislots / symbols. Therefore, for the same time-domain resource allocation, PUSCH / PDSCH iterations in non-SBFD slots / minislots / symbols will have greater physical resources, i.e., a larger number of resource elements (REs), compared to PUSCH / PDSCH iterations in SBFD slots / minislots / symbols. Consequently, greater bandwidth can be utilized in non-SBFD slots / minislots / symbols, the reliability of PUSCH / PDSCH iterations can be improved, and communication efficiency can be improved.

[0105] For example, with larger resources and the same transport block size (TBS), push / PDSCH iterations in non-SBFD slots / minislots / symbols can transmit more encoded bits (e.g., multiple cycles from a circular buffer), thus improving the reliability of the iterations. For example, multi-push scheduling or multi-PDSCH scheduling can map larger TBSs to transmissions in non-SBFD slots / minislots / symbols with larger resources, improving the data rate for the same advertised MCS. Furthermore, since the DCI size does not increase in this disclosure, overhead issues can be avoided.

[0106] Figure 7 shows a flowchart 700 of a method implemented in a terminal device according to some exemplary embodiments of the present disclosure. For illustrative purposes, the method 500 will be described in terms of a terminal device 510 with reference to Figure 5.

[0107] In block 710, terminal equipment 510 receives downlink control information (DCI) from network equipment 520, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated. In block 720, terminal equipment 510 determines a first FDRA for a first communication in a first bandwidth and a second FDRA for a second communication in a second bandwidth based on at least one FDRA field in the DCI, where the first communication is either SBFD communication or non-SBFD communication, and the second communication is the other of either SBFD communication or non-SBFD communication. In block 730, terminal equipment 510 performs the first communication and the second communication with network equipment 520, respectively, based on the first FDRA and the second FDRA.

[0108] In some exemplary embodiments, terminal equipment 510 receives configuration information from network equipment 520, which includes one or more of the following: frequency band, a first number of time units for both uplink and downlink transmissions, a first position of the first number of time units in a wireless frame, a second number of time units for uplink transmissions, a second position of the second number of time units in a wireless frame, a third number of time units for downlink transmissions, a third position of the third number of time units in a wireless frame, or a resource allocation type.

[0109] In some exemplary embodiments, the time unit is a slot, or mini-slot, or symbol.

[0110] In some exemplary embodiments, the configuration information includes trigger information, which prompts the terminal device 510 to determine different FDRAs for SBFD and non-SBFD communications.

[0111] In some exemplary embodiments, the DCI further includes trigger information, which prompts the terminal device 510 to determine different FDRAs for SBFD and non-SBFD communications.

[0112] In some exemplary embodiments, the terminal device 510 determines a first FDRA based on at least one FDRA field in the DCI, and the terminal device 510 determines a second FDRA based on the first FDRA and an offset.

[0113] In some exemplary embodiments, based on determining that the resource allocation type indicated by configuration information from network device 520 is type 0, terminal device 510 determines a first set of a first number of resource block groups (RGB) based on at least one FDRA field in DCI.

[0114] In some exemplary embodiments, the terminal device 510 determines a second set of RGB values ​​of a second number based on a first number and an offset.

[0115] In some exemplary embodiments, based on determining that the resource allocation type indicated by configuration information from the network device is type 1, the terminal device 510 determines a first index and a first length of a first starting resource block based on at least one FDRA field in the DCI.

[0116] In some exemplary embodiments, terminal device 510 determines a second index of a second starting resource block based on a first index and an offset, and terminal device 510 determines a second length based on a first length and an offset.

[0117] In some exemplary embodiments, terminal device 510 determines a second index of a second starting resource block based on a first index, an offset, and a further offset set by the network device.

[0118] In some exemplary embodiments, the offset includes one or more of the ratio of the bandwidth of the subband for SBFD communication to the bandwidth of the non-SBFD communication band, or values ​​set by the network device 520.

[0119] In some exemplary embodiments, based on determining that the resource allocation type notified by configuration information from the network device is type 0, the terminal device 510 determines a first set of a first number of resource block groups (RGB) based on at least one FDRA field in the DCI, and the terminal device 510 determines a second set of a second number of RGB based on the configuration from the network device.

[0120] In some exemplary embodiments, the type of first communication associated with at least one FDRA field is predefined or set by the network device 520.

[0121] In some exemplary embodiments, SBFD communication is performed on an SBFD slot, or an SBFD minislot, or an SBFD symbol, while non-SBFD communication is performed on a non-SBFD slot, or a non-SBFD minislot, or a non-SBFD symbol.

[0122] In some exemplary embodiments, the first and second communications are transmissions to the network device 520, or the first and second communications are receptions from the network device 520.

[0123] In some exemplary embodiments, the first and second communications are physical uplink shared channel (PUSCH) iterations or physical downlink shared channel (PDSCH) iterations.

[0124] In some exemplary embodiments, the first and second communications are multi-PUSCH scheduling or multi-PDSCH scheduling.

[0125] Figure 8 shows a flowchart 800 of a method implemented in a network device in some exemplary embodiments of the present disclosure. For illustrative purposes, the method 800 will be described in reference to a network device 520 with reference to Figure 5.

[0126] In block 810, the network device 520 transmits downlink control information (DCI) to the terminal device 510, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated, the at least one FDRA in the DCI being used to determine a first FDRA in the first bandwidth of a first communication and a second FDRA in the second bandwidth of a second communication, the first communication being either an SBFD communication or a non-SBFD communication, and the second communication being the other of either an SBFD communication or a non-SBFD communication. In block 820, the network device 520 performs the first and second communications with the terminal device, respectively, based on the first and second FDRAs.

[0127] In some exemplary embodiments, the network device 520 transmits configuration information to the terminal device 510, which includes one or more of the following: frequency band, a first number of time units for both uplink and downlink transmissions, a first position of the first number of time units in a wireless frame, a second number of time units for uplink transmissions, a second position of the second number of time units in a wireless frame, a third number of time units for downlink transmissions, a third position of the third number of time units in a wireless frame, or a resource allocation type.

[0128] In some exemplary embodiments, the time unit is a slot, or mini-slot, or symbol.

[0129] In some exemplary embodiments, configuration information includes trigger information, which prompts terminal equipment to determine different FDRAs for SBFD and non-SBFD communications.

[0130] In some exemplary embodiments, the DCI further includes trigger information, which prompts the terminal device 510 to determine different FDRAs for SBFD and non-SBFD communications.

[0131] In some exemplary embodiments, the network device 520 determines a first FDRA based on at least one FDRA field in the DCI, and the network device 520 determines a second FDRA based on the first FDRA and the offset.

[0132] In some exemplary embodiments, based on determining that the resource allocation type is type 0, the network device 520 determines a first set of a first number of resource block groups (RGB) based on at least one FDRA field in the DCI.

[0133] In some exemplary embodiments, the network device 520 determines a second set of RGB values ​​of a second number based on a first number and an offset.

[0134] In some exemplary embodiments, based on determining that the resource allocation type is type 1, the network device 520 determines a first index and a first length of a first starting resource block based on at least one FDRA field in the DCI.

[0135] In some exemplary embodiments, the network device 520 determines a second index of a second starting resource block based on a first index and an offset, and the network device 520 determines a second length based on a first length and an offset.

[0136] In some exemplary embodiments, the network device 520 determines a second index of a second starting resource block based on a first index, an offset, and a further offset defined in the network device.

[0137] In some exemplary embodiments, the offset includes one or more of the ratio of the bandwidth of the subband for SBFD communication to the bandwidth of the non-SBFD communication band, or values ​​defined in the network equipment.

[0138] In some exemplary embodiments, network device 520 transmits a configuration to terminal device 510, the configuration indicating that the second FDRA includes a second set of RGBs of a second number.

[0139] In some exemplary embodiments, network device 520 sends a notification to terminal device 510 which notifies of the type of first communication associated with at least one FDRA field.

[0140] In some exemplary embodiments, SBFD communication is performed on an SBFD slot, or an SBFD minislot, or an SBFD symbol, while non-SBFD communication is performed on a non-SBFD slot, or a non-SBFD minislot, or a non-SBFD symbol.

[0141] In some exemplary embodiments, the first and second communications are either received from the terminal device 510, or the first and second communications are transmitted to the terminal device 510.

[0142] In some exemplary embodiments, the first and second communications are physical uplink shared channel (PUSCH) iterations or physical downlink shared channel (PDSCH) iterations.

[0143] In some exemplary embodiments, the first and second communications are multi-PUSCH scheduling or multi-PDSCH scheduling.

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

[0145] In some exemplary embodiments, the apparatus comprises: means for receiving from a network device to a terminal device, wherein the downlink control information (DCI) includes at least one frequency domain resource allocation (FDRA) field for at least one communication that is dynamically scheduled or activated; means for determining a first FDRA in a first bandwidth of a first communication and a second FDRA in a second bandwidth of a second communication based on at least one FDRA field in the DCI; and means for performing a first communication and a second communication with the network device, respectively, based on the first FDRA and the second FDRA, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is the other either an SBFD communication or a non-SBFD communication.

[0146] In some exemplary embodiments, the device further comprises means for receiving configuration information from network equipment, the configuration information indicating at least one of a frequency band, a first number of time units for both uplink and downlink transmissions, a first position of the first number of time units in a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units in a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units in a radio frame, or a resource allocation type.

[0147] In some exemplary embodiments, the time unit is a slot, or mini-slot, or symbol.

[0148] In some exemplary embodiments, configuration information includes trigger information, which prompts terminal equipment to determine different FDRAs for SBFD and non-SBFD communications.

[0149] In an exemplary embodiment, the DCI further includes trigger information, which prompts the terminal equipment to determine different FDRAs for SBFD and non-SBFD communications.

[0150] In some exemplary embodiments, means for determining the first FDRA and the second FDRA include means for determining the first FDRA based on at least one FDRA field in the DCI, and means for determining the second FDRA based on the first FDRA and the offset.

[0151] In some exemplary embodiments, means for determining a first FDRA include means for determining a first set of a first number of resource block groups (RGB) based on at least one FDRA field in the DCI, according to a determination that the resource allocation type indicated by configuration information from a network device is of type 0.

[0152] In some exemplary embodiments, means for determining a second FDRA include means for determining a second set of a second number of RGB values ​​based on a first number and an offset.

[0153] In some exemplary embodiments, means for determining the first FDRA include means for determining a first index and a first length of a first starting resource block based on at least one FDRA field in the DCI, according to a determination that the resource allocation type indicated by configuration information from a network device is of type 1.

[0154] In some exemplary embodiments, means for determining the second FDRA include means for determining the second index of the second starting resource block based on a first index and an offset, and means for determining the second length based on a first length and an offset.

[0155] In some exemplary embodiments, means for determining a second index include means for determining a second index of a second starting resource block based on a first index, an offset, and a further offset set by a network device.

[0156] In some exemplary embodiments, the offset includes at least one of the ratio of the bandwidth of the subband for SBFD communication to the bandwidth of the non-SBFD communication band, or a value set by the network equipment.

[0157] In some exemplary embodiments, means for determining the first FDRA and the second FDRA include means for determining a first set of a first number of resource block groups (RGB) based on at least one FDRA field in the DCI, according to a determination that the resource allocation type indicated by configuration information from the network device is type 0, and means for determining a second set of a second number of RGB based on the configuration from the network device.

[0158] In some exemplary embodiments, the type of first communication associated with at least one FDRA field is either predefined or configured by the network equipment.

[0159] In some exemplary embodiments, SBFD communication is performed on an SBFD slot, or an SBFD minislot, or an SBFD symbol, while non-SBFD communication is performed on a non-SBFD slot, or a non-SBFD minislot, or a non-SBFD symbol.

[0160] In some exemplary embodiments, the first and second communications are transmissions to network devices, or the first and second communications are receptions from network devices.

[0161] In some exemplary embodiments, the first and second communications are physical uplink shared channel (PUSCH) iterations or physical downlink shared channel (PDSCH) iterations.

[0162] In some exemplary embodiments, the first and second communications are multi-PUSCH scheduling or multi-PDSCH scheduling.

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

[0164] Apparatus in some exemplary embodiments includes means for transmitting downlink control information (DCI) to terminal equipment in a network device, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one communication to be dynamically scheduled or activated, wherein at least one FDRA in the DCI is used to determine a first FDRA in a first bandwidth for a first communication and a second FDRA in a second bandwidth for a second communication; and means for performing first and second communications with terminal equipment, respectively, based on the first and second FDRAs, wherein the first communication is either an SBFD communication or a non-SBFD communication, and the second communication is either an SBFD communication or a non-SBFD communication.

[0165] In some exemplary embodiments, the apparatus further comprises means for transmitting configuration information to a terminal device, wherein the configuration information indicates at least one of the following: a frequency band, a first number of time units for both uplink and downlink transmissions, a first position of the first number of time units in a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units in a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units in a radio frame, or a resource allocation type.

[0166] In some exemplary embodiments, the time unit is a slot, or mini-slot, or symbol.

[0167] In some exemplary embodiments, configuration information includes trigger information, which prompts terminal equipment to determine different FDRAs for SBFD and non-SBFD communications.

[0168] In an exemplary embodiment, the DCI further includes trigger information, which prompts the terminal device to determine different FDRAs for SBFD and non-SBFD communications.

[0169] In an exemplary embodiment, the apparatus further comprises means for determining a first FDRA based on at least one FDRA field in the DCI, and means for determining a second FDRA based on the first FDRA and an offset.

[0170] In some exemplary embodiments, means for determining a first FDRA include means for determining a first set of a first number of resource block groups (RGB) based on at least one FDRA field in the DCI, according to a determination that the resource allocation type is type 0.

[0171] In some exemplary embodiments, means for determining a second FDRA include means for determining a second set of a second number of RGBs based on a first number and an offset.

[0172] In some exemplary embodiments, means for determining the first FDRA include means for determining a first index and a first length of a first starting resource block based on at least one FDRA field in the DCI, according to the determination that the resource allocation type is type 1.

[0173] In some exemplary embodiments, means for determining the second FDRA include means for determining the second index of the second starting resource block based on a first index and an offset, and means for determining the second length based on a first length and an offset.

[0174] In some exemplary embodiments, means for determining a second index include means for determining a second index of a second starting resource block based on a first index, an offset, and a further offset defined in the network device.

[0175] In some exemplary embodiments, the offset includes at least one of the ratio of the bandwidth of the subband for SBFD communication to the bandwidth of the non-SBFD communication band, or a value defined in the network equipment.

[0176] In some exemplary embodiments, the device further comprises means for transmitting a setting to a terminal device, the setting indicating that the second FDRA includes a second set of RGBs of a second number.

[0177] In some exemplary embodiments, the apparatus further comprises means for transmitting a notification to a terminal device, wherein the notification indicates a type of first communication relating to at least one FDRA field.

[0178] In an exemplary embodiment, SBFD communication is performed on an SBFD slot, or an SBFD minislot, or an SBFD symbol, while non-SBFD communication is performed on a non-SBFD slot, or a non-SBFD minislot, or a non-SBFD symbol.

[0179] In some exemplary embodiments, the first and second communications are either received from a terminal device or transmitted to a terminal device.

[0180] In some exemplary embodiments, the first and second communications are physical uplink shared channel (PUSCH) iterations or physical downlink shared channel (PDSCH) iterations.

[0181] In exemplary embodiments, the first and second communications are multi-PUSCH scheduling or multi-PDSCH scheduling.

[0182] Figure 9 shows a simplified block diagram of a device 900 suitable for implementing some exemplary embodiments of the present disclosure. The device 900 may be provided for implementing, for example, a communication device such as a terminal device 510 as shown in Figure 5, or a network device 520. As shown, the device 900 includes one or more processors 910, one or more memories 920 connected to the processors 910, and one or more communication modules 940 connected to the processors 910.

[0183] The communication module 940 is for bidirectional communication. The communication module 940 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communication with other network elements.

[0184] The processor 910 may be of any type suitable for a local technology network and may include, in non-limiting examples, one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. The device 900 may have multiple processors, such as special-purpose integrated circuit chips, which are time-slewn to a clock that synchronizes the main processor.

[0185] Memory 920 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) 924, electronically programmable 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, but are not limited to, random-access memory (RAM) 922 and other volatile memories that do not persist for the power-down duration.

[0186] The computer program 930 includes computer executable instructions that are executed by the associated processor 910. The program 930 may be stored in the ROM 924. The processor 910 can perform any appropriate operations and processes by loading the program 930 into the RAM 922.

[0187] Embodiments of the present disclosure may be implemented by program 930 so that the apparatus 900 can perform any process of the present disclosure, as discussed with reference to Figures 6-8. Embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0188] In some exemplary embodiments, the program 930 may be tangibly contained in a computer-readable medium that may be contained in device 900 (such as in memory 920) or in other storage devices accessible by device 900. Device 900 can load the program 930 from the computer-readable medium into RAM 922 and execute it. The computer-readable medium may include any type of tangible non-volatile storage, such as ROM, EPROM, flash® memory, hard disk, CD, DVD, etc.

[0189] Figure 10 shows a block diagram of an example of a computer-readable medium 1000 in some exemplary embodiments of the present disclosure. The computer-readable medium 1000 has a program 930 stored therein. Although the computer-readable medium 1000 is depicted in the form of a CD or DVD in Figure 10, it should be noted that the computer-readable medium 1000 may be any other form suitable for transporting or holding the program 930.

[0190] In general, various embodiments of this disclosure may be implemented in hardware or special-purpose circuits, software, logic, or any combination thereof. Some embodiments 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 embodiments of this disclosure are illustrated and described using block diagrams, flowcharts, or any other graphic representation, but it should be understood that any blocks, apparatus, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, special-purpose circuits or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof, in non-limiting examples.

[0191] This disclosure also provides at least one computer program product tangibly stored in a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as those contained in a program module, which are executed on a device on a target real or virtual processor to perform the methods described above with reference to any of Figures 7-8. 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 functions of the program modules can be combined or divided amongst the program modules as desired in various embodiments. The machine-executable instructions of the program modules can be executed in a local or distributed device. In a distributed device, the program modules can be located on both local and remote storage media.

[0192] Program code for performing the methods of this disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the program code is executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagrams are performed. The program code may run entirely on the machine, partially on the machine, as a standalone software package, partially on the machine, partially on a remote machine, or entirely on a remote machine or server.

[0193] 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, and the like.

[0194] 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, or semiconductor systems, apparatus, devices, or any suitable combination thereof. More specific examples of computer-readable storage media include electrical connections with one or more wires, portable computer diskettes, 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 any suitable combination thereof. As used herein, the term “non-temporary” refers to the medium itself (i.e., tangible and not signaling), as opposed to the persistence of data storage (e.g., ROM versus RAM).

[0195] Furthermore, although the operations are described in a specific order, this should not be understood as requiring that such operations be performed in a specific order shown, or sequentially, or that all illustrated operations be performed in order to achieve a desired result. In certain circumstances, multitasking and parallel processing may be preferable. Similarly, although some specific implementation details are included in the above description, these should not be interpreted as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented separately or in any preferred subcombination in multiple embodiments.

[0196] While 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 attached claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for carrying out the claims.

Claims

1. Terminal device, Means for receiving downlink control information (DCI) from network equipment, wherein the DCI includes at least one frequency domain resource allocation (FDRA) field for at least one dynamically scheduled communication; Means for determining a first FDRA in a first bandwidth of a first communication based on the at least one FDRA field in the DCI, Means for determining the second FDRA in the second bandwidth of the second communication based on the first FDRA and the offset, Means for performing the first and second communications with the network equipment, respectively, based on the first and second FDRAs, Equipped with, The first communication is a non-SBFD communication, and the second communication is an SBFD communication. Terminal equipment.

2. Means for receiving configuration information from the aforementioned network device, wherein the configuration information is frequency band, A first number of time units for both uplink and downlink transmissions, The first position of the first number of time units within the wireless frame, A second number of time units for uplink transmission, The second position in the second number of time units within the wireless frame, A third number of time units for downlink transmission, The third position in the third number of time units within the wireless frame, or Resource allocation type, A means for receiving, indicating at least one of the following The terminal device according to claim 1, further comprising:

3. The terminal device according to claim 1 or 2, wherein the DCI further includes trigger information, the trigger information prompting the terminal device to determine different FDRAs for the SBFD communication and the non-SBFD communication.

4. The means for determining the first FDRA according to the determination that the resource allocation type indicated by the configuration information from the network device is type 0 is: Means for determining a first set of a first number of resource block groups (RBGs) based on the at least one FDRA field in the DCI, Equipped with, The means for determining the second FDRA is, Means for determining a second set of second RBGs of a second number based on the first number and the offset, A terminal device according to claim 1 or 2, comprising:

5. The means for determining the first FDRA according to the determination that the resource allocation type indicated by the configuration information from the network device is type 1 is: Means for determining the first index and first length of the first starting resource block based on the at least one FDRA field in the DCI, Equipped with, The means for determining the second FDRA is, Means for determining the second index of the second starting resource block based on the first index and the offset, Means for determining a second length based on the first length and the offset, A terminal device according to claim 1 or 2, comprising:

6. The means for determining the second index is, Means for determining the second index of the second starting resource block based on the first index, the offset, and a further offset set by the network device, The terminal device according to claim 5, further comprising:

7. The terminal device according to claim 1 or 2, wherein the SBFD communication is performed using an SBFD slot, an SBFD mini-slot, or an SBFD symbol, and the non-SBFD communication is performed using a non-SBFD slot, a non-SBFD mini-slot, or a non-SBFD symbol.

8. Means for transmitting downlink control information (DCI) to terminal equipment, wherein the DCI includes at least one frequency domain resource allocation (FDRA) field for at least one dynamically scheduled communication, and a first FDRA in a first bandwidth of a first communication is determined based on the at least one FDRA field in the DCI, and a second FDRA in a second bandwidth of a second communication is determined based on the first FDRA and an offset, Means for performing the first and second communications with the terminal device, respectively, based on the first and second FDRAs, Equipped with, The first communication is a non-SBFD communication, and the second communication is an SBFD communication. Network equipment.

9. Means for transmitting configuration information to the terminal device, wherein the configuration information is frequency band, A first number of time units for both uplink and downlink transmissions, The first position of the first number of time units within the wireless frame, A second number of time units for uplink transmission, The second position in the second number of time units within the wireless frame, A third number of time units for downlink transmission, The third position in the third number of time units within the wireless frame, or Resource allocation type, A means for transmission that shows at least one of the following, The network device according to claim 8, further comprising:

10. The means for determining the first FDRA according to the determination that the resource allocation type is type 0 is: Means for determining a first set of a first number of resource block groups (RBGs) based on the at least one FDRA field in the DCI, Equipped with, The means for determining the second FDRA is, Means for determining a second set of second RBGs of a second number based on the first number and the offset, A network device according to claim 8 or 9, comprising:

11. Means for determining the first FDRA according to the determination that the resource allocation type is type 1, Means for determining the first index and first length of the first starting resource block based on the at least one FDRA field in the DCI, Equipped with, The means for determining the second FDRA is, Means for determining the second index of the second starting resource block based on the first index and the offset, Means for determining a second length based on the first length and the offset, A network device according to claim 8 or 9, comprising:

12. The means for determining the second index is, Means for determining the second index of the second starting resource block based on the first index, the offset, and a further offset defined by the network device, The network device according to claim 11, comprising:

13. The network device according to claim 8 or 9, wherein the SBFD communication is performed using an SBFD slot, an SBFD mini-slot, or an SBFD symbol, and the non-SBFD communication is performed using a non-SBFD slot, a non-SBFD mini-slot, or a non-SBFD symbol.

Images