Scheduling downlink control information (DCI) in subband full duplex (SBFD) slots

Abstract

A method for wireless communication by a user equipment (UE) includes receiving a configuration of a downlink bandwidth portion (BWP). The method also includes receiving a frequency domain resource allocation (FDRA) in the time slot. The FDRA includes a first type of bits corresponding to a downlink allocation within the downlink BWP and a second type of bits corresponding to any one of a known sequence or repetition bits. The method also includes communicating according to the FDRA.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. patent application No. 17 / 894,959, filed on August 24, 2022, entitled “SCHEDULING DOWNLINK CONTROLINFORMATION (DCI) IN SUB-BAND FULL-DUPLEX (SBFD) SLOTS,” the disclosure of which is expressly incorporated by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to enhancing decodability when downlink control information (DCI) is scheduled in sub-band full-duplex (SBFD) time slots. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephone, 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, transmit power, etc.). 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 issued by the Third Generation Partnership Project (3GPP). Narrowband (NB) Internet of Things (IoT) and enhanced machine type communication (eMTC) are sets of enhancements to LTE for machine type communication.

[0005] A wireless communication network may include multiple base stations (BSs) that may support communications for multiple user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. Downlinks (or forward links) refer to the communication link from a BS to a UE, while uplinks (or reverse links) refer to the communication link from a UE to a BS. As will be described in more detail, a BS may be referred to as a Node B, an evolved Node B (eNB), a gNB, an access point (AP), a radio head, a transmit and receive point (TRP), a new radio (NR) BS, a 5G Node B, etc.

[0006] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is an enhancement set of the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation, so as to better support mobile broadband Internet access. Summary of the invention

[0007] In various aspects of the present disclosure, a method for wireless communication by a user equipment (UE) includes receiving a configuration of a downlink bandwidth part (BWP). The method also includes receiving a frequency domain resource allocation (FDRA) in a time slot. The FDRA includes a first type of bits corresponding to a downlink allocation within the downlink BWP and a second type of bits corresponding to either a known sequence or a repeated bit. The method also includes communicating according to the FDRA.

[0008] In other aspects of the present disclosure, a method for wireless communication by a network device includes configuring a BWP. The method may also include sending an FDRA in a time slot. The FDRA includes a first type of bit corresponding to a downlink allocation (the downlink allocation falls within the downlink BWP) and a second type of bit corresponding to either a known sequence or a repeated bit. The method also includes communicating according to the FDRA.

[0009] Other aspects of the present disclosure relate to an apparatus for wireless communication. The apparatus has a memory and at least one processor coupled to the memory. The processor is configured to receive a configuration of a downlink bandwidth part (BWP). The processor is also configured to receive a frequency domain resource allocation (FDRA) in a time slot. The FDRA includes a first type of bit corresponding to a downlink allocation within the downlink BWP and a second type of bit corresponding to either a known sequence or a repeated bit. The processor is also configured to communicate according to the FDRA.

[0010] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices, and processing systems as generally described with reference to and as illustrated in the accompanying drawings and description.

[0011] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the disclosed concepts, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order that the features of the present disclosure may be understood in detail, a more specific description may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain aspects of the present disclosure and therefore should not be considered as limiting the scope thereof, as the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0013] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0014] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a user equipment (UE) in a wireless communication network according to various aspects of the present disclosure.

[0015] Figure 3 is a block diagram illustrating an example decomposed base station architecture in accordance with aspects of the present disclosure.

[0016] Figure 4 In-band full-duplex operation in which devices transmit and receive simultaneously on the same frequency resources is illustrated in accordance with various aspects of the present disclosure.

[0017] Figure 5 Sub-band frequency division duplex (FDD) operations in which devices simultaneously transmit and receive on different frequency resources are illustrated in accordance with various aspects of the present disclosure.

[0018] Figure 6 is a diagram illustrating a full-duplex communication mode according to various aspects of the present disclosure.

[0019] Figure 7 is a diagram illustrating a sub-band full-duplex (SBFD) time slot according to various aspects of the present disclosure.

[0020] Figure 8is a block diagram illustrating a frequency domain resource allocation (FDRA) overlapping with a configured downlink (DL) bandwidth part (BWP) in accordance with various aspects of the present disclosure.

[0021] Fig. 9 is a block diagram illustrating repeated useful FDRA bitmap bits in accordance with various aspects of the present disclosure.

[0022] Fig.10 is a block diagram illustrating the repetition of useful FDRA bitmap bits when a bandwidth part (BWP) spans multiple disjoint frequency bands in accordance with various aspects of the present disclosure.

[0023] Fig.11 is a table illustrating the number of allocated resource blocks (RBs) and RB starting positions according to various aspects of the present disclosure.

[0024] Fig.12 is a block diagram illustrating a type 1 frequency domain resource allocation (FDRA) overlapping with a configured downlink (DL) bandwidth part (BWP) according to aspects of the present disclosure.

[0025] Fig.13 is a block diagram illustrating a type 1 frequency domain resource allocation (FDRA) overlapping with a configured downlink (DL) bandwidth part (BWP) according to aspects of the present disclosure.

[0026] Fig.14 is a flow chart illustrating an example process performed, for example, by a user equipment (UE) according to various aspects of the present disclosure.

[0027] Fig.15 is a flow chart illustrating an example process, for example, performed by a network device, according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0028] The following is a more comprehensive description of various aspects of the present disclosure with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, 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. Based on the teachings, those skilled in the art should recognize that the scope of the present disclosure is intended to cover any aspect of the present disclosure, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, a device or a method can be implemented using any number of aspects described. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structures and functionality as a supplement to the various aspects of the present disclosure described or in addition. It should be understood that any aspect of the present disclosure disclosed can be embodied by one or more elements of the claims.

[0029] 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, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] It should be noted that although various aspects may be described using terms commonly associated with 5G and later wireless technologies, various aspects of the present disclosure may be applied in communication systems based on other generations (such as and including 3G and / or 4G technologies).

[0031] A Sub-Band Full Duplex (SBFD) timeslot contains resources for both downlink and uplink communications, and potentially a guard band between the downlink and uplink resources. An SBFD timeslot enables a device to transmit and receive simultaneously.

[0032] Frequency Domain Resource Allocation (FDRA) allocates resource blocks (e.g., sub-bands) for each transmission and reception. Due to the varying frequency allocation, only a portion of the configured bandwidth part (BWP) may overlap with the allocated sub-band. For example, the allocated downlink sub-band may be in the lower half of the band, while the configured downlink BWP spans the entire band.

[0033] The FDRA is carried in the downlink control information (DCI) and may include a bitmap or a resource indicator value (RIV). If the BWP spans a larger bandwidth than the allocated (or useful) bandwidth, the bitmap or RIV may contain redundant bits. The bitmap and RIV are designed for the configured BWP, not just the useful bandwidth.

[0034] Bits that fall outside the configured BWP in the conflicting transmission direction are referred to as "useless" bits. According to aspects of the present disclosure, redundant bits associated with a bitmap or RIV, if fixed and known to a user equipment (UE), may be used by the UE to improve the speed and reliability associated with decoding the DCI. That is, the UE may replace the log-likelihood ratios (LLRs) corresponding to useless bits with infinity and negative infinity. For example, the base station may send a fixed sequence in the useless bits, which may be either all zeros or any other sequence configured to the radio resource control (RRC) of the UE.

[0035] Redundant bits associated with a bitmap or RIV can also be used to repeat certain fields in the DCI, and thus improve decodability. For example, if the number of useful bits is equal to the number of useless bits, all useful bits can be repeated. If the number of useful bits is greater than the number of useless bits, some useful bits can be repeated. If the number of useful bits is less than the number of useless bits, some useful bits can be repeated more than once. In some aspects, repetition can start from the first bit, the second bit of the bitmap, or occur according to a sequence configured by RRC. In the case where the BWP spans more than one disjoint frequency band, the repeated bit can be a bit in a lower sub-band, a higher sub-band, or can be a combination of these bits configured by RRC. In some aspects, useless bits can be used to send repetitions of other fields in the DCI, such as time domain resource allocation (TDRA).

[0036] Various aspects of the present disclosure improve transmission efficiency by avoiding sending one or more useless bits. Additionally, decodability may also be improved, allowing the UE to decode the DCI faster and with higher reliability than in the prior art.

[0037] Figure 1 1 is a diagram illustrating a network 100 in which various aspects of the present disclosure may be practiced. The network 100 may be a 5G or NR network, or some other wireless network (such as an LTE network). The wireless network 100 may include a plurality of BSs 110 (shown as BSs 110a, BSs 110b, BSs 110c, and BSs 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE), and may also be referred to as a base station, an NR BS, a Node B, a gNB, a 5G Node B, an access point, a transmission and reception point (TRP), a network node, a network entity, etc. A base station may be implemented as an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. A base station may be implemented in an aggregated or monolithic base station architecture, or alternatively, in a decomposed base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0038] Each BS can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0039] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "AP", "Node B", "5G NB", "TRP", and "cell" may be used interchangeably.

[0040] In some aspects, the cell need not be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

[0041] The wireless network 100 may also include a relay station. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a BS or a UE) and transmit the transmissions of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in FIG. 1 , a relay station 110 d may communicate with a macro BS 110 a and a UE 120 d to facilitate communication between the BS 110 a and the UE 120 d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0042] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0043] For example, BSs 110 (shown as BS110a, BS110b, BS110c, and BS110d) and core network 130 may exchange communications via backhaul links 132 (e.g., S1, etc.). Base stations 110 may communicate with each other directly or indirectly (e.g., through core network 130) through other backhaul links (e.g., X2, etc.).

[0044] The core network 130 may be an evolved packet core (EPC), which may include at least one mobile management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may be a control node that handles signaling between the UE 120 and the EPC. All user IP packets may be delivered through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to the IP services of the network operator. The operator's IP services may include the Internet, the intranet, the IP multimedia subsystem (IMS), and the packet switched (PS) streaming media services.

[0045] The core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations 110 or access node controllers (ANCs) may interface with the core network 130 via a backhaul link 132 (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UE 120. In some configurations, the various functions of each access network entity or base station 110 may be distributed across various network devices (e.g., radio heads and access network controllers), or merged into a single network device (e.g., base station 110).

[0046] UE 120 (e.g., 120a, 120b, 120c) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE may 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device or a satellite radio), a component or sensor of a vehicle, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate via a wireless or wired medium.

[0047] One or more UEs 120 may establish a protocol data unit (PDU) session for a network slice. In some cases, the UE 120 may select a network slice based on an application or subscription service. By enabling different network slices to serve different applications or subscriptions, the UE 120 may improve its resource utilization in the wireless network 100 while also meeting the performance specifications of the respective applications of the UE 120. In some cases, the AMF ( Figure 1 ), to serve the network slice used by UE 120. In addition, session management of the network slice can be performed by an access and mobility management function (AMF).

[0048] UE 120 may include a downlink control information (DCI) decoding module 140. For simplicity, only one UE 120d is shown as including the DCI decoding module 140. The DCI decoding module 140 may receive a configuration of a downlink bandwidth part (BWP). The DCI decoding module 140 may also receive a frequency domain resource allocation (FDRA) in a time slot. The FDRA includes a first type of bit corresponding to a downlink allocation within the downlink BWP and a second type of bit corresponding to either a known sequence or a repeated bit. The DCI decoding module 140 may also communicate according to the FDRA.

[0049] The core network 130 or the base station 110 or any other network device (e.g., Figure 3) may include a DCI encoding module 138. For simplicity, only one base station 110a is shown as including a DCI encoding module 138. The DCI encoding module 138 may configure the BWP. The DCI encoding module 138 may also send an FDRA in a time slot. The FDRA includes a first type of bits corresponding to a downlink allocation (the downlink allocation falls within the downlink BWP) and a second type of bits corresponding to either a known sequence or a repeated bit. The DCI encoding module 138 may also communicate according to the FDRA.

[0050] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. For example, MTC and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide connectivity to or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as user premises equipment (CPE). UE 120 may be included in a housing that houses components of UE 120 (such as a processor component, a memory component, etc.).

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

[0052] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. 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, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein performed by base station 110. For example, base station 110 may configure UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0053] As pointed out above, Figure 1 Provided only as an example. Other examples may be found in relation to Figure 1 The examples described are different.

[0054] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 A base station in the base station and Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0055] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Reducing the MCS lowers throughput but increases the reliability of transmission. The transmit processor 220 may also process system information (e.g., for semi-static resource allocation information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM) or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t may be transmitted via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, position coding may be used to generate synchronization signals to convey additional information.

[0056] At the UE 120, antennas 252a to 252r may receive downlink signals from the base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to the data sink 260, and provide decoded control information and system information to the controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0057] On the uplink, at the UE 120, a transmit processor 264 may receive data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280 and process the data and control information. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 254, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the core network 130 via the communication unit 244. The core network 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0058] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component of the UE 120 may perform one or more techniques associated with encoding and decoding the scheduling DCI, as described in more detail elsewhere. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of may perform or direct e.g. Fig.14 and Fig.15 The processes and / or operations of other processes as described. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0059] In some aspects, UE 120 and / or base station 110 may include means for receiving, means for communicating, means for configuring, and means for transmitting. Such means may include combining Figure 2 One or more components of a UE 120 or base station 110 are described.

[0060] As pointed out above, Figure 2 This is provided as an example only. Other examples can be found in the reference Figure 2 The examples described are different.

[0061] The deployment of a communication system such as a 5G New Radio (NR) system may be arranged with various components or constituent parts 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 radio access network (RAN) node, a core network node, a network element or network equipment such as a base station (BS), or one or more units (or one or more components) performing base station functionality may be implemented in an aggregated or decomposed architecture. For example, a BS such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit and receive point (TRP) or a cell, etc. may be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0062] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN 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 (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0063] Base station type operations or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0064] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (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 distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0065] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RTRIC 315, and SMO framework 305) may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or send 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 the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, the unit may include a wired interface that is configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0066] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 310 may be logically divided 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, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0067] DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340. In some aspects, DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional partition such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0068] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional partitioning (such as lower layer functional partitioning). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0069] 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, 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 specific implementations, the SMO framework 305 may communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0070] 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-RTRIC 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 on 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 311 with the near-RTRIC 325.

[0071] 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 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 O1) or via the creation of RAN management policies (such as A1 policies).

[0072] Full-duplex communication is simultaneous two-way communication. For example, while the UE is receiving downlink data, the UE can send uplink data. There are two types of full-duplex operation: intra-band full-duplex and sub-band full-duplex.

[0073] Figure 4 In-band full-duplex operation in which a device transmits and receives simultaneously on the same frequency resources is illustrated in accordance with various aspects of the present disclosure. Downlink and uplink transmissions share the same in-band full-duplex time and frequency resources. In a first scenario 410, uplink (UL) and downlink (DL) resources completely overlap. In a second scenario 420, uplink and downlink resources partially overlap.

[0074] Figure 5 Sub-band frequency division duplex (FDD) (also known as flexible duplex or sub-band full duplex (SBFD)) operation in which devices transmit and receive simultaneously on different frequency resources according to various aspects of the present disclosure is illustrated. Figure 5 In the example of , downlink resources 502 are separated from uplink resources 504 in the frequency domain by a guard band 506. Thus, an SBFD timeslot contains resources for both downlink and uplink communications, and potentially a guard band between the downlink and uplink resources. An SBFD timeslot enables a device to transmit and receive simultaneously.

[0075] Figure 6 6 is a diagram illustrating a full-duplex communication mode according to various aspects of the present disclosure. For example, a first scenario 610 depicts a full-duplex base station communicating with a half-duplex UE (shown as UE1 and UE2) in non-overlapping uplink and downlink sub-bands (e.g., as Figure 5In a first scenario 610, a full-duplex first gNB may transmit to UE1 on a downlink channel and receive from UE2 on an uplink channel. However, UE2 may cause interference to UE1 due to uplink transmissions to the first gNB. Furthermore, the second gNB may cause interference to the first gNB due to downlink communications with both UE1 and UE2. Additionally, the first gNB may experience self-interference from both downlink communications and uplink communications.

[0076] In the second scenario 620, a full-duplex gNB and a full-duplex UE1 communicate with partially or completely overlapping uplink and downlink sub-bands (e.g., Figure 4 In the second scenario 620, UE1 experiences self-interference from full-duplex uplink and downlink communications with the first gNB, and also receives interference from UE2, which sends uplink communications to the second gNB. UE1 also receives interference from the downlink communications of the second gNB.

[0077] In a third scenario 630, a full-duplex UE1 communicates with multiple transmit and receive points (m-TRPs). The full-duplex UE1 simultaneously communicates with a first gNB of the m-TRP in the uplink and with a second gNB of the m-TRP in the downlink. UE1 is configured in full-duplex mode, and therefore, UE1 experiences self-interference due to uplink and downlink communications with the first gNB and the second gNB. As a result of the uplink communications from UE1, interference to UE2 is also received from UE1. As shown in the third scenario 630, UE2 receives downlink communications from the second gNB.

[0078] Although the foregoing examples are described with respect to a gNB, it should be noted that any network node, including Figure 3 The components described.

[0079] The time slot format for full-duplex communication can be defined as downlink plus uplink "D+U". In a "D+U" time slot, the frequency band is used for both UL transmission and DL transmission. DL transmission and UL transmission may occur in overlapping frequency bands (e.g., in-band full-duplex) or adjacent frequency bands (e.g., sub-band full-duplex). In a given "D+U" symbol, a half-duplex UE either transmits in the UL frequency band or receives in the DL frequency band. In a given "D+U" symbol, a full-duplex UE may transmit in the UL frequency band and / or receive in the DL frequency band in the same time slot. A "D+U" time slot may contain only DL symbols, only UL symbols, or full-duplex symbols.

[0080] Figure 7710 is a diagram illustrating a sub-band full-duplex (SBFD) time slot according to various aspects of the present disclosure. The diagram depicts a subframe / time slot decomposition for communication between a full-duplex TRP, a full-duplex UE (UE1), and a half-duplex UE (UE2). In this example, an entity may perform flexible downlink and uplink operations in time across time slots and across UEs. That is, simultaneous physical downlink shared channel (PDSCH) and physical uplink shared channel (PUSCH) grants for the same subframe / time slot for different UEs may be configured. A full-duplex UE may be configured for uplink grants and downlink grants. The UE may change the uplink transmission and / or downlink reception bandwidth portion between each time slot with zero delay. The UE may utilize full reciprocity (e.g., full duplex) to send a sounding reference signal (SRS) to cover the entire downlink bandwidth portion, and utilize partial reciprocity (e.g., half-duplex) to send a sounding reference signal (SRS) to cover a portion of the downlink bandwidth. Downlink control (DL CTL) information may be sent across all frequency resources or across a portion of the frequency resources. In this example, the dashed lines of time slot 710 depict the subframe / time slot decomposition for full-duplex TRP and half-duplex UEs.

[0081] Frequency domain resource allocation (FDRA) allocates resource blocks (e.g., subbands) for each transmission and reception. The two types of allocations include type 0 allocation and type 1 allocation. Type 0 allocation is a disjoint resource block (RB) allocation specified by a bitmap. The allocation is in multiple resource block groups (RBGs). The RBG size depends on the bandwidth part (BWP) size and the configuration type. The size of the bitmap is nine bits or eighteen bits. In type 1 allocation, the allocation of consecutive RBs is determined by the RB_start value and the number of consecutive RBs combined in the resource indicator value (RIV) field.

[0082] Due to varying frequency allocations, only a portion of the configured bandwidth part (BWP) may overlap with the allocated sub-band. For example, the allocated downlink sub-band may be located in the lower half of the band, while the configured downlink BWP spans the entire band.

[0083] The FDRA is carried in the downlink control information (DCI) and may include a bitmap or a resource indicator value (RIV). If the BWP spans a larger bandwidth than the allocated (or useful) bandwidth, the bitmap or RIV may contain redundant bits. The bitmap and RIV indicate the BWP designed for the configuration, not just the useful bandwidth.

[0084] Figure 8is a block diagram illustrating a frequency domain resource allocation (FDRA) that overlaps a configured downlink (DL) bandwidth portion (BWP) according to aspects of the present disclosure. The bits of the FDRA that fall outside the configured BWP in the conflicting transmission direction are referred to as "useless" bits. For example, Figure 8 A downlink (DL) BWP 802 is shown. In addition, Figure 8 An FDRA comprising nine bits is shown: five bits are used for downlink allocation 804, and four bits are used for uplink allocation 806. The five bits of downlink allocation 804 are consistent with the configured downlink BWP. However, the four bits used for uplink allocation 806 conflict with the downlink BWP. Because the bandwidth (e.g., DL BWP 802) is configured for downlink communication, these four conflicting uplink allocation bits are referred to as "useless" bits.

[0085] According to aspects of the present disclosure, redundant bits, if fixed and known to a user equipment (UE), can help the UE decode DCI faster and with higher reliability. That is, the UE can replace the log likelihood ratio (LLR) of the corresponding useless bits with infinity and negative infinity. For example, the base station can send a fixed sequence in these bits, which is either all zeros or any other sequence configured to the radio resource control (RRC) of the UE. Therefore, the UE can easily decode the known information.

[0086] Redundant bits can also be used to repeat certain fields in the DCI, and thus improve decodability. For example, if the number of useful bits is equal to the number of useless bits, all useful bits can be repeated. If the number of useful bits is greater than the number of useless bits, some useful bits can be repeated. If the number of useful bits is less than the number of useless bits, some useful bits can be repeated more than once. In some aspects, repetition can occur starting from the first bit of the bitmap, starting from the second bit of the bitmap, or according to a sequence configured by RRC. Because the UE is expecting a specific number of bits, all bits are sent to the UE.

[0087] Fig. 9 is a block diagram illustrating repeated useful FDRA bitmap bits according to various aspects of the present disclosure. Fig. 9 In the example of , the downlink BWP range 902 is illustrated as having nine bits. Bits 1-5 correspond to the downlink allocation 804. Bits 6-9 correspond to the uplink allocation 806. In this example, the useful bits are bits 1-5, and the unused bits are bits 6-9. According to aspects of the present disclosure, a portion of these bits are repeated in the unused positions. Fig. 9In the example of , bits 1-4 are repeated in the bit positions corresponding to uplink allocation 806. More specifically, bits 1-5 were originally sent in their original positions corresponding to downlink allocation 804. Bits 1-4 are also repeated in the original positions corresponding to bits 6-9 of uplink allocation 806. Column 908 indicates what is actually sent.

[0088] In some examples, the BWP spans more than one disjoint frequency band. In such examples, the repeated bits may be bits in the lower sub-band, the upper sub-band, or may be a combination of these bits configured by RRC. In some aspects, the unused bits may be used to send repetitions of other fields in the DCI, such as the time domain resource allocation (TDRA).

[0089] Fig.10 is a block diagram illustrating the repetition of useful FDRA bitmap bits when a bandwidth part (BWP) spans multiple non-intersecting frequency bands in accordance with various aspects of the present disclosure. Fig.10 , BWP 902 spans a first downlink allocation 804, an uplink allocation 806, and a second downlink allocation 1010. Column 1012 shows what is actually sent. In this example, the first three bits 1-3 are repeated in the bit positions corresponding to the uplink allocation 806 (i.e., the positions of the original bits 5-7). The first four bits 1-4 and the last two bits 8 and 9 are sent in their original bit positions. Therefore, in this example, the repeated bits are bits in the lower sub-band.

[0090] Aspects of the present disclosure also address type 1 FDRA allocations. In these aspects, the RIV indication is complex because it is unclear which bits will be useful and which bits will not be useful. For example, assuming the length of the BWP is five resource blocks, the required RIV indication is log2(5×6 / 2)=4 bits. The possible allocations are Fig.11 Shown in.

[0091] Fig.11 is a table illustrating the number of allocated resource blocks (RBs) and the RB starting positions according to various aspects of the present disclosure. Fig.11In the example of , each row corresponds to an RB starting position. Each column corresponds to the number of allocated RBs. The table gives the RIV value corresponding to each possible RB starting value in each row and each possible number of allocated RBs in each column. For example, the values ​​in the last row have a column marked as Number of allocated RBs = 2 (the third column from the left) and a RIV value of 5. A RIV value of 5 corresponds to an RB_start value of zero and two allocated RBs. If the number of allocated RBs is 2, the RB may start at resource 0, 1, 2, or 3, but not at 4. For another example, if the number of allocated RBs is only one, the RB may start at resource 0, 1, 2, 3, or 4.

[0092] Fig.12 802 is a block diagram illustrating a type 1 frequency domain resource allocation (FDRA) overlapping with a configured downlink (DL) bandwidth part (BWP) 802 according to aspects of the present disclosure. Fig.12 In the example of , DL BWP 802 overlaps DL allocation 804 in only three RBs. Therefore, the valid RIV values ​​are 0, 1, 2, 5, 6, and 10, which if converted to a binary RIV indication are 0000, 0001, 0010, 0101, 0110, and 1010. This binary representation shows that no bit can be considered fixed or unused.

[0093] According to aspects of the present disclosure, the UE may use its knowledge of possible RIV values ​​in decoding unknown DCI values. Fig.12 In the example shown, when the UE decodes the RIV field and decodes the most significant bit as 1, the UE can safely assume that the rest of the bit field is 010. This technique can also be applied to half-duplex time slots.

[0094] Fig.13 802 is a block diagram illustrating a type 1 frequency domain resource allocation (FDRA) overlapping with a configured downlink (DL) bandwidth part (BWP) 802 according to aspects of the present disclosure. Fig.13 In the example of bits, of which bits are useful bits, among which represents the number of resource blocks (RBs) in the bandwidth part, and In other aspects, the first 10 bits of the remaining bits are fixed and known to the UE. bits are repeated partially or completely.

[0095] Fig.1414 is a flow chart illustrating an example process 1400 performed, for example, by a user equipment (UE) in accordance with various aspects of the present disclosure. The example process 1400 is an example of enhancing decodability when downlink control information (DCI) is scheduled in a sub-band full duplex (SBFD) time slot. The operations of the process 1400 may be implemented by the UE 120.

[0096] At block 1402, a user equipment (UE) receives a configuration of a downlink bandwidth part (BWP). For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.) may receive the configuration. In some aspects, the downlink BWP is discontinuous, and the method further includes: when the second type bit is a repeated bit, receiving an indication that the configuration includes a repeated allocated discontinuous frequency band.

[0097] At block 1404, a user equipment (UE) receives a frequency domain resource allocation (FDRA) in a time slot. The FDRA includes a first type of bit corresponding to the downlink allocation within the downlink BWP and a second type of bit corresponding to either a known sequence or a repeated bit. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receiving processor 258, controller / processor 280, memory 282, etc.) may receive the FDRA. In some aspects, the known sequence includes zero or a sequence configured to the UE. In some aspects, the repeated bit is a repeated time domain resource allocation (TDRA) bit. In other aspects, the repeated bit is a bitmap bit of type 0 FDRA, and the time slot is a sub-band full-duplex (SBFD) time slot. In yet other aspects, the repeated bit is a bit indicated based on a source indicator value (RIV) from type 1 FDRA, and the time slot is a sub-band full-duplex (SBFD) time slot. In further aspects, the repetition bit is a bit indicated based on the RIV value from a Type 1 FDRA and the time slot is a half-duplex time slot.

[0098] At block 1406, a user equipment (UE) communicates according to the FDRA. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receiving processor 258, TX MIMO processor 266, transmitting processor 264, controller / processor 280, memory 282, etc.) may communicate according to the FDRA. In some aspects, the communication includes receiving repeated bits from the repeated allocation. In these aspects, when the number of first type bits is the same as the number of second type bits, the repeated allocation is all of the downlink allocation. In other aspects, the communication includes receiving repeated bits from the repeated allocation. In these aspects, when the number of first type bits is greater than the number of second type bits, the repeated allocation is part of the downlink allocation. In yet other aspects, the communication includes receiving repeated bits from the repeated allocation. In these aspects, the repeated allocation is multiple repetitions of the downlink allocation when the number of first type bits is less than the number of second type bits.

[0099] Fig.15 1 is a flow chart illustrating an example process 1500 performed, for example, by a network device in accordance with various aspects of the present disclosure. The example process 1500 is an example of enhancing decodability when scheduling downlink control information (DCI) in a sub-band full duplex (SBFD) time slot. The operations of the process 1500 may be implemented by a network device such as a base station 110.

[0100] At block 1502, the base station 110 configures the BWP. For example, the base station (e.g., using the antenna 234, the MOD / DEMOD 232, the TX MIMO processor 230, the transmit processor 220, the controller / processor 280, the memory 282, etc.) may configure the BWP. In some aspects, the downlink BWP is discontinuous, and the method further includes: when the second type bit is a repeated bit, receiving an indication including a configuration of a repeated allocated discontinuous frequency band.

[0101] At box 1504, the base station 110 sends an FDRA in a time slot. The FDRA includes a first type of bit corresponding to a downlink allocation (the downlink allocation falls within the downlink BWP) and a second type of bit corresponding to either a known sequence or a repeated bit. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) can send the FDRA. In some aspects, the known sequence includes zero or a sequence configured to the UE. In some aspects, the repeated bit is a repeated time domain resource allocation (TDRA) bit. In other aspects, the repeated bit is a bitmap bit of type 0 FDRA, and the time slot is a sub-band full-duplex (SBFD) time slot. In some other aspects, the repeated bit is a bit indicated based on a source indicator value (RIV) from a type 1 FDRA, and the time slot is a sub-band full-duplex (SBFD) time slot. In further aspects, the repetition bit is a bit indicated based on the RIV value from a Type 1 FDRA and the time slot is a half-duplex time slot.

[0102] At box 1506, the base station 110 communicates according to the FDRA. The FDRA includes a first type of bit corresponding to the downlink allocation (the downlink allocation falls within the downlink BWP) and a second type of bit corresponding to either a known sequence or a repeated bit. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, MIMO detector 236, receiving processor 238, TX MIMO processor 230, transmitting processor 220, controller / processor 240, memory 242, etc.) can communicate according to the FDRA. In some aspects, the communication includes sending repeated bits from the repeated allocation. In these aspects, when the number of the first type of bits is the same as the number of the second type of bits, the repeated allocation is all of the downlink allocation. In other aspects, the communication includes sending repeated bits from the repeated allocation. In these aspects, when the number of the first type of bits is greater than the number of the second type of bits, the repeated allocation is part of the downlink allocation. In some other aspects, the communication includes sending repeated bits from the repeated allocation. In these aspects, the repeated allocation is a plurality of repetitions of the downlink allocation when the number of first type bits is less than the number of second type bits.

[0103] Example aspects

[0104] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving a configuration of a downlink bandwidth part (BWP); receiving a frequency domain resource allocation (FDRA) in a time slot, the FDRA comprising: a first type of bits corresponding to the downlink allocation within the downlink BWP; and a second type of bits corresponding to either a known sequence or a repeated bit; and communicating according to the FDRA.

[0105] Aspect 2: The method according to aspect 1, wherein the known sequence includes zero or a sequence configured for the UE.

[0106] Aspect 3: A method according to aspect 1, wherein the communication includes receiving the repeated bits from a repeated allocation, and when the number of the first type bits is the same as the number of the second type bits, the repeated allocation includes all of the downlink allocation.

[0107] Aspect 4: The method according to aspect 1, wherein the communication includes receiving the repeated bits from a repeated allocation, and when the number of the first type bits is greater than the number of the second type bits, the repeated allocation includes a portion of the downlink allocation.

[0108] Aspect 5: A method according to aspect 1, wherein the communication includes receiving the repetition bits from a repetition allocation, and when the number of the first type bits is less than the number of the second type bits, the repetition allocation includes multiple repetitions of the downlink allocation.

[0109] Aspect 6: The method according to any one of Aspects 3 to 5 further includes: when the second type bit is the repeated bit, receiving a configuration of a repeated allocated sequence.

[0110] Aspect 7: The method according to any one of Aspects 3 to 5, wherein the downlink BWP is discontinuous, and the method further comprises: when the second type bit is the repeated bit, receiving an indication including a configuration of a repeatedly allocated discontinuous frequency band.

[0111] Aspect 8: The method according to any one of aspects 3 to 7, wherein the repeated bits include repeated time domain resource allocation (TDRA) bits.

[0112] Aspect 9: A method according to any one of Aspects 3 to 7, wherein: the repetition bit comprises a bitmap bit of type 0FDRA; and the time slot comprises a sub-band full-duplex (SBFD) time slot.

[0113] Aspect 10: A method according to any one of Aspects 3 to 7, wherein: the repetition bit includes a bit indicated based on a resource indicator value (RIV) from a type 1 FDRA; and the time slot includes a sub-band full-duplex (SBFD) time slot.

[0114] Aspect 11: A method according to any one of Aspects 3 to 7, wherein: the repetition bit includes a bit indicated based on a resource indicator value (RIV) from a Type 1 FDRA; and the time slot includes a half-duplex time slot.

[0115] Aspect 12: A method for wireless communication by a network device, the method comprising: configuring a downlink bandwidth part (BWP); sending a frequency domain resource allocation (FDRA) in a time slot, the FDRA comprising: a first type of bit corresponding to the downlink allocation, the downlink allocation falling within the downlink BWP; and a second type of bit corresponding to either a known sequence or a repeated bit; and communicating according to the FDRA.

[0116] Aspect 13: The method according to aspect 12, wherein the known sequence comprises zero or a sequence configured to a user equipment (UE).

[0117] Aspect 14: A method according to aspect 12, wherein the communication includes sending the repeated bits from a repeated allocation, and when the number of the first type bits is the same as the number of the second type bits, the repeated allocation includes all of the downlink allocation.

[0118] Aspect 15: The method according to aspect 12, wherein the communicating comprises sending the repetition bits from a repetition allocation, and when the number of the first type bits is greater than the number of the second type bits, the repetition allocation comprises a portion of the downlink allocation.

[0119] Aspect 16: A method according to aspect 12, wherein the communication includes sending the repetition bits from a repetition allocation, and when the number of the first type of bits is less than the number of the second type of bits, the repetition allocation includes multiple repetitions of the downlink allocation.

[0120] Aspect 17: The method according to any one of Aspects 14 to 16, further comprising: when the second type bit is the repeated bit, sending a configuration of a repeated allocated sequence.

[0121] Aspect 18: A method according to any one of Aspects 14 to 16, wherein the downlink BWP is discontinuous, and the method further comprises: when the second type bit is the repeated bit, sending an indication including a configuration of a repeatedly allocated discontinuous frequency band.

[0122] Aspect 19: The method according to any one of aspects 14 to 18, wherein the repeated bits include repeated time domain resource allocation (TDRA) bits.

[0123] Aspect 20: A method according to any one of Aspects 14 to 18, wherein: the repetition bit comprises a bitmap bit of type 0FDRA; and the time slot comprises a sub-band full-duplex (SBFD) time slot.

[0124] Aspect 21: A method according to any one of Aspects 14 to 18, wherein: the repetition bit includes a bit indicated based on a resource indicator value (RIV) from a Type 1 FDRA; and the time slot includes a sub-band full-duplex (SBFD) time slot.

[0125] Aspect 22: A method according to any one of aspects 14 to 18, wherein: the repetition bit includes a bit indicated based on a resource indicator value (RIV) from a type 1 FDRA; and the time slot includes a half-duplex time slot.

[0126] Aspect 23: An apparatus for wireless communication by a user equipment (UE), the apparatus comprising: a memory; and at least one processor coupled to the memory, the at least one processor being configured to: receive a configuration of a downlink bandwidth part (BWP); receive a frequency domain resource allocation (FDRA) in a time slot, the FDRA comprising: a first type of bits corresponding to a downlink allocation within the downlink BWP; and a second type of bits corresponding to either a known sequence or a repeated bit; and communicate according to the FDRA.

[0127] Aspect 24: The apparatus according to Aspect 23, wherein the known sequence comprises zero or a sequence configured to the UE.

[0128] Aspect 25: An apparatus according to Aspect 23, wherein the processor communicates by receiving the repetition bits from a repetition allocation, and when the number of the first type bits is the same as the number of the second type bits, the repetition allocation includes all of the downlink allocation.

[0129] Aspect 26: An apparatus according to aspect 23, wherein the processor communicates by receiving the repeated bits from a repeated allocation, and when the number of the first type bits is greater than the number of the second type bits, the repeated allocation includes a portion of the downlink allocation.

[0130] Aspect 27: An apparatus according to Aspect 23, wherein the processor communicates by receiving the repetition bits from a repetition allocation, and when the number of the first type bits is less than the number of the second type bits, the repetition allocation includes multiple repetitions of the downlink allocation.

[0131] Aspect 28: An apparatus according to any one of aspects 24 to 27, wherein the at least one processor is further configured to: when the second type bit is the repetition bit, receive a configuration of a repetition allocated sequence.

[0132] Aspect 29: An apparatus according to any one of Aspects 23 to 27, wherein the downlink BWP is discontinuous, and the method further comprises: when the second type bit is the repeated bit, receiving an indication including a configuration of a repeatedly allocated discontinuous frequency band.

[0133] Aspect 30: An apparatus according to any one of aspects 23 to 29, wherein the repetition bits comprise repeated time domain resource allocation (TDRA) bits.

[0134] 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.

[0135] As used, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used, a processor is implemented using hardware, firmware, and / or a combination of hardware and software.

[0136] Some aspects are described in conjunction with thresholds. As used, 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.

[0137] It will be apparent that the described systems and / or methods can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Therefore, the operation and performance of these systems and / or methods are described without reference to specific software code, and it should be understood that software and hardware used to implement these systems and / or methods can be designed based at least in part on these descriptions.

[0138] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically set forth in the claims and / or is not disclosed in the specification. Although each dependent claim listed below may directly rely only on one claim, the disclosure of various aspects includes each dependent claim and each other claim combination in the claim set. The phrase "at least one" mentioned in the list of items refers to any combination of those items, including a single member. For example, "at least one of a, b or c" is intended to cover a, b, c, ab, ac, bc and abc, and any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc, or any other ordering of a, b and c).

[0139] The elements, actions or instructions used should not be interpreted as critical or essential unless explicitly described as such. In addition, as used, the articles "a" and "an" are intended to include one or more items, and they can be used interchangeably with "one or more". In addition, as used, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, combinations of related items and unrelated items, etc.), and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms will be used. In addition, as used, the terms "having" and the like are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated.

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: Receive downlink bandwidth part (BWP) configuration; receiving a frequency domain resource allocation (FDRA) in a time slot, the FDRA comprising: a first type of bits corresponding to a downlink allocation within the downlink BWP; and a second type of bits corresponding to either a known sequence or repeated bits; and The communication is performed according to the FDRA. 2 . The method of claim 1 , wherein the known sequence comprises zero or a sequence configured to the UE.

3. The method of claim 1, wherein the communicating comprises receiving the repeated bits from a repeated allocation, the repeated allocation comprising all of the downlink allocation when the number of the first type bits is the same as the number of the second type bits.

4. The method of claim 1, wherein the communicating comprises receiving the repeated bits from a repeated allocation, the repeated allocation comprising a portion of the downlink allocation when the number of the first type bits is greater than the number of the second type bits.

5. The method of claim 1, wherein the communicating comprises receiving the repetition bits from a repetition allocation comprising multiple repetitions of the downlink allocation when the number of the first type bits is less than the number of the second type bits.

6. The method according to claim 1, further comprising: When the second type bit is the repetition bit, a configuration of a repetition allocated sequence is received.

7. The method of claim 1, wherein the downlink BWP is discontinuous, and the method further comprises: When the second type bit is the repetition bit, the reception indication includes configuration of repeatedly allocated discontinuous frequency bands.

8. The method of claim 1, wherein the repeated bits comprise repeated time domain resource allocation (TDRA) bits.

9. The method according to claim 1, wherein: The repetition bits include bitmap bits of type 0FDRA; and The time slots include sub-band full-duplex (SBFD) time slots.

10. The method of claim 1, wherein: The repetition bits include bits indicated based on a resource indicator value (RIV) from a Type 1 FDRA; and The time slots include sub-band full-duplex (SBFD) time slots.

11. The method according to claim 1, wherein: The repetition bits include bits indicated based on a resource indicator value (RIV) from a Type 1 FDRA; and The time slots include half-duplex time slots.

12. A method for wireless communication by a network device, the method comprising: Configure the downlink bandwidth part (BWP); transmitting a frequency domain resource allocation (FDRA) in a time slot, the FDRA comprising: a first type of bits corresponding to a downlink allocation, the downlink allocation falling within the downlink BWP; and a second type of bits corresponding to either a known sequence or repeated bits; and The communication is performed according to the FDRA.

13. The method of claim 12, wherein the known sequence comprises zero or a sequence configured to a user equipment (UE).

14. The method of claim 12, wherein the communicating comprises sending the repeated bits from a repeated allocation, the repeated allocation comprising all of the downlink allocation when the number of the first type bits is the same as the number of the second type bits.

15. The method of claim 12, wherein the communicating comprises sending the repeated bits from a repeated allocation, the repeated allocation comprising a portion of the downlink allocation when the number of bits of the first type is greater than the number of bits of the second type.

16. The method of claim 12, wherein the communicating comprises sending the repetition bits from a repetition allocation comprising multiple repetitions of the downlink allocation when the number of bits of the first type is less than the number of bits of the second type.

17. The method according to claim 12, further comprising: When the second type bit is the repeated bit, a configuration of a repeated allocated sequence is transmitted.

18. The method of claim 12, wherein the downlink BWP is discontinuous, and the method further comprises: When the second type bit is the repetition bit, sending indicates configuration of a discontinuous frequency band including repeated allocation.

19. The method of claim 12, wherein the repeated bits comprise repeated time domain resource allocation (TDRA) bits.

20. The method of claim 12, wherein: The repetition bits include bitmap bits of type 0FDRA; and The time slots include sub-band full-duplex (SBFD) time slots.

21. The method of claim 12, wherein: The repetition bits include bits indicated based on a resource indicator value (RIV) from a Type 1 FDRA; and The time slots include sub-band full-duplex (SBFD) time slots.

22. The method of claim 12, wherein: The repetition bits include bits indicated based on a resource indicator value (RIV) from a Type 1 FDRA; and The time slots include half-duplex time slots.

23. An apparatus for wireless communication by a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: Receive downlink bandwidth part (BWP) configuration; receiving a frequency domain resource allocation (FDRA) in a time slot, the FDRA comprising: a first type of bits corresponding to a downlink allocation within the downlink BWP; and a second type of bits corresponding to either a known sequence or repeated bits; and The communication is performed according to the FDRA.

24. The apparatus of claim 23, wherein the known sequence comprises zero or a sequence configured to the UE.

25. The apparatus of claim 23, wherein the at least one processor is further configured to communicate by receiving the repeated bits from a repeated allocation, wherein the repeated allocation includes all of the downlink allocation when the number of the first type bits is the same as the number of the second type bits.

26. The apparatus of claim 23, wherein the at least one processor is further configured to communicate by receiving the repetition bits from a repetition allocation that comprises a portion of the downlink allocation when the number of the first type bits is greater than the number of the second type bits.

27. The apparatus of claim 23, wherein the at least one processor is further configured to communicate by receiving the repetition bits from a repetition allocation, wherein the repetition allocation comprises multiple repetitions of the downlink allocation when the number of the first type bits is less than the number of the second type bits.

28. The apparatus of claim 23, wherein the at least one processor is further configured to receive a configuration of a repeated allocated sequence when the second type bit is the repeated bit.

29. The apparatus of claim 23, wherein the downlink BWP is discontinuous, and the at least one processor is further configured to receive a configuration indicating a discontinuous frequency band including repeated allocations when the second type bit is the repetition bit.

30. The apparatus of claim 23, wherein the repeated bits comprise repeated time domain resource allocation (TDRA) bits.

Images