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] Exemplary embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to terminal equipment, network equipment, methods, apparatus, and computer-readable storage media for multi-slot scheduling solutions in the context of sub-band non-overlapping full duplex (SBFD). [Background technology]

[0002] Recently, the 3rd Generation Partnership Project (3GPP®) agreed to initiate a study item on SBFD, which enables simultaneous downlink (DL) and uplink (UL) transmissions on different physical resource blocks (PRBs) or sub-bands within unpaired Broadband New Radio (NR) cells.

[0003] Multiple UL or DL ​​transmissions can be scheduled in multiple slots, which is called multi-slot scheduling. In multi-slot scheduling, multiple transmissions may have the same frequency domain resource allocation. When multi-slot scheduling is performed in the context of SBFD, the same frequency domain resource allocation may result in inefficient use of frequency resources and communication efficiency. Summary of the Invention

[0004] Generally, the exemplary embodiments of the present disclosure provide a solution for multi-slot scheduling in the context of SBFD.

[0005] In a first aspect, a terminal device is provided, the terminal device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least receive downlink control information (DCI) from a network device, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one dynamically scheduled or activated communication, 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 first and second communication with the network device based on the first and second FDRA, respectively, wherein the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0006] In a second aspect, a network device is provided, the network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device to: transmit at least Downlink Control Information (DCI) to a terminal device, the DCI including at least one Frequency Domain Resource Allocation (FDRA) field for at least one dynamically scheduled or activated communication, the at least one FDRA in the DCI for determining a first FDRA in a first bandwidth for the first communication and a second FDRA in a second bandwidth for the second communication; and perform first and second communications with the terminal device based on the first FDRA and the second FDRA, respectively, wherein the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0007] In a third aspect, there is provided a method performed by a terminal device, the method including: receiving, at the terminal device, 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, 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 the at least one FDRA field in the DCI, and performing the first communication and the second communication with the network device based on the first FDRA and the second FDRA, respectively, where the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0008] In a fourth aspect, a method performed by a network device is provided, the method including: transmitting, in the network device, downlink control information (DCI) to a terminal device, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one dynamically scheduled or activated communication, the at least one FDRA field in the DCI 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 based on the first FDRA and the second FDRA, respectively, where the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0009] In a fifth aspect, an apparatus is provided, comprising: means for receiving downlink control information (DCI) from a network device including at least one Frequency Domain Resource Allocation (FDRA) field for at least one communication to be dynamically scheduled or activated in a terminal device, means 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 based on the at least one FDRA field in the DCI, and means for performing first and second communications with the network device based on the first FDRA and the second FDRA, respectively, wherein the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0010] In a sixth aspect, an apparatus is provided, comprising: means, in a network equipment, for transmitting, to a terminal device, downlink control information (DCI) including at least one Frequency Domain Resource Allocation (FDRA) field for at least one communication to be dynamically scheduled or activated, where the 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 respectively performing first and second communication with the terminal device based on the first FDRA and the second FDRA, where the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

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

[0012] In an eighth aspect, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to carry out at least the method of the third or fourth aspect.

[0013] In a ninth aspect, a terminal device is provided, the terminal device comprising: a receiving circuit configured to receive downlink control information (DCI) from a network device, the downlink control information (DCI) including 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 the at least one FDRA field in the DCI; and an executing circuit configured to execute first and second communications with the network device based on the first FDRA and second FDRA, respectively, where the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0014] In a tenth aspect, a network device is provided, the network device comprising: 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 dynamically scheduled or activated communication, the at least one FDRA field in the DCI 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 respectively execute first and second communications with the terminal device based on the first FDRA and the second FDRA, wherein the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0015] In an eleventh aspect, there is provided a computer readable medium comprising program instructions which, when executed by an apparatus, cause the apparatus to perform at least the method of the third or fourth aspect.

[0016] It should be understood that the Abstract is not intended to identify key or essential features of 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 become readily apparent through the following description. [Brief explanation of the drawings]

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

[0018] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are provided for illustrative purposes to help those skilled in the art understand and practice the present disclosure, and are not intended to imply any limitations on the scope of the present disclosure. The disclosure described herein may be implemented in various forms other than those described below.

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

[0020] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is understood that it is within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly stated.

[0021] Although terms such as "first" and "second" may be used herein to describe various elements, it should be understood that these elements are not limited by these terms. These terms are merely used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0022] The terminology in the examples is for the purpose of describing particular embodiments and is not intended to limit the exemplary embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly indicates otherwise. It should be further understood that, as used herein, the terms "comprises," "comprising," "has," "having," "includes," and / or "including" identify, but do not exclude, the presence of stated features, elements, and / or components, etc. As used herein, "at least one of, " and "at least one of " and similar expressions, when a list of two or more elements is joined by "and," mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0023] As used in this application, the term "circuit" means (a) hardware-only circuit implementations (e.g., analog and / or digital-only implementations); (b) a combination of hardware circuitry and software, e.g., (where applicable); (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) software (including digital signal processors), which cooperate with hardware processor(s) with software and memory(s) to cause a device, such as a mobile phone or server, to perform various functions; (c) hardware circuitry(s) and processor(s), such as microprocessor(s) or portions of microprocessors(s), that require software (e.g., firmware) to operate, but that may be absent when not necessary for operation; It may refer to one or more, or all, of the following:

[0024] This definition of circuit applies to all uses of the term in this application, including the claims. As a further example, as used herein, the term circuit also covers simply a hardware circuit or processor (or processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware implementation. The term circuit also covers, for example, a baseband 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, if applicable to particular claim elements.

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

[0026] As used herein, the term "network equipment" refers to a node in a communication network through which terminal equipment accesses the network and receives services therefrom. Network equipment may refer to a base station (BS) or access point (AP), e.g., a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a new radio (NR) NB (also referred to as gNB), a remote radio unit (RRU), or, depending on the terminology and technology applied, a radio header (RH), a remote radio head (RRH), an integrated access backhaul (IAB) node, a relay, or a low-power node such as a femto or pico node.

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

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

[0029] For this reason, 3GPP® has agreed to initiate a Release 18 (R18) study item on the evolution of duplexing in NR to address the above challenges. One of the objectives of this study item is to enable simultaneous DL and UL transmissions on different physical resource blocks (PRBs) / subbands within unpaired wideband NR cells, sometimes referred to as subband non-overlapping full duplex (SBFD).

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

[0031] The following text box describes some non-limiting objectives of the R18 study items related to SBFD. However, it should be noted that exemplary embodiments of the present disclosure are not limited to the objectives set forth in the text box. [Table 1]

[0032] SBFD may introduce at least one type of crosslink interference (CLI), which may be referred to as common channel inter-subband CLI. This interference can be categorized as follows: (1) gNB self-interference, (2) intra-cell inter-UE common channel inter-subband CLI, (3) inter-cell inter-UE common channel inter-subband CLI, and (4) inter-gNB common channel inter-subband CLI.

[0033] 2A shows a schematic diagram 210 of co-channel interference types in an SBFD deployment. It is assumed that gNB 201 and gNB 202 are in the same frequency domain partitioning, UE 203 and UE 204 are in the cell of gNB 201, and UE 205 and UE 206 are in the cell of gNB 202. There may be gNB self-interference 212, an intra-cell UE-to-UE co-channel inter-subband CLI 214, an inter-cell UE-to-UE co-channel inter-subband CLI 216, or a gNB-to-gNB co-channel inter-subband CLI 218.

[0034] In addition to these new CLI types (1) to (4), when different frequency domain partitioning is used in adjacent cells, the system may also be affected by intra-co-channel subband CLI, i.e., CLI due to transmission on overlapping frequency resources, (5) gNB-to-gNB inter-cell co-channel intra-subband CLI, and (6) UE-to-UE inter-cell co-channel intra-subband CLI.

[0035] 2B shows another schematic diagram 220 of co-channel interference types in an SBFD deployment. It is assumed that gNB 207 and gNB 208 are in different frequency domain partitions, UE 209 is in the cell of gNB 207, and UE 219 is in the cell of gNB 208. There may be a gNB-to-gNB inter-cell co-channel intra-subband CLI 222 or a UE-to-UE inter-cell co-channel intra-subband CLI 224.

[0036] There are two main types of frequency domain resource allocation (FDRA) for the physical uplink shared channel (PUSCH) in 5G NR: resource allocation (RA) type 0 and RA type 1. A network device (such as a gNB) configures either type 0 or type 1, or both types 0 and 1, to indicate the RA type to be used for the scheduled PUSCH transmission via the scheduling DCI.

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

[0038] 3A shows a schematic diagram 310 of an example of RA type 0 of 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 FIG. 3A.

[0039] RA type 1 is the starting resource block (RB start ) and the length of the contiguously allocated resource blocks (L RBs FDRA is shown via RA type 0 (denoted by ). FIG. 3B is a schematic diagram 320 illustrating an example of RA type 0 FDRA for PUSCH. As shown in FIG. 3B, the BWP size 322 is equal to 20 RBs, and the RB start 324 and L RBs 326 (equal to 10 RBs) can be used to denote FDRA.

[0040] It should be appreciated that RA type 1 can reduce the overhead of the DCI by avoiding the use of bitmaps. The resource block allocation information in the scheduling DCI provides the scheduled UE with the size (

number

number

[0041] The resource allocation field for uplink type 1 contains RB start and L RBs Contains the resource indication value (RIV) corresponding to RB. start and L RBs Based on this, RIV is given as follows: If

number

number

number

number

[0042] It should be noted that although FIGS. 3A-3B are illustrated for the FDRA procedure for the PUSCH, a similar FDRA procedure is also applicable to the Physical Downlink Shared Channel (PDSCH) and will not be repeated in this disclosure.

[0043] Several techniques have been defined and refined in previous releases of the 3GPP® specifications that allow for scheduling multiple UL or DL ​​transmissions across multiple slots in a single scheduling DCI. For example, there are two techniques that allow multiple UL transmissions to be scheduled in multiple slots using a single DCI, called PUSCH repetitions and multi-PUSCH scheduling. These techniques share the following design aspects: A single DCI schedules multiple PUSCHs, each PUSCH within a slot. The scheduled PUSCH has the same frequency domain resource allocation (ie, the same number of physical resource blocks (PRBs) and the same locations of these PRBs in the frequency domain) as indicated by the single DCI.

[0044] However, there are design differences between these technologies, as follows:

[0045] For PUSCH repetitions, only a single start and length of the PUSCH within a slot are indicated by the scheduling DCI, i.e., a 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 repetition type. (1) For PUSCH repetition type A (introduced / enhanced in Rel-15 / 16), the same start and length indicated by the single SLIV apply to all scheduled PUSCHs. (2) For PUSCH repetition type B (introduced in Rel-16), the single SLIV is used to determine multiple back-to-back nominal repetitions of the same length, each of which may cross a slot boundary. Each nominal repetition is then split into multiple actual repetitions if it crosses a slot boundary or an invalid symbol. All PUSCH repetitions are used to transmit one transport block using different redundancy versions and the same hybrid automatic repeat request (HARQ) process number.

[0046] In multi-PUSCH scheduling (introduced / enhanced in Rel-16 / 17), multiple SLIVs can be indicated by the scheduling DCI, where each valid SLIV corresponds to one PUSCH from multiple scheduled PUSCHs. The scheduled PUSCHs are used to transmit different transport blocks with different HARQ process numbers.

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

[0048] In addition to PUSCH / PDSCH repetitions scheduled by DCI (called dynamic grant (DG)), there is also a framework for transmitting repetitions without a scheduling DCI, called semi-persistent scheduling (SPS) for PDSCH or configured grant (CG) for PUSCH. The idea behind SPS / CG scheduling is that transmission opportunities are pre-configured via RRC, and the gNB / UE can transmit data on these opportunities without sending or waiting for a DCI. There are also two types of CG PUSCH: Type 1 CG PUSCH does not require an activation DCI, while Type 2 CG PUSCH requires a DCI to activate the use of the transmission opportunity. For Type 1 CG PUSCH, the time and frequency resources of the transmission opportunity are indicated by RRC configuration. For Type 2 CG PUSCH, the time and frequency resources of the transmission opportunity are indicated by an activation DCI.

[0049] Based on the description of SBFD operation shown in FIG. 1C, it is observed that two slot types exist for both DL and UL transmissions: SBFD slots and non-SBFD slots. FIG. 4 shows an example diagram 400 of SBFD slots and non-SBFD slots. As shown in FIG. 4, DL transmissions can occur in non-SBFD slots 432 and SBFD slots 434, and UL transmissions can occur in SBFD slots 434 and non-SBFD slots 436. In other words, non-overlapping DL and UL subbands both exist in SBFD slot 434, with the entire band being used for DL ​​transmissions in non-SBFD slot 432 and the entire band being used for UL transmissions in non-SBFD slot 436. In some embodiments, non-SBFD slots 432 may also be referred to as legacy slots or full DL slots, and non-SBFD slots 436 may also be referred to as legacy slots or full UL slots.

[0050] It should be noted that although SBFD slots and non-SBFD slots are illustrated with reference to FIG. 4, the present disclosure also applies to SBFD minislots and non-SBFD minislots, or SBFD symbols and non-SBFD symbols, or other time units not listed here.

[0051] In the context of this disclosure, the term "SBFD-aware UE" may be used, and an SBFD-aware UE is aware of an operating mode with respect to at least the time and frequency locations of subbands for SBFD operation. In the context of this disclosure, the terms SBFD-aware, FDU-aware, SBFD-capable, FDU-capable, etc. may be used interchangeably.

[0052] Based on the description of multi-slot scheduling, scheduled PUSCH / PDSCH have the same frequency domain resource allocation. In the context of SBFD, the same frequency domain resource allocation for scheduled PUSCH / PDSCH may result in low frequency domain resource efficiency, so further consideration is required.

[0053] Exemplary embodiments of the present disclosure provide a solution for multi-slot scheduling in the context of SBFD. In particular, a terminal device can receive DCI from a network device and determine different FDRAs for SBFD communication and non-SBFD communication. The terminal device can then perform communication based on the different FDRAs. This allows for greater utilization of bandwidth in non-SBFD time units, improving the reliability of multi-slot scheduling and achieving higher resource efficiency. The principles and exemplary embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0054] 5 illustrates an example of a network environment 500 in which some exemplary embodiments of the present disclosure may be implemented. The environment 500, which is part of a communications network, includes a terminal device 510 and a network device 520.

[0055] Communications environment 500 may include any suitable number of devices and cells. In communications environment 500, network equipment 520 may provide service to terminal equipment 510, and network equipment 520 and terminal equipment 510 may communicate data and control information with each other. In some embodiments, network equipment 520 and terminal equipment 510 may communicate over a direct link / channel.

[0056] In system 500, the link from network device 520 to terminal device 510 is referred to as the downlink (DL), and the link from terminal device 510 to network device 520 is referred to as the uplink (UL). In the downlink, network device 520 is the transmit (TX) device (or transmitter) and terminal device 510 is the receive (RX) device (or receiver). In the uplink, terminal device 510 is the transmit TX device (or transmitter) and network device 520 is the 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 can provide multiple cells.

[0057] Communications in network environment 500 may be conducted according to any suitable communications protocol(s), including, but not limited to, cellular communications 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 communications protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or other protocols now known or developed in the future. Further, communications may utilize any suitable wireless communications technology, including, but not limited to, code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread OFDM (DFT-s-OFDM), and / or any other technology now known or developed in the future.

[0058] It should be understood that the number of devices (i.e., terminal device 510 and network device 520) and their connection relationships and types shown in Figure 5 are for illustrative purposes only, without implying any limitations. For example, environment 500 may include any suitable number of devices adapted for implementing embodiments of the present disclosure. For example, although Figure 5 depicts terminal device 510 as a mobile phone, terminal device 510 may be any type of user equipment.

[0059] 6 illustrates an example of a process flow 600 in accordance with some exemplary embodiments of the present disclosure. For purposes of explanation, the process flow 600 will be described with reference to FIG. 5. The process flow 600 includes a terminal device 510 and a network device 520. Although the process flow 300 has been described in the network environment 500 of FIG. 5, it should be understood that the process flow may be applied to other communication scenarios as well.

[0060] 6, the network device 520 may transmit 610 the configuration information 612 to the terminal device 510. The configuration information in some examples is transmitted in an RRC message or RRC signaling.

[0061] In some embodiments, the configuration information 612 may indicate one or more 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 within a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units within a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units within a radio frame, or a resource allocation type. In some embodiments, the time unit may be any one of a slot, a minislot, or a symbol. In some embodiments, the configuration information 612 may indicate one or more of: frequency band, the number of slots / minislots / symbols during which the frequency band is divided into multiple subbands, and at least one subband is used for DL ​​transmission and at least one other subband is 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 for which the entire frequency band is used for DL ​​or UL transmission, 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, and resource allocation type, can be shown.

[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] At the other end of the communication, terminal device 510 receives 614 configuration information 612. In this disclosure, it is assumed that terminal device 510 is an SBFD-aware UE.

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

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

[0066] Network device 520 transmits DCI 622 to terminal device 510. In some embodiments, DCI 622 includes at least one FDRA field for at least one dynamically scheduled or activated communication.

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

[0068] In some examples, DCI 622 may indicate that some of the communications are scheduled or configured in SBFD time units and other portions of the communications are scheduled or configured in non-SBFD time units, which may be slots, minislots, or symbols.

[0069] For example, DCI 622 may indicate that a first communication is scheduled or configured in an SBFD slot and a second communication is scheduled or configured in a non-SBFD slot. In other embodiments, DCI 622 may indicate that a first communication is scheduled or configured in a non-SBFD slot and a 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 examples, 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 PUSCH repetition or multi-PUSCH scheduling. In some other examples, the first and second communications are PDSCH repetition or multi-PDSCH scheduling. In some other examples, the first and second communications may be Type 1 CG PUSCH transmissions, Type 2 CG PUSCH transmissions, or DG PUSCH transmissions.

[0072] In some exemplary embodiments, the number of communications scheduled or configured by DCI 622 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, DCI 622 includes at least one FDRA field, e.g., DCI 622 includes a single FDRA field. In some exemplary embodiments, the at least one FDRA is associated with a first bandwidth of the first communication. In some examples, the type of the first communication (SBFD or non-SBFD) may be predefined by being preconfigured by network device 520.

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

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

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

[0077] At the other end of the communication, terminal device 510 receives (624) DCI 622. Thus, terminal device 510 can obtain at least one filed FDRA (e.g., a single filed FDRA).

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

[0079] In some exemplary embodiments, the terminal equipment 510 determines a first FDRA based on at least one FDRA field in the DCI 622, and the terminal equipment 510 may determine a second FDRA based on the first FDRA or based on settings from the network equipment 520.

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

[0081] [When resource allocation type is RA type 0] The terminal device 510 may determine the first FDRA based on the FDRA filed in the DCI 612 or based on settings from the network device 520. Specifically, the terminal device 510 may determine a first set of a first number of RBGs, and then determine the first FDRA based on the first set of the first number of RBGs (which may be referred to as a first RBG size).

[0082] For example, terminal device 510 may determine the first RBG size for the first communication based on an FDRA field, such as a bitmap, in DCI 622. In another example, if network device 520 sets UL / DL wideband RBG sizes and the first communication is associated with the UL / DL wideband bandwidth, terminal device 510 may determine the first RBG size for the first communication based on the set UL / DL wideband RBG sizes. In another example, if network device 520 sets UL / DL subband RBG sizes and the first communication is associated with the UL / DL subband bandwidth, terminal device 510 may determine the first RBG size for the first communication based on the set UL / DL subband RBG sizes.

[0083] The terminal device 510 may determine the second FDRA based on the first FDRA or based on settings from the network device 520. Specifically, the terminal device 510 may determine a second set of the second number of RBGs, and then determine the second FDRA based on the second set of the second number of RBGs (also referred to as a second RBG size).

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

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

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

[0087] In some other examples, when network device 520 configures UL / DL wideband RBG sizes and the second communication is associated with the UL / DL wideband bandwidth, terminal device 510 may determine the second RBG size of the second communication based on the configured UL / DL wideband RBG size. In another example, when network device 520 configures UL / DL subband RBG sizes and the second communication is associated with the UL / DL subband bandwidth, terminal device 510 may determine the second RBG size of the second communication based on the configured UL / DL subband RBG size.

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

[0089] For example, the terminal device 510 may determine the first index and the first length of the first starting resource block based on an FDRA field such as an RIV in the DCI 622. If the first communication is related to a UL / DL wideband bandwidth, the first index and the first length of the first starting resource block may be determined based on the wideband RB start and broadband L RBSIf the first communication is associated with the UL / DL subband bandwidth, the first index and the first length of the first starting resource block can be expressed as: start and subband L RBS It can be expressed as:

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

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

[0092] For example, if the first communication is SBFD communication and the second communication is non-SBFD communication, the second index of the second starting resource block is the subband RB start If the first communication is a non-SBFD communication and the second communication is an SBFD communication, the second index of the second starting resource block may be determined by the wideband RB start ×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 configured by the network device 520. For example, the following equation (5) may be used: Wideband RB start ×offset = subband RB start +offset2(5)

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

[0095] It should be understood that equation (5) is used for illustrative purposes only and is not limiting, and that, for example, a further offset may be represented by offset3, which may be a positive or negative value, and equation (6) may be used. Wideband 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 / Wideband L RBS =offset (7)

[0097] For example, if the first communication is an SBFD communication and the second communication is a non-SBFD communication, the second length is the subband L RBS If the first communication is a non-SBFD communication and the second communication is an SBFD communication, the second length may be determined by the wideband L RBS ×offset.

[0098] In this manner, the terminal device 510 can determine the first FDRA and the second FDRA based on one or more of at least one FDRA field in the DCI 622, the resource allocation type, the offset, or the further offset.

[0099] In some other exemplary embodiments, if DCI 622 schedules or configures a single transmission / reception on an SBFD slot / minislot / symbol and the FDRA field in DCI 622 is associated with a subband bandwidth or a wideband bandwidth, terminal device 510 may determine the FDRA for the single transmission / reception on the SBFD slot / minislot / symbol in a similar manner.

[0100] The network device 520 determines the first FDRA and the second FDRA (650). The determination at 650 is similar to the determination at 640 and therefore will not be repeated here.

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

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

[0103] 4 and taking DL transmission as an example, when 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, 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 performs the second communication (second transmission) based on the second FDRA during the non-SBFD slot 432, and then performs the first communication (first transmission) based on the first FDRA during the SBFD slot 434.

[0104] According to the exemplary embodiment with reference to FIG. 6, when communications are dynamically scheduled or activated by DCI, the terminal device 510 can determine different FDRAs for SBFD communications and non-SBFD communications. In this manner, the exemplary embodiment provides a solution for indicating larger physical resources for PUSCH / PDSCH repetitions in non-SBFD slots / minislots / symbols compared to PUSCH / PDSCH repetitions in SBFD slots / minislots / symbols. Therefore, for the same time-domain resource allocation, PUSCH / PDSCH repetitions in non-SBFD slots / minislots / symbols have larger physical resources, i.e., a larger number of resource elements (REs), compared to PUSCH / PDSCH repetitions in SBFD slots / minislots / symbols. Therefore, the larger bandwidth of non-SBFD slots / minislots / symbols can be utilized, the reliability of PUSCH / PDSCH repetitions can be improved, and communication efficiency can be improved.

[0105] For example, with larger resources and the same transport block size (TBS), PUSCH / PDSCH repetitions in non-SBFD slots / minislots / symbols can carry more coded bits (e.g., multiple cycles from a circular buffer), thus improving the reliability of the repetitions. For example, in multi-PUSCH or multi-PDSCH scheduling, larger TBSs can be mapped to transmissions in non-SBFD slots / minislots / symbols with larger resources, improving the data rate for the same signaled MCS. Furthermore, the DCI size is not increased in this disclosure, thereby avoiding overhead issues.

[0106] 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 from the perspective of the terminal device 510 with reference to FIG.

[0107] In block 710, the terminal device 510 receives downlink control information (DCI) from the network device 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, the terminal device 510 determines 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 the at least one FDRA field in the DCI, the first communication being one of an SBFD communication or a non-SBFD communication, and the second communication being the other of an SBFD communication or a non-SBFD communication. In block 730, the terminal device 510 performs the first communication and the second communication with the network device 520, respectively, based on the first FDRA and the second FDRA.

[0108] In some demonstrative embodiments, terminal device 510 receives configuration information from network device 520, the configuration information indicating one or more 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 within a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units within a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units within a radio frame, or a resource allocation type.

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

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

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

[0112] In some exemplary embodiments, terminal device 510 determines a first FDRA based on at least one FDRA field in the DCI, and 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 the 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 the DCI.

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

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

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

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

[0118] In some exemplary embodiments, the offset includes one or more of the following: a ratio of the bandwidth of the sub-band for SBFD communications to the bandwidth of the band for non-SBFD communications, or a value set by network device 520.

[0119] In some exemplary embodiments, based on determining that the resource allocation type notified by the configuration information from the network equipment is Type 0, the terminal equipment 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 equipment 510 determines a second set of a second number of RGB based on the configuration from the network equipment.

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

[0121] In some exemplary embodiments, SBFD communications are performed on SBFD slots, or SBFD minislots, or SBFD symbols, and non-SBFD communications are performed on non-SBFD slots, or non-SBFD minislots, or non-SBFD symbols.

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

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

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

[0125] 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 from the perspective of the network device 520 with reference to FIG.

[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 dynamically scheduled or activated communication, the at least one FDRA in the DCI being 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, the first communication being one of an SBFD communication or a non-SBFD communication, and the second communication being the other of the SBFD communication or the non-SBFD communication. In block 820, the network device 520 performs the first communication and the second communication with the terminal device, respectively, based on the first FDRA and the second FDRA.

[0127] In some demonstrative embodiments, the network device 520 transmits configuration information to the terminal device 510, the configuration information indicating one or more 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 within a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units within a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units within a radio frame, or a resource allocation type.

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

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

[0130] In some example embodiments, the DCI further includes trigger information that prompts 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 an 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 the first number and the 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 the 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 the second starting resource block based on the first index and the offset, and the network device 520 determines a second length based on the first length and the offset.

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

[0137] In some exemplary embodiments, the offset includes one or more of a ratio between the bandwidth of the sub-band for SBFD communications and the bandwidth of the band for non-SBFD communications, or a value 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 number of second RGB sets.

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

[0140] In some exemplary embodiments, SBFD communications are performed on SBFD slots, or SBFD minislots, or SBFD symbols, and non-SBFD communications are performed on non-SBFD slots, or non-SBFD minislots, or non-SBFD symbols.

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

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

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

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

[0145] In some example embodiments, an apparatus comprises: means for receiving, at a terminal device from a network device, downlink control information (DCI), the downlink control information including 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 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 means for respectively performing the first communication and the second communication with the network device based on the first FDRA and the second FDRA, wherein the first communication is one of an SBFD communication or a non-SBFD communication, and the second communication is the other of the SBFD communication or the non-SBFD communication.

[0146] In some demonstrative embodiments, the apparatus further comprises means for receiving configuration information from the network device, 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 within a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units within a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units within a radio frame, or a resource allocation type.

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

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

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

[0150] In some exemplary embodiments, the means for determining the first FDRA and the second FDRA comprises 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 an offset.

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

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

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

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

[0155] In some exemplary embodiments, the means for determining the second index comprises means for determining a second index of a second starting resource block based on the first index, the offset, and a further offset configured by the network equipment.

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

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

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

[0159] In some exemplary embodiments, SBFD communications are performed on SBFD slots, or SBFD minislots, or SBFD symbols, and non-SBFD communications are performed on non-SBFD slots, or non-SBFD minislots, or non-SBFD symbols.

[0160] In some exemplary embodiments, the first and second communications are sent to the network device, or the first and second communications are received from the network device.

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

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

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

[0164] In some demonstrative embodiments, an apparatus comprises: means for transmitting, in a network equipment to a terminal device, downlink control information (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 the terminal device, respectively, based on the first FDRA and the second FDRA, wherein the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of SBFD communication or non-SBFD communication.

[0165] In some demonstrative embodiments, the apparatus further comprises means for transmitting configuration information to the terminal device, 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 within a radio frame, a second number of time units for uplink transmissions, a second position of the second number of time units within a radio frame, a third number of time units for downlink transmissions, a third position of the third number of time units within a radio frame, or a resource allocation type.

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

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

[0168] In an exemplary embodiment, the DCI further includes trigger information that 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, the means for determining the first FDRA comprises means for determining, based on at least one FDRA field in the DCI, a first set of a first number of resource block groups (RGB) in accordance with a determination that the resource allocation type is Type 0.

[0171] In some exemplary embodiments, the means for determining the second FDRA comprises means for determining a second set of RGB of a second number based on the first number and the offset.

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

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

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

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

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

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

[0178] In an exemplary embodiment, SBFD communications are performed on SBFD slots, or SBFD minislots, or SBFD symbols, and non-SBFD communications are performed on non-SBFD slots, or non-SBFD minislots, or non-SBFD symbols.

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

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

[0181] In an exemplary embodiment, the first communication and the second communication are multi-PUSCH scheduling or multi-PDSCH scheduling.

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

[0183] The communication module 940 is for two-way communication. The communication module 940 has at least one antenna to facilitate communication. The communication interface may 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, by way of non-limiting example, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 900 may have multiple processors, such as application-specific integrated circuit chips that are time-slaved to a clock that synchronizes a main processor.

[0185] The memory 920 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, read-only memory (ROM) 924, electronically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage devices. Examples of volatile memory include, but are not limited to, random access memory (RAM) 922 and other volatile memories that do not persist through 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 load the program 930 into the RAM 922 to perform any suitable operations and processes.

[0187] The embodiments of the present disclosure may be implemented by a program 930 such that the device 900 may execute any process of the present disclosure, as discussed with reference to Figures 6 to 8. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0188] In some demonstrative embodiments, the program 930 may be tangibly contained in a computer-readable medium, which may be included in the device 900 (such as in memory 920) or other storage device accessible by the device 900. The device 900 may 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] 10 illustrates a block diagram of an example of a computer-readable medium 1000 according to some exemplary embodiments of the present disclosure. The computer-readable medium 1000 has stored thereon a program 930. It should be noted that although the computer-readable medium 1000 is depicted in FIG. 10 in the form of a CD or DVD, the computer-readable medium 1000 may be in any other form suitable for carrying or retaining the program 930.

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

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

[0192] Program code for carrying out the methods of the present 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 apparatus such that, when executed by the processor or controller, the functions / acts specified in the flowcharts and / or block diagrams are performed. The program code can run entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

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

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

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

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

Claims

1. A terminal device, at least one processor; When executed by the at least one processor, the terminal device is configured to: receiving downlink control information (DCI) from a network device, the DCI including at least one frequency domain resource allocation (FDRA) field for at least one dynamically scheduled or activated communication; 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 the at least one FDRA field in the DCI; performing the first communication and the second communication with the network device based on the first FDRA and the second FDRA, respectively; at least one memory storing instructions for executing the Equipped with the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of the SBFD communication or non-SBFD communication; Terminal equipment.

2. The at least one memory, when executed by the at least one processor, causes the terminal device to receiving setting information from the network device, the setting information comprising: frequency band, a first number of time units for both uplink and downlink transmissions; a first position of the first number of time units within a radio frame; a second number of time units for uplink transmission; a second position of the second number of time units within the radio frame; a third number of time units for downlink transmission; a third position of the third number of time units within the radio frame; or resource allocation type, receiving, indicating at least one of:

2. The terminal device according to claim 1, wherein the terminal device stores instructions for executing the following:

3. The terminal device according to claim 2 , wherein the time unit is a slot, a minislot, or a symbol.

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

5. The terminal device according to claim 1 , 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.

6. The at least one memory, when executed by the at least one processor, causes the terminal device to determining the first FDRA based on the at least one FDRA field in the DCI; determining the second FDRA based on the first FDRA and an offset; storing instructions for determining the first FDRA and the second FDRA by 6. A terminal device according to claim 1.

7. The at least one memory, when executed by the at least one processor, causes the terminal device to determining a first set of a first number of resource block groups (RGB) based on the at least one FDRA field in the DCI according to a determination that the resource allocation type indicated by the configuration information from the network device is Type 0; and storing instructions for determining the first FDRA by The terminal device according to claim 6.

8. The at least one memory, when executed by the at least one processor, causes the terminal device to determining a second number of second RGB sets based on the first number and the offset; and storing instructions for determining the second FDRA by The terminal device according to claim 7.

9. The at least one memory, when executed by the at least one processor, causes the terminal device to determining a first index and a first length of a first starting resource block based on the at least one FDRA field in the DCI according to a determination that the resource allocation type indicated by the configuration information from the network device is Type 1; The terminal device according to claim 6, further comprising: a memory for storing instructions for causing the first FDRA to be determined by:

10. The at least one memory, when executed by the at least one processor, causes the terminal device to determining a second index for a second starting resource block based on the first index and the offset; determining a second length based on the first length and the offset; The terminal device of claim 9 , further comprising: a memory for storing instructions for causing the second FDRA to be determined by:

11. The at least one memory, when executed by the at least one processor, causes the terminal device to determining the second index of the second starting resource block based on the first index, the offset, and a further offset configured by the network equipment; The terminal device according to claim 10, further comprising: a memory for storing instructions for causing the second index to be determined by:

12. The offset is the ratio of the bandwidth of the subband for the SBFD communication to the bandwidth of the band for the non-SBFD communication, or a value set by the network device; 12. The terminal device according to claim 6, comprising at least one of:

13. The at least one memory, when executed by the at least one processor, causes the terminal device to determining a first set of a first number of resource block groups (RGB) based on the at least one FDRA field in the DCI according to a determination that the resource allocation type indicated by the configuration information from the network device is Type 0; determining a second set of a second number of RGB colors based on settings from the network device; storing instructions for determining the first FDRA and the second FDRA by 6. A terminal device according to claim 1.

14. 14. The terminal device according to claim 1, wherein the first communication type associated with the at least one FDRA field is predefined or configured by the network device.

15. 15. The terminal device according to claim 1, wherein the SBFD communication is performed in an SBFD slot, a SBFD minislot, or an SBFD symbol, and the non-SBFD communication is performed in a non-SBFD slot, a non-SBFD minislot, or a non-SBFD symbol.

16. 16. The terminal device according to claim 1, wherein the first communication and the second communication are transmitted to the network device, or the first communication and the second communication are received from the network device.

17. 17. The terminal device according to claim 1, wherein the first communication and the second communication are Physical Uplink Shared Channel (PUSCH) repetitions or Physical Downlink Shared Channel (PDSCH) repetitions.

18. The terminal device according to claim 1 , wherein the first communication and the second communication are multi-PUSCH scheduling or multi-PDSCH scheduling.

19. at least one processor; When executed by the at least one processor, the network device is configured to: 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 dynamically scheduled or activated communication, the at least one FDRA in the DCI 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; performing the first communication and the second communication with the terminal device based on the first FDRA and the second FDRA, respectively; at least one memory storing instructions to cause the Equipped with the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of the SBFD communication or non-SBFD communication; Network equipment.

20. The at least one memory, when executed by the at least one processor, causes the network device to transmitting setting information to the terminal device, the setting information comprising: frequency band, a first number of time units for both uplink and downlink transmissions; a first position of the first number of time units within a radio frame; a second number of time units for uplink transmission; a second position of the second number of time units within the radio frame; a third number of time units for downlink transmission; a third position of the third number of time units within the radio frame; or resource allocation type, indicating and transmitting at least one of:

20. The network appliance of claim 19, further comprising instructions for causing the network appliance to:

21. 21. The network equipment of claim 20, wherein the time unit is a slot, a minislot, or a symbol.

22. 22. The network equipment of claim 20 or 21, wherein the configuration information includes trigger information, the trigger information prompting the terminal equipment to determine different FDRAs for the SBFD communication and the non-SBFD communication.

23. 22. The network equipment of claim 19, wherein the DCI further includes trigger information, the trigger information prompting the terminal equipment to determine different FDRAs for the SBFD communication and the non-SBFD communication.

24. The at least one memory, when executed by the at least one processor, causes the network device to determining the first FDRA based on the at least one FDRA field in the DCI; determining the second FDRA based on the first FDRA and an offset; 24. The network device according to claim 19, wherein the network device stores instructions for causing the network device to execute the following:

25. The at least one memory, when executed by the at least one processor, causes the network device to determining a first set of a first number of resource block groups (RGB) based on the at least one FDRA field in the DCI according to determining that the resource allocation type is Type 0; 25. The network device of claim 24, further storing instructions that cause the first FDRA to be determined by:

26. The at least one memory, when executed by the at least one processor, causes the network device to determining a second number of second RGB sets based on the first number and the offset; 26. The network device of claim 25, further storing instructions that cause the second FDRA to be determined by:

27. The at least one memory, when executed by the at least one processor, causes the network device to determining, according to a determination that the resource allocation type is Type 1, a first index and a first length of a first starting resource block based on the at least one FDRA field in the DCI; 25. The network device of claim 24, further storing instructions that cause the first FDRA to be determined by:

28. The at least one memory, when executed by the at least one processor, causes the network device to determining a second index for a second starting resource block based on the first index and the offset; determining a second length based on the first length and the offset; 28. The network device of claim 27, further storing instructions that cause the second FDRA to be determined by:

29. The at least one memory, when executed by the at least one processor, causes the network device to determining the second index of the second starting resource block based on the first index, the offset, and a further offset defined in the network equipment; 30. The network device of claim 28, further storing instructions that cause the second index to be determined by:

30. The offset is the ratio of the bandwidth of the subband for the SBFD communication to the bandwidth of the band for the non-SBFD communication, or a value defined in the network device; 30. The network device of claim 24, comprising at least one of:

31. The at least one memory, when executed by the at least one processor, causes the network device to sending a configuration to the terminal device, the configuration indicating that the second FDRA includes a second number of second RGB sets; 24. The network device according to claim 19, wherein the network device stores instructions for causing the network device to execute the following:

32. The at least one memory, when executed by the at least one processor, causes the network device to sending a notification to the terminal device, the notification indicating a type of the first communication associated with the at least one FDRA field; 32. The network device of claim 19, wherein the network device stores instructions to cause the network device to execute the following:

33. 33. The network equipment of claim 19, wherein the SBFD communication is performed in an SBFD slot, a SBFD minislot, or an SBFD symbol, and the non-SBFD communication is performed in a non-SBFD slot, a non-SBFD minislot, or a non-SBFD symbol.

34. 34. The network device according to claim 19, wherein the first communication and the second communication are received from the terminal device, or the first communication and the second communication are transmitted to the terminal device.

35. 35. The network equipment of claim 19, wherein the first communication and the second communication are Physical Uplink Shared Channel (PUSCH) repetitions or Physical Downlink Shared Channel (PDSCH) repetitions.

36. The network device according to claim 19 , wherein the first communication and the second communication are multi-PUSCH scheduling or multi-PDSCH scheduling.

37. receiving, from a network device at a terminal device, downlink control information (DCI) including 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 the at least one FDRA field in the DCI; performing the first communication and the second communication with the network device based on the first FDRA and the second FDRA, respectively; Including, the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of the SBFD communication or non-SBFD communication; method.

38. transmitting, in a network device, downlink control information (DCI) to a terminal device, the DCI including at least one Frequency Domain Resource Allocation (FDRA) field for at least one dynamically scheduled or activated communication, the at least one FDRA field in the DCI 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; performing the first communication and the second communication with the terminal device based on the first FDRA and the second FDRA, respectively; Including, the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of the SBFD communication or non-SBFD communication; method.

39. means for receiving, from a network device, downlink control information (DCI) including 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 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; means for performing the first communication and the second communication with the network device based on the first FDRA and the second FDRA, respectively; Equipped with the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of the SBFD communication or non-SBFD communication; Device.

40. means, in a network equipment, for transmitting, to a terminal device, Downlink Control Information (DCI) including 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 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; means for performing the first communication and the second communication with the terminal device based on the first FDRA and the second FDRA, respectively; Equipped with the first communication is one of SBFD communication or non-SBFD communication, and the second communication is the other of the SBFD communication or non-SBFD communication; Device.

41. A computer readable medium comprising program instructions for causing an apparatus to perform at least the method of claim 37 or 38.

Images