Method and apparatus for handling uplink sub-band based transmission

Abstract

The present disclosure is generally directed to a wireless communication system and method, and particularly to resource configuration and allocation for time division duplex. The various embodiments described in detail below relate to scheduling and configuration of time-frequency communication resources within an uplink subband that is configured within a set of resources that are otherwise configured for downlink transmissions or transmissions with a flexible direction. Various embodiments are described below for dynamically scheduling downlink transmissions within resources of an uplink subband, for modifying / expanding the resources of the uplink subband in order to improve uplink and downlink transmission resource balance in real time. The following disclosure also provides various embodiments for resolving uplink and downlink transmission time collisions within the uplink sub-band and for transmitting downlink reference signals on the UL sub-band.

Description

Technical Field

[0001] The present disclosure is generally directed to wireless communication systems and methods, and more particularly to time division duplex resource configuration and allocation. Background Art

[0002] Over-the-air radio resources are a key component in wireless communication networks. Effective communication relies heavily on the efficient allocation of these resources. These resources are shared by base stations and end devices for communication in either the uplink or downlink direction. Reducing and eliminating signal interference and collisions during this sharing is often a key aspect of designing efficient wireless communication systems. Summary of the invention

[0003] The present disclosure is generally directed to wireless communication systems and methods, and more particularly to time division duplexing of frequency resources.

[0004] In some example embodiments, a method performed by a wireless terminal device is disclosed. The method may include: receiving a configuration of a first set of time-frequency resources as downlink time-frequency resources or direction-flexible time-frequency resources from a wireless access network node; and receiving a configuration of an uplink subband for uplink transmission from the wireless access network node, the uplink subband occupying consecutive resource blocks in frequency and a set of symbols in time within the first set of time-frequency resources.

[0005] In the above example implementation, the method may further include: receiving scheduling of a second set of time-frequency resources for uplink transmission from the radio access network node, the second set of time-frequency resources being partially within the uplink subband and partially outside the uplink subband in time.

[0006] In any of the above embodiments, the configuration of the uplink subband is received from a radio access network node through semi-static radio resource control (RRC) signaling or a medium access control (MAC) control element (CE).

[0007] In any of the above embodiments, a portion of the second set of time-frequency resources outside the uplink sub-band is implemented as a time domain adjustment of the uplink sub-band.

[0008] In any of the above embodiments, the time domain adjustment of the uplink subband is valid only during the scheduling of the second set of time-frequency resources for uplink transmission, or before the next time domain adjustment of the uplink subband, or within a predetermined or configured time period after the scheduling of the second set of time-frequency resources for uplink transmission.

[0009] In any of the above embodiments, the scheduling of the second set of time-frequency resources is received from the radio access network node as a downlink control information (DCI) message.

[0010] In any of the above embodiments, the configuration of the uplink subband is sent in response to the wireless access network node receiving a capability report from the wireless terminal device, which capability report indicates that the wireless terminal device supports sub-band full-duplex (SBFD) or that the wireless terminal device supports the use of a second set of time-frequency resources for uplink transmission.

[0011] In any of the above embodiments, the DCI message includes one or more parameters indicating the time and frequency positions of the second set of time-frequency resources to the wireless terminal device.

[0012] In any of the above embodiments, the DCI message includes an indication indicating to the wireless terminal device that the uplink subband is to be extended according to the second set of time-frequency resources.

[0013] In any of the above embodiments, the radio access network node is prohibited from further scheduling any resource that is temporally quasi-co-located with a portion of the second set of time-frequency resources outside the uplink sub-band and within the frequency resource range of the uplink sub-band.

[0014] In any of the above embodiments, flexible resources are configured for the uplink subband in the time-frequency resources of the uplink subband through signaling from the radio access network node; or part of the time-frequency resources of the uplink subband is allowed to be configured as flexible resources through signaling.

[0015] In any of the above embodiments, the transmission direction of the flexible resources is determined based on the direction of the transmission scheduled in the flexible resources.

[0016] In any of the above embodiments, the flexible resources configured in the uplink sub-band include one or more OFDM symbols across the entire frequency range of the uplink sub-band.

[0017] In any of the above embodiments, the flexible resources configured in the uplink sub-band include one or more frequency resource blocks spanning the entire OFDM symbol range of the uplink sub-band.

[0018] In any of the above implementations, the signaling includes RRC signaling.

[0019] In any of the above embodiments, the flexible resources are configured in response to the wireless access network node receiving a capability report from the wireless terminal device, which capability report indicates that the wireless terminal device supports sub-band full duplex (SBFD) or the wireless terminal device supports flexible resources in an uplink sub-band.

[0020] In another example embodiment, a method performed by a wireless terminal is disclosed. The method may include: receiving a configuration of a first set of time-frequency resources as time-frequency resources or direction-flexible time-frequency resources for a downlink from a wireless access network node; receiving a configuration of an uplink subband for uplink transmission from the wireless access network node, the uplink subband occupying contiguous resource blocks in frequency and a set of OFDM symbols in time within the first set of time-frequency resources; and receiving a downlink transmission from the wireless access network node in the configured uplink subband.

[0021] In the above embodiments, receiving a downlink transmission in the configured uplink subband may include receiving signaling from a radio access network node to schedule a downlink transmission in at least a portion of the uplink subband.

[0022] In any of the above embodiments, at least a portion of the uplink subband does not correspond to other portions of the uplink subband overlapping with at least a portion of the uplink subband and other portions of the uplink subband scheduled for uplink transmission.

[0023] In any of the above embodiments, when scheduling downlink transmission, the signaling is included in a DCI from a radio access network node.

[0024] In any of the above embodiments, the wireless access network node is prohibited from further scheduling uplink transmissions on a second set of time-frequency resources, where the second set of time-frequency resources overlaps with at least a portion of the configured uplink subband in time and is within the frequency resource range of the configured uplink subband.

[0025] In any of the above embodiments, the method may further include: determining a first priority of an uplink sub-band, wherein the first priority is used as a basis for determining whether to allow scheduling of downlink transmission in the uplink sub-band.

[0026] In any of the above embodiments, if the first priority of the uplink subband is lower than the second priority associated with the downlink transmission, downlink transmission is allowed; and if the first priority of the uplink subband is higher than the second priority associated with the downlink transmission, downlink transmission is prohibited.

[0027] In any of the above embodiments, the method may also include: resolving a scheduling conflict between two downlink transmissions of the same priority with time overlap within an uplink subband or a scheduling conflict between a downlink transmission and an uplink transmission by retaining the transmission within the frequency range of the uplink subband and discarding the transmission outside the frequency range of the uplink subband.

[0028] In any of the above embodiments, the method may further include: prohibiting scheduling dynamic PDSCH downlink transmission and dynamic PUSCH / PUCCH through the same PDCCH with overlapping time within the uplink subband.

[0029] In any of the above embodiments, the method may also include: resolving scheduling conflicts between dynamic PDSCH downlink transmissions and dynamic PUCCH / PUCCH uplink transmissions that overlap in time within an uplink subband based on the timing of the corresponding scheduling PDCCHs for dynamic PDSCH downlink transmissions and dynamic PUSCH / PUCCH uplink transmissions.

[0030] In any of the above embodiments, the method may also include: resolving scheduling conflicts between dynamic PDSCH downlink transmissions and semi-static PUSCH / PUCCH uplink transmissions that overlap in time within an uplink subband based on the OFDM symbol-level time interval between the corresponding scheduling PDCCHs for dynamic PDSCH downlink transmissions and semi-static PUSCH / PUCCH uplink transmissions.

[0031] In any of the above embodiments, the method may also include: resolving scheduling conflicts between dynamic PDSCH downlink transmissions and semi-static PUSCH / PUCCH uplink transmissions that overlap in time within an uplink subband by retaining semi-static PUSCH / PUCCH uplink transmissions and discarding dynamic PDSCH downlink transmissions.

[0032] In any of the above embodiments, the method may also include: resolving scheduling conflicts between temporally overlapping semi-static PDSCH downlink transmissions and dynamic PUCCH / PUCCH uplink transmissions within an uplink subband by retaining dynamic PUSCH / PUCCH uplink transmissions and discarding semi-static PDSCH downlink transmissions.

[0033] In any of the above embodiments, the method may also include: resolving the scheduling conflict between the semi-static PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband by retaining the semi-static PUSCH / PUCCH uplink transmission and discarding the semi-static PDSCH downlink transmission.

[0034] In any of the above embodiments, the method may further include: the downlink transmission is configured to transmit a downlink reference signal in an uplink subband.

[0035] In some other embodiments, methods performed by a wireless access network node (or base station) are disclosed. These methods correspond to methods performed by the above-mentioned wireless terminal device when semi-statically and dynamically configuring and reconfiguring uplink subbands, uplink transmission / reception, and downlink transmission / reception on uplink subbands during its communication.

[0036] In some other embodiments, a wireless communication device is disclosed. The wireless communication device may include a processor and a memory, wherein the processor is configured to read a code from the memory and implement any one of the above methods.

[0037] In some other embodiments, a computer program product is disclosed, the computer program product comprising a non-transitory computer-readable program medium having computer code stored thereon. When executed by a processor, the computer code may cause the processor to implement any of the above methods.

[0038] Other aspects and alternatives of the above-described embodiments and their implementations are described in more detail in the following figures, description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 An example wireless communication network including a radio access network, a core network, and a data network is shown.

[0040] Figure 2 An example radio access network including a plurality of mobile stations or UEs and radio access network nodes communicating with each other over an over-the-air wireless communication interface is shown.

[0041] Figure 3 An example slot structure illustrating the time-frequency resources of the uplink subband is shown.

[0042] Figure 4 An example slot structure illustrating the time-frequency resources of the uplink subband is shown.

[0043] Figure 5 An example slot structure illustrating the time-frequency resources of the uplink subband is shown.

[0044] Figure 6 An example slot structure illustrating adjustment of time-frequency resources of uplink subbands is shown.

[0045] Figure 7 An example slot structure illustrating adjustment of time-frequency resources of uplink subbands is shown.

[0046] Figure 8 An example slot structure illustrating adjustment of time-frequency resources of uplink subbands is shown.

[0047] Fig. 9 An example slot structure illustrating adjustment of time-frequency resources of uplink subbands is shown.

[0048] Fig.10 An example slot structure illustrating the configuration of downlink resources within an uplink subband is shown.

[0049] Fig.11 An example slot structure illustrating the configuration of downlink resources within an uplink subband is shown.

[0050] Fig.12 An example slot structure illustrating the configuration of downlink resources within an uplink subband is shown.

[0051] Fig.13 An example slot structure illustrating the configuration of downlink resources within an uplink subband is shown.

[0052] Fig.14 An example slot structure illustrating the configuration of downlink resources within an uplink subband is shown.

[0053] Fig.15 An example slot structure illustrating the configuration of downlink resources within an uplink subband is shown.

[0054] Fig.16 An example slot structure illustrating the configuration of downlink resources within an uplink subband is shown. DETAILED DESCRIPTION

[0055] Examples of techniques and implementations and / or embodiments described in the present disclosure may be used to facilitate efficient configuration and allocation of uplink and downlink time-frequency communication resources in wireless networks. The term "exemplary" is used to mean "an example of..." and does not mean an ideal or preferred example, implementation, or embodiment unless otherwise specified. The section titles used in the present disclosure are intended to facilitate understanding of the disclosed implementations and are not intended to limit the techniques disclosed in the sections to the corresponding sections. The disclosed implementations may also be embodied in a variety of different forms, and therefore, the scope of the present disclosure or the claimed subject matter is intended to be interpreted as not being limited to any of the embodiments set forth below. Various implementations may be embodied as methods, devices, components, systems, or non-transitory computer-readable media. Therefore, embodiments of the present disclosure may, for example, take the form of hardware, software, firmware, or any combination thereof.

[0056] ] The present disclosure is generally directed to wireless communication systems and methods, and in particular to resource configuration and allocation for time division duplexing. The various embodiments described in detail below relate to the scheduling and configuration of time-frequency communication resources within an uplink subband, which is configured within a set of resources that are otherwise configured for downlink transmissions or transmissions with flexible direction. Various embodiments of dynamically scheduling downlink transmissions within the resources of an uplink subband, modifying / extending the resources of an uplink subband to improve the balance of uplink and downlink transmission resources in real time are described below. The following disclosure also provides various embodiments for resolving uplink and downlink transmission time conflicts within an uplink subband and transmitting downlink reference signals on a UL subband.

[0057] Wireless Network Overview

[0058] Figure 1 The example wireless communication network shown as 100 in FIG. 1 may include wireless terminal devices or user equipment (UE) 110, 111, and 112, an operator network 102, various service applications 140, and other data networks 150. For example, the operator network 102 may include access networks 120 and 121 and a core network 130. The operator network 110 may be configured to transmit voice, data, and other information (collectively referred to as data services) between UE 110, UE 111, and UE 112, between UE and service application 140, or between UE and other data networks 150. The access networks 120 and 121 may be configured as various wireless access network nodes (WANNs, alternatively referred to as base stations) to interact with the UE on one side of the communication session and the core network 130 on the other side. The core network 130 may include various network nodes configured to control the communication session and perform network access management and traffic routing. The service application 140 may be hosted by various application servers deployed outside the core network 130 but connected to the core network 130. Likewise, other data networks 150 may also be connected to the core network 130 .

[0059] exist Figure 1 In the wireless communication network of 100, UEs can communicate with each other through a wireless access network. For example, UEs 110 and 112 can be connected to the same access network 120 and communicate through the same access network 120. UEs can communicate with each other through both the access network and the core network. For example, UE 110 can be connected to access network 120, and UE 111 can be connected to access network 121, and therefore, UE 110 and UE 111 can communicate with each other through access networks 120 and 121 and core network 130. The UE can also communicate with service applications 140 and data network 150 through the core network 130. In addition, as shown in 113, the UEs can communicate directly with each other through sidelink communications.

[0060] Figure 2 Further shown is an example system diagram of a wireless access network 120, which includes a WANN 202 serving UE 110 and UE 112 via an air interface 204. The wireless transmission resources of the air interface 204 include a combination of frequency, time and / or space resources. Each of UE 110 and UE 112 can be a mobile or fixed terminal device equipped with a mobile access unit such as a SIM / USIM module for accessing the wireless communication network 100. UE 110 and UE 112 can each be implemented as a terminal device, including but not limited to a mobile phone, a smart phone, a tablet computer, a tablet computer, a vehicle-mounted communication device, a roadside communication device, a sensor device, a smart appliance (such as a TV, a refrigerator and an oven), or other devices capable of wireless communication via a network. As shown in FIG. Figure 2 As shown, each UE, such as UE 112, may include a transceiver circuit 206 coupled to one or more antennas 208 to enable wireless communications with WANN 120 or with another UE, such as UE 110. Transceiver circuit 206 may also be coupled to processor 210, which may also be coupled to memory 212 or other storage device. Memory 212 may be transitory or non-transitory and may store therein computer instructions or codes that, when read and executed by processor 210, cause processor 210 to implement the various methods described herein.

[0061] Similarly, WANN 120 may include a base station or other wireless network access point capable of wirelessly communicating with one or more UEs over air interface 204 and communicating with core network 130. For example, WANN 120 may be implemented in the form of a 2G base station, a 3G nodeB, an LTE eNB, a 4G LTE base station, a 5G NR base station, a 5G centralized unit base station, or a 5G distributed unit base station without limitation. Each type of these WANs may be configured to perform a corresponding set of wireless network functions. WANN 202 may include a transceiver circuit 214 coupled to one or more antennas 216, which may include various forms of antenna towers 218 to enable wireless communication with UE 110 and UE 112. Transceiver circuit 214 may be coupled to one or more processors 220, which may also be coupled to a memory 222 or other storage device. The memory 222 may be transient or non-transitory and may store therein instructions or codes that, when read and executed by the one or more processors 220 , cause the one or more processors 220 to implement various functions of the WANN 120 described herein.

[0062] Wireless access networks (such as Figure 2 The data packets in the examples described in the examples may be transmitted as protocol data units (PDUs). The data included therein may be encapsulated into PDUs at different network layers, and the PDUs are wrapped with nested and / or layered protocol headers. Once a connection (e.g., a radio link control (RRC) connection) is established between the sender and the receiver, the PDUs may be transmitted between the sender or sender (these two terms are used interchangeably) and the receiver or receiver (these two terms are also used interchangeably). Any sender or receiver may be such as Figure 2 110 and 120, or wireless terminal devices such as Figure 2 Each device can be both a sending device and a receiving device for bidirectional communication.

[0063] UL sub-band

[0064] In a wireless access communication network, for a carrier or frequency band configured for time division duplex (TDD), each time slot is configured for downlink (DL) or for uplink (UL) communication. A time slot can also be configured as a flexible time slot, which can be used for DL ​​or for UL communication, but not for both at the same time. For simplicity, the term "time slot" is alternatively referred to as a "time slot" in this article. Because DL services are generally more dominant than UL services in a wireless access network, DL time slots are generally configured more in number than UL time slots. An example of a typical cyclic time slot structure may be DDDSU, where D represents a DL time slot, U represents a UL time slot, and S represents a flexible time slot. For example, a flexible time slot may contain a DL symbol and a UL symbol. Therefore, the number of UL time slots is generally small and often discontinuous, thereby limiting the performance of UL transmission. For example, the amount of UL data may be limited, and more importantly, due to the frequent UL time slot discontinuity, the timeliness and edge coverage of UL transmission are relatively poor.

[0065] In some example embodiments, sub-band full duplex (SBFD) techniques may be employed to provide improved UL support. For example, a time-frequency resource comprising several consecutive resource blocks (RBs) in the frequency domain and several consecutive OFDM symbols within a DL or flexible slot may be configured as a UL sub-band. In other words, a time-frequency resource referred to as a UL sub-band may be configured to support UL transmissions within an additional DL or flexible slot.

[0066] An example of SBFD time-frequency resource configuration is as follows: Figure 3-5 As shown. Figure 3-Figure 5In each of the figures in FIG. 1 , the horizontal axis represents the time slot in units of OFDM symbols, and the vertical axis represents the frequency resource in units of resource blocks (RBs). A particular time slot may be configured with a configuration of DL, UL, or F (flexible) OFDM symbols (for simplicity, OFDM symbols may be alternatively referred to as symbols hereinafter). For example, Figure 3 The time slot in includes 9 DL symbols followed by 5 UL symbols. For another example, Figure 4 A time slot in includes 9 DL symbols, followed by 2 F symbols, and then followed by 3 UL symbols. For another example, Figure 5 A time slot in consists of 9 F symbols followed by 5 UL symbols. Figure 3-Figure 5 In each of the Figures, an example UL subband is configured, occupying one or more RBs in frequency and in time and in other DL ( Figure 3 and Figure 4 ) or F( Figure 5 ) OFDM symbol occupies several (for example, 7) OFDM symbols. A person skilled in the art will understand that Figure 3-5 The DL, UL, F symbol configurations and UL subband configurations shown in are merely non-limiting examples.

[0067] In some example implementations of SBFD described above, the UL subbands may be configured via RRC signaling. Therefore, the configuration and reconfiguration of UL subbands within other DL or F time-frequency resources is semi-static rather than fully dynamic. As a result, such implementations, while allowing for overall additional UL support when needed, are very limited or unable to provide a dynamic balance of UL and DL resources based on the real-time needs of various services and applications. Specifically, SBFD based on RRC signaling does not provide dynamic and fast reconfiguration of UL subbands when UL traffic decreases and more resources are needed for DL ​​transmission.

[0068] One potential solution for providing more real-time configuration in SBFD is to allow dynamic scheduling of DL transmissions within the time-frequency resources of the UL subbands that have been configured via RRC, as described in further detail in various embodiments below.

[0069] In addition, if DL transmission is allowed within the time-frequency resources of the UL subband, new problems will arise. For example, within the time-frequency resources of the UL subband, various potential DL transmissions and various potential UL transmissions may overlap in the time domain. How to solve their time domain overlap? This application also provides some solutions.

[0070] In addition, in the present disclosure, a new UL scheduling transmission based on UL subband is also provided, which can dynamically balance DL resources and UL resources, thereby improving resource utilization.

[0071] Dynamic adjustment of UL subbands to include additional symbols

[0072] In some example embodiments, when it is determined that more UL time-frequency resources are needed in real time, UL transmissions in the configured UL subbands may be dynamically adjusted (e.g., extended) in a time slot in the time domain to include additional OFDM symbols outside the configured UL subbands.

[0073] In this way, the original RRC configuration of the base station for the UL subband in other DL or F time slots can be determined based on the expected UL transmission requirements of the service or application associated with a particular RRC session. Considering that the UL subband can be dynamically adjusted / extended in time, the semi-static RRC configuration of the UL subband can be oriented towards the conservative end (smaller UL resource configuration). During the RRC session, if the UL traffic becomes heavier than expected and the traditional semi-static UL subband configuration becomes insufficient to effectively handle the UL traffic at that time, the UL transmission scheduled within the UL subband can be dynamically adjusted / extended in the time domain to additional OFDM symbols outside the UL subband. In some example embodiments, the extended UL symbols may occupy RBs within those semi-statically configured UL subbands. In some specific embodiments, the extended UL symbols may occupy the same RBs of the semi-statically configured UL subbands configured / scheduled for UL transmission.

[0074] The above-described example implementations may be advantageous in providing an adaptive and dynamic balance between UL and DL resource configurations while keeping any previous subband filtering techniques (including filter design and frequency locking, etc.) unchanged, because the frequency domain resources of the UL subband may not need to be changed (only the time resources are extended), which is beneficial for subband filter design and frequency locking.

[0075] The time-frequency resources of the UL subband (including the extended symbols within the RB of the UL subband) can be used for any UL transmission, including but not limited to any one of PUSCH (Physical Uplink Shared Channel), PRACH (Physical Random Access Channel), PUCCH (Physical Uplink Control Channel) or SRS (Sounding Reference Signal) scheduled by DCI (Downlink Control Information) and / or configured by RRC signaling. For example, PUCCH communication includes uplink communication carrying HARQ-ACK (Hybrid Automatic Repeat Request Acknowledgement), CSI (Channel State Indication) or SR (Scheduling Request). For example, HARQ-ACK includes uplink HARQ-ACK corresponding to PDSCH (Physical Downlink Shared Channel) communication and uplink HARQ-ACK corresponding to PDCCH (Physical Downlink Control Channel) communication.

[0076] In some example embodiments, DCI may be used to schedule dynamic time extension of UL transmissions. In a specific example embodiment, the UL subband may be semi-statically configured for the UE so that the UE knows the time-frequency resources of the UL subband. Then, when the DCI from the corresponding base station is used in the PDCCH to schedule uplink transmissions (e.g., PUSCH / PUCCH / PRACH transmissions) using the UL subband resources, a parameter may be introduced into the DCI to achieve the above-described dynamic time extension. For example, the parameter may be used for one of the following purposes:

[0077] (1) It can be used to notify that the time domain resources of the UL subband are adjusted, and the adjusted time domain resources of the UL subband also include symbols outside the UL subband configured / indicated / scheduled by the DCI for UL transmission (e.g., PUSCH / PUCCH / PRACH transmission). In this case, the valid time window of the time domain resources of the adjusted UL subband scheduled by the DCI can be one of the following: the time domain resources of the UL subband adjusted by the DCI scheduling the UL transmission are only valid for the current UL transmission scheduling; or the time domain resources of the UL subband adjusted by the DCI scheduling the UL transmission are valid until the time domain resources of the UL subband are readjusted by another DCI scheduling the UL transmission next time; or once the adjustment is indicated in the DCI scheduling the current UL transmission, the time domain resources of the adjusted UL subband are valid for a subsequent predefined or configured time period. To this end, the time domain resources of the UL subband are adjusted during the above-mentioned various optional time windows, so that all symbols scheduled for UL transmission are part of the adjusted UL subband during the valid time window.

[0078] (2) Even if the symbols so scheduled for uplink transmission (e.g., PUSCH / PUCCH / PRACH transmission) exceed the time domain resources of the UL sub-band, it can also be used to notify that the scheduled uplink transmission (e.g., PUSCH / PUCCH / PRACH transmission) will be transmitted according to the symbols configured / indicated / scheduled for uplink transmission in the DCI. For this purpose, the time domain resources of the UL sub-band are not adjusted, but a part of the symbols scheduled for UL transmission can be outside the UL sub-band in the time domain.

[0079] In some example embodiments, the above-mentioned DCI associated with PUSCH transmission may correspond to a DCI format for scheduling PUSCH transmission. The DCI associated with PRACH transmission may correspond to a DCI format for triggering PRACH transmission. Similarly, the DCI associated with PUCCH transmission may correspond to a DCI format for scheduling PDSCH, or to a DCI that does not schedule PDSCH. In some example embodiments, a dedicated or special DCI format for DCI may be configured by the base station to schedule / indicate UL transmissions in a UL subband. Alternatively, a dedicated or special CORESET / PDCCH monitoring opportunity (MO) for DCI may be configured by the base station to schedule / indicate UL transmissions in a UL subband.

[0080] Therefore, the method does not require a new / dedicated DCI or DCI format to modify the UL subband, but reuses the DCI format and framework to schedule UL transmission, and only by adding one or more of the above parameters to the DCI. If the base station wants to adjust the time domain resources of the UL subband, the base station can set the value of the parameter, such as an indicator or a flag, to a specific state A to indicate that the UL subband will be modified. For example, the base station sets the parameter value in the DCI to a specific state A, and schedules UL transmission (e.g., PUSCH / PUCCH / PRACH transmission) through the DCI, then the symbols configured / indicated / scheduled for UL transmission in the DCI are automatically configured for the UL subband and UL transmission. In this way, the time domain resources of the UL subband are dynamically adjusted / extended while scheduling UL transmission, so that a dynamic balance between UL resources and DL resources can be achieved. If the uplink transmission is PUSCH, the PUSCH may include UL SCH and exclude UL SCH.

[0081] The above parameters can be implemented in a variety of ways and include more additional items. For example, a set of parameters can be used to indicate the number and position of UL symbol adjustment / extension. These parameters can be included in the DCI. In some other embodiments, the DCI may only need to include an indicator for indicating whether there is an adjustment / extension to the UL subband. The parameters specifying the actual way in which the adjustment / extension should be performed can be included in the scheduling of the DCI, or alternatively, preconfigured / predefined, or can be semi-statically configured by, for example, RRC signaling or MAC CE signaling. When the indication in the DCI exists or is activated, this preconfigured / predefined or semi-statically configured parameter indicating the adjustment / extension method may become valid, otherwise it may be invalid. The adjustment / extension method may have different options, represented by different preconfigured / predefined or semi-statically configured parameter sets. These parameter sets can be identified by indexes. Therefore, the indicator in the DCI can, for example, use an index to additionally specify a specific preconfigured / predefined or semi-statically configured parameter set, which indicates the way to adjust / extend symbols in the time domain of the UL subband.

[0082] In some embodiments, the parameter may be configured for the UE via higher layer signaling (such as RRC signaling or MAC CE signaling). Once the RRC configures the parameter to exist for the UE, the parameter may be included in the DCI for dynamic scheduling of UL transmissions outside the UL subband. Otherwise, the parameter may not be included in the DCI for dynamic scheduling.

[0083] In some other embodiments, the above parameters or indications may not need to be included in the DCI or reconfigured. Instead, the UE and the base station may follow predefined and agreed rules for dynamic scheduling of UL transmissions via DCI. For example, the predefined and agreed rules correspond to one of the two purposes of the above parameters. For example, for a UE supporting SBFD, the DCI from the base station may schedule UL transmissions (e.g., PUSCH / PUCCH / PRACH transmissions) in a UL subband, and the scheduled time domain resources configured / indicated for the UL transmission may exceed the time domain resources of the UL subband (or otherwise outside the time domain resources of the subband), then the UE shall perform UL transmission in the configured / indicated resources, the configured / indicated resources include time resources outside the time domain range of the UL subband, but the frequency domain resources used for the scheduled UL transmission are still within the frequency domain resource range of the UL subband. In this way, if the base station needs to schedule UL transmission for the SBFD UE through DCI, the time domain resources of the UL transmission can be configured or indicated as time domain resources exceeding the UL subband, and the UL transmission is performed in the configured / indicated time domain resources.

[0084] An example of dynamic time domain extension of a semi-statically configured UL subband is Figure 6-9 Similarly, Figure 6-9 In , the horizontal axis represents the time slot in units of OFDM symbols, and the vertical axis represents the frequency resource in units of RBs. Figure 6 In the UL subband, the UL subband starts at symbol #2 and ends at symbol #8. The UL transmission can be scheduled by the base station through DCI for all or part of the frequency resources and for the adjusted time domain resources outside the UL subband (for example, the base station can schedule PUSCH / PUCCH / PRACH in the UL subband through the scheduling DCI in the PDCCH). Figure 6 In the example of , the DCI may schedule multiple additional symbols outside the UL subband for UL transmission (e.g., symbols #9 and #10 outside the UL subband in addition to symbols #2 to #8 within the UL subband). Specifically, the base station may schedule PUSCH / PUCCH / PRACH transmission to occupy symbols #2 to #10. Figure 6 The time domain position of the UL transmission with time adjustment indicated in may be specified in the scheduling DCI.

[0085] The DCI may include the above parameter (alternatively referred to as an indicator or a plane) with a value of A to signal the UE to perform UL transmission in the scheduled time domain resources symbol #2 to symbol #10. For UEs that do not perform UL transmission extending outside the UL subband under such scheduling, the DCI sets the value of the parameter to B instead of A. When the parameter is set to the value A, it may also indicate a modification of the UL subband to include resources outside the UL subband semi-statically configured by the DCI within the valid time window as described above, in other words, when the above scheduling DCI includes the parameter with a value of B, the UE performs UL transmission only in the scheduled time domain resources symbol #2 to symbol #8, and does not perform UL transmission in symbol #9 to symbol #10.

[0086] To describe the above example implementation in another way, please note that in Figure 6In one DL time slot, one UL subband is configured in the time domain to occupy a total of 7 consecutive symbols from symbol #2 to symbol #8. The base station schedules the example PUSCH / PUCCH / PRACH in the UL subband through the DCI in the PDCCH. The DCI may indicate that the PUSCH / PUCCH / PRACH occupies the time domain resources from symbol #2 to symbol #10. Symbols #9 and #10 are not configured for the UL subband (here symbols #9 and #10 are initially configured as DL symbols, but may also be UL symbols or flexible symbols). If the base station sets the value of the parameter in the DCI to notify that the time domain resources of the UL subband are adjusted to include the symbols configured / indicated for PUSCH / PUCCH / PRACH in the DCI. In this way, the UE should consider that symbols #9 and #10 are dynamically configured for the UL subband to transmit PUSCH / PUCCH / PRACH. That is, as described above, within the valid time window, the UL subband is dynamically adjusted to include symbols #2 to #10. In this way, the UE transmits PUSCH / PUCCH / PRACH in symbol #2 to symbol #10 of the UL subband. Alternatively, if the base station sets the value of the parameter in the DCI to notify that PUSCH / PUCCH / PRACH is transmitted according to the symbol configured / indicated for PUSCH / PUCCH / PRACH in the DCI. In this way, the UE transmits PUSCH / PUCCH / PRACH in symbol #2 to symbol #10 of the UL subband, although symbols #9 and #10 are not originally configured for the UL subband.

[0087] Figure 7-9 The example shown in Figure 6 The example in is similar to that in Figure 7 In the case of (i) the additional symbols that may be scheduled by DCI outside the UL subband may be the initially preconfigured UL symbols; (2) in the case of Figure 8 In (3), the additional symbols that may be scheduled by DCI outside the UL subband may be the initially preconfigured F (flexible) symbols; and Fig. 9 In , the UL subband is configured (eg, by RRC) in F symbols, and the additional symbols that may be scheduled by DCI outside the UL subband may be the initially preconfigured UL symbols. The basic principles for scheduling UL transmissions apply to these cases.

[0088] In order to better support the above-mentioned dynamic UL subband adjustment, corresponding UE capabilities can be introduced. In other words, the UE may or may not support dynamic UL subband adjustment for UL transmission. The UE can therefore report this capability or not to the base station. If the UE reports to the base station that such a capability is supported at the UE, the base station can dynamically schedule / configure the UE to perform UE transmission outside the symbols of the UL subband in the manner exemplarily described above. Otherwise, the base station will prohibit dynamically scheduling / configuring the UE to perform these UL transmission operations. For example, if the UE does not report the capability or explicitly reports that it does not have this capability, the base station will avoid scheduling PUSCH / PUCCH / PRACH that exceeds the time domain range of the UL subband.

[0089] In some example embodiments, as described above, the above-described dynamic UL transmission scheduling and operation may be limited to the frequency domain of the UL subband. Figure 6-9 In the above example, for the dynamically adjusted symbols #9 and #10 for UL transmission, only the resources in the frequency domain of the UL subband can be dynamically scheduled as frequency resources for UL transmission. In this way, among other advantages, the subband filter design and frequency locking may not need to be modified.

[0090] In some example embodiments, in order to avoid / reduce interference of DL transmissions to UL transmissions, some additional scheduling or configuration restrictions may be predefined and adopted. Figure 6 In the example, for symbols outside the time domain resources of the UL subband dynamically scheduled for UL PUSCH / PUCCH / PRACH transmission, the base station may not allow DL transmission to be scheduled in the frequency domain of the UL subband. In other words, it may be prohibited to schedule DL transmissions in the frequency domain of the UL subband. Figure 6 DL transmission is scheduled in symbol #9 and symbol #10 in the frequency resource range of the UL subband in .

[0091] Dynamic scheduling of downlink transmissions in UL sub-band resources

[0092] In some other cases, at certain specific times, for example, the UL subbands configured by RRC may not be fully used for UL transmission, and the DL traffic becomes too heavy, dynamic scheduling can be implemented to use the UL subbands for DL ​​transmission. Thus, in some example embodiments, a method for scheduling DL transmission in the resources of the UL subband is provided so that the resources of the UL subband can be used for DL ​​transmission in a dynamic manner. Figure 6-9 The basic principles for dynamically scheduling UL transmissions in various embodiments are applicable to such dynamic DL transmission scheduling.

[0093] For example, in the case where the UE is configured with a UL subband through RRC signaling, if the UE is scheduled to perform DL reception in resource A (i.e., DL transmission performed by the base station) through DCI in the PDCCH, and resource A overlaps with the resources of the UL subband in the time domain, the UE should perform DL reception from resource A.

[0094] In this case, the base station can ensure that the UL transmission of the UE in the UL subband and the DL reception using the UL subband resources do not overlap in the time domain. In this way, the resources of the UL subband can be dynamically used for DL ​​reception (DL transmission of the base station), thereby achieving flexible and dynamic use of UL subband resources.

[0095] For another example, in the case where the UE is configured with a UL subband through RRC signaling, if the base station schedules UL transmission to occupy some symbols in the UL subband, and the UL subband still has some idle symbols, the base station can schedule DL transmission in the idle symbols, such as Fig.10 For example, Fig.10 As shown, the PDSCH for DL ​​transmission (performed by the base station) and corresponding DL reception by the UE is scheduled to use symbols not used for UL transmission in the UL subband in addition to symbols outside the UL subband (e.g., as Fig.10 As shown in , in the time domain, resource A is partially in the UL subband and partially outside the UL subband). For part of the symbols of the UL subband used for PDSCH transmission, a parameter may also be introduced in the DCI of the PDCCH that schedules the PDSCH, and the value of the parameter may be used to notify the UE to receive the PDSCH in the UL subband or not to receive the PDSCH. Alternatively, the base station may use the value of the parameter to notify the UE to ignore the PDSCH transmission in the UL subband time resource. In other words, the UE may consider that a part of the PDSCH transmission located in the UL subband is not transmitted.

[0096] To implement the above Figure 6-9 The implementation of the parameters or indications of dynamic DCI scheduling described herein is applicable to the scheduling of DL transmission / reception in the UL subband. Figure 6-9 And the embodiments described regarding the UE's ability to support such dynamic scheduling, reporting of UE capabilities, and operations of the UE and the base station based on such reporting may be applied herein to dynamic scheduling of DL transmission / reception in a UL subband.

[0097] As just one example, the parameters related to dynamic scheduling may be configured for the UE via high-layer signaling (such as RRC signaling or MAC CE signaling). Once the RRC configures the parameter to exist for the UE, the parameter may be included in the DCI for scheduling DL transmissions that overlap with the UL subband in time, otherwise the parameter is not included in the DCI scheduling.

[0098] As just another example, in order to better support dynamic scheduling of DL transmission / reception in UL sub-band time resources, corresponding UE capabilities may be introduced. If the UE reports to the base station that it supports the capability, i.e., the UE can perform the above-mentioned DL reception, the base station may schedule / configure the UE to partially perform the operation of dynamic DL reception in the UL sub-band time resources. Otherwise, the base station prohibits scheduling / configuring the UE to perform such an operation. For example, if the UE does not report the capability or reports that it does not have such capability, the base station will prohibit scheduling PDSCH to use the resources of the UL sub-band.

[0099] To avoid interference of DL transmission to UL transmission, the following restrictions may be optionally adopted: Figure 5 In the UL subband, in symbols #9 and #10, a PDSCH is scheduled in the resources of the UL subband, and then UL transmission is prohibited for the remaining frequency domain resources in symbols #9 and #10 in the UL subband. That is, within the resources of one UL subband, even if DL reception and UL transmission are for different UEs, DL reception and UL transmission cannot be scheduled at the same time.

[0100] Similar to the above Figure 6-9 In order to avoid / reduce interference of DL transmissions on UL transmissions, some scheduling restrictions may be adopted. Fig.10 In the example, in symbols #9 and #10, one PDSCH is scheduled in the resources of the UL subband, and then for the remaining frequency domain resources in symbols #9 and #10 in the UL subband, UL transmission may be prohibited (so as to reduce DL and UL interference to the UL subband in frequency). That is, within the resources of one UL subband, DL reception and UL transmission may not be scheduled at the same time even when DL reception and UL transmission are for different UEs, respectively.

[0101] UL sub-band configuration

[0102] In some embodiments, in addition to configuring the time-frequency resources of the UL subband for the UE (for example, configuring some OFDM symbols in the time domain and some continuous RBs in the frequency domain for the UL subband), the base station can also configure some flexible resources within the resource range of the UL subband in the time domain or the frequency domain, or in both the time domain and the frequency domain. The flexible resource here is just a name. It is actually a resource located in the UL subband. Its flexibility and particularity lies in that if necessary, even if it is part of the UL subband, the resource allows the resource to be used for DL ​​transmission (obviously, it can also be used for UL transmission because it belongs to the UL subband). For example, in the time domain, a part of the OFDM symbol within the resource range of the UL subband can be configured as a flexible resource. For another example, in the frequency domain, a part of the RB within the UL subband can be configured as a flexible resource. Within the time-frequency resource range of the UL subband, the transmission direction of the flexible resource can then be determined based on the transmission direction configured or scheduled by the base station.

[0103] The above method is similar to the configuration of flexible symbols in the time slot structure. The configuration of the base station can be performed semi-statically or dynamically. If dynamically configured by the base station, these flexible resources within the UL subband can help balance the resources used for DL ​​transmission and UL transmission in real time.

[0104] In the context of an originally configured DL time slot with a semi-statically configured UL subband, an example time slot structure configured based on the above UL subband configuration is as follows Fig.11 As shown in Figure 1, all symbols are initially configured as DL symbols. Fig.11 FIG. 4 shows an exemplary new time slot structure according to the above embodiment, in which the UL subband of the SBFD UE is configured with flexible resources. Fig.11 In the example, the 3rd DL symbol to the 14th DL symbol are configured for the UL subband of the SBFD UE in the time domain, and several consecutive RBs are configured for the UL subband in the frequency domain. The base station can also configure the 11th symbol to the 14th symbol in the time domain resources within the UL subband and within the entire frequency resource range of the UL subband as flexible resources for the UL subband. In this way, in the time-frequency domain of the UL subband, these flexible resources can be used according to the direction of the transmission scheduled / configured by the base station on these flexible resources. The base station and the UE can therefore be scheduled to use the flexible resources in the UL subband to perform DL reception (by the UE) or UL transmission (from the UE) in the new time slot structure.

[0105] Fig.12 and 13 Other example slot structures are shown in which the UL subband is configured by the base station using flexible resources within the UL subband. The UL subband is configured by the base station using flexible resources within the UL subband. Fig.12 and 13 The example in is similar to Fig.11 , except that the slots shown are initially configured as flexible slots (with all flexible symbols) and mixed slots with mixed DL symbols and flexible symbols. The number of flexible symbols within the UL subband can be determined based on Figure 11-13 In addition, for all graphs in Figure 11-13 In all figures in FIG, if the flexible symbols within a UL subband and the UL symbols within a UL subband need to be interleaved, the base station can configure the time slot structure in this way.

[0106] exist Fig.14 In the example shown, the flexible resources within the UL subband are configured in the frequency domain rather than the time domain. In other words, multiple RBs of the UL subband can be configured as flexible RBs. Fig.14 Specifically, the base station can configure a new time slot structure. Fig.14 In the time-frequency domain of the UL subband, the time slot is initially configured as a DL time slot containing all DL symbols. In the time domain, the 3rd DL symbol to the 14th DL symbol are configured for the UL subband of the SBFD UE, and several consecutive RBs are configured for the UL subband in the frequency domain. Then, the base station can also configure some RBs in the frequency domain resources of the UL subband and on all symbols of the UL subband in the time domain as flexible resources in the UL subband. In this way, in the time-frequency domain of the UL subband, these flexible resources can be used according to the transmission direction scheduled / configured by the base station in the flexible resources. The base station and the UE can perform DL or UL transmission in the flexible resources within the UL subband of the new time slot structure.

[0107] Fig.15 and Fig.16 Other example slot structures are shown in which the UL subband is configured by the base station using flexible frequency resources within the UL subband. Fig.12 and 13 The example in is similar to Fig.14 The example is shown in Figure 1, except that the slots shown are initially configured as flexible slots (with all flexible symbols) and mixed slots with mixed DL symbols and flexible symbols. The number of flexible RB resources within the UL subband can be based on Figure 14-16 In addition, for all graphs in Figure 14-16 In all figures in FIG, if the flexible band of RBs within a UL subband and the UL symbols within a UL subband need to be interleaved, the base station may configure the slot structure in this way.

[0108] Example configuration implementations performed by the base station and the UE are further described below, including: The base station may configure the UL subband for the UE based on RRC signaling. As described above, the base station may also configure flexible resources of the UL subband for the UE simultaneously or subsequently within the time-frequency resources of the UL subband based on, for example, RRC signaling, MAC CE signaling, DCI signaling, etc. The base station may schedule / configure UL reception or DL ​​transmission on the flexible resources within the UL subband for UEs with corresponding capabilities.

[0109] On the UE side, the UE receives RRC signaling for configuring the UL subband from the base station to obtain the UL subband. The UE simultaneously or subsequently receives signaling for configuring flexible resources within the UL subband from the base station and obtains the UL subband with flexible resources. The UE can then receive scheduling / configuration signaling from the base station and perform UL transmission or DL ​​reception within the UL subband on the flexible resources.

[0110] In some further embodiments, regarding scheduling of UL transmission or DL ​​reception in a UL subband with flexible resources, Figure 6-10 The basic principles of apply and can be combined, for example, in terms of DCI design, UL transmission and DL reception, adaptive modifications are sufficient.

[0111] In addition, in order to simplify UE design and support UL subbands with flexible resources, corresponding UE capabilities are introduced. If the UE reports this capability, the base station can configure UL subbands with flexible resources for the UE and allow scheduling of UL transmission or DL ​​reception in the UL subband. Otherwise, if the UE does not report this capability or explicitly reports that it does not have this capability, the base station will prohibit configuring UL subbands with flexible resources for the UE.

[0112] Example 4

[0113] Allowing DL reception in the UL subband can help to dynamically balance DL and UL resources. However, when DL reception is allowed in the UL subband, such DL reception may overlap in the time domain with other possible UL transmissions in the UL subband. Even though such DL reception and UL transmission may be on different RBs, they may need to be avoided in order not to complicate the air interface design. In addition, some DL receptions may be scheduled or configured outside the UL subband and may potentially overlap in time with DL reception or UL transmission in the UL subband. For the same reasons mentioned above, this situation may need to be avoided. Therefore, it may be necessary to specify some predefined options and rules to avoid these overlapping transmissions / receptions and to select transmission or reception when a conflict occurs.

[0114] Generally, the UL transmission in this article includes but is not limited to semi-statically configured PUSCH / PUCCH and dynamically scheduled PUSCH / PUCCH. Similarly, the DL reception in this article includes but is not limited to semi-statically configured SPS PDSCH / CSI-RS / DLPRS, and dynamically scheduled PDSCH / CSI-RS / DL PRS.

[0115] Option 1: Prioritize UL subbands

[0116] In some example embodiments, the base station may configure priorities or priorities for the UL subbands of the UE. The above conflicts may then be resolved based on the various priorities.

[0117] For example, for DL ​​reception, if its priority is higher than that of the UL subband, the base station may be allowed to schedule or configure DL reception in the UL subband. Otherwise, scheduling or configuring DL reception in the UL subband may be prohibited.

[0118] Likewise, under this rule, if predefined, if the priority of DL reception is lower than or equal to the priority of the UL subband, the UE will not expect to schedule or configure DL reception within the UL subband. In this case, the UE will not receive / process the DL reception. Also under this rule, if DL reception is scheduled or configured within the UL subband, the base station should ensure that such DL reception has a higher priority than the priority of the UL subband.

[0119] In some example embodiments, the priority of the UL subband configured by the base station above may not be considered valid for UL transmission. In other words, even if the priority of the UL transmission is different from the priority of the UL subband, the UL transmission may always be scheduled or configured within the UL subband. When scheduling / configuring UL transmission in the UL subband, the base station may ignore the UL subband priority.

[0120] In some further example embodiments, within a UL subband, if DL reception and UL transmission overlap in the time domain, higher priority channels / signals may continue to be retained and transmitted, while lower priority channels / signals are discarded for transmission / reception. Within a UL subband, the UE will not expect DL reception and UL transmission of the same priority to overlap in the time domain. Thus, the base station should ensure that during the scheduling process, DL reception and UL transmission of the same priority within a UL subband do not overlap in the time domain.

[0121] Option 2 - Absolute Priority and Equal Priority Solutions

[0122] In some example embodiments, the base station and the UE may reach an agreement based on a pre-established rule that if there is a time domain overlap between DL receptions of the same priority, between DL receptions and UL transmissions of the same priority, or between UL transmissions of the same priority, then the DL reception or UL transmission in the UL subband is retained and the DL reception or UL transmission outside the UL subband is discarded.

[0123] Within the UL sub-band, the UE will accordingly not expect DL reception and UL transmission of the same priority to overlap in the time domain. Therefore, the base station should ensure that DL reception and UL transmission with the same priority within the UL sub-band do not overlap in the time domain.

[0124] In some other example embodiments, DL reception and UL transmission with the same priority in the UL subband overlap in the time domain, and the base station and the UE may agree that the UL transmission is always retained, while the DL reception is discarded, because the UL transmission should be preferentially transmitted in the UL subband. In some other example embodiments, DL reception and UL transmission with the same priority in the UL subband overlap in the time domain, and if, for example, the base station and the UE agree that the DL reception is scheduled within the UL subband only in an emergency, the base station and the UE may agree that the DL reception is always retained, while the UL transmission is discarded, so that the DL reception should be preferentially transmitted.

[0125] If channels / signals (DL reception / UL transmission) of different priorities overlap in the time domain, whether they are in the UL subband or not, the higher priority channel or signal may be retained and transmitted, while the lower priority channel and signal transmission is discarded.

[0126] Option 3 - No time overlap is allowed between DG PDSCH and DG PUSCH / PUCCH in the UL subband

[0127] In some example embodiments, within a UL subband, if the dynamic PDSCH (DL transmission) scheduled by PDCCH (denoted as DG PDSCH) and the dynamic PUSCH / PUCCH (UL transmission) scheduled by PDCCH (denoted as DGPUSCH / PUCCH) overlap in the time domain, the following rules may be predefined and considered.

[0128] For example, if DG PDSCH is allowed to be transmitted in a UL subband, the base station and the UE may agree according to a predefined rule that the base station always ensures that DG PDSCH and DG PUSCH / PUCCH do not overlap in the UL subband in the time domain. Otherwise, if DGPDSCH or DG PUSCH / PUCCH is scheduled in a certain time domain resource in the UL subband, DG PUSCH / PUCCH or DGPDSCH cannot be scheduled in that time domain resource to avoid their time domain overlap. From the UE's perspective, the UE will not expect a DG PDSCH and a DG PUSCH / PUCCH to overlap in the time domain within the UL subband. If they overlap in the time domain, the UE does not process them and regards this situation as a base station scheduling error. Option 4 - DG PDSCH and DGPUSCH / PUCCH in UL subband: time-based scheduling

[0129] In some example embodiments, in a UL subband, if a DG PDSCH scheduled by a PDCCH and a DG PUSCH / PUCCH scheduled by a PDCCH overlap in the time domain and if they have the same priority, one of the following rules may be predefined and implemented.

[0130] Rule 1

[0131] If DG PDSCH is scheduled by PDCCH1 and DG PUSCH / PUCCH is scheduled by PDCCH2, and DG PDSCH and DG PUSCH / PUCCH overlap in the time domain in the UL subband, the DG PDSCH or DG PUSCH / PUCCH corresponding to the PDCCH with a later start (or end) symbol between PDCCH1 and PDCCH2 is retained for transmission, while the DG PDSCH or DG PUSCH / PUCCH corresponding to the PDCCH with an earlier start (or end) symbol is discarded.

[0132] For example, if the start (or end) symbol of PDCCH1 is later than the start (or end) symbol of PDCCH2, DG PUSCH / PUCCH is retained and DG PDSCH is discarded. If the start (or end) symbol of PDCCH2 is later than the start (or end) symbol of PDCCH1, DG PUSCH / PUCCH is retained and DG PDSCH is discarded.

[0133] Rule 2

[0134] Contrary to Rule 1 above, if DG PDSCH is scheduled by PDCCH1 and DG PUSCH / PUCCH is scheduled by PDCCH2, and DG PDSCH and DG PUSCH / PUCCH overlap in the time domain in the UL subband, the DG PDSCH or DG PUSCH / PUCCH corresponding to the PDCCH with an earlier start (or end) symbol between PDCCH1 and PDCCH2 is retained, and the DG PDSCH or DG PUSCH / PUCCH corresponding to the PDCCH with a later start (or end) symbol is discarded.

[0135] For example, if the start (or end) symbol of PDCCH1 is earlier than the start (or end) symbol of PDCCH2, DG PUSCH / PUCCH is reserved for transmission and DG PDSCH is discarded. If the start (or end) symbol of PDCCH2 is earlier than the start (or end) symbol of PDCCH1, DG PUSCH / PUCCH is reserved for transmission and DG PDSCH is discarded.

[0136] Rule 3

[0137] If DG PDSCH is scheduled by PDCCH1 and DG PUSCH / PUCCH is scheduled by PDCCH2, and DG PDSCH and DGPUSCH / PUCCH overlap in the time domain in the UL subband, and one of them has multiple repetition transmissions, the channel with repetition transmissions is reserved for transmission, and the channel without repetition transmissions is discarded.

[0138] For example, if DG PDSCH is scheduled to have repeated transmission and DG PUSCH / PUCCH is scheduled to have no repeated transmission, DG PDSCH is retained and DG PUSCH / PUCCH is discarded. For another example, if DG PDSCH is scheduled to have no repeated transmission and DG PUSCH / PUCCH is scheduled to have repeated transmission, DG PUSCH / PUCCH is retained and DG PDSCH is discarded.

[0139] Rule 4

[0140] If DG PDSCH is scheduled by PDCCH1 and DG PUSCH / PUCCH is scheduled by PDCCH2, and DG PDSCH and DG PUSCH / PUCCH overlap in the time domain in the UL subband, and they both have multiple repeated transmissions, the above Rule 1 or Rule 2 can be used to determine which one of them is retained and which one is discarded.

[0141] Option 5 - DG PDSCH and CG PUSCH / PUCCH in UL subband: time-based or assumed priority scheduling

[0142] In some example embodiments, in a UL subband, if the DG PDSCH scheduled by the PDCCH and the semi-static / configured granted PUSCH / PUCCH (denoted as CG PUSCH / PUCCH) overlap in the time domain, and if they have the same priority, one of the following rules may be predefined and considered.

[0143] Rule 5

[0144] If there is at least T duration between the end of the end symbol of the PDCCH corresponding to the DG PDSCH and the start of the start symbol of the CG PUSCH / PUCCH, the DG PDSCH is retained and transmitted, and the CG PUSCH / PUCCH is discarded. Otherwise, the CG PUSCH / PUCCH is retained and transmitted, and the DG PDSCH is discarded. Here, the start of the T duration starts from the end of the end symbol of the PDCCH.

[0145] Here, the duration of T may be defined as follows: T may be defined based on N1 in the existing protocol TS 38.213, or may be defined based on N2 in the existing protocol TS 38.213, or may be defined as 14 symbols.

[0146] Rule 6

[0147] In some implementations, the CG PUSCH / PUCCH is always reserved and transmitted, and the DG PDSCH is dropped. In other words, when they overlap in the time domain in the UL subband, a higher priority can be given to the UL transmission.

[0148] Option 6 - SPS PDSCH and DG PUSCH / PUCCH in UL subband: time-based or assumed priority scheduling

[0149] In some example embodiments, in a UL subband, if a semi-static PDSCH (denoted as SPS PDSCH) and a dynamic PUSCH / PUCCH (denoted as DG PUSCH / PUCCH) scheduled by a PDCCH overlap in the time domain, and if they have the same priority, one of the following rules may be predefined and considered.

[0150] Rule 7

[0151] If there is at least Q duration between the end of the end symbol of the PDCCH corresponding to the DG PUSCH / PUCCH and the start of the start symbol of the SPS PDSCH, the DG PUSCH / PUCCH is retained and transmitted, and the SPS PDSCH is discarded; otherwise, the SPS PDSCH is retained and transmitted. The DG PUSCH / PUCCH is discarded. Here, the start of the Q duration starts from the end of the end symbol of the PDCCH.

[0152] Here, the Q duration may be defined as follows: Q may be defined based on N1 in the existing protocol TS 38.213, or may be defined based on N2 in the existing protocol TS 38.213, or may be defined as 14 symbols.

[0153] Rule 8

[0154] In some example embodiments, DG PUSCH / PUCCH is always reserved and transmitted, and SPS PDSCH is discarded. Since their time domains overlap in the UL subband, UL transmission can be given a higher priority. In other words, if the resources of DG PUSCH / PUCCH and SPS PDSCH scheduled / configured by the base station for the SBFD UE overlap in the time domain in the UL subband, the base station considers that the UE transmits DG PUSCH / PUCCH, so the base station does not transmit SPS PDSCH. If the UE finds that the resources of DG PUSCH / PUCCH and SPS PDSCH overlap in the time domain of the UL subband, the UE transmits DG PUSCH / PUCCH, and the UE does not receive SPS PDSCH under this rule.

[0155] Option 7 - SPS PDSCH and CG PUSCH / PUCCH in UL subband

[0156] In some example embodiments, in a UL subband, if the SPS PDSCH and the CG PUSCH / PUCCH overlap in the time domain, and if they have the same priority, one of the following rules may be predefined and considered.

[0157] Rule 9

[0158] Under this example rule, CG PUSCH / PUCCH is always retained and transmitted, and SPS PDSCH is discarded. Because their time domains overlap in the UL subband, and UL transmission can be given a higher priority. In other words, if the resources of CG PUSCH / PUCCH and SPS PDSCH configured by the base station for the SBFD UE overlap in the time domain in the UL subband, then under this rule, the base station can consider that the UE transmits CG PUSCH / PUCCH, so the base station does not transmit SPS PDSCH. Under this example rule, the UE can find that the resources of CG PUSCH / PUCCH and SPS PDSCH overlap in the time domain of the UL subband, and then the UE transmits CG PUSCH / PUCCH, and the UE does not receive SPS PDSCH.

[0159] Rule 10

[0160] The UE does not expect the CG PUSCH / PUCCH and SPS PDSCH to overlap in the time domain of the UL subband. That is, the base station configures the CG PUSCH / PUCCH and SPS PDSCH for the SBFD UE, and the base station shall ensure that the resources of the CG PUSCH / PUCCH and SPS PDSCH in the UL subband do not overlap in the time domain. Under this rule, if the UE finds that the resources of the CG PUSCH / PUCCH and SPS PDSCH in the UL subband overlap in the time domain, the UE does not perform any reception and transmission.

[0161] Transmission of DL reference signals in UL subbands

[0162] In some example embodiments, it may be allowed to transmit a downlink reference signal (such as a general DL transmission) within the resources of the UL subband. The downlink reference signal here includes, but is not limited to, a reference signal for channel measurement (e.g., a semi-static CSI-RS (channel state information reference signal) or a CSI-RS triggered based on a PDCCH) or a reference signal for positioning (e.g., a DL PRS). If the reference signal is configured to use the resources of the UL subband (e.g., symbols in the UL subband) for link transmission, the UE and the base station may consider one of the following embodiments, in which the resources of the UL subband used for transmitting the reference signal are represented as resource B.

[0163] 1) When the reference signal is used for a UE with SBFD capability:

[0164] In some example embodiments, the reference signal is always sent on resource B. If the UL transmission of the SBFD UE is scheduled / configured to include resource B, the SBFD UE should be instructed to perform rate matching on resource B. In other words, the UL transmission is punctured in resource B, i.e., the UL transmission skips resource B. Specifically, the UE uses UL subband resources other than resource B for UL transmission.

[0165] In some alternative example embodiments, if no UL transmission of any SBFD UE is scheduled / configured to include resource B, the reference signal is transmitted in resource B. Otherwise, the base station does not transmit the reference signal in resource B. The base station should indicate to the UE via signaling whether the reference signal is transmitted on resource B to the SBFD UE.

[0166] In some other alternative example embodiments, the base station explicitly signals to the UE whether resource B is used for reference signal or UL transmission. The UE determines whether resource B is used for reference signal or UL transmission accordingly according to the signaling of the base station. The signaling may be RRC signaling / MAC CE, or the signaling may be DCI signaling (e.g., in the DCI scheduling UL transmission).

[0167] In some other alternative implementations, when the UE requests a reference signal, the UE may simultaneously inform the base station whether the reference signal is to be transmitted in resource B. For example, when the UE needs to request a reference signal, the UE sends a request signaling to the base station, and at the same time informs the base station in the request signaling (if the resource B is known) that resource B will be used for UL transmission, or resource B is used to receive a reference signal.

[0168] ·In some other alternative embodiments, if the SBFD UE's DL PDSCH reception is scheduled / configured in resource C, and resource C contains resource B, and the DL PDSCH reception is determined to be received from the UE (i.e., the base station determines that the DL PDSCH is transmitted in resource B), the UE then considers that the reference signal is transmitted in resource B, but the DL PDSCH reception is transmitted in resource C other than resource B (skipping resource B).

[0169] 2) Reference signals are used for legacy UEs (or UEs without SBFD capability):

[0170] In some embodiments, the reference signal is always sent on resource B so that legacy UEs will receive the reference signal. If the UL transmission of a SBFD UE is scheduled / configured to include resource B, the SBFD-capable UE should perform rate matching on that resource B. The SBFD UE always performs rate matching on resource B, or the SBFD UE is signaled whether to perform rate matching on resource B. Solve the overlap problem of NACK-only PUCCH with different priorities in the time domain

[0171] In some embodiments, the network can configure the priority of the physical channel for the UE. When a first physical channel with a higher priority overlaps with a second physical channel with a lower priority in the time domain, the first physical channel can cancel the second physical channel. This means that the UE can discard (or cancel) the second physical channel transmission and only transmit the first physical channel. Alternatively, the UE can discard the information of the second physical channel, or the information of the second physical channel may not be multiplexed in the first physical channel.

[0172] The network may configure a NACK-only feedback mode for the UE. The configured NACK-only feedback mode may be applied to the physical downlink shared channel (PDSCH). For the PDSCH, the network may configure or indicate a NACK-only physical uplink control channel (PUCCH). When the UE correctly decodes the PDSCH, the UE may not send a NACK-only PUCCH. When the UE does not correctly decode the PDSCH, the UE may send a NACK-only PUCCH.

[0173] The first NACK-only PUCCH may correspond to the first group of PDSCHs. The first group of PDSCHs may include one or more PDSCHs. The first NACK-only PUCCH with a higher priority overlaps with a second physical channel with a lower priority in the time domain. In some embodiments, the first NACK-only PUCCH with a higher priority may cancel the second physical channel with a lower priority. This means that regardless of the decoding result of the first group of PDSCHs, the UE may discard (or cancel) the second physical channel transmission. More specifically, even if the UE correctly decodes the first group of PDSCHs, the UE may discard (or cancel) the second physical channel. When the UE correctly decodes the first group of PDSCHs, the UE may not send the first NACK-only PUCCH, or the UE may not send anything. The UE may determine the PUCCH resources based solely on the decoding result of the first group of PDSCHs.

[0174] In some embodiments, the first NACK-only PUCCH with a higher priority may not cancel the second physical channel with a lower priority. In addition, when the UE correctly decodes the first set of PDSCHs, the first NACK-only PUCCH with a higher priority may not cancel the second physical channel with a lower priority. This means that when the UE correctly decodes the first set of PDSCHs, the UE can send the second physical channel.

[0175] The second NACK-only PUCCH may correspond to the second group PDSCH. The second group PDSCH may include one or more PDSCHs. The first NACK-only PUCCH with a higher priority overlaps with the second NACK-only PUCCH with a lower priority in the time domain. The first NACK-only PUCCH with a higher priority may not cancel the second NACK-only PUCCH with a lower priority. The UE may determine the PUCCH resources based on the decoding results of the first group PDSCH and the second group PDSCH.

[0176] In addition, when the UE correctly decodes the first group of PDSCHs, the first PUCCH with a higher priority and containing only NACK may not cancel the second PUCCH with a lower priority and containing only NACK. When the UE does not decode at least one of the first group of PDSCHs, the UE may send the first NACK-only PUCCH. When the UE correctly decodes the first group of PDSCHs and does not decode at least one of the second group of PDSCHs, the UE may send the second NACK-only PUCCH. When the UE correctly decodes the first group of PDSCHs and correctly decodes the second group of PDSCHs, the UE may not send the first NACK-only PUCCH or the second NACK-only PUCCH.

[0177] Through the embodiments, the UE may avoid unnecessary discarding or cancellation, and thus may improve spectrum efficiency.

[0178] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter may be embodied in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be interpreted as not being limited to any exemplary embodiment set forth herein. It is intended to provide a reasonably broad scope for the subject matter claimed or covered. Among other things, for example, the subject matter may be embodied as a method, device, component, system, or non-transitory computer-readable medium for storing computer code. Therefore, the embodiment may, for example, take the form of hardware, software, firmware, storage media, or any combination thereof. For example, the above method embodiment may be implemented by a component, device, or system including a memory and a processor by executing a computer code stored in the memory.

[0179] Throughout the specification and claims, in addition to the meanings explicitly stated, terms may have slightly different meanings that are suggested or implied in the context. Likewise, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, it is intended that the claimed subject matter includes all or part of the combination of the example embodiments.

[0180] In general, terms can be understood at least in part from the usage in the context. For example, terms used in this article, such as "and", "or", or "and / or", can include multiple meanings, which can depend at least in part on the context in which these terms are used. Typically, "or", if used to associate a list, such as A, B, or C, is intended to represent A, B, and C used here for inclusion, and A, B, or C used here only for exclusion. In addition, the term "one or more" used in this article, at least in part depending on the context, can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, and characteristics in a plural sense. Similarly, terms such as "one", "an", or "the" can be understood to convey singular usage or to convey plural usage, which depends at least in part on the context. In addition, the term "based on" can be understood to not necessarily be intended to convey a set of exclusive factors, but can allow the presence of additional factors that are not necessarily explicitly described, again, at least in part depending on the context.

[0181] References to features, advantages, or similar language in this specification do not mean that all features and advantages that may be realized by the present solution should be included or included in any single embodiment thereof. Rather, language referring to features and advantages is understood to mean that a particular feature, advantage, or characteristic described in conjunction with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of features and advantages and similar language throughout the specification may, but do not necessarily, refer to the same embodiment.

[0182] Furthermore, the features, advantages, and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One of ordinary skill in the relevant art will recognize, based on the description herein, that the present solution may be practiced without one or more of the particular features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.

Claims

1. A method performed by a wireless access network node, comprising: configuring the first group of time-frequency resources as downlink time-frequency resources or direction-flexible time-frequency resources to a user equipment UE; as well as An uplink subband for uplink transmission is configured for the UE, the uplink subband occupying consecutive resource blocks in frequency and a group of symbols in time within the first set of time-frequency resources.

2. The method according to claim 1 also includes scheduling a second set of time-frequency resources for uplink transmission for the UE, and the second set of time-frequency resources is partially within the uplink subband and partially outside the uplink subband in time.

3. The method according to claim 2, wherein: The configuration of the uplink subband is performed by the radio access network node through semi-static radio resource control RRC signaling or a medium access control MAC control element CE.

4. The method according to claim 3, wherein: A portion of the second set of time-frequency resources outside the uplink subband is implemented as a time domain adjustment of the uplink subband.

5. The method according to claim 4, wherein: The time domain adjustment of the uplink subband is valid only during the scheduling of the second set of time-frequency resources for the uplink transmission, or before the next time domain adjustment of the uplink subband, or within a predetermined or configured time period after the scheduling of the second set of time-frequency resources for the uplink transmission.

6. The method according to claim 3, wherein: The scheduling of the second set of time-frequency resources is performed by the radio access network node through a downlink control information DCI message.

7. The method according to claim 6, wherein: Configuring the uplink subband is performed in response to the radio access network node receiving a capability report from the UE, the capability report indicating that the UE supports subband full-duplex (SBFD) or that the UE supports using the second set of time-frequency resources for the uplink transmission.

8. The method according to claim 6, wherein: The DCI message includes one or more parameters indicating to the UE the time and frequency locations of the second set of time-frequency resources.

9. The method according to claim 6, wherein: The DCI message includes an indication indicating to the UE that the uplink subband is to be extended according to the second set of time-frequency resources.

10. The method according to claim 2, wherein: The radio access network node is prohibited from further scheduling any resources that are quasi-co-located in time with a portion of the second set of time-frequency resources outside the uplink sub-band and within a frequency resource range of the uplink sub-band.

11. The method according to claim 1, wherein: configuring flexible resources for the uplink subband in the time-frequency resources of the uplink subband through signaling; or It is allowed to configure a part of the time-frequency resources of the uplink subband as flexible resources through signaling.

12. The method according to claim 11, wherein: A transmission direction of the flexible resources is determined based on a direction of transmission scheduled in the flexible resources.

13. The method according to claim 12, wherein: The flexible resources configured in the uplink subband include one or more OFDM symbols across an entire frequency range of the uplink subband.

14. The method according to claim 12, wherein: The flexible resources configured in the uplink subband include one or more frequency resource blocks spanning an entire OFDM symbol range of the uplink subband.

15. The method according to claim 11, wherein: The signaling includes RRC signaling.

16. The method according to claim 11, wherein: The flexible resources are configured in response to the radio access network node receiving a capability report from the UE, the capability report indicating that the UE supports sub-band full-duplex (SBFD) or that the UE supports flexible resources in an uplink sub-band.

17. A method performed by a wireless access network node, comprising: configuring the first group of time-frequency resources as downlink time-frequency resources or direction-flexible time-frequency resources to a user equipment UE; configuring an uplink subband for uplink transmission for the UE, the uplink subband occupying consecutive resource blocks in frequency and a group of OFDM symbols in time within the first set of time-frequency resources; as well as Downlink transmissions are transmitted in the configured uplink subbands.

18. The method according to claim 17, wherein: Transmitting the downlink transmission in the configured uplink subband includes generating signaling to the UE to schedule the downlink transmission in at least a portion of the uplink subband.

19. The method according to claim 18, wherein: The at least one portion of the uplink subband does not correspond to other portions of the uplink subband overlapping with the at least one portion of the uplink subband and other portions of the uplink subband scheduled for uplink transmission.

20. The method according to claim 18, wherein: When scheduling the downlink transmission, the signaling is included in a DCI to the UE.

21. The method according to claim 20, wherein: The radio access network node is prohibited from further scheduling uplink transmissions on a second set of time-frequency resources that temporally overlap with the at least a portion of the configured uplink subband and are within a frequency resource range of the configured uplink subband.

22. The method of claim 17, further comprising configuring a first priority of the uplink subband, the first priority being used as a basis for determining whether to allow scheduling of downlink transmission in the uplink subband.

23. The method of claim 22, wherein: If the first priority of the uplink subband is lower than a second priority associated with the downlink transmission, allowing the downlink transmission; and If the first priority of the uplink subband is higher than a second priority associated with the downlink transmission, the downlink transmission is prohibited.

24. The method according to claim 17 also includes resolving a scheduling conflict between two downlink transmissions of the same priority with time overlap within the uplink subband or a scheduling conflict between a downlink transmission and an uplink transmission by retaining the transmission within the frequency range of the uplink subband and discarding the transmission outside the frequency range of the uplink subband.

25. The method of claim 17, further comprising refraining from scheduling dynamic PDSCH downlink transmissions and dynamic PUSCH / PUCCH by the same PDCCH with overlapping time within the uplink subband.

26. The method according to claim 17 also includes resolving scheduling conflicts between the dynamic PDSCH downlink transmission and the dynamic PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband based on the timing of the corresponding scheduling PDCCHs for the dynamic PDSCH downlink transmission and the dynamic PUSCH / PUCCH uplink transmission.

27. The method according to claim 17 also includes resolving scheduling conflicts between the dynamic PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband based on the OFDM symbol-level time interval between the corresponding scheduling PDCCHs for the dynamic PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission.

28. The method of claim 17, further comprising resolving a scheduling conflict between the dynamic PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband by retaining the semi-static PUSCH / PUCCH uplink transmission and discarding the dynamic PDSCH downlink transmission.

29. The method of claim 17, further comprising resolving a scheduling conflict between the semi-static PDSCH downlink transmission and the dynamic PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband by retaining the dynamic PUSCH / PUCCH uplink transmission and discarding the semi-static PDSCH downlink transmission.

30. The method of claim 17, further comprising resolving a scheduling conflict between the semi-static PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband by retaining the semi-static PUSCH / PUCCH uplink transmission and discarding the semi-static PDSCH downlink transmission.

31. The method of claim 17, wherein: The downlink transmission is configured for transmitting a downlink reference signal in the uplink subband.

32. A method performed by a wireless terminal device, comprising: receiving, from the radio access network node, a configuration of using the first set of time-frequency resources as downlink time-frequency resources or directionally flexible time-frequency resources; and A configuration of uplink subbands for uplink transmission is received from the radio access network node, the uplink subbands occupying consecutive resource blocks in frequency and a group of symbols in time within the first set of time-frequency resources.

33. The method of claim 32, further comprising receiving, from the radio access network node, a schedule of a second set of time-frequency resources for uplink transmission, the second set of time-frequency resources being partially within the uplink subband and partially outside the uplink subband in time.

34. The method of claim 33, wherein: The configuration of the uplink subband is received from the radio access network node through semi-static radio resource control RRC signaling or a medium access control MAC control element CE.

35. The method of claim 34, wherein: A portion of the second set of time-frequency resources outside the uplink subband is implemented as a time domain adjustment of the uplink subband.

36. The method of claim 35, wherein: The time domain adjustment of the uplink subband is valid only during the scheduling of the second set of time-frequency resources for the uplink transmission, or before the next time domain adjustment of the uplink subband, or within a predetermined or configured time period after the scheduling of the second set of time-frequency resources for the uplink transmission.

37. The method of claim 34, wherein: The scheduling of the second set of time-frequency resources is received as a downlink control information (DCI) message from the radio access network node.

38. The method of claim 37, wherein: The configuration of the uplink subband is sent in response to the wireless access network node receiving a capability report from the wireless terminal device, wherein the capability report indicates that the wireless terminal device supports sub-band full-duplex SBFD or the wireless terminal device supports uplink transmission using the second set of time-frequency resources.

39. The method of claim 37, wherein: The DCI message includes one or more parameters indicating the time and frequency locations of the second set of time-frequency resources to the wireless terminal device.

40. The method of claim 37, wherein: The DCI message includes an indication indicating to the wireless terminal device that the uplink subband is to be extended according to the second set of time-frequency resources.

41. The method of claim 33, wherein: The radio access network node is prohibited from further scheduling any resources that are quasi-co-located in time with a portion of the second set of time-frequency resources outside the uplink sub-band and within a frequency resource range of the uplink sub-band.

42. The method of claim 32, wherein: configuring flexible resources for the uplink subband in the time-frequency resources of the uplink subband through signaling from the radio access network node; or It is allowed to configure a part of the time-frequency resources of the uplink subband as flexible resources through signaling.

43. The method of claim 42, wherein: A transmission direction of the flexible resources is determined based on a direction of transmissions scheduled in the flexible resources.

44. The method of claim 43, wherein: The flexible resources configured in the uplink subband include one or more OFDM symbols across an entire frequency range of the uplink subband.

45. The method of claim 43, wherein: The flexible resources configured in the uplink subband include one or more frequency resource blocks spanning an entire OFDM symbol range of the uplink subband.

46. ​​The method of claim 42, wherein: The signaling includes RRC signaling.

47. The method of claim 42, wherein: The flexible resources are configured in response to the radio access network node receiving a capability report from the wireless terminal device, the capability report indicating that the wireless terminal device supports sub-band full-duplex (SBFD) or that the wireless terminal device supports flexible resources in an uplink sub-band.

48. A method performed by a wireless terminal device, comprising: receiving, from the radio access network node, a configuration of using the first set of time-frequency resources as downlink time-frequency resources or directionally flexible time-frequency resources; receiving, from the radio access network node, a configuration of uplink subbands for uplink transmission, the uplink subbands occupying consecutive resource blocks in frequency and a group of OFDM symbols in time within the first set of time-frequency resources; as well as A downlink transmission is received from the radio access network node in the configured uplink subband.

49. The method of claim 48, wherein: Receiving a downlink transmission in the configured uplink subband includes receiving signaling from the radio access network node to schedule downlink transmissions in at least a portion of the uplink subband.

50. The method of claim 49, wherein: The at least one portion of the uplink subband does not correspond to other portions of the uplink subband overlapping with the at least one portion of the uplink subband and other portions of the uplink subband scheduled for uplink transmission.

51. The method of claim 49, wherein: When scheduling the downlink transmission, the signaling is included in a DCI from the radio access network node.

52. The method of claim 51, wherein: The radio access network node is prohibited from further scheduling uplink transmissions on a second set of time-frequency resources that temporally overlap with the at least a portion of the configured uplink subband and are within a frequency resource range of the configured uplink subband.

53. The method of claim 48, further comprising determining a first priority for the uplink subband, the first priority being used as a basis for determining whether to allow scheduling of downlink transmissions in the uplink subband.

54. The method of claim 53, wherein: If the first priority of the uplink subband is lower than a second priority associated with the downlink transmission, allowing the downlink transmission; and If the first priority of the uplink subband is higher than a second priority associated with the downlink transmission, the downlink transmission is prohibited.

55. The method according to claim 48 also includes resolving a scheduling conflict between two downlink transmissions of the same priority with time overlap within the uplink subband or a scheduling conflict between a downlink transmission and an uplink transmission by retaining the transmission within the frequency range of the uplink subband and discarding the transmission outside the frequency range of the uplink subband.

56. The method of claim 48, further comprising refraining from scheduling dynamic PDSCH downlink transmissions and dynamic PUSCH / PUCCH by the same PDCCH with overlapping time within the uplink subband.

57. The method according to claim 48 also includes resolving scheduling conflicts between the dynamic PDSCH downlink transmission and the dynamic PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband based on the timing of the corresponding scheduling PDCCHs for the dynamic PDSCH downlink transmission and the dynamic PUSCH / PUCCH uplink transmission.

58. The method according to claim 48 also includes resolving scheduling conflicts between the dynamic PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband based on the OFDM symbol-level time interval between the corresponding scheduling PDCCHs for the dynamic PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission.

59. The method of claim 48, further comprising resolving a scheduling conflict between the dynamic PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband by retaining the semi-static PUSCH / PUCCH uplink transmission and discarding the dynamic PDSCH downlink transmission.

60. The method of claim 48, further comprising resolving a scheduling conflict between the semi-static PDSCH downlink transmission and the dynamic PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband by retaining the dynamic PUSCH / PUCCH uplink transmission and discarding the semi-static PDSCH downlink transmission.

61. The method of claim 48, further comprising resolving a scheduling conflict between the semi-static PDSCH downlink transmission and the semi-static PUSCH / PUCCH uplink transmission that overlap in time within the uplink subband by retaining the semi-static PUSCH / PUCCH uplink transmission and discarding the semi-static PDSCH downlink transmission.

62. The method of claim 48, wherein: The downlink transmission is configured for transmitting a downlink reference signal in the uplink subband.

63. The radio access network node according to any one of claims 1-62, the radio access network node comprising a memory for storing instructions and a processor for executing the instructions to implement the method according to any one of claims 1-62.

64. A computer-readable non-transitory medium for storing computer instructions, which, when executed by a processor of a radio access network node according to any one of claims 1-62, implement the method according to any one of claims 1-62.

Images