Cross-subband scheduling in full duplex networks

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may receive a bandwidth portion (BWP) configuration that indicates that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received. The UE may receive downlink control information (DCI) in the at least one sub-band, the downlink control information (DCI) including a grant to schedule communications in one or more sub-bands associated with the BWP. Numerous other aspects are provided.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Non-Provisional Patent Application No. 17 / 820,136, filed on August 16, 2022, entitled “CROSS SUB-BAND SCHEDULING IN A FULL-DUPLEX NETWORK” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and more particularly to techniques and apparatus for cross-sub-band scheduling in a full-duplex network. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region or global level. New Radio (NR) (which may be referred to as 5G) is an enhancement set to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful.

[0006] In the case of full-duplex communication, the bandwidth part (BWP) may span more than one sub-band (in some combination of one or more downlink sub-bands and one or more uplink sub-bands). For example, in order to reduce or eliminate delays, it is not desirable to switch or modify the configuration of the BWP during the course of full-duplex communication when transitioning from a half-duplex time slot to a full-duplex time slot. Therefore, in some scenarios, the BWP may span more than one sub-band. However, in some full-duplex scenarios, the power consumption of the UE may be unnecessarily high in these scenarios, where the BWP spans more than one sub-band and the network node schedules the UE in only one sub-band of the BWP (because the UE will still process the entire bandwidth of the BWP). Summary of the invention

[0007] Some aspects described herein relate to a method of performing wireless communications by a user equipment (UE). The method may include receiving a bandwidth part (BWP) configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received. The method may include receiving downlink control information (DCI) in at least one subband, the downlink control information (DCI) including a grant to schedule communications in one or more subbands associated with the BWP.

[0008] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include sending a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be sent. The method may include sending a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include at least one processor and at least one memory communicatively coupled to the at least one processor, the at least one memory storing processor-readable code. The processor-readable code, when executed by the at least one processor, may be configured to cause the UE to receive a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received. The processor-readable code, when executed by the at least one processor, may be configured to cause the UE to receive a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0010] Some aspects described herein relate to a network node for wireless communication. The network node may include at least one processor and at least one memory communicatively coupled to the at least one processor, the at least one memory storing processor readable code. The processor readable code, when executed by the at least one processor, may be configured to cause the network node to send a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one sub-band associated with the BWP in which a grant is to be sent. The processor readable code, when executed by the at least one processor, may be configured to cause the network node to send a DCI in at least one sub-band, the DCI including a grant to schedule communications in one or more sub-bands associated with the BWP.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network node. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be sent. The instruction set, when executed by one or more processors of the network node, may cause the network node to send a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which to receive a grant. The apparatus may include means for receiving a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for sending a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be sent. The apparatus may include means for sending a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices, or processing systems as fully described with reference to the accompanying drawings and the specification and as illustrated in the accompanying drawings and the specification.

[0016] The foregoing has broadly outlined the features and technical advantages of examples according to the present disclosure in an effort to make the following specific embodiments better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the following description. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to fully understand the above features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate some typical aspects of the present disclosure and should not be considered to limit its scope, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2 is a diagram illustrating an example network node communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0021] Figure 4 is a diagram illustrating an example of full-duplex communication in a wireless network according to the present disclosure.

[0022] FIG. 5A to FIG. 5C is a diagram illustrating an example associated with cross-sub-band scheduling in a full-duplex network according to various aspects of the present disclosure.

[0023] Figure 6 is a flow chart illustrating an example process performed, for example, by a UE supporting cross-sub-band scheduling in a full-duplex network according to the present disclosure.

[0024] Figure 7 is a flow chart illustrating an example process performed, for example, by a network node supporting cross-sub-band scheduling in a full-duplex network in accordance with the present disclosure.

[0025] Figure 8 is a diagram of an example apparatus for wireless communication supporting cross-sub-band scheduling in a full-duplex network according to the present disclosure.

[0026] Fig. 9 is a diagram of an example apparatus for wireless communication supporting cross-sub-band scheduling in a full-duplex network according to the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function given throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It will be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is independently or in combination with any other aspect of the present disclosure. For example, the aspect of any amount set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method that is practiced using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. Any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Various aspects generally relate to cross-subband scheduling in a full-duplex network. As used herein, cross-subband scheduling refers to scheduling a UE to communicate in one or more subbands associated with a bandwidth part (BWP) (e.g., scheduling the UE in a first subband associated with the BWP, a second subband associated with the BWP, or both the first subband and the second subband), wherein the communication may be scheduled based on scheduling information (e.g., downlink control information (DCI)) received on any of the one or more subbands. Some aspects more specifically relate to BWP configuration of a BWP for supporting cross-subband scheduling in a full-duplex network, and dynamic adaptation of the BWP configuration. In some aspects, a network node may send and a UE may receive a BWP configuration indicating that the BWP is configured with cross-subband scheduling, wherein the BWP configuration indicates at least one subband associated with the BWP in which a grant is to be communicated. In some aspects, a network node may send, and a UE may receive, a DCI including a grant to schedule communications in one or more subbands associated with a BWP, wherein the DCI is sent and received in at least one subband indicated by the BWP configuration.

[0030] Certain aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques may be used to reduce the power consumption of the UE by eliminating the need for the UE to process the entire bandwidth of the BWP while enabling the UE to be scheduled for communication in one or more sub-bands of the entire bandwidth. In addition, in some examples, the described techniques may reduce buffering at the UE, thereby reducing power consumption and saving memory and processing resources. In addition, in some examples, the described techniques may improve the decoding reliability of the physical downlink control channel (PDCCH) carrying the DCI by enabling the frequency domain resource allocation (FDRA) field of the DCI to carry redundant bits. For example, if the UE is scheduled only in a single sub-band associated with the BWP, some bits of the FDRA field will indicate the FDRA associated with the single sub-band. However, other bits of the FDRA (i.e., bits that would otherwise be used to indicate the FDRA associated with one or more other sub-bands associated with the BWP) may instead carry redundant bits associated with the single sub-band, thereby improving decoding reliability.

[0031] Figure 11 is a diagram illustrating an example of a wireless network according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other network entities. The network node 110 is an entity that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). For another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0032] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, or one or more DUs. For example, the network node 110 may include an NR network node, an LTE network node, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul interfaces, midhaul interfaces, or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks) using any suitable transport network.

[0033] Each network node 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a network node 110 or a network node subsystem serving the coverage area, depending on the context in which the term is used.

[0034] The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or a home network node.

[0035] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts). Figure 1 In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0036] In some aspects, the term "base station" or "network node" may refer to a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with the network node 110). In some aspects, the term "base station" or "network node" may refer to a plurality of devices configured to perform one or more functions. For example, in some distributed systems, each of a number of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeat the execution of at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions but not another base station function. In this way, a single device may include more than one base station.

[0037] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul communication link or a wired backhaul communication link. In some aspects, the network controller 130 may be a CU or a core network device, or the network controller 130 may include a CU or a core network device.

[0038] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile network nodes 110 (e.g., mobile network nodes). In some examples, the network nodes 110 may be interconnected with each other or to one or more other network nodes 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0039] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a network node 110 or a UE 120) and transmit the data transmissions to a downstream station (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, network node 110d (e.g., a relay network node) may communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communications between network node 110a and UE 120d. A network node 110 that relays communications may be referred to as a relay station, relay network node, or relay.

[0040] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, a UE function of a network node, or any other suitable device configured to communicate via a wireless medium.

[0041] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, or location tags, which may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0042] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may also be referred to as a radio technology or air interface. Frequency may also be referred to as a carrier or frequency channel. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0043] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0044] Devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes arise in conjunction with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0045] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics or FR2 characteristics, and thus the features of FR1 or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0046] Considering the above examples, unless otherwise specifically stated, if the term "below 6 GHz" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0047] In some aspects, UE 120 may include a communication manager 140. As described in greater detail elsewhere herein, the communication manager 140 may receive a bandwidth part (BWP) configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which to receive a grant; and receive downlink control information (DCI) in at least one subband including a grant to schedule communications in one or more subbands associated with the BWP. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0048] In some aspects, the network node 110 may include a communication manager 150. As described in greater detail elsewhere herein, the communication manager 150 may send a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be sent; and send a DCI in at least one subband including a grant to schedule communications in one or more subbands associated with the BWP. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0049] Figure 2 is a diagram illustrating an example network node communicating with a UE in a wireless network according to the present disclosure. The network node may correspond to Figure 1 Similarly, the UE may correspond to a network node 110. Figure 1 UE 120. Network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T ≥ 1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R ≥ 1). Figure 2 The network node 110 depicted in FIG. 1 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components that facilitate direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0050] At the network node 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0051] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 or other network nodes 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data to the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0052] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the network node 110 via the communication unit 294.

[0053] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. An antenna panel, antenna group, set of antenna elements, or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or coupled to one or more transmit or receive components (such as Figure 2 One or more antenna elements of one or more components).

[0054] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein.

[0055] At the network node 110, uplink signals from the UE 120 or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted via the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and provide the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modem 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein.

[0056] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2Any other component of the network node 110 may perform one or more techniques associated with cross-sub-band scheduling in a full-duplex network, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, or Figure 2 Any other component of the Figure 6 The process of 600 Figure 7 10 or other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of network node 110 or UE 120 (e.g., directly or after compilation, conversion, or interpretation), may cause one or more processors, UE 120, or network node 110 to perform or direct, for example, Figure 6 The process of 600 Figure 7 The operations of process 700 or other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, or interpreting instructions, etc.

[0057] In some aspects, the UE 120 includes means for receiving a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received; or means for receiving a DCI in at least one subband including a grant to schedule communications in one or more subbands associated with the BWP. Means for the UE 120 to perform operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0058] In some aspects, the network node 110 includes means for sending a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be sent; or means for sending a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP. In some aspects, means for the network node 110 to perform operations described herein may include, for example, one or more of the following: the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0059] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also called an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0060] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0061] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0062] Figure 3 3 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0063] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

[0064] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0065] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partitioning (such as that defined by 3GPP). In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0066] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions, or low PHY layer functions (such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc.) based on functional splitting (e.g., functional splitting defined by 3GPP). In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0067] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0068] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0069] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0070] Figure 4 400, 405, and 410 are diagrams illustrating examples of full-duplex communication in a wireless network according to the present disclosure. "Full-duplex communication" in a wireless network refers to simultaneous bidirectional communication between devices in the wireless network. For example, a UE operating in full-duplex mode may send uplink communications and receive downlink communications at the same time (e.g., in the same time slot or the same symbol). "Half-duplex communication" in a wireless network refers to unidirectional communication (e.g., only downlink communication or only uplink communication) between devices at a given time (e.g., in a given time slot or a given symbol).

[0071] like Figure 4As shown, examples 400 and 405 illustrate examples of in-band full-duplex (IBFD) communications. In IBFD, a UE may transmit uplink communications to a base station and receive downlink communications from a base station on the same time and frequency resources. As shown in example 400, in a first example of IBFD, the time and frequency resources used for uplink communications may completely overlap with the time and frequency resources used for downlink communications. As shown in example 405, in a second example of IBFD, the time and frequency resources used for uplink communications may partially overlap with the time and frequency resources used for downlink communications.

[0072] like Figure 4 As further shown, example 410 illustrates an example of sub-band full-duplex (SBFD) communication, which may also be referred to as "sub-band frequency division duplex (SBFDD)" or "flexible duplex". In SBFD, a UE may transmit uplink communications to a base station and receive downlink communications from a base station at the same time but on different frequency resources. For example, the different frequency resources may be sub-bands of a frequency band such as a time division duplex band. In this case, the frequency resources used for downlink communications may be separated from the frequency resources used for uplink communications in the frequency domain by a guard band.

[0073] In some aspects, the techniques and apparatus described herein in connection with cross-sub-band scheduling in a full-duplex network can be applied, for example, in conjunction with Figure 4 The full-duplex communication.

[0074] The wireless communication system may support cross-slot scheduling to reduce unnecessary buffering at the UE. For example, the UE may start buffering the entire bandwidth of the downlink BWP for potential communication scheduling of the network node at the beginning of control channel monitoring (e.g., physical downlink control channel (PDCCH) monitoring) in the search space opportunity. This is because as early as the beginning of monitoring, the communication can be scheduled by downlink control information (DCI) provided via the control channel. However, when, for example, the UE is not fully active, it is very likely that there is no communication scheduled for the UE in the search space opportunity. As a result, the UE may perform unnecessary buffering. In order to reduce such buffering, cross-slot scheduling may be used to ensure the minimum offset between the control channel and the communication scheduled by the control channel. This means that the UE does not need to buffer data during the time period corresponding to the minimum offset. In addition, if the UE does not receive any scheduling DCI in the search space opportunity, the UE may not be required to buffer data after the minimum offset.

[0075] Cross-slot scheduling can be applied to downlink communications and uplink communications. In the case of downlink communications, K0 is a value indicating the minimum offset between a downlink time slot in which a PDCCH communication (carrying a scheduling DCI) scheduling a physical downlink shared channel (PDSCH) communication is received and a time slot in which the PDSCH communication is scheduled. Typically, a UE does not expect to be scheduled for a PDSCH communication with a K0 less than the active K0. In the case of uplink communications, K2 is a value indicating the minimum offset between a downlink time slot in which a PDCCH communication (carrying a scheduling DCI) scheduling a physical uplink shared channel (PUSCH) communication is received and a time slot in which the PUSCH communication is scheduled. Typically, a UE does not expect to be scheduled for a PUSCH communication with a K2 less than the active K2 value.

[0076] In operation, the offset values ​​K0 and K2 may be configured via RRC signaling and may be configured per BWP, and there may be up to two candidate minimum offset values ​​for both K0 and K2 (for a given BWP). The configuration of a single offset value (for K0 and K2) is functionally the same as configuring a "zero" value and different configuration values ​​in the configuration of two offset values. If two RRC values ​​are configured for a BWP, the value "zero" is a valid configuration. The range of configuration values ​​is a range of integer values ​​from 0 slots to 16 slots, and the slots are based on the parameter set of the BWP. The active K0 for a downlink BWP or the active K2 for an uplink BWP may be signaled via a one-bit indication carried in, for example, a DCI.

[0077] Cross-slot scheduling has an impact on power savings at the UE. For example, if the UE is configured with a minimum K0 of two slots for the downlink BWP, the UE may relax the PDCCH decoding constraints in the downlink BWP and, in some cases, may be able to enter sleep mode during the two slots between the slot in which the DCI scheduling the PDSCH communication is received and the slot in which the PDSCH communication is to be received, thereby reducing power consumption. It is worth noting that cross-slot scheduling reduces power consumption by controlling the operation of the UE with respect to the time domain.

[0078] In the case of full-duplex communication, the BWP may cover more than one sub-band (in some combination of one or more downlink sub-bands and one or more uplink sub-bands). For example, to reduce or eliminate delays, when transitioning from a half-duplex timeslot to a full-duplex timeslot, it is not desirable to switch or modify the configuration of the BWP during the course of full-duplex communication. Therefore, in some scenarios, the BWP may span more than one sub-band.

[0079] In operation during full-duplex communication, the network node may decide to schedule the UE in one sub-band or more than one sub-band, depending on factors such as traffic load or interference. For example, a DCI communicated in a first sub-band of a BWP may schedule a first communication in the first sub-band of the BWP and a second communication in a second (different) sub-band. In some scenarios, the network node may decide to schedule the UE in only one sub-band. If the UE knows that it will be scheduled in only one sub-band of the BWP, multiple advantages may be achieved. One advantage is that the UE will not need to process the entire bandwidth of the BWP, thereby reducing the power consumption of the UE. It is worth noting that such energy savings may be achieved if the BWP is switched or modified, but as described above, this will result in undesirable delays. Another advantage is that the UE will not need to buffer other sub-bands associated with the BWP (e.g., if communications are scheduled in the same sub-band in which the scheduling DCI is received). Another advantage is that, since the frequency domain resource allocation (FDRA) field in the scheduling DCI is defined per BWP (rather than per sub-band), the FDRA field can carry redundant bits, thereby improving the decoding reliability of the PDCCH.

[0080] Various aspects generally relate to cross-subband scheduling in a full-duplex network. As used herein, cross-subband scheduling refers to scheduling a UE to communicate in one or more subbands associated with a BWP (e.g., scheduling a UE in a first subband associated with the BWP, a second subband associated with the BWP, or both the first subband and the second subband). Some aspects more specifically relate to BWP configurations of a BWP for supporting cross-subband scheduling in a full-duplex network, and dynamic adaptation of the BWP configuration. In some aspects, a network node may send and a UE may receive a BWP configuration indicating that the BWP is configured with cross-subband scheduling, wherein the BWP configuration indicates at least one subband associated with the BWP in which a grant is to be communicated. In some aspects, a network node may send and a UE may receive a DCI including a grant to schedule communications in one or more subbands associated with the BWP, wherein the DCI is sent and received in at least one subband indicated by the BWP configuration.

[0081] Certain aspects of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques may be used to reduce the power consumption of the UE by eliminating the need for the UE to process the entire bandwidth of the BWP while enabling the UE to be scheduled for communication in one or more sub-bands of the entire bandwidth. In addition, in some examples, the described techniques may reduce buffering at the UE, thereby reducing power consumption and saving processing resources. It is noteworthy that the techniques for cross-sub-band scheduling described herein reduce power consumption by controlling the operation of the UE in the frequency domain (rather than the time domain). In addition, in some examples, the described techniques may improve the decoding reliability of the PDCCH carrying the DCI by enabling the FDRA field of the DCI to carry redundant bits. For example, if the UE is scheduled only in a single sub-band associated with the BWP, some bits of the FDRA field will indicate the FDRA associated with the single sub-band. However, other bits of the FDRA (i.e., bits that would otherwise be used to indicate the FDRA associated with one or more other sub-bands associated with the BWP) may instead carry redundant bits associated with the single sub-band, thereby improving decoding reliability.

[0082] FIG. 5A to FIG. 5C is a diagram illustrating an example associated with cross-sub-band scheduling in a full-duplex network according to various aspects of the present disclosure.

[0083] like Figure 5A As shown, example 500 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as the wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink. In some aspects, the network node 110 and the UE 120 may support full-duplex communication.

[0084] In a first operation 502, the network node 110 may send and the UE 120 may receive a BWP configuration indicating that the BWP is configured with cross-sub-band scheduling. That is, the BWP configuration may configure a BWP that supports cross-sub-band scheduling (e.g., when the BWP is active in a full-duplex time slot or in a half-duplex time slot divided into multiple sub-bands). In some aspects, the network node 110 may send and the UE 120 may receive the BWP configuration via RRC signaling. That is, in some aspects, the BWP that supports cross-sub-band scheduling may be RRC configured.

[0085] In some aspects, the BWP configuration indicates at least one sub-band associated with the BWP in which a grant for scheduled communications is to be communicated. For example, the BWP configuration may indicate that the UE 120 may be expected to communicate a grant in a single sub-band of the BWP. As another example, the BWP configuration may indicate that the UE 120 may be expected to communicate a grant in any one or more of a plurality of sub-bands of the BWP. In some aspects, the BWP configuration may include information identifying one or more sub-bands in which the UE 120 may be expected to communicate a grant.

[0086] In some aspects, the BWP configuration includes an indication of a set of sub-bands associated with the BWP in which communications are to be sent (in the case of uplink communications) or received (in the case of downlink communications). For example, the BWP configuration may indicate that the UE 120 may be expected to communicate on a single sub-band associated with the BWP. As another example, the BWP configuration may indicate that the UE 120 may be expected to communicate on any one or more of a plurality of sub-bands associated with the BWP. In some aspects, the BWP configuration may include information identifying a set of sub-bands on which the UE 120 may be expected to communicate.

[0087] In some aspects, the BWP configuration is valid only when the BWP overlaps more than one sub-band in the frequency domain. That is, when the BWP overlaps a single sub-band in the frequency domain, the BWP configuration may not be applicable. Thus, in some aspects, the UE 120 may apply the BWP configuration based at least in part on determining that the BWP overlaps multiple sub-bands in the frequency domain.

[0088] In a second operation 504, the network node 110 may send and the UE 120 may receive a DCI including a grant to schedule one or more communications in one or more sub-bands associated with the BWP. In some aspects, the network node 110 may send and the UE 120 may receive a DCI including a grant in at least one sub-band associated with the BWP in which the grant is to be received by the UE 120. In some aspects, the DCI may schedule one or more downlink communications, such as one or more PDSCH communications. In some aspects, the DCI may schedule one or more uplink communications, such as one or more PUSCH communications. In some aspects, the grant in the DCI may schedule one or more communications to be sent or received in a full-duplex time slot. Alternatively, in some aspects, the grant in the DCI may schedule communications to be sent or received in a half-duplex time slot. Thus, in some aspects, a BWP configuration may be applied in a half-duplex time slot (e.g., when the half-duplex time slot is divided into a plurality of sub-bands).

[0089] In some aspects, the DCI may include an indication of an update to a set of subbands associated with a BWP in which communications are to be sent or received. For example, as described above, a BWP configuration may indicate a set of subbands on which a UE 120 may expect to communicate. Here, a DCI scheduling a communication may include an indication (e.g., a one-bit indication) that indicates to the UE 120 whether future communications will occur in the same set of subbands as indicated in the BWP configuration or in a different set of subbands of the BWP, as indicated in the DCI. In this manner, the set of subbands on which a UE 120 may expect to communicate may be dynamically updated via the DCI.

[0090] In some aspects, the update to the subband set is applicable to a specific number of time slots after receiving the DCI. That is, in some aspects, the update to the subband set may be activated a specific number of time slots after the time slot in which the UE 120 receives the DCI. In some aspects, the specific number of time slots may be configured via RRC signaling. In some aspects, the specific number of time slots may be configured on a per-BWP basis. In some aspects, the specific number of time slots may be configured on a per-component carrier basis. In some aspects, the specific number of time slots may be based at least in part on the capabilities of the UE 120. In some aspects, the UE 120 may indicate capability information to the network node 110, the capability information indicating the minimum number of time slots required for the UE 120 to apply the update to the subband set.

[0091] In some aspects, the FDRA indicated in the DCI may span more than one sub-band associated with the BWP. In such aspects, if the BWP configuration (or DCI) indicates that communication will occur in a single sub-band associated with the BWP, the UE 120 may identify an error. That is, when the FDRA in the DCI spans multiple sub-bands and the UE 120 expects to communicate on a single sub-band, the UE 120 may identify an error situation. Additionally or alternatively, the UE 120 may identify the actual FDRA (in other words, the FDRA that the UE 120 will use in association with sending or receiving communications) based at least in part on the overlap between the FDRA indicated in the DCI and the single sub-band in which communication will occur. That is, the UE 120 may assume that the actual FDRA is the overlap between the FDRA signaled by the DCI and the single sub-band in which the UE expects communication to occur.

[0092] In a third operation 506, communications may be sent or received in one or more sub-bands according to the grant. For example, in the case of downlink communications (e.g., PDSCH communications), the network node 110 may send downlink communications in one or more sub-bands according to the grant, and the UE 120 may receive downlink communications in one or more sub-bands according to the grant. As another example, in the case of uplink communications (e.g., PUSCH communications), the UE 120 may send uplink communications in one or more sub-bands according to the grant, and the network node 110 may receive uplink communications in one or more sub-bands according to the grant.

[0093] Figure 5B are diagrams illustrating various examples of cross-sub-band scheduling as described herein.

[0094] exist Figure 5B In the left example in FIG. , the BWP includes a first downlink subband (DL1), an uplink subband (UL), and a second downlink subband (DL2). In this example, the BWP configuration indicates that the BWP is configured for cross-subband scheduling, and the UE 120 may expect a grant on the first downlink subband, and the UE 120 may expect to schedule PDSCH communications on the first downlink subband and the second downlink subband. As shown, the network node 110 may send DCI on the first downlink subband, and the UE 120 may receive DCI on the first downlink subband. Here, the DCI schedules a first PDSCH communication (PDSCH1) on the first downlink subband, and schedules a second PDSCH communication (PDSCH2) on the second downlink subband. The network node 110 may send the first PDSCH communication and the second PDSCH communication according to the grant, and the UE 120 may receive the first PDSCH communication and the second PDSCH communication according to the grant.

[0095] exist Figure 5BIn the central example in FIG. 1 , the BWP includes a first downlink subband (DL1), an uplink subband (UL), and a second downlink subband (DL2). In this example, the BWP configuration indicates that the BWP is configured for cross-subband scheduling, the UE 120 may expect a grant on the first downlink subband, and the UE 120 may expect to schedule PDSCH communications only on the first downlink subband. As shown, the network node 110 may send DCI on the first downlink subband, and the UE 120 may receive DCI on the first downlink subband. Here, the DCI schedules PDSCH communications (PDSCH) on the first downlink subband. The network node 110 may send PDSCH communications based on the grant, and the UE 120 may receive PDSCH communications based on the grant. It is worth noting that in this example, the UE 120 is notified that the UE 120 will be scheduled only in one subband of the BWP. Therefore, the UE 120 does not need to process the entire bandwidth of the BWP, which reduces power consumption. Furthermore, the UE 120 does not need to buffer other sub-bands associated with the BWP, which reduces power consumption and saves memory and processing resources. Additionally, the FDRA field in the DCI may carry redundant bits to improve decoding reliability of the PDCCH.

[0096] exist Figure 5B In the right example in , the BWP includes a first downlink subband (DL1), a second downlink subband (DL2), and a third downlink subband (DL3). In this example, the BWP configuration indicates that the BWP is configured for cross-subband scheduling, the UE 120 may expect a grant on the first downlink subband, and the UE 120 may expect to schedule PDSCH communications only on the first downlink subband. As shown, the network node 110 may send DCI on the first downlink subband, and the UE 120 may receive DCI on the first downlink subband. Here, the DCI schedules PDSCH communications (PDSCH) on the first downlink subband. The network node 110 may send PDSCH communications based on the grant, and the UE 120 may receive PDSCH communications based on the grant. It is worth noting that in this example, the BWP configuration is applied to a half-duplex time slot. In addition, as for Figure 5B The same advantages as described in the central image.

[0097] Figure 5C is a diagram illustrating an example of dynamic updates associated with cross-sub-band scheduling as described herein.

[0098] exist Figure 5CIn the example in , the BWP includes a first downlink subband (DL1), an uplink subband (UL), and a second downlink subband (DL2). In this example, the BWP configuration indicates that the BWP is configured for cross-subband scheduling, UE 120 may expect a grant on the first downlink subband, and UE 120 may expect to schedule PDSCH communications on the first downlink subband and the second downlink subband. As shown, in the first time slot (time slot 1), the network node 110 may send DCI on the first downlink subband, and the UE 120 may receive DCI on the first downlink subband. Here, the DCI in the first time slot schedules a first PDSCH communication (PDSCH1) on the first downlink subband, and schedules a second PDSCH communication (PDSCH2) on the second downlink subband. In this example, the DCI includes an indication that the set of subbands on which the UE 120 can expect downlink communications has been updated to include only the first downlink subband (rather than the first downlink subband and the second downlink subband). Here, the update to the subband set applies to two time slots after receiving the DCI (e.g., based at least in part on the RRC configuration or the capabilities of the UE 120, etc.). As shown, the network node 110 may send the first PDSCH communication and the second PDSCH communication in the first time slot according to the grant, and the UE 120 may receive the first PDSCH communication and the second PDSCH communication in the first time slot according to the grant.

[0099] As further shown, in the second time slot (time slot 2), the network node 110 may send additional DCI on the first downlink sub-band, and the UE 120 may receive the additional DCI on the first downlink sub-band. Here, the DCI in the second time slot schedules a third PDSCH communication (PDSCH3) on the first downlink sub-band, and schedules a fourth PDSCH communication (PDSCH4) on the second downlink sub-band. It is worth noting that the update to the sub-band set has not been applied to the second time slot. As shown, the network node 110 may send a third PDSCH communication and a fourth PDSCH communication in the second time slot according to the grant, and the UE 120 may receive a third PDSCH communication and a fourth PDSCH communication in the second time slot according to the grant.

[0100] As further shown, in the third time slot (time slot 3), the network node 110 may send additional DCI on the first downlink sub-band, and the UE 120 may receive the additional DCI on the first downlink sub-band. Here, the DCI in the third time slot schedules the fifth PDSCH communication (PDSCH5) on the first downlink sub-band. It is worth noting that the update to the sub-band set is applied to the third time slot. As shown, the network node 110 may send the fifth PDSCH communication in the third time slot according to the grant, and the UE 120 may receive the fifth PDSCH communication in the third time slot according to the grant. In this example, the UE 120 is notified that the UE 120 will be scheduled in only one sub-band of the BWP in the third time slot. Therefore, the UE 120 does not need to process the entire bandwidth of the BWP during the third time slot, which reduces power consumption. In addition, the UE 120 does not need to buffer other sub-bands associated with the BWP during the third time slot, which reduces power consumption and saves memory and processing resources. Additionally, the FDRA field in the DCI of the third slot may carry redundant bits to improve the decoding reliability of the PDCCH.

[0101] Figure 6 is a flow chart illustrating an example process 600 performed, for example, by a UE supporting cross-sub-band scheduling in a full-duplex network in accordance with the present disclosure. Example process 600 is an example of a UE (eg, UE 120) performing operations associated with cross-sub-band scheduling in a full-duplex network.

[0102] like Figure 6 As shown, in some aspects, process 600 may include receiving a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received (block 610). For example, a UE (such as by using Figure 8 The depicted communications manager 140 or receiving component 802) may receive a BWP configuration indicating that the BWP is configured with a cross-sub-band schedule, the BWP configuration indicating at least one sub-band associated with the BWP in which to receive a grant, as described above.

[0103] like Figure 6 As further shown, in some aspects, process 600 may include receiving a DCI in at least one sub-band, the DCI including a grant to schedule communications in one or more sub-bands associated with the BWP (block 620). For example, a UE (such as by using Figure 8 The depicted communication manager 140 or receiving component 802) can receive DCI in at least one sub-band, the DCI comprising a grant to schedule communications in one or more sub-bands associated with a BWP, as described above.

[0104] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes described elsewhere herein.

[0105] In a first additional aspect, process 600 includes sending or receiving communications in one or more frequency sub-bands in accordance with a license.

[0106] In a second additional aspect, alone or in combination with the first aspect, the BWP configuration includes an indication of a set of subbands associated with the BWP in which communications are to be sent or received, the one or more subbands included in the set of subbands.

[0107] In a third additional aspect, alone or in combination with one or more of the first and second aspects, process 600 includes applying a BWP configuration based at least in part on determining that the BWP overlaps a plurality of sub-bands in the frequency domain.

[0108] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, a grant in a DCI schedules a communication to be transmitted or received in a full-duplex time slot.

[0109] In a fifth additional aspect, alone or in combination with one or more of the first to fourth aspects, a grant in a DCI schedules a communication to be transmitted or received in a half-duplex time slot.

[0110] In a sixth additional aspect, either alone or in combination with one or more of the first to fifth aspects, the DCI includes an indication of an update to a set of subbands associated with the BWP in which communications are to be sent or received, the update to the set of subbands being applicable to a specific number of time slots after receiving the DCI.

[0111] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, a certain number of time slots is configured on a per BWP basis.

[0112] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, a certain number of time slots is configured on a per component carrier basis.

[0113] In a ninth additional aspect, alone or in combination with one or more of the first to eighth aspects, the particular number of time slots is based at least in part on capabilities of the UE.

[0114] In a tenth additional aspect, either alone or in combination with one or more of the first to ninth aspects, the FDRA indicated in the DCI spans more than one subband associated with the BWP, and process 600 includes identifying an error based at least in part on an indication that communications are to be sent or received in a single subband.

[0115] In an eleventh additional aspect, either alone or in combination with one or more of aspects one to ten, the FDRA indicated in the DCI spans more than one sub-band associated with the BWP, and process 600 includes identifying the actual FDRA based at least in part on an overlap between the FDRA and a single sub-band, and based at least in part on an indication that communications are to be sent or received in a single sub-band.

[0116] Figure 7 is a flow chart illustrating an example process 700 performed, for example, by a network node supporting cross-sub-band scheduling in a full-duplex network in accordance with the present disclosure. Example process 700 is an example of a network node (eg, network node 110) performing operations associated with cross-sub-band scheduling in a full-duplex network.

[0117] like Figure 7 As shown, in some aspects, process 700 may include sending a BWP configuration indicating that the BWP is configured with a cross-subband schedule, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be sent (block 710). For example, a network node (such as by using Fig. 9 The depicted communication manager 150 or transmitting component 904) may transmit a BWP configuration indicating that the BWP is configured with a cross-sub-band schedule, the BWP configuration indicating at least one sub-band associated with the BWP in which a grant is to be transmitted, as described above.

[0118] like Figure 7 As further shown, in some aspects, process 700 may include sending a DCI in at least one sub-band, the DCI including a grant to schedule communications in one or more sub-bands associated with the BWP (block 720). For example, a network node (such as by using Fig. 9 The depicted communication manager 150 or transmitting component 904) can transmit DCI in at least one sub-band, the DCI comprising a grant to schedule communications in one or more sub-bands associated with the BWP, as described above.

[0119] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes described elsewhere herein.

[0120] In a first additional aspect, process 700 includes sending or receiving communications in one or more frequency sub-bands in accordance with a license.

[0121] In a second additional aspect, alone or in combination with the first aspect, the BWP configuration includes an indication of a set of subbands associated with the BWP in which communications are to be sent or received, the one or more subbands included in the set of subbands.

[0122] In a third additional aspect, alone or in combination with one or more of the first and second aspects, a grant in a DCI schedules a communication to transmit or receive in a full-duplex time slot.

[0123] In a fourth additional aspect, alone or in combination with one or more of the first to third aspects, a grant in a DCI schedules a communication to be transmitted or received in a half-duplex time slot.

[0124] In a fifth additional aspect, either alone or in combination with one or more of the first to fourth aspects, the DCI includes an indication of an update to a set of subbands associated with the BWP in which communications are to be sent or received, the update to the set of subbands being applicable to a specific number of time slots after receiving the DCI.

[0125] In a sixth additional aspect, alone or in combination with one or more of the first to fifth aspects, a certain number of time slots is configured on a per BWP basis.

[0126] In a seventh additional aspect, alone or in combination with one or more of the first to sixth aspects, a certain number of time slots is configured on a per component carrier basis.

[0127] In an eighth additional aspect, alone or in combination with one or more of the first to seventh aspects, the particular number of time slots is based at least in part on capabilities of the UE.

[0128] Figure 8 800 is a diagram of an example apparatus 800 for wireless communication supporting cross-sub-band scheduling in a full-duplex network according to the present disclosure. The apparatus 800 may be a UE, or the UE may include the apparatus 800. In some aspects, the apparatus 800 includes a receiving component 802, a transmitting component 804, and a communication manager 140, which may communicate with each other (e.g., via one or more buses). As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device) using the receiving component 802 and the transmitting component 804.

[0129] In some aspects, the apparatus 800 may be configured to perform the Figures 5A-5C Additionally or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as Figure 6 In some aspects, the apparatus 800 may include the above-mentioned process 600. Figure 2 One or more components of the UE.

[0130] The receiving component 802 may receive communications from the device 806, such as reference signals, control information, data communications, or combinations thereof. The receiving component 802 may provide the received communications to one or more other components of the device 800, such as the communications manager 140. In some aspects, the receiving component 802 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 802 may include the above in combination with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the UE.

[0131] The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 806. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 804 for transmission to the device 806. In some aspects, the transmission component 804 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 806. In some aspects, the transmission component 804 may include the above in combination with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the UE. In some aspects, the transmit component 804 can be co-located with the receive component 802 in a transceiver.

[0132] The communication manager 140 may receive or may cause the receiving component 802 to receive a BWP configuration indicating that the BWP is configured with a cross-subband schedule, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received. The communication manager 140 may receive or may cause the receiving component 802 to receive a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

[0133] The communication manager 140 may include the above combined Figure 2 The controller / processor, memory, or combination thereof of the UE described herein. In some aspects, the communication manager 140 includes a collection of components. Alternatively, the collection of components may be separate and distinct from the communication manager 140. In some aspects, one or more components in the collection of components may include the above-mentioned Figure 2The controller / processor, memory, or combination thereof of the described UE may be implemented therein. Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0134] The receiving component 802 can receive a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which to receive a grant. The receiving component 802 can receive a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0135] Transmitting component 804 or receiving component 802 can transmit or receive communications, respectively, in one or more frequency sub-bands according to the license.

[0136] Transmitting component 804 or receiving component 802 can apply a BWP configuration based at least in part on determining that the BWP overlaps a plurality of sub-bands in the frequency domain.

[0137] Fig. 9 is a diagram of an example apparatus 900 for wireless communication supporting cross-sub-band scheduling in a full-duplex network according to the present disclosure. The apparatus 900 may be a network node, or the network node may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902, a sending component 904, and a communication manager 150, which may communicate with each other (e.g., via one or more buses). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a network node, or another wireless communication device) using the receiving component 902 and the sending component 904.

[0138] In some aspects, the apparatus 900 may be configured to perform the Figures 5A-5C Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as Figure 7 In some aspects, the apparatus 900 may include the above-mentioned process 700. Figure 2 One or more components of the network node.

[0139] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or combinations thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900, such as the communications manager 150. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components. In some aspects, the receiving component 902 may include the above in combination with Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories or combinations thereof of the network node.

[0140] The transmission component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 906. In some aspects, the communication manager 150 may generate communications and may transmit the generated communications to the transmission component 904 for transmission to the device 906. In some aspects, the transmission component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 906. In some aspects, the transmission component 904 may include the above in combination with Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the network node. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0141] The communication manager 150 may send or may cause the sending component 904 to send a BWP configuration indicating that the BWP is configured with a cross-sub-band schedule, the BWP configuration indicating at least one sub-band associated with the BWP in which a grant is to be sent. The communication manager 150 may send or may cause the sending component 904 to send a DCI in at least one sub-band, the DCI including a grant to schedule communications in one or more sub-bands associated with the BWP. In some aspects, the communication manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.

[0142] The communication manager 150 may include the above combined Figure 2 The controller / processor, memory, scheduler, communication unit, or combination thereof of the network node described herein. In some aspects, the communication manager 150 includes a collection of components. Alternatively, the collection of components may be separate and distinct from the communication manager 150. In some aspects, one or more components in the collection of components may include the above-mentioned components. Figure 2The controller / processor, memory, scheduler, communication unit, or combination thereof of the described network node, or may be implemented therein. Additionally or alternatively, one or more components in the component set may be at least partially implemented as software stored in the memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0143] The transmitting component 904 can transmit a BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which to transmit a grant. The transmitting component 904 can transmit a DCI in at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0144] Transmitting component 904 or receiving component 902 can transmit or receive communications, respectively, in one or more frequency sub-bands according to the license.

[0145] The following provides an overview of some aspects of the disclosure:

[0146] Aspect 1: A method of wireless communication performed by a UE, the method comprising: receiving a BWP configuration, the BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received; and receiving a DCI in the at least one subband, the DCI including a grant to schedule communications in one or more subbands associated with the BWP.

[0147] Aspect 2: The method according to aspect 1, further comprising sending or receiving the communication in the one or more sub-bands according to the license.

[0148] Aspect 3: A method according to any one of aspects 1 to 2, wherein the BWP configuration includes an indication of a set of sub-bands associated with the BWP in which communications are to be sent or received, and the one or more sub-bands are included in the set of sub-bands.

[0149] Aspect 4: The method according to any one of aspects 1 to 3, further comprising applying the BWP configuration based at least in part on determining that the BWP overlaps with multiple sub-bands in the frequency domain.

[0150] Aspect 5: The method according to any one of aspects 1 to 4, wherein the grant in the DCI schedules the communication to be transmitted or received in a full-duplex time slot.

[0151] Aspect 6: The method according to any one of aspects 1 to 4, wherein the grant in the DCI schedules the communication to be transmitted or received in a half-duplex time slot.

[0152] Aspect 7: A method according to any one of Aspects 1 to 6, wherein the DCI includes an indication of an update to a set of sub-bands associated with the BWP in which communications are to be sent or received, the update to the set of sub-bands being applicable to a specific number of time slots after receiving the DCI.

[0153] Aspect 8: The method according to aspect 7, wherein the specific number of time slots is configured on a per BWP basis.

[0154] Aspect 9: The method according to aspect 7, wherein the specific number of time slots is configured on a per component carrier basis.

[0155] Aspect 10: The method according to any one of aspects 7 to 9, wherein the specific number of time slots is based at least in part on the capabilities of the UE.

[0156] Aspect 11: A method according to any one of Aspects 1 to 10, wherein the FDRA indicated in the DCI spans more than one sub-band associated with the BWP, and the method also includes identifying an error based at least in part on an indication that communications are to be sent or received in a single sub-band.

[0157] Aspect 12: A method according to any one of Aspects 1 to 10, wherein the FDRA indicated in the DCI spans more than one sub-band associated with the BWP, and the method further includes identifying the actual FDRA based at least in part on an overlap between the FDRA and a single sub-band and at least in part on an indication that communications are to be sent or received in the single sub-band.

[0158] Aspect 13: A method of wireless communication performed by a network node, the method comprising: sending a BWP configuration, the BWP configuration indicating that the BWP is configured with cross-subband scheduling, the BWP configuration indicating at least one sub-band associated with the BWP in which a grant is to be sent; and sending a DCI in the at least one sub-band, the DCI including a grant to schedule communication in one or more sub-bands associated with the BWP.

[0159] Aspect 14: The method according to aspect 13, further comprising sending or receiving the communication in the one or more sub-bands according to the license.

[0160] Aspect 15: A method according to any one of Aspects 13 to 14, wherein the BWP configuration includes an indication of a set of sub-bands associated with the BWP in which communications are to be sent or received, the one or more sub-bands being included in the set of sub-bands.

[0161] Aspect 16: The method according to any one of aspects 13 to 15, wherein the grant in the DCI schedules the communication to be transmitted or received in a full-duplex time slot.

[0162] Aspect 17: The method according to any one of aspects 13 to 15, wherein the grant in the DCI schedules the communication to be transmitted or received in a half-duplex time slot.

[0163] Aspect 18: A method according to any one of Aspects 13 to 17, wherein the DCI includes an indication of an update to a set of subbands associated with the BWP in which communications are to be sent or received, the update to the set of subbands being applicable to a specific number of time slots after receiving the DCI.

[0164] Aspect 19: The method according to aspect 18, wherein the specific number of time slots is configured on a per BWP basis.

[0165] Aspect 20: The method according to aspect 18, wherein the specific number of time slots is configured on a per component carrier basis.

[0166] Aspect 21: The method according to any one of aspects 18 to 20, wherein the specific number of time slots is based at least in part on the capabilities of the user equipment.

[0167] Aspect 22: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 12.

[0168] Aspect 23: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 12.

[0169] Aspect 24: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 12.

[0170] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 12.

[0171] Aspect 26: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 12.

[0172] Aspect 27: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 13 to 21.

[0173] Aspect 28: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 13 to 21.

[0174] Aspect 29: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 13 to 21.

[0175] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 13 to 21.

[0176] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 13 to 21.

[0177] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0178] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware or hardware and software. "Software" should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable program, a thread of execution, a process or a function, etc., whether it is described in software, firmware, middleware, microcode, hardware description language or other terms. As used herein, a "processor" is implemented with a combination of hardware or hardware and software. It will be obvious that the system or method described herein can be implemented in different forms of hardware or a combination of hardware and software. The actual dedicated control hardware or software code for implementing these systems or methods does not limit various aspects. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement these systems or methods based at least in part on the description herein.

[0179] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0180] Although the specific combination of features is stated in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically described in the claims or not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of the following: a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0181] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected with the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "having", "containing", "comprising" and similar terms are intended to be open terms that do not limit the elements (for example, element "comprising" A can also contain B) that they modify. In addition, the phrase "based on" is intended to represent "based on at least in part", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used consecutively is intended to be inclusive and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: at least one memory; and at least one processor, the at least one processor being communicatively coupled to the at least one memory, the at least one processor being configured to cause the UE to: receiving a bandwidth part (BWP) configuration indicating that the BWP is configured with a cross-subband schedule, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received; as well as Downlink control information (DCI) is received in the at least one sub-band, the downlink control information (DCI) including a grant to schedule communications in one or more sub-bands associated with the BWP. 2 . The UE of claim 1 , wherein the at least one processor is further configured to cause the UE to send or receive the communication in the one or more sub-bands according to the grant.

3. The UE of claim 1, wherein the BWP configuration comprises an indication of a set of subbands associated with the BWP in which communications are to be sent or received, the one or more subbands being included in the set of subbands. 4 . The UE of claim 1 , wherein the at least one processor is further configured to cause the UE to apply the BWP configuration based at least in part on determining that the BWP overlaps with a plurality of sub-bands in the frequency domain.

5. The UE of claim 1, wherein the DCI includes an indication of an update to a set of subbands associated with the BWP in which communications are to be sent or received, the update to the set of subbands being applicable to a specific number of time slots after receiving the DCI. The UE according to claim 5 , wherein the specific number of time slots is configured on a per BWP basis. The UE according to claim 5 , wherein the specific number of time slots is configured on a per component carrier basis.

8. The UE of claim 5, wherein the specific number of time slots is based at least in part on capabilities of the UE.

9. The UE of claim 1 , wherein a frequency domain resource allocation (FDRA) indicated in the DCI spans more than one sub-band associated with the BWP, and the at least one processor is further configured to identify an error based at least in part on an indication that communications are to be sent or received in a single sub-band.

10. A UE according to claim 1, wherein the frequency domain resource allocation (FDRA) indicated in the DCI spans more than one sub-band associated with the BWP, and the at least one processor is further configured to identify the actual FDRA based at least in part on an overlap between the FDRA and a single sub-band and at least in part on an indication that communications are to be sent or received in the single sub-band.

11. A network node for wireless communication, the network node comprising: at least one memory; and at least one processor, the at least one processor being communicatively coupled to the at least one memory, the at least one processor being configured to cause the network node to: transmitting a bandwidth part (BWP) configuration indicating that the BWP is configured with a cross-subband schedule, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be transmitted; as well as Downlink control information (DCI) is transmitted in the at least one sub-band, the downlink control information (DCI) including a grant to schedule communications in one or more sub-bands associated with the BWP.

12. The network node of claim 11, wherein the at least one processor is further configured to cause the network node to transmit or receive the communication in the one or more frequency sub-bands in accordance with the grant.

13. The network node of claim 11, wherein the BWP configuration includes an indication of a set of subbands associated with the BWP in which communications are to be sent or received, the one or more subbands being included in the set of subbands.

14. The network node of claim 11, wherein the DCI includes an indication of an update to a set of subbands associated with the BWP in which communications are to be sent or received, the update to the set of subbands applicable for a specific number of time slots after receiving the DCI.

15. The network node of claim 14, wherein the specific number of time slots is configured on a per BWP basis.

16. The network node of claim 14, wherein the specific number of time slots is configured on a per component carrier basis.

17. The network node of claim 14, wherein the particular number of time slots is based at least in part on capabilities of user equipment.

18. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a bandwidth part (BWP) configuration indicating that the BWP is configured with a cross-subband schedule, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be received; as well as Downlink control information (DCI) is received in the at least one sub-band, the downlink control information (DCI) including a grant to schedule communications in one or more sub-bands associated with the BWP.

19. The method of claim 18, further comprising sending or receiving the communication in the one or more sub-bands in accordance with the license.

20. The method of claim 18, wherein the BWP configuration includes an indication of a set of subbands associated with the BWP in which communications are to be sent or received, the one or more subbands being included in the set of subbands.

21. The method of claim 18, further comprising applying the BWP configuration based at least in part on determining that the BWP overlaps a plurality of sub-bands in the frequency domain.

22. The method of claim 18, wherein the DCI includes an indication of an update to a set of subbands associated with the BWP in which communications are to be sent or received, the update to the set of subbands applicable for a particular number of time slots after receiving the DCI.

23. The method of claim 22, wherein the specific number of time slots is configured on a per BWP basis.

24. The method of claim 22, wherein the specific number of time slots is configured on a per component carrier basis.

25. The method of claim 22, wherein the particular number of time slots is based at least in part on capabilities of the UE.

26. The method of claim 18, wherein a frequency domain resource allocation (FDRA) indicated in the DCI spans more than one sub-band associated with the BWP, and the method further comprises identifying an error based at least in part on an indication that communications are to be sent or received in a single sub-band.

27. A method according to claim 18, wherein the frequency domain resource allocation (FDRA) indicated in the DCI spans more than one sub-band associated with the BWP, and the method further comprises identifying the actual FDRA based at least in part on an overlap between the FDRA and a single sub-band and at least in part on an indication that communications are to be sent or received in the single sub-band.

28. A method of wireless communication performed by a network node, the method comprising: transmitting a bandwidth part (BWP) configuration indicating that the BWP is configured with a cross-subband schedule, the BWP configuration indicating at least one subband associated with the BWP in which a grant is to be transmitted; as well as Downlink control information (DCI) is transmitted in the at least one sub-band, the downlink control information (DCI) including a grant to schedule communications in one or more sub-bands associated with the BWP.

29. The method of claim 28, further comprising sending or receiving the communication in the one or more sub-bands in accordance with the license.

30. The method of claim 28, wherein the BWP configuration includes an indication of a set of subbands associated with the BWP in which communications are to be sent or received, the one or more subbands being included in the set of subbands.

Images