Adaptive resource allocation length

Abstract

This disclosure provides systems, methods, and devices for wireless communication that support enhanced frequency domain resource allocation. In a first aspect, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to: receive resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and communicating with the second network node using the transmission bandwidth for the transmission based on the number of bits. Other aspects and features are also claimed and described.

Description

Technical Field

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application No. 17 / 930,256, filed on September 7, 2022, entitled “ADAPTABLE RESOURCE ALLOCATION LENGTH,” which is expressly incorporated herein by reference in its entirety.

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to enhanced frequency domain resource allocation.Some features enable and provide improved communications, including variable length bitmaps for frequency domain resource allocation. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as a base station (or Node B) that may support communication for multiple user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0006] The base station may send data and control information to the UE on the downlink, or receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmissions from neighboring base stations or other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from other UEs communicating with neighboring base stations or from uplink transmissions of other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows with more UEs accessing long-range wireless communication networks and more short-range wireless systems deployed in communities. Research and development continues to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications. Summary of the invention

[0008] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. The sole purpose of this summary is to present some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to more specific embodiments presented later.

[0009] In one aspect of the present disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to: receive resource allocation information, the resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and communicate with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0010] In additional aspects of the disclosure, a method for wireless communication includes receiving resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0011] In an additional aspect of the disclosure, an apparatus includes: means for receiving resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and means for communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0012] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations including: receiving resource allocation information including a number of bits corresponding to a transmission bandwidth for a transmission; and communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0013] In another aspect of the present disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to: receive resource allocation information, the resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and communicate with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0014] In additional aspects of the disclosure, a method for wireless communication includes: transmitting resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0015] In an additional aspect of the disclosure, an apparatus includes: means for transmitting resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and means for communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0016] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations including: sending resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

[0017] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may 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.

[0018] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or use can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementations can range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some practical environments, the equipment in conjunction with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by adding a dash and a second label to distinguish between similar components after the reference label. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label, regardless of the second reference label.

[0020] Figure 1 is a block diagram illustrating details of an example wireless communication system in accordance with one or more aspects.

[0021] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) according to one or more aspects.

[0022] Figure 3A is a diagram of a first example of full-duplex operation.

[0023] Figure 3B is a diagram of a second example of full-duplex operation.

[0024] Figure 3C is a diagram of a third example of the full-duplex operation.

[0025] Figure 3D is a diagram of a fourth example of the full-duplex operation.

[0026] Figure 3E is a diagram of a fifth example of the full-duplex operation.

[0027] Figure 3F is a diagram of a sixth example of the full-duplex operation.

[0028] Figure 3G is a diagram of an example of a BWP switching delay table.

[0029] Figure 3H is a diagram of an example antenna layout.

[0030] Fig. 3I is a diagram of an example timing diagram.

[0031] Figure 3J is exemplified in Fig. 3I The timing diagram for Figure 3H Schematic diagram of the antenna operation of the antenna layout.

[0032] Figure 3K is exemplified in Fig. 3I The timing diagram for Figure 3H Illustration of antenna leakage for an antenna layout of FIG.

[0033] Figure 4 is a block diagram illustrating an example wireless communication system supporting enhanced frequency-domain resource allocation according to one or more aspects.

[0034] Figure 5 is a flow diagram illustrating an example process for supporting enhanced frequency-domain resource allocation in accordance with one or more aspects.

[0035] Figure 6 is a flow diagram illustrating an example process for supporting enhanced frequency-domain resource allocation in accordance with one or more aspects.

[0036] FIG. 7A to FIG. 7C is a time slot diagram illustrating example resource allocations according to one or more aspects.

[0037] Fig. 8A and Figure 8B is a time slot diagram illustrating example resource allocations according to one or more aspects.

[0038] Fig.9A and Fig. 9B is a time slot diagram illustrating example resource allocations according to one or more aspects.

[0039] Fig.10 is a flow diagram illustrating an example process for supporting enhanced frequency-domain resource allocation in accordance with one or more aspects.

[0040] Fig.11 is a flow diagram illustrating an example process for supporting enhanced frequency-domain resource allocation in accordance with one or more aspects.

[0041] Fig.12 is a block diagram of an example UE supporting enhanced frequency-domain resource allocation according to one or more aspects.

[0042] Fig.13 is a block diagram of an example base station supporting enhanced frequency-domain resource allocation according to one or more aspects.

[0043] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0044] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to limit the scope of the present disclosure. Instead, the specific embodiments include specific details for providing a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0045] The present disclosure as a whole relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various specific implementations, various techniques and devices can be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices) and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0046] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0047] For example, a TDMA network may implement a radio technology such as the Global System for Mobile Communications (GSM). The Third Generation Partnership Project (3GPP) defines the standards for the GSM EDGE (Enhanced Data Rate for GSM Evolution) Radio Access Network (RAN) (also referred to as GERAN). GERAN is the radio component of the network of GSM / EDGE together with connecting base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents a component of the GSM network through which telephone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to subscriber phones (also referred to as user terminals or user equipment (UE)) and from subscriber phones to the PSTN and the Internet. The network of a mobile phone operator may include one or more GERANs, which may be coupled to the UTRAN in the case of a UMTS / GSM network. Additionally, the operator network may also include one or more LTE networks, or one or more other networks. Various network types may use different radio access technologies (RATs) and RANs.

[0048] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration between telecommunication association groups with the goal of defining a globally applicable third generation (3G) mobile phone specification. 3GPP LTE is a 3GPP plan with the goal of improving the UMTS mobile phone standard. 3GPP can define the specifications of next generation mobile networks, mobile systems and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G or 5G NR technology; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of the present disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0049] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT), with ultra-high density (e.g., about 1M nodes / km 2 ), ultra-low complexity (e.g., about 10s of bits / sec), ultra-low power consumption (e.g., about 10+ years battery life), and deep coverage with the ability to reach challenging locations; (2) including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) providing services with enhanced mobile broadband (including extremely high capacity (e.g., about 10Tbps / km 2 ), coverage of extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization).

[0050] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. 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). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically referred to (interchangeably) as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is typically (interchangeably) referred to as the “millimeter wave” (mmWave) band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “mmWave” band by the International Telecommunication Union (ITU).

[0051] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used herein, the term "mmWave" or the like can broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0052] 5G NR devices, networks, and systems may be implemented using optimized OFDM-based waveform features. These features may include scalable parameter sets and transmit time intervals (TTIs); a common flexible framework that efficiently multiplexes services and features using dynamic, low-latency time division duplex (TDD) designs or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can efficiently address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD or TDD implementations, the subcarrier spacing may appear at 15kHz, such as over bandwidths of 1MHz, 5MHz, 10MHz, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz over 80MHz / 100MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, the subcarrier spacing may occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments transmitting over mmWave components at 28GHz TDD, the subcarrier spacing may occur at 120kHz over a 500MHz bandwidth.

[0053] 5G NR's scalable parameter set facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design in which uplink or downlink scheduling information, data, and acknowledgments are located in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0054] For clarity, certain aspects of devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0055] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum depending on load and availability. Thus, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein may be applied to other communication systems and applications beyond the specific examples provided.

[0056] Although various aspects and specific implementations are described in this application by the illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementation or use can be implemented via integrated chip specific implementation or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail equipment or purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of specific implementation can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems containing one or more described aspects. In some practical environments, the equipment in combination with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be implemented in a wide variety of embodiments of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0057] Figure 1 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in are likely to have related corresponding components in other network arrangements (including, for example, cellular-style network arrangements and non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.)).

[0058] Figure 1The illustrated wireless network 100 includes multiple base stations 105 and other network entities. A base station may be a station that communicates with a UE, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In a specific implementation of the wireless network 100 herein, the base station 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in a specific implementation of the wireless network 100 herein, the base station 105 may provide wireless communication using one or more frequencies (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof) in the same frequency as an adjacent cell. In some examples, a separate base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0059] A base station may provide communication coverage for a macro cell or a small cell (such as a pico cell or a femto cell) or other types of cells. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with a service subscription with a network provider. A small cell (such as a pico cell) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription with a network provider. A small cell (such as a femto cell) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c use their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0060] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous or asynchronous operation.

[0061] UE 115 is dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that although in the standards and specifications promulgated by 3GPP, mobile devices are generally referred to as UEs, such devices may be additionally or otherwise referred to as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, mobile phones, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices or vehicle modules or some other suitable terminology by those skilled in the art. Within this document, a "mobile" device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices, such as specific implementations that may include one or more UE 115, include mobile phones, cellular phones, smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet computers, and personal digital assistants (PDAs). The mobile device may additionally be an IoT or "Internet of Everything" (IoE) device, such as a car or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-rotor helicopter, a quad-rotor helicopter, a smart energy or security device, a solar panel or solar array, city lighting, tap water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, the UE may be a device including a universal integrated circuit card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The illustrated specific implementation UE 115a-115d is an example of a mobile smart phone type device accessing the wireless network 100. A UE may also be a machine specifically configured for connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The illustrated UEs 115e - 115k are examples of various machines that access the wireless network 100 and are configured for communication.

[0062] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication link (represented as a lightning ball) indicates the wireless transmission between the UE and the serving base station (which is a base station designated to serve the UE on the downlink or uplink) or the expected transmission between the base stations and the backhaul transmission between the base stations. The UE may operate as a base station or other network node in some scenarios. The backhaul communication between the base stations of the wireless network 100 may be performed using a wired or wireless communication link.

[0063] In operation, at the wireless network 100, base stations 105a-105c use 3D beamforming and collaborative spatial techniques (such as coordinated multi-point (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0064] The wireless network 100 of the specific implementation supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e as drones. The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine type devices such as UE 115f (thermometer), UE 115g (smart meter) and UE 115h (wearable device) can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which is then reported to the network through small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD communications or low-latency FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e.

[0065] Figure 2 1 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be Figure 1 For a restricted association scenario (as described above), base station 105 may be any one of the base stations in the UE and one of the UEs. Figure 1 The small cell base station 105f in the example of FIG. 105 and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the list of accessible UEs of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown in FIG. 1 , the base station 105 may be equipped with antennas 234a through 234t and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communication.

[0066] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (such as a processor). The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, the transmit processor 220 may process (e.g., encode and symbol map) the data and the control information, respectively, to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a to 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include pre-coding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., analog-convert, amplify, filter, and up-convert it) to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0067] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols when necessary, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller 280, such as a processor.

[0068] On the uplink, at the UE 115, the transmit processor 264 may receive and process data from the data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from the controller 280 (e.g., for a physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, if necessary, further processed by the modulators 254a to 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if necessary, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller 240 .

[0069] The controllers 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as performing or directing Figure 4 , Figure 5 , Figure 6 , Fig.10 or Fig.11 Execution of the illustrated processes or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0070] In some cases, the UE 115 and the base station 105 may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or the base station 105 may traditionally perform a medium sensing procedure to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-send (LBT) procedure (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some specific implementations, the CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. In particular, a signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating the use of the channel. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT procedure may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets (as a manifestation of a collision).

[0071] The deployment of a communication system (such as a 5G New Radio (NR) system) can 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 a network equipment (such as a base station (BS), or one or more units (or one or more components) performing base station functionality can 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 receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0072] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack 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, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0073] Base station type operations or network designs 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.

[0074] Figure 3A , Figure 3B and Figure 3C An example of full-duplex communication mode is shown. Figure 3A In FIG. 1 , a full-duplex base station and a half-duplex UE operation are shown. Figure 3B In FIG. 1 , a full-duplex base station and a full-duplex UE operation are shown, and in FIG. Figure 3C , full-duplex UE operation (e.g., sub-band full-duplex (SBFD) UE operation) utilizing a full-duplex base station with multiple TRPs is shown. Full-duplex operation corresponds to sending and / or receiving data via multiple antennas at the same time. Half-duplex operation corresponds to sending or receiving data via a single antenna at a specific time.

[0075] Figure 3A , Figure 3B and Figure 3CInterference caused by full-duplex operation is depicted. For illustration, external interference (e.g., channel link interference) and self-interference may be caused during full-duplex operation. External interference is caused by external sources such as by nearby UEs or base stations. Self-interference is caused by the device itself that performs multiple operations. Self-interference may be caused by leakage, such as when transmit energy from a transmit antenna is received by a receive antenna directly or indirectly (e.g., by reflection).

[0076] exist Figure 3A , Figure 3B and Figure 3C In the example, multiple TRPs are illustrated, such as a first TRP (TRP1) and a second TRP (TRP2). The first TRP and the second TRP may include or correspond to the same base station (such as the same gNB) or to different base stations. Figure 3A , Figure 3B and Figure 3C In the embodiment, the first TRP (TRP1) can operate in the same frequency band or in different frequency bands. For example, the first TRP (TRP1) can operate in a first frequency band such as FR 4 or 60 GHz, and the second TRP (TRP2) can operate in a second frequency band such as FR 2 or 28 GHz.

[0077] Additionally, Figure 3A , Figure 3B and Figure 3C A plurality of UEs are illustrated in FIG. 1 , such as a first UE (UE1) and a second UE (UE2). In some implementations, the UE is a full-duplex capable UE with multiple antenna modules. Figure 3A , Figure 3B and Figure 3C The signal path between the TRP and the UE is further depicted.

[0078] refer to Figure 3A , Figure 3A An example diagram 300 for a first type of full-duplex communication is illustrated. Figure 3A , diagram 300 illustrates two signal paths (beam paths) between a TRP and a UE and example interference. Figure 3A In the illustrated example, a first TRP (TRP1) transmits downlink data to a first UE (UE1) via a first signal path, and a first TRP (TRP2) receives uplink data from a second UE (UE2) via a second signal path. The first TRP and the UE experience interference. For example, the first TRP experiences self-interference from simultaneous transmission and reception. Additionally, the device receives interference caused by other nearby devices. For example, the operation of the second TRP 2 may be performed at all other nodes such as Figure 3AThe illustrated first UE and the first TRP cause interference. Additionally, the transmission of uplink data by the second UE may cause interference at the first UE (as shown) and at the second TRP. Operations at the second TRP may also be performed at other devices such as Figure 3A Interference is caused at the first TRP shown.

[0079] refer to Figure 3B , Figure 3B An example diagram 310 for a second type of full-duplex communication is illustrated. Figure 3B , diagram 310 illustrates three signal paths (beam paths) between a TRP and a UE and example interference. Figure 3B In the illustrated example, a first TRP (TRP1) transmits downlink data to a first UE (UE1) via a first signal path, and the first TRP (TRP1) receives uplink data from the first UE (UE1) via a second signal path. Additionally, a second TRP (TRP2) transmits downlink data to a second UE (UE2) via a third signal path. The first TRP experiences interference. For example, the first TRP experiences self-interference from simultaneous transmission and reception and from the operation of the second TRP and the UE. Additionally, other devices may receive interference caused by the operation of other nearby devices, such as reference Figure 3A described.

[0080] refer to Figure 3C , Figure 3C An example diagram 320 for a third type of full-duplex communication is illustrated. Figure 3C , diagram 320 illustrates three signal paths (beam paths) between a TRP and a UE and example interference. Figure 3C In the illustrated example, a first TRP (TRP1) receives uplink data from a first UE (UE1) via a first signal path, and a second TRP (TRP2) sends downlink data to the first UE via a second signal path and sends downlink data to a second UE (UE2) via a third signal path. These devices may receive interference caused by their own full-duplex operation and / or the operation of other nearby devices, as shown in FIG. Figure 3A and Figure 3B described.

[0081] Figure 3D , Figure 3E and Figure 3F An example of full-duplex communication operation is shown. Figure 3D and Figure 3F In-band full-duplex (IBFD) operation is shown in Figure 3E Sub-band full-duplex operation is shown in FIG. In-band full-duplex (IBFD) operation corresponds to transmitting and receiving on the same time and frequency resources. Figure 3D 330 and Figure 3E As shown in the diagram 340 of FIG. 340 , downlink and uplink resources share the same time and frequency resources. The downlink and uplink resources may overlap completely or partially, as shown in FIG. Figure 3D and Figure 3E Sub-band full-duplex operation, often referred to as frequency division duplex (FDD) or flexible duplex, corresponds to sending and receiving data simultaneously but on different frequency resources. Figure 3F As shown in FIG. 350 , downlink resources are separated from uplink resources by a relatively “thin” guard band. Figure 3F A guard band is what typically distinguishes SBFD from paired spectrum (eg, IBFD) in current wireless standard specifications.

[0082] Figure 3G An example of a table of FDRA lengths for RBG sizes for a given combination of corresponding BWP sizes is illustrated. Figure 3G The RBG size table 360 ​​is illustrated. Figure 3G , configurations 1 and 2 correspond to the configurations of the FDRA field. Configuration 1 indicates a 9-bit length FDRA field and a 9-bit bitmap, and configuration 2 indicates an 18-bit length FDRA field and an 18-bit bitmap. Based on the size of the BWP (e.g., an active BWP or a configured BWP), the device may determine the RBG size. For example, based on the BWP size being 1 to 36 resource blocks and the configuration being 1, the RBG size is 2, i.e., 2 RBGs per bit in the bitmap represented by FDRA.

[0083] Figure 3H is a diagram of an example antenna layout, and Fig. 3I is a diagram of an example timing diagram. Figure 3J is exemplified in Fig. 3I The timing diagram for Figure 3H Schematic diagram of the antenna operation of the antenna layout. Figure 3K is exemplified in Fig. 3I The timing diagram for Figure 3H Illustration of antenna leakage for an antenna layout of FIG.

[0084] refer to Figure 3H , illustrates an antenna architecture with two separate panels for simultaneous transmit and receive operation (full duplex (FD) operation). In some implementations, panel #1 is used for DL ​​transmission at both edges of the band, and panel #2 is used for UL reception at the middle of the band. This architecture can improve isolation by more than 50 dB, for example.

[0085] When operating in sub-band full-duplex, the isolation can be improved by more than 40 dB by locating the downlink and uplink in different parts of the frequency band and locating the guard band between the uplink and downlink parts and by utilizing one or more other improvements. The improvements can include using receive weighted overlap and add (WOLA) to reduce adjacent channel leakage ratio (ACLR) leakage to the uplink signal, including an analog low pass filter (LPF) to improve the dynamic range of the analog-to-digital converter (ADC), and / or including improvements to the receive automatic gain control (AGC) state to improve the noise figure (NF).

[0086] In addition or alternatively to such improvements, digital integrated circuits for ACLR may result in improvements of 20 dB or more by using nonlinear models for each transmit and receive pair.

[0087] refer to Fig. 3I , illustrates an example timing diagram for FDD, where both panels are operating, i.e., in full-duplex operation. Figure 3J Example Fig. 3I During the timing diagram Figure 3H How to operate the panel. Figure 3K Example Fig. 3I During the timing diagram Figure 3H antenna performance.

[0088] By avoiding switching BWP, the network can configure the time slot more flexibly, resulting in higher throughput and less overhead. Additionally, the network will have much smaller latency. For example, the delay incurred in BWP switching depends on time and UE capabilities. For illustration, the time slot length (time in milliseconds) and the type of UE (type 1 or type 2) can be used to determine the delay for switching BWP in the time slot. The delay can also depend on the subcarrier spacing.

[0089] Figure 4 An example of a wireless communication system 400 supporting enhanced frequency domain resource allocation according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 400 can implement aspects of the wireless communication system 100. For example, the wireless communication system 400 may include a network such as one or more network entities and one or more UEs such as UE 115 (also referred to as a first UE) and a second UE 403. Figure 4 As illustrated in the example of , the network entity includes an entity corresponding to a base station such as base station 105. Alternatively, the network entity may include or correspond to a different network device (e.g., not a base station). Enhanced frequency domain resource allocation can reduce latency and increase throughput. For example, avoiding switching BWP reduces latency and increases throughput by avoiding delays incurred in switching BWP. Therefore, network and device performance can be improved.

[0090] The base station 105, the UE 115, and the second UE 403 may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. 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). The frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is typically referred to (interchangeably) as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is typically (interchangeably) referred to as the “mmWave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the “mmWave” band by the International Telecommunication Union (ITU).

[0091] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, it can broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if used herein, the term "mmWave" or the like can broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0092] It should be noted that for some data channels, the SCS may be equal to 15kHz, 30kHz, 60kHz, or 120kHz. The base station 105 and the UE 115 may be configured to communicate via one or more component carriers (CCs), such as a representative first CC 481, a second CC 482, a third CC 483, and a fourth CC 484. Although four CCs are shown, this is for illustration only, and more or less than four CCs may be used. One or more CCs may be used to convey control channel transmissions, data channel transmissions, and / or sidelink channel transmissions.

[0093] Such transmissions may include a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), or a physical sidelink feedback channel (PSFCH). Such transmissions may be scheduled by aperiodic grants and / or periodic grants.

[0094] Each periodic grant may have a corresponding configuration, such as configuration parameters / settings. The periodic grant configuration may include a configured grant (CG) configuration and settings. Additionally or alternatively, one or more periodic grants (e.g., their CGs) may have or be assigned to a CC ID, such as an expected CC ID.

[0095] Each CC may have a corresponding configuration, such as a configuration parameter / setting. The configuration may include bandwidth, bandwidth portion, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof. Additionally or alternatively, one or more CCs may have or be assigned a cell ID or a bandwidth portion (BWP) ID. The cell ID may include a unique cell ID for the CC, a virtual cell ID, or a specific cell ID for a specific CC in multiple CCs. Additionally or alternatively, one or more CCs may have or be assigned a HARQ ID. Each CC may also have corresponding management functions, such as beam management or BWP switching functionality. In some implementations, two or more CCs are quasi-co-located so that the CCs have the same beam and / or the same symbol.

[0096] In some implementations, the control information may be communicated via the base station 105, the UE 115, and the second UE 403. For example, the control information may be communicated using a MAC-CE transmission, an RRC transmission, a DCI (downlink control information) transmission, an UCI (uplink control information) transmission, an SCI (sidelink control information) transmission, another transmission, or a combination thereof.

[0097] The UE 115 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 402, a memory 404, a transmitter 410, a receiver 412, an encoder 413, a decoder 414, a resource manager 415, a SBFD manager 416, and antennas 252a-r. The processor 402 may be configured to execute instructions stored at the memory 404 to perform the operations described herein. In some specific implementations, the processor 402 includes or corresponds to the controller / processor 280, and the memory 404 includes or corresponds to the memory 282. The memory 404 may also be configured to store resource allocation information data 406, carrier information data 408, spectrum information data 442, setting data 444, or a combination thereof, as further described herein.

[0098] Resource allocation information data 406 includes or corresponds to data associated with or corresponding to resources of a bandwidth allocated for a particular transmission (or multiple transmissions) in a time slot. For example, resource allocation information data 406 may include resource element data. Resource element (RE) data may include data about physical layer resource elements such as resource blocks or groups thereof. Resource element data may include the number of RE groups (or RB groups (RBGs)) and / or identification of RBGs (such as by offset from a reference or core RBG). In some implementations, resource element data is indicated by a bitmap of RBGs corresponding to an active BWP. As explained in more detail below, the bitmap may correspond to the entirety of the RBGs of a BWP, or only to RBGs of a BWP that partially or completely overlap with a corresponding transmission band (e.g., a DL transmission band for a DL BWP).

[0099] In other examples, the resource element data may include a starting resource element for a particular transmission and a number of resource elements (e.g., consecutive or contiguous REs) for the particular transmission. In such implementations, the resource element data may be associated with or referred to as resource information or timing information. For example, a single indicator (e.g., a resource indicator value (RIV) or a start and length indicator value (SLIV)) may be used to indicate both the starting RE (or RB) and the number (e.g., quantity or amount) of REs (or RBs).

[0100] In some implementations, the resource allocation information data 406 also includes timing information, such as TDRA information. The timing information may be included in or indicated by the TDRA field. The timing information may indicate a specific time slot for transmission. For example, the TDRA field may indicate an offset of a time or time slot for a specific transmission and may be associated with other transmission information such as FDRA information. The timing information may be used to determine a specific time slot configuration by identifying the time slot.

[0101] Additionally or alternatively, the resource allocation information data 406 may include resource configuration data. The resource configuration data may include or correspond to a value identifying or indicating an RBG size. The RBG size may include or correspond to a value identifying the number of RBs per group. The number of REs per RB may be fixed by the network or otherwise indicated, such as by an RB size indication. Each BWP and / or subband may have its own RBG size, and therefore, the resource configuration data may include a BWP or band-specific RBG size. The resource allocation information data 406 may include data received from the network (e.g., base station 105) and / or programmed into the memory 404. The resource allocation information data 406 may be configured by RRC and / or modified by MAC-CE, DCI, and / or other control signaling (e.g., broadcast spectrum control signaling).

[0102] The carrier information data 408 includes or corresponds to data associated with or corresponding to a carrier configuration. For example, the carrier information data 408 may include carrier configuration information. The carrier configuration information may include information about one or more settings or parameters for a component carrier, a channel, and / or a cell. For example, the carrier configuration information may include RBG size information, transmission type information, time slot type information, channel bandwidth information, frequency band information, SCS information, bandwidth part (BWP) information, etc.

[0103] The transmission type information may include or correspond to information indicating an operating mode or non-full-duplex time slot format, uplink, downlink, sidelink, broadcast, etc. The time slot type information may include information indicating a specific time slot configuration of multiple time slots of a frame, a location and size of a frequency band or a sub-band thereof. For example, the time slot type may include an indication of UL, DL, and mixed full-duplex time slot configurations for each time slot of a radio frame or subframe. Additionally, the time slot type information may include multiple types of full-duplex configurations and sub-types. For example, the time slot type information may include within-band non-overlapping (SBFD), partially overlapping, or fully overlapping configurations (such as Figures 3D to 3F As shown) and one or more sub-configurations for each type, such as 7A to 9B The BWP information includes or indicates one or more configured BWPs and an active BWP. The BWP information may also include or indicate a BWP size and placement of one or more of the configured BWPs.

[0104] The spectrum information data 442 includes or corresponds to data indicating or corresponding to spectrum allocation and / or configuration. For example, the spectrum information data 442 may include or correspond to spectrum configuration data. The spectrum configuration data may include configuration information for different spectrums such as LTE, 5G, FR1, FR2, terrestrial broadcast, etc. For example, the spectrum configuration data may include out-of-band emission (OOBE) requirements or spectrum efficiency masks (SEM). Such settings may be used to determine the amount of resource blocks and / or the spacing of guard bands between different sub-bands used for time slots.

[0105] The scheduling information may include or indicate one or more pieces of information used to schedule one or more specific transmissions. For example, the scheduling information may include or indicate one or more of the resource allocation information data 406, the carrier information data 408, or the spectrum information data 442.

[0106] The scheduling information may include one or more pieces of component information. In a specific example, the scheduling information includes configuration information (e.g., channel configuration information) and resource allocation information. In some implementations, the resource allocation information includes timing information, and in other implementations, the scheduling information includes timing information.

[0107] The setting data 444 includes or corresponds to data associated with the enhanced frequency domain resource allocation operation. The setting data 444 may include one or more types of enhanced frequency domain resource allocation operation modes and / or thresholds or conditions for switching between enhanced frequency domain resource allocation operation modes and / or their configurations. For example, the setting data 444 may have data indicating different thresholds and / or conditions for different enhanced frequency domain resource allocation modes such as fixed length field mode, transmission overlap mode, no transmission overlap mode, variable length field mode, etc., or combinations thereof.

[0108] The transmitter 410 is configured to send data to one or more other devices, and the receiver 412 is configured to receive data from one or more other devices. For example, the transmitter 410 may send data via a network such as a wired network, a wireless network, or a combination thereof, and the receiver 412 may receive data via the network. For example, the UE 115 may be configured to send and / or receive data via: a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that allows two or more electronic devices to communicate therein. In some specific implementations, the transmitter 410 and the receiver 412 may be replaced by a transceiver. Additionally or alternatively, the transmitter 410 or the receiver 412 may include or correspond to the reference Figure 2 One or more components of the UE 115.

[0109] The encoder 413 and the decoder 414 may be configured to encode and decode data for transmission. The resource manager 415 (or resource allocation manager) may be configured to perform resource allocation determination operations. For example, the resource manager 415 may be configured to determine and / or indicate resources for a particular transmission based on a bitmap. For illustration, the resource manager 415 may determine a non-contiguous subset of resource elements from a larger pool of resource elements based on a bitmap, wherein the subset of resource elements overlaps an applicable transmission band or subband.

[0110] In some implementations, the resource manager 415 determines resource block groups (RBGs) based on a bitmap that include a variable number of RBs and each RB includes multiple REs. The RBG representing the transmission bandwidth corresponds to the position of a bit of the bitmap having a specific value, such as 0 or 1. The resource manager 415 can be configured to interpret the FDRA field to determine resource allocation. The FDRA field can be interpreted based on a time slot configuration, such as where a subband is located in a given time slot and overlaps with an active BWP. The resource manager 415 can determine the valid bits of a preset length field (e.g., a 9 or 18-bit length field), i.e., which bits of the FDRA field carry resource allocation information (e.g., FDRA information) and which bits of the FDRA field carry non-resource allocation information, or when the field has a variable length, the resource manager 415 can determine the length (number of bits) of the field carrying resource allocation information (e.g., the FDRA field). Reference 7A to 8B Examples of determining significant bits are further shown and described, and reference is made to FIG. 9A to FIG. 9B Examples of determining variable field lengths are further shown and described.

[0111] The SBFD manager 416 may be configured to perform improved SBFD operations, such as time slot configuration and timing operations for SBFD. For example, the SBFD manager 416 may be configured for timing of a particular transmission. For illustration, the SBFD manager 416 may receive timing information such as a TDRA field and determine a particular time slot for a corresponding transmission based on the timing information. The TDRA field may be associated with the FDRA.

[0112] Additionally, the SBFD manager 416 may be configured to determine a slot configuration for a particular time slot and transmission. For example, the SBFD manager 416 may be configured to receive slot type information, such as via RRC, and may determine a slot configuration for a plurality of time slots, such as a plurality of time slots of a radio frame. For illustration, the slot type information may indicate that a first time slot is a DL time slot, a second time slot is a UP time slot, a third time slot is a FD type 1, a fourth time slot is a SBFD type 1, a fifth time slot is a SBFD type 2, etc., and each time slot has its own slot configuration indicating the frequency band or subband of the time slot. Examples of time slot configurations are described in Figures 3D to 3F and 7A to 9B SBFD manager 416 may be configured to determine a timeslot configuration for a particular timeslot and transmission based on a timeslot type / configuration matching the timeslot identified by the timing information.

[0113] The second UE 403 may include one or more elements similar to the UE 115. In some implementations, the UE 115 and the second UE 403 are different types of UEs. For example, either UE may be of higher quality or have different operating constraints. For illustration, one of the UEs may have a larger form factor or may be a current generation device and therefore have more advanced capabilities and / or reduced battery constraints, higher processing constraints, etc.

[0114] The base station 105 includes a processor 430, a memory 432, a transmitter 434, a receiver 436, an encoder 437, a decoder 438, a resource manager 439, a SBFD manager 440, and antennas 234a-t. The processor 430 may be configured to execute instructions stored at the memory 432 to perform the operations described herein. In some implementations, the processor 430 includes or corresponds to the controller / processor 240, and the memory 432 includes or corresponds to the memory 242. The memory 432 may be configured to store resource allocation information data 406, carrier information data 408, spectrum information data 442, setting data 444, or a combination thereof, similar to the UE 115 and as further described herein.

[0115] The transmitter 434 is configured to send data to one or more other devices, and the receiver 436 is configured to receive data from one or more other devices. For example, the transmitter 434 may send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 436 may receive data via the network. For example, the UE and / or the base station 105 may be configured to send and / or receive data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that allows two or more electronic devices to communicate. In some specific implementations, the transmitter 434 and the receiver 436 may be replaced by a transceiver. Additionally or alternatively, the transmitter 434 or the receiver 436 may include or correspond to the reference Figure 2 One or more components of the UE 115.

[0116] The encoder 437 and the decoder 438 may include the same functionality as described with reference to the encoder 413 and the decoder 414, respectively. The resource manager 439 may include similar functionality as described with reference to the resource manager 415. For example, the resource manager 439 may be configured to determine and generate resource allocation information (e.g., FDRA field) for the time slot and transmission, which may be interpreted by another device based on the time slot configuration of the time slot. The SBFD manager 440 may include similar functionality as described with reference to the SBFD manager 416.

[0117] During operation of the wireless communication system 400, the network (e.g., the base station 105) may determine that the UE 115 has enhanced frequency domain resource allocation capabilities. For example, the UE 115 may send a message 448 including an enhanced frequency domain resource allocation indicator 490 (e.g., an enhanced frequency domain resource allocation capability indicator). The indicator 490 may indicate enhanced frequency domain resource allocation capabilities for one or more communication modes such as downlink, uplink, etc. In some embodiments, the network entity (e.g., the base station 105) transmits control information to indicate to the UE 115 that an enhanced frequency domain resource allocation operation and / or a specific type of enhanced frequency domain resource allocation operation is to be used. For example, in some embodiments, a configuration transmission 450 is sent to the UE 115. The configuration transmission 450 may include or indicate the use of an enhanced frequency domain resource allocation operation or the adjustment or implementation of a specific type of enhanced frequency domain resource allocation operation. For example, the configuration transmission 450 may include carrier information data 408 (e.g., Figure 4 ), spectrum information data 442, setting data 444, or any combination thereof.

[0118] During operation, the devices of the wireless communication system 400 perform enhanced frequency domain resource allocation operations. For example, the network and the UE 115 may exchange transmissions via uplink and / or downlink communications in a full duplex mode (e.g., SBFD mode) with enhanced resource allocation flexibility, such as Figure 4 This enhanced resource allocation flexibility enables the device to adjust resources and increase throughput by operating in FD (analog transmission and reception) without switching BWP and incurring switching delays. Enhanced resource allocation flexibility can be achieved by using variable-length resource allocation information, where the length of the resource allocation information indicates the transmission bandwidth (and which RBGs are used for transmission). The device can determine the variable-length resource allocation information (the effective bits of the preset length field or the length of the variable length field) based on the transmission type or time slot configuration information.

[0119] exist Figure 4In the example of , the base station 105 optionally sends a configuration message 452 to the UE 115 via a downlink channel. In some specific implementations, the configuration message 452 includes time slot type information or transmission type information. For example, the time slot type information may include information indicating a specific time slot configuration of a time slot of a frame, a location and size of a frequency band or subband. For another example, the transmission type information may indicate UL, DL, half-duplex (HD), FD, etc. The configuration message 452 corresponds to Figure 4 In other specific implementations, the configuration message 452 may include or correspond to a broadcast message, a PDCCH, an SCI, a SL-MAC-CE, or a SL-RRC message.

[0120] Additionally or alternatively, the configuration message 452 may include bandwidth portion information or RBG size information. For example, the configuration message 452 may indicate a plurality of configured BWPs and active BWPs. For another example, the configuration message may indicate the number of RBs per RBG group for each BWP or at least the active BWP.

[0121] The base station 105 sends the resource allocation information 454 to the UE 115 via a downlink channel for a specific transmission in a specific time slot. For example, the base station 105 may send the resource allocation information 454 in a second message or transmission (such as a scheduling or signaling message for the specific transmission) separate from the configuration message 452. Alternatively, in other specific implementations, the base station 105 may send the resource allocation information 454 in the configuration message 452. The message carrying the resource allocation information 454 may be configured to be sent periodically or aperiodically.

[0122] Additionally or alternatively, resource allocation information 454 may be transmitted with other information, such as scheduling information, or as part of other information. Scheduling information may include other types of information, such as timing information (e.g., TDRA field), RBG size, BWP information, or a combination thereof. Resource allocation information 454 may be transmitted in a transmission or message that may include or correspond to a PDCCH transmission, such as a DCI, a PDSCH transmission, a MAC-CE transmission, a SL transmission, a broadcast transmission, etc.

[0123] As an illustrative, non-limiting example, the band (location and channel bandwidth), SCS and parameter set (cyclic prefix) may be indicated in the locationAndBandwidth, subcarrierSpacing and cyclicPrefix fields of the BWP information element, such as indicated in the IE BWP. The bandwidth part and its information may be further configured by the IE ServingCellConfig. The number of consecutive RBs may be indicated for resource allocation type 0 using the higher layer parameter rbg-Size configured by PDSCH-Config, or for resource allocation type 1 using a resource indication value (RIV) that provides both the starting RB number and the length in terms of consecutive resource blocks.

[0124] The UE 115 determines resource allocations for a particular time slot and transmission based on at least the resource allocation information 454. For example, the UE 115 parses or interprets information fields corresponding to the resource allocation information 454 based on the active BWP and the time slot configuration. For illustration, the UE 115 may receive and / or determine the active BWP or time slot configuration based on the configuration message 452 and / or the signaling / scheduling message.

[0125] In some implementations, the UE 115 interprets the field to determine the valid bits of the field. For example, the field may include or correspond to a bitmap, wherein the bits of the bitmap are mapped to or correspond to the RBGs of the active BWP portion. The UE 115 may determine that a particular bit of the bitmap is active or potentially usable for transmission in the time slot based on the time slot configuration of the time slot. That is, the UE 115 may determine which RBGs of the active BWP and the corresponding bits of the bitmap coincide or overlap with the frequency band or subband of the time slot. The UE 115 may also determine which RBGs of the active BWP and the corresponding bits of the bitmap do not coincide or overlap with the frequency band or subband of the time slot.

[0126] UE 115 may determine the number and position of the valid bits (the first bits with resource allocation / FDRA information) that are the bits in the bitmap where the corresponding RBG overlaps with the corresponding subband (e.g., DL BWP and DL subband) in which transmission may occur. 7A to 9B The UE 115 may also determine that the second bits (number and position of bits) do not include resource allocation / FDRA information, which are bits in the bitmap where the corresponding RBG does not overlap with the corresponding subband (e.g., DL BWP and DL subband) and indicates where transmission is not possible for this time slot / time slot configuration, as shown in reference 7A to 9B Said and shown.

[0127] In other specific implementations, the UE 115 determines the length of the variable length resource allocation field and interprets or parses the field based on the determined length. For example, the field may include or correspond to a variable length bitmap, where the bits of the bitmap map to or correspond to RBG subsets of the active BWP portion that overlap with corresponding subbands (e.g., DL BWP and DL subband) in which transmission is configurable or possible for the time slot. The UE 115 may determine the number of bits of the bitmap based on the RBG size of each subband. The subbands may have the same RBG size or different RBG sizes. Based on the amount of overlap and the amount of RBG size, the UE 115 may determine how many bits are needed to convey the overlapping RBGs and the mapping of the RBGs to the bits. For example, as referenced 7A to 9B As described and shown, in the partitioned subbands, based on the overlap amount and RBG size, a 3-bit bitmap may include 1 bit in the first subband and 2 bits in the second subband, or 2 bits in the first subband and 1 bit in the second subband.

[0128] The UE 115 sends or receives one or more transmissions 456 based on the resource allocation information 454. For example, the UE 115 sends or receives one or more transmissions 456 based on the RBGs identified from the resource allocation information 454. For illustration, the UE 115 may send or receive transmissions using specific RBGs identified by a bitmap indicated by the resource allocation of the signaling / scheduling message.

[0129] In some implementations, the UE 115 sends or receives one or more transmissions 456 based on scheduling information such as configuration information, resource allocation information 454, and timing information. For example, the UE 115 sends or receives one or more transmissions 456 based on one or more of the configuration message 452 and the resource allocation information 454.

[0130] Scheduling information may include or correspond to resource information in a specific domain. For example, scheduling information may include or correspond to frequency domain resource assignments (frequency domain resource assignment information) or timing domain resource assignments (timing domain resource assignment information). Scheduling information may include time and / or frequency information for sending resources.

[0131] In some implementations, UE 115 may send or receive additional transmissions (eg, periodically) of transmission 456 based on the scheduling information, as further described in Figure 6 In other specific implementations, UE 115 may send or receive a second transmission (e.g., aperiodic) of transmission 456 based on second scheduling information received in an additional transmission such as a second signaling transmission, as further described in Figure 5 described.

[0132] Therefore, the network (e.g., base station 105, UE 115, and second UE 403) may be able to more efficiently and effectively utilize available spectrum by using more available spectrum through improved flexible scheduling without BWP switching. Improved spectrum utilization through enhanced frequency domain resource allocation may increase throughput and reduce latency, which may result in reduced link failures. Therefore, network performance and experience may be improved due to increased speed and reduced failures.

[0133] refer to Figure 5 , Figure 5 is a timing diagram 500 illustrating a wireless communication system supporting enhanced frequency domain resource allocation according to one or more aspects. Figure 5 The example corresponds to the example of enhanced frequency domain resource allocation for non-periodic operation.

[0134] Figure 5 Examples include Figure 1 , Figure 2 and Figure 4 The devices described are similar to devices such as UE 115 and network entities (eg, base station 105). Figure 5 The equipment may include Figure 2 and Figure 4 One or more of the components described. Figure 5 In the embodiment, these devices may communicate and receive transmissions according to the maximum number of resource elements per frequency band using antennas 252a-r, transmitters 410, receivers 412, encoders 413 and / or decoders 414, or may communicate and receive transmissions according to the maximum number of resource elements per frequency band using antennas 234a-t, transmitters 434, receivers 436, encoders 437 and / or decoders 438. In some implementations, the network entity may include or correspond to multiple TRPs of a single base station (e.g., base station 105), multiple base stations, or any combination thereof.

[0135] At 510, base station 105 sends configuration information to UE 115. For example, base station 105 may send a downlink transmission including the configuration information. Figure 5 As illustrated in the example of , base station 105 sends RRC signaling (e.g., RRC transmission or message) including configuration information to UE 115.

[0136] As reference Figure 4The configuration information may include or indicate a transmission type, bandwidth portion information (e.g., type or size), resource block group information, time slot type, or a combination thereof. For example, the configuration information may include information about time slot configuration details for a plurality of upcoming time slots. The time slot type or configuration information may indicate a UL time slot configuration, a downlink configuration, an FD configuration, or a SBFD configuration (e.g., subband size and position). The downlink transmission may include or correspond to an RRC message, a MAC-CE, a DCI, a PDCCH, or a PDSCH.

[0137] At 515, UE 115 may determine configuration information. For example, UE 115 may receive and parse the transmission from base station 105 at 510 to determine configuration information. The configuration information may include or correspond to reference Figure 4 The configuration information, such as carrier information data 408, spectrum information data 442, or both, may include or indicate time slot type information, transmission type information, BWP information, RBG size information, resource allocation mode information (e.g., type 0 or type 1), or a combination thereof.

[0138] In some implementations, the UE 115 determines a slot configuration for a plurality of upcoming slots based on configuration information such as its slot type information. Determining the slot configuration may include determining a slot type or configuration for a plurality of slots of a frame.

[0139] In some implementations, the UE 115 may optionally determine the active BWP based on the configuration information. For example, the UE 115 determines the size and location of the active BWP based on one or more configured BWPs. Additionally or alternatively, the UE 115 determines the RBG size of the active BWP.

[0140] At 520, the base station 105 sends a signaling indication including resource allocation information. For example, the base station 105 may send the resource allocation information in a downlink transmission. Figure 5 As illustrated in the example of , the base station sends a DCI including resource allocation information. In other specific implementations, the base station 105 may send a PDCCH, a MAC CE, an RRC, or another type of transmission. The resource allocation information may include or correspond to the reference Figure 4 The resource allocation information. For example, the resource allocation information may include or indicate a bitmap for RBG identification or resources using a common reference element and an offset.

[0141] In some implementations, the base station 105 sends a signaling indication including scheduling information such as resource allocation information and / or timing information. The scheduling information may include or correspond to an indication of time and / or frequency information for sending resources. The timing information may include or correspond to timing or time domain resource allocation information (e.g., a TDRA field), and the resource allocation information may include or correspond to frequency domain resource allocation information (e.g., an FDRA field or a portion thereof). In some implementations, the timing and frequency information of the scheduling information are separate, i.e., in separate fields. In other implementations, the timing and frequency information of the scheduling information may be included in a joint field.

[0142] Alternatively, the resource allocation information may indicate the starting resource and the number of resources used for a specific transmission.For illustration, the resource allocation information may include or indicate a RIV for a specific BWP, the RIV indicating the starting resource and the number of resources used for a specific transmission.

[0143] At 525, UE 115 may determine timing information based on receiving the signaling indication at 520 or receiving the configuration information at 510. For example, UE 115 may receive and parse the signaling indication (signaling transmission) to determine or identify the signaling information. The signaling information may include or indicate scheduling information or a portion thereof, such as timing information. Figure 5 As illustrated in the example of , UE 115 receives DCI including an indication of a particular transmission and timing information. Based on the timing information (e.g., TDRA field), UE 115 determines the time slot for the particular transmission. The TDRA field may indicate a time slot offset (K0) from the time slot indicated by the received signaling. The time slot offset may be indirectly indicated by reference to a specific row in an allocation list (e.g., a PDSCH or PUSCH TDRA allocation list) or an indication of the specific row.

[0144] At 530, UE 115 may determine time slot configuration information. For example, UE 115 may determine a time slot configuration or a time slot type for a particular upcoming time slot based on the scheduling information and / or the configuration information. Determining the time slot configuration may include determining a particular future time slot for future transmission (n+5) based on the timing information (e.g., timing offset K0), and determining a particular time slot configuration (e.g., amount and location of frequency bands / subbands) based on the configuration information, such as based on the time slot type information indicating a particular time slot configuration for the indicated time slot.

[0145] At 535, UE 115 may determine resource information. For example, UE 115 may determine resources to use for a particular transmission based on a slot configuration for a particular time slot and resource allocation information. Determining the particular resources to use may include interpreting the resource allocation information based on the slot configuration for the particular time slot to determine a transmission bandwidth for the transmission and which resource elements (e.g., RBGs) are included in the transmission bandwidth.

[0146] In some implementations, a device (e.g., UE 115 or base station 105) determines the amount of active or valid bits of resource allocation information. For example, UE 115 may determine the amount of active or valid bits of resource allocation information based on the currently active BWP and time slot configuration. For illustration, UE 115 may determine the total number of bits in the field (e.g., FDRA field) based on conventional methods (RBG size). Then, UE 115 may determine the valid (or invalid) bits of the field based on the time slot configuration type and BWP type. For example, the UE may determine one or more overlapping portions between an active BWP and a corresponding frequency band or subband (e.g., a DL subband for a DL BWP). The UE may determine which RBGs of a BWP correspond to / overlap the corresponding subbands of a time slot and find such corresponding bits in the FDRA field.

[0147] Determining a valid bit of resource allocation information (of a field) may include determining a position of the valid bit in the resource allocation information. For example, since the resource allocation information may include or correspond to a bitmap, identifying the bit as valid or invalid includes identifying the position. As indicated above, the valid bit may include or correspond to a bit indicating resource allocation information such as FDRA information.

[0148] After identifying the valid bits or identifying the invalid bits, the UE 115 may parse the valid bits. For example, the UE 115 may evaluate the value of each valid bit to determine whether the valid bit indicates that the resource (RBG) is active for the transmission. Based on parsing the valid bits, the UE 115 determines which RBGs are active and included in the transmission bandwidth. The UE 115 may optionally parse the non-valid bits of the resource allocation information (field) to determine one or more other information.

[0149] In other specific implementations, a device (e.g., UE 115 or base station 105) determines the length of the variable length resource allocation information. For example, UE 115 may determine the number of bits of the resource allocation information based on the current active BWP, the slot configuration, and the RBG size information. For illustration, UE 115 may determine the total number of bits in the variable length field for indicating the resource allocation information based on the amount of overlap between the corresponding subbands of the active BWP and the slot configuration. Depending on how much overlap there is, for example, depending on how many RBGs of the active BWP overlap with the corresponding subband, the UE determines how many bits are needed to map each RBG set based on the RBG size. For example, when 24 of the 100 RBGs of the active DL BWP overlap with the DL subband, UE 115 determines that the field length is 6 bits when the RBG size is 4. If the RBG size is 8, the field length will be 3 bits. In some implementations, the RBG size may be different for different subbands, so when a first subband with a first RBG size of 4 overlaps with 8 RBGs and a second subband with a second RBG size of 8 overlaps with 16 RBGs, the field length may be 4 bits.

[0150] After identifying the field length and determining the mapping of bits to RBGs, the UE 115 may parse the bits of the field. For example, the UE 115 may evaluate the value of each bit to determine whether the bit indicates that the corresponding resource (RBG) is active for the transmission. Based on the bits of the parsed field, the UE 115 determines which RBGs are active and included in the transmission bandwidth. Since the field is a variable length field, the overhead for communicating the transmission bandwidth is reduced and more flexible compared to a fixed implementation. Additionally, by reducing the amount of bits, additional information can be included in the signaling message or indication.

[0151] At 540, the base station 105 and the UE 115 communicate one or more transmissions to each other based on the resource allocation information. For example, the base station 105 and the UE 115 may communicate with each other in DL, UL, or FD (e.g., SBFD) based on the transmission bandwidth indicated by the resource allocation information of the signaling message at 520. By utilizing the frequency band, the first maximum number of resources may be larger due to utilization / optimization of resource allocation. A larger maximum number of resources results in a larger individual allocation / transmission bandwidth and increased throughput.

[0152] As an example illustration, UE 115 may: 1) send the transmission in a first subband and receive the second transmission in a second subband; 2) send the transmission in the first subband and send the second transmission in the second subband; 3) receive the transmission in the first subband and send the second transmission in the second subband; 4) receive the transmission in the first subband and receive the second transmission in the second subband; 5) send the transmission in the first subband and retransmit the transmission in the second subband, and receive the second transmission in a third subband located between the first subband and the second subband; or 6) send the transmission in the first subband and the second subband, and receive the second transmission in a third subband located between the first subband and the second subband, all according to the transmission bandwidth and resources indicated by the resource allocation information.

[0153] Optionally, UE 115 and base station 105 may perform one or more additional operations. For example, base station 105 may send a second signaling indication including second scheduling information such as second resource allocation information. UE 115 and base station 105 may perform similar steps 525-540 to communicate one or more second transmissions.

[0154] Therefore, in Figure 5 In an example of FIG. 1 , devices of a network may be able to have more flexible utilization of full-duplex time slot configurations by using flexible resource allocation information.

[0155] refer to Figure 6 , Figure 6 is a timing diagram 600 illustrating a wireless communication system supporting enhanced frequency-domain resource allocation according to one or more aspects. Figure 6 Examples may include or correspond to examples of enhanced frequency domain resource allocation for periodic operation and / or multiple devices.

[0156] Figure 6 Examples include Figure 1 , Figure 2 and Figure 4 The devices described are similar to devices such as UE 115, a network entity (eg, base station 105) and a third wireless communication device (eg, a network node). The network node may include or correspond to a UE or a base station. Figure 6 The equipment may include Figure 2 and Figure 4 One or more of the components described in . Figure 6In the embodiment, these devices may communicate and receive transmissions according to the maximum number of resource elements per frequency band using antennas 252a-r, transmitters 410, receivers 412, encoders 413 and / or decoders 414, or may communicate and receive transmissions according to the maximum number of resource elements per frequency band using antennas 234a-t, transmitters 434, receivers 436, encoders 437 and / or decoders 438. In some implementations, the network entity may include or correspond to multiple TRPs of a single base station (e.g., base station 105), multiple base stations, or any combination thereof.

[0157] At 610, base station 105 sends configuration information to UE 115. For example, base station 105 may send a downlink transmission including the configuration information. Figure 6 As illustrated in the example of , the base station 105 sends RRC signaling (e.g., RRC transmission or message) including configuration information to the UE 115. In some specific implementations, the configuration information includes scheduling information, such as resource allocation information and / or timing information. The downlink transmission may include or correspond to an RRC message, a MAC-CE, a DCI, a PDCCH, or a PDSCH.

[0158] The configuration information and scheduling information may indicate or include the above reference Figure 4 and Figure 5 Additionally, the resource allocation information and / or timing information may indicate or include the information referred to above. Figure 4 and Figure 5 The information described.

[0159] At 615, UE 115 may determine the configuration information. For example, UE 115 may receive and parse the transmission from base station 105 at 610 to determine the configuration information, as described in reference to Figure 5 as described in 515.

[0160] In some implementations, the UE 115 determines a slot configuration for a plurality of upcoming slots based on configuration information such as its slot type information. Determining the slot configuration may include determining a slot type or configuration for a plurality of slots of a frame.

[0161] In some implementations, the UE 115 may optionally determine the active BWP based on the configuration information. For example, the UE 115 determines the size and location of the active BWP based on one or more configured BWPs. Additionally or alternatively, the UE 115 determines the RBG size of the active BWP.

[0162] At 620, UE 115 may determine timing information based on receiving the configuration indication at 610. For example, UE 115 may receive and parse the periodic grant to determine or identify scheduling information (e.g., periodic scheduling information). The periodic scheduling information may include or indicate scheduling information for multiple transmissions, such as multiple transmissions over multiple time slots. For illustration, UE 115 may determine timing information for multiple transmissions, such as by indicating an offset and period for repeating grants and / or transmissions.

[0163] At 625, UE 115 may determine time slot configuration information. For example, UE 115 may determine a time slot configuration or a time slot type for a plurality of upcoming time slots based on the scheduling information and / or the configuration information. Determining the time slot configuration may include determining a specific future time slot for the first future transmission (n+5) based on the timing information (e.g., timing offset K0), and determining a corresponding time slot configuration (e.g., amount and location of frequency bands / subbands) based on the configuration information, such as based on the time slot type information indicating a specific time slot configuration for the indicated time slot.

[0164] At 630, UE 115 may determine resource information. For example, UE 115 may determine resources to use for a particular transmission based on a slot configuration for a particular time slot and resource allocation information. Determining the particular resources to use may include interpreting the resource allocation information based on the slot configuration for the particular time slot to determine a transmission bandwidth for the transmission and which resource elements (e.g., RBGs) are included in the transmission bandwidth.

[0165] In some implementations, a device (e.g., UE 115 or base station 105) determines the amount of active or valid bits of resource allocation information. For example, UE 115 may determine the amount of active or valid bits of resource allocation information based on the currently active BWP and time slot configuration. For illustration, UE 115 may determine the total number of bits in the field (e.g., FDRA field) based on conventional methods (RBG size). Then, UE 115 may determine the valid (or invalid) bits of the field based on the time slot configuration type and BWP type. For example, the UE may determine one or more overlapping portions between an active BWP and a corresponding frequency band or subband (e.g., a DL subband for a DL BWP). The UE may determine which RBGs of a BWP correspond to / overlap the corresponding subbands of a time slot and find such corresponding bits in the FDRA field.

[0166] Determining a valid bit of resource allocation information (of a field) may include determining a position of the valid bit in the resource allocation information. For example, since the resource allocation information may include or correspond to a bitmap, identifying the bit as valid or invalid includes identifying the position. As indicated above, the valid bit may include or correspond to a bit indicating resource allocation information such as FDRA information.

[0167] After identifying the valid bits or identifying the invalid bits, the UE 115 may parse the valid bits. For example, the UE 115 may evaluate the value of each valid bit to determine whether the valid bit indicates that the resource (RBG) is active for the transmission. Based on parsing the valid bits, the UE 115 determines which RBGs are active and included in the transmission bandwidth. The UE 115 may optionally parse the non-valid bits of the resource allocation information (field) to determine one or more other information.

[0168] In other specific implementations, a device (e.g., UE 115 or base station 105) determines the length of the variable length resource allocation information. For example, UE 115 may determine the number of bits of the resource allocation information based on the current active BWP, the slot configuration, and the RBG size information. For illustration, UE 115 may determine the total number of bits in the variable length field for indicating the resource allocation information based on the amount of overlap between the corresponding subbands of the active BWP and the slot configuration. Depending on how much overlap there is, for example, depending on how many RBGs of the active BWP overlap with the corresponding subband, the UE determines how many bits are needed to map each RBG set based on the RBG size. For example, when 24 of the 100 RBGs of the active DL BWP overlap with the DL subband, UE 115 determines that the field length is 6 bits when the RBG size is 4. If the RBG size is 8, the field length will be 3 bits. In some implementations, the RBG size may be different for different subbands, so when a first subband with a first RBG size of 4 overlaps with 8 RBGs and a second subband with a second RBG size of 8 overlaps with 16 RBGs, the field length may be 4 bits.

[0169] After identifying the field length and determining the mapping of bits to RBGs, the UE 115 may parse the bits of the field. For example, the UE 115 may evaluate the value of each bit to determine whether the bit indicates that the corresponding resource (RBG) is active for the transmission. Based on the bits of the parsed field, the UE 115 determines which RBGs are active and included in the transmission bandwidth. Since the field is a variable length field, the overhead for communicating the transmission bandwidth is reduced and more flexible compared to a fixed implementation. Additionally, by reducing the amount of bits, additional information can be included in the signaling message or indication.

[0170] At 635, the base station 105 and the UE 115 communicate one or more transmissions with each other and / or a third device for the first time slot based on the resource allocation information. For example, the UE 115 may communicate with the base station 105 and / or the third device in DL, UL, or FD (e.g., SBFD) based on the transmission bandwidth indicated by the resource allocation information of the signaling message at 620. By utilizing the frequency band, the first maximum number of resources may be larger due to utilization / optimization of resource allocation. A larger maximum number of resources results in a larger individual allocation / transmission bandwidth and increased throughput.

[0171] As an example illustration, UE 115 may: 1) send the transmission in a first subband and receive the second transmission in a second subband; 2) send the transmission in the first subband and send the second transmission in the second subband; 3) receive the transmission in the first subband and send the second transmission in the second subband; 4) receive the transmission in the first subband and receive the second transmission in the second subband; 5) send the transmission in the first subband and retransmit the transmission in the second subband, and receive the second transmission in a third subband located between the first subband and the second subband; or 6) send the transmission in the first subband and the second subband, and receive the second transmission in a third subband located between the first subband and the second subband, all according to the transmission bandwidth and resources indicated by the resource allocation information.

[0172] At 640, the base station 105 and the UE 115 communicate one or more transmissions with each other and / or a third device for the second time slot based on the second resource allocation information. For example, the UE 115 may communicate with the base station 105 and / or the third device in DL, UL, or FD (e.g., SBFD) based on the second transmission bandwidth indicated by the second resource allocation information.

[0173] In some implementations, the second resource allocation information may be the same as the resource allocation information used for the first time slot and the first transmission. In other implementations, the second resource allocation information may be different from the resource allocation information used for the first time slot and the first transmission. When the resource allocation information and the second resource allocation information are the same, the transmit bandwidth and the second transmit bandwidth may still be different. For example, the same bit value, length, and placement in the FDRA field may result in different interpretations based on different time slot configurations, different BWPs, and different RBG sizes. For illustration, changing the active BWP for the second time slot and the second transmission may adjust the transmit bandwidth and which RBGs are used.

[0174] Optionally, UE 115 and base station 105 may perform one or more additional operations. For example, base station 105 may send a second configuration information or signaling indication including second scheduling information such as third resource allocation information. UE 115 and base station 105 may perform similar steps 620-640 to convey one or more third transmissions for third resource allocation information.

[0175] Therefore, in Figure 6 In an example of FIG. 1 , devices of a network may be able to have more flexible utilization of full-duplex time slot configurations by using flexible resource allocation information.

[0176] In some implementations, a device may generate or interpret (e.g., parse) resource allocation information differently based on time slot information such as time slot configuration information. For example, a UE may interpret a field or bitmap differently based on the configuration of a time slot such as DL, UL, or FD (e.g., SBFD).

[0177] An example of interpreting resource allocation differently based on time slot configuration information is FIG. 7A to FIG. 7C Example in. FIG. 7A to FIG. 7C Each illustrates a transmission frequency band (or simply referred to as a frequency band) for a specific time slot, which represents a channel bandwidth for the duration of the time slot. FIG. 7A to FIG. 7C Further illustrated is a visual representation of a configured (eg, active) BWP overlaid on the transmit band of a time slot. FIG. 7A to FIG. 7C A time slot or transmission band in may include one or more sub-bands, and a BWP may overlap at least a portion of one or more of its sub-bands. FIG. 7A to FIG. 7C In the example, the device may generate or interpret the same resource allocation of the bitmap differently based on different time slot configurations (e.g., different layouts, placements, sizes, and parameters of the time slots such as RBG size). As an illustrative example, FIG. 7A to FIG. 7C Different slot configurations (e.g., subband configurations) of the 10 ...

[0178] refer to Fig. 7A , illustrates a frequency band 700 with a first time slot configuration. The first time slot configuration may be referred to as a DL configuration or a DL-only configuration. The first time slot configuration has a single DL frequency band 722 spanning the length of the frequency band 700 / time slot. The active BWP, BWP 712, is illustrated as overlapping a portion of the frequency band 700.

[0179] BWP 712 may be a DL BWP, a UL BWP, or a joint (UL / DL) BWP. As an illustrative example, BWP 712 is a DL BWP; and the DL BWP falls entirely within the DL frequency band 722. Thus, for the DL BWP, the device may determine that the effective length of the resource allocation and / or the FDRA field is all 9 bits. That is, the DL BWP is completely overlapped (e.g., completely within the downlink bandwidth (DL frequency band or subband)).

[0180] As an illustrative example, a device may receive a 9-bit resource allocation, where each bit corresponds to one or more RBGs. A bit value of zero means that the corresponding one or more RBGs are not allocated for transmission, and a bit value of 1 means that the corresponding one or more RBGs are allocated for transmission.

[0181] In the above example, each of the 9 bits conveys information whether or not the RBG is assigned by a bit value, since the 9 bits correspond to a BWP that falls entirely within the DL subband. The effective length of the FDRA is then determined by the number of bits that actually convey information, referred to as active bits.

[0182] refer to Figure 7B , illustrates a frequency band 710 with a second time slot configuration. The second time slot configuration may be referred to as a hybrid configuration or SBFD. The second time slot configuration has a single DL subband 724 and a single UL subband 726 in the frequency band 710 / time slot. An active BWP, BWP 712, is illustrated that overlaps a portion of each subband.

[0183] Similar to Fig. 7A , Figure 7B The BWP 712 of can be a DL BWP, a UL BWP, or a joint (UL / DL) BWP. As an illustrative example, the BWP 712 is a DL BWP; and a portion of the DL BWP overlaps with a portion of the DL subband 724. As in Figure 7B or Figure 7C In the example, when the BWP partially overlaps with the DL subband, each bit of the resource allocation may not be completely useful or convey FDRA information. In the case of using 9 bits to convey allocation in a scenario where the DL BWP partially overlaps with the DL subband, each bit conveys information only when the corresponding one or more RBGs even partially overlap with the DL subband. Otherwise, the bit may not convey any information regardless of its value and may be ignored by the UE. These bits that do not convey information may still correspond to certain RBGs, but the UE can safely assume that these RBGs will never be allocated for transmission regardless of the value of these bits that do not convey any information. The effective length of the FDRA is not determined by the number of bits that actually do not convey information (referred to as inactive bits).

[0184] refer to Figure 7C , illustrates a frequency band 720 with a third time slot configuration. The third time slot configuration may be referred to as a hybrid configuration or SBFD. The third time slot configuration has two DL subbands 724 and 728 separated by a single UL subband 726 in the frequency band 720 / time slot. An active BWP is illustrated that overlaps a portion of each subband.

[0185] Similar to Fig. 7A and Figure 7B , Figure 7C The BWP 712 may be a DL BWP, a UL BWP, or a joint (UL / DL) BWP. As an illustrative example, the BWP 712 is a DL BWP; and a portion of the DL BWP overlaps with portions of both DL subbands 724 and 728. Thus, for the DL BWP, the device may determine that the effective length of the resource allocation and / or the FDRA field is a portion of the bits of the FDRA field that corresponds to the portion of the DL BWP that overlaps with the DL subbands 724 and 728. An active bit is a bit that conveys information, and an inactive bit is a bit that does not convey information.

[0186] exist Figure 7C In the example of , the effective length of the resource allocation and / or the FDRA field is 6 of the 9 bits, i.e., the first 4 bits and the last 2 bits of the 9-bit field in the DL example. These first 4 bits and the last 2 bits correspond to the active bits, where the BWP 712 (in this case, the DL BWP) overlaps with each of the DL subbands 724 and 728. Alternatively, if the BWP 712 is a ULBWP, the device may determine that the effective length of the resource allocation and / or the FDRA field is 3 of the 9 bits. The position of the active bit in this example corresponds to the position where the BWP 712 (in this case, the UL BWP) overlaps with the UL subband 726, i.e., the three bits at bit positions four to six.

[0187] Therefore, if FIG. 7A to FIG. 7C As illustrated, the same resource allocation information (e.g., a bitmap and / or field having the same number of bits and exactly the same values) may be interpreted differently based on an activity bit of the resource allocation, where the activity bit is determined based on BWP 712, frequency band (700, 710, or 720), or RBG size.

[0188] exist FIG. 7A to FIG. 7C In the example of , each bit of the bitmap corresponds to an RBG group that completely overlaps (ie, not partially overlaps) the bandwidth of the corresponding band or subband. In other examples, such as FIG. 8A to FIG. 8BAs shown, one or more bits of the bitmap may correspond to RBG groups that only partially overlap with the bandwidth of the corresponding frequency band or subband. That is, the RBG may overlap both with the bandwidth of the corresponding frequency band or subband, and with the bandwidth of the guard band or the bandwidth of the non-corresponding frequency band or subband. The corresponding frequency band or subband corresponds to the frequency band in which the BWP 712 is configured to transmit in this direction, such as a DL BWP and a DL subband, a joint BWP and any subband, etc. The non-corresponding frequency band or subband corresponds to the frequency band in which the BWP 712 is not configured to transmit in this direction, such as a DL BWP and a UL subband, a UL BWP and a DL subband, a joint BWP and a guard band, etc.

[0189] Fig. 8A and Figure 8B An example of overlapping transmission is illustrated, i.e., where the RBG represented by the bits of the bitmap partially overlaps with the corresponding subband. In such an example, one or more RBs of the RBG may be outside the corresponding subband. Fig. 8A and Figure 8B In the example of , the RBG corresponding to bit 4 and the RBG corresponding to bit 7 partially overlap with the DL subband (and UL subband). Depending on the mode or setting, the equipment of the network may handle such a situation differently, such as interpreting the resource allocation information differently. For example, in some implementations, the overlapping RBGs may not be allocated or transmitted. In other implementations, only the portion overlapping with the transmission band is allocated for the DL BWP, such as the top portion of the RB corresponding to the RBG of bit 7 and the bottom portion of the RB corresponding to the RBG of bit 4.

[0190] refer to Fig. 8A , illustrates a frequency band 800 with a fourth slot configuration with RBG overlap. The fourth slot configuration may be referred to as a hybrid configuration or SBFD. The fourth slot configuration has two DL subbands 832 and 836 separated by a single UL subband 834 in the frequency band 800 / slot. An active BWP, BWP 822, is illustrated that overlaps a portion of each subband.

[0191] exist Fig. 8A In the example of , when overlap is not allowed (as shown by bars 842 and 844 with vertical stripes), the effective length of the resource allocation and / or the FDRA field for BWP 822 in the DL is 5 of 9 bits, i.e., the first 3 bits and the last 2 bits of the 9-bit field. In the case that the DL BWP partially overlaps with the DL subband, the device can parse the received resource allocation based on the active bit for the FDRA information. Each bit in the resource allocation conveys information only when the corresponding one or more RBGs even partially overlap with the DL subband.

[0192] refer to Figure 8B , illustrates another example of explaining the fourth time slot configuration with RBG overlap. Figure 8B As shown, the time slot configuration of frequency band 810 is Fig. 8A The time slot configuration of the frequency band 800 is the same. However, in some operating modes or with some configuration settings, the device may interpret that overlapping portions of the RBGs may be sent (i.e., the strips 842 and 844 with vertical stripes have been removed from the ends of the DL subbands 832 and 836). Therefore, the effective length of the resource allocation and / or the FDRA field of the BWP 822 in the DL is 7 of the 9 bits, i.e., the first 4 bits and the last 3 bits of the 9-bit field. In the event that the DL BWP partially overlaps the DL subband, the device may parse the received resource allocation based on the active bit for the FDRA information. Each bit in the resource allocation conveys information only when the corresponding one or more RBGs even partially overlap the DL subband.

[0193] and Fig. 8A Compared with the effective length of resource allocation, Figure 8B The effective length of the resource allocation in is longer because overlap is enabled or allowed. In particular, Figure 8B The effective length of the resource allocation in has more active bits (e.g., 7 active bits compared to 5 active bits). Figure 8B , the effective length of the resource allocation is longer, but the device may only communicate the overlapping portion of the overlapping bits (e.g., bit positions 3 and 6, i.e., only send bits that fall into DL subbands 832 and 836 (previously represented by Fig. 8A The strips 842 and 844 in the figure occupy RBs or RBGs).

[0194] exist Figure 8B 832 and 836 and UL subband 834. Although not illustrated in other figures for simplicity, in any other specific implementation, a guard band (e.g., guard bands 852 and 854) may be used between two subbands and / or between channels or frequency bands. When transmitting overlapping portions of RBs, the device may not transmit the RBs that overlap with the guard bands.

[0195] Fig.9A and Fig. 9B An example of the transmission of a variable length resource indication is illustrated. For example, the FDRA field may be a variable length field having a number of bits corresponding only to the overlap between the BWP and the subbands of the slot configuration. For illustration, impossible or allocated RBGs, i.e., RBGs of the BWP that do not overlap with the corresponding subband (i.e., RBGs that overlap with the guard band or non-corresponding subband) are excluded from representation in the bitmap. Thus, for a given combination of a BWP and a corresponding subband of the slot configuration, the bitmap size may be reduced or increased accordingly to the size of the actual potentially assignable RBG.

[0196] refer to Fig.9A, illustrates a frequency band 900 with a fifth slot configuration with RBG overlap. The fifth slot configuration may be referred to as a hybrid configuration or SBFD. The fifth slot configuration has two DL subbands 942 and 946 separated by a single UL subband 944 in the frequency band 900 / slot.

[0197] Fig.9A Another example of the interpretation of the bitmap for BWP resource allocation, variable field length allocation is illustrated. Currently, the FDRA field can have 9 or 18 bits. However, the FDRA field is not a variable length field, that is, a field that can have other lengths (number of bits) determined based on a variable / input set. Fig.9A In the example of , the length of the field or bitmap itself can be 1 to n bits, where n is greater than 18. The bitmap length itself can depend on how many bits are needed to convey the information, rather than 7A to 8B Thus, in the above example, as illustrated, for DLBWP, the FDRA field / bitmap will be for Fig. 7A is 9 bits long. Figure 7B is 2 bits long. Figure 7C is 5 bits long. Fig. 8A is 5 bits long, and for Figure 8B 7 bits long.

[0198] For example, in Fig.9A The BWP 920 (reference BWP) is illustrated in FIG. The BWP 920 may be divided into segments overlapping with corresponding subbands, and transmission therein may be possible. Fig.9A As illustrated in the example of , BWP 920 has three segments: a first segment 952, a second segment 954, and a third segment 956. When BWP 920 corresponds to a DL BWP or a DL / UL BWP, BWP 920 may be able to indicate transmissions occurring in a first downlink subband 942 and a second downlink subband 946. In such a specific implementation, BWP 920 may not be able to indicate transmissions occurring in an uplink subband such as uplink subband 944. Therefore, portions of the BWP such as the second segment 954 may be unallocated or unassignable for certain timeslot configurations. Rather than including such bits in a field for indicating transmission resources and bandwidth as non-resource allocation information or bits, they may be completely removed from the field to reduce the fields and length of the transmission or message. When interpreting resource allocation information, the device may determine the length (number of bits) of the resource allocation information based only on corresponding segments such as segments 952 and 956 where BWP 920 overlaps with corresponding subbands (942 and 946). The device may determine the length (number of bits) of the resource allocation information independently of the overlap between the BWP 920 and the non-corresponding subband ( 944 ), such as the segment 954 .

[0199] exist Fig.9A In the example of , the first bitmap 932 corresponding to the BWP 920 is 7 bits long, and the second bitmap 934 corresponding to the BWP 920 is 20 bits long. The first bitmap 932 has 4 bits in the bottom subband (third DL subband 946) and 3 bits in the top subband (first DL subband 942), and each bit represents the same number of RBs or RBGs (with the same RBG size). The second bitmap 934 has 15 bits in the bottom subband (third DL subband 946) and 5 bits in the top subband (first DL subband 942), and each bit represents the same number of RBs or RBGs (with the same RBG size).

[0200] refer to Fig. 9B , illustrating the explanation Fig.9A Another example of the fifth time slot configuration. Fig. 9B As shown, the time slot configuration of frequency band 910 is Fig.9A The time slot configuration of frequency band 900 is the same. Fig. 9B In the example of , the first bitmap 936 corresponding to BWP 920 is 8 bits long, and the second bitmap 938 corresponding to BWP 920 is 8 bits long. The first bitmap 936 has 6 bits in the bottom subband (third DL subband 946) and 2 bits in the top subband (first DL subband 942), and the bits in the top subband represent more RBs or RBGs (with larger RBG sizes). The second bitmap 938 has 6 bits in the bottom subband (third DL subband 946) and 2 bits in the top subband (first DL subband 942), and the bits in the top subband represent more RBs or RBGs (with larger RBG sizes). Compared to the first bitmap 936, the second bitmap 938 represents a BWP (e.g., 920) with bits that only partially overlap with DL subbands 942 and 946. In some implementations, those bits and RBGs may not be sent, and in other implementations, only the overlapping RBs may be sent, as shown in reference to Figure 8B described.

[0201] The number of bits in the FDRA field in the scheduling DCI is given by the total number of RBGs that fully or partially overlap the subband divided by the RBG size. If each subband has a different RBG size, the total number of bits sent in the FDRA is:

[0202]

[0203] Fig.10 1 is a flow chart illustrating example blocks executed by a wireless communication device (eg, a UE or a base station) configured according to aspects of the present disclosure. These example blocks will also be described with respect to Fig.12 The example UE 115 is used for description. Fig.12 1 is a block diagram illustrating a UE 115 configured according to one aspect of the present disclosure. The UE 115 includes Figure 2 and / or Figure 4 115. For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in a memory 282 and controls components of the UE 115 that provide features and functionality of the UE 115. The UE 115 sends and receives signals via wireless radios 1201a-r and antennas 252a-r under the control of the controller / processor 280. The wireless radios 1201a-r include various components and hardware, such as those described in Figure 2 As illustrated for UE 115, it includes modulators / demodulators 254a-r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266. Fig.12 As illustrated in the example of , the memory 282 stores resource allocation logic 1202, resource element mapping logic 1203, SBFD logic 1204, resource allocation information data 1205, timing information data 1206, time slot configuration data 1207, and setting data 1208. The data (1202-1208) stored in the memory 282 may include or correspond to data stored in Figure 4 data (406, 408, 442 and / or 444) in memory 404.

[0204] At block 1000, a wireless communication device such as a UE receives resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission. For example, a UE (e.g., UE 115) may receive resource allocation information 454 from another device (e.g., base station 105 or second UE 403). As described above, the resource allocation information may include or correspond to a bitmap indicating FDRA information.

[0205] Resource allocation information can be found in Figure 4 Configuration sends 450, Figure 4 Configuration message 452, Figure 4 Signaling messages, Figure 5 DCI or Figure 6 RRC sent or received in a message, or including or corresponding to Figure 4 Configuration sends 450, Figure 4 Configuration message 452, Figure 4 Signaling messages, Figure 5 DCI or Figure 6For illustration, a receiver of UE 115 (e.g., receiver processor 258 or receiver 412) receives resource allocation information 454 from base station 105 via wireless radios 1201a-r and antennas 252a-r, each of which includes at least a portion of the scheduling information. As another example, resource allocation information 454 may be included in a Figures 4 to 6 The configuration sending and / or signaling sending is sent or received in a message, or includes or corresponds to the configuration sending and / or signaling sending.

[0206] At block 1001, the UE communicates with a second network node using a transmission bandwidth for transmission based on the number of bits. For example, UE 115 may transmit or receive at least one of transmission 456 to another UE such as second UE 403 or to a network device such as base station 105. The first transmission may include or correspond to Figure 4 One or more of the transmissions 456, or one or more of the uplink or downlink transmissions, as referenced Figure 5 or Figure 6 described.

[0207] When the UE receives the first transmission, the UE 115 may receive a downlink transmission or a sidelink transmission based on the resource allocation information. For illustration, a receiver of the UE 115 (e.g., a receiver processor 258 or a receiver 412) receives the first transmission 456 via wireless radios 1201a-r and antennas 252a-r using the transmission bandwidth for the transmission.

[0208] When the UE sends the first transmission, the UE 115 may send an uplink transmission or a sidelink transmission based on the resource allocation information. For illustration, a transmitter of the UE 115 (e.g., the transmitter processor 264 or the transmitter 410) sends the first transmission 456 via the wireless radio 1201a-r and the antenna 252a-r using the transmission bandwidth for transmission.

[0209] In other specific implementations, the wireless communication device (e.g., UE or base station) may perform additional blocks (or the wireless communication device may be configured to further perform additional operations). For example, the wireless communication device (e.g., UE 115) may perform one or more of the above operations, such as referring to Figure 4 7. As another example, a wireless communication device (eg, UE 115) may perform one or more aspects presented below.

[0210] In the first aspect, the network node further receives time slot type information; and interprets resource allocation information based on the time slot type information, wherein a transmission bandwidth for transmission is based on the interpretation of the resource allocation information.

[0211] In a second aspect, alone or in combination with the first aspect, the resource allocation information corresponds to a bitmap of resource element information for an active bandwidth part (BWP).

[0212] In a third aspect, alone or in combination with one or more of the above aspects, interpreting which resource elements indicating an active BWP are active or assigned for transmission.

[0213] In a fourth aspect, alone or in combination with one or more of the above aspects, which bits of a bitmap indicating active BWPs are assignable for sending are explained.

[0214] In a fifth aspect, either alone or in combination with one or more of the above aspects, the network node further: receives timing information (e.g., TDRA); and determines a time slot based on the timing information, wherein interpreting the resource allocation information includes interpreting the resource allocation information based on a time slot configuration for the time slot, and the time slot configuration is based on the time slot type information and the timing information.

[0215] In a sixth aspect, alone or in combination with one or more of the above aspects, the network node further: determines a corresponding position, a corresponding size, a corresponding type, and a corresponding RBG size for each of the first subband, the second subband, and the third subband based on the time slot configuration; determines whether an active bandwidth part (BWP) overlaps with at least a portion of each of the first subband, the second subband, or the third subband; determines which resource block groups of the active BWP overlap with at least the portion of the first subband, the second subband, or the third subband based on the determination of whether the active BWP overlaps with at least the portion of each of the first subband, the second subband, or the third subband; and determines a decoding bitmap based on the determination of which resource block groups of the resource block groups of the active BWP overlap with at least the portion of the first subband, the second subband, or the third subband, wherein the resource allocation information is interpreted based on the decoding bitmap for identifying the number of bits.

[0216] In a seventh aspect, either alone or in combination with one or more of the above aspects, the total number of bits of the decoding bitmap corresponds to the total number of RBGs of the active BWP, and wherein the number and positions of the decoding bits of the decoding bitmap correspond to the number of overlapping RBGs between the active BWP and the first subband, the second subband, or the third subband, wherein the resource allocation information corresponds to a bitmap of RBGs for the active BWP, and wherein the decoding bits of the decoding bitmap are used to identify the number of bits corresponding to the transmission bandwidth used for transmission.

[0217] In an eighth aspect, alone or in combination with one or more of the above aspects, the network node further: determines a corresponding position, a corresponding size, a corresponding type, and a corresponding RBG size for each of the first subband, the second subband, and the third subband based on the time slot configuration; determines whether an active bandwidth part (BWP) overlaps with at least a portion of each of the first subband, the second subband, or the third subband; determines which resource block groups of the active BWP overlap with at least the portion of the first subband, the second subband, or the third subband based on the determination of whether the active BWP overlaps with at least the portion of each of the first subband, the second subband, or the third subband; and determines a length of a variable length field including resource allocation information based on the determination of which resource block groups of the active BWP overlap with at least a portion of the first subband, the second subband, or the third subband, wherein the length of the variable length field corresponds to the number of overlapping RBGs between the active BWP and the first subband and the third subband, and wherein the length of the variable length field corresponds to the number of bits.

[0218] In some such aspects, the interpretation results in a first interpretation of resource allocation information for a first time slot configuration, and wherein the interpretation results in a second interpretation of resource allocation information for a second time slot configuration different from the first time slot configuration.

[0219] In some such aspects, the first interpretation has a different number of valid / active bits or a different position / order of the valid / active bits.

[0220] In some such aspects, the first time slot configuration is a first SBFD time slot configuration, and wherein the second time slot configuration is a second SBFD time slot configuration, an uplink time slot configuration, or a downlink time slot configuration.

[0221] In a ninth aspect, alone or in combination with one or more of the above aspects, to communicate with a second network node, the network node: sends the transmission; or receives the transmission.

[0222] In a tenth aspect, alone or in combination with one or more of the above aspects, to communicate with the second network node, the network node communicates with the second network node in full duplex.

[0223] In an eleventh aspect, alone or in combination with one or more of the above aspects, to communicate with a second network node in full duplex, the network node: transmits or receives the transmission and receives a second transmission in sub-band full duplex.

[0224] In some such aspects, the sub-band full-duplex mode may include: sending the transmission in the first sub-band and receiving the second transmission in the second sub-band; receiving the transmission in the first sub-band and sending the second transmission in the second sub-band; sending the transmission in the first sub-band and sending a third transmission (e.g., a retransmission of the transmission) in the second sub-band and receiving the second transmission in a third sub-band located between the first sub-band and the second sub-band; or sending the transmission in the first sub-band and the second sub-band and receiving the second transmission in a third sub-band located between the first sub-band and the second sub-band.

[0225] In a twelfth aspect, alone or in combination with one or more of the above aspects, transmission occurs in a timeslot having a sub-band full-duplex configuration. For example, transmission occurs in a SBFD timeslot type such as a timeslot having at least one DL subband and at least one UL subband.

[0226] In a thirteenth aspect, alone or in combination with one or more of the above aspects, the number of bits corresponds to the valid bits of a frequency domain resource allocation (FDRA) field.

[0227] In some such aspects, the valid bit is a bit indicating FDRA information or a bit of a bitmap of RBG information for an active BWP, or the valid bit is a bit of an active BWP corresponding to an RBG that overlaps the transmit band / subbands.

[0228] In a fourteenth aspect, alone or in combination with one or more of the above aspects, the number of bits corresponds to the total number of bits of the FDRA field.

[0229] In a fifteenth aspect, either alone or in combination with one or more of the above aspects, the resource allocation information includes a first set of bits indicating FDRA information and a second set of bits indicating non-FDRA information. The second set of bits indicating non-FDRA information may include or correspond to reserved bits that may be allocated to another function at a later time.

[0230] In a sixteenth aspect, alone or in combination with one or more of the above aspects, the resource allocation information comprises a FDRA field, wherein the FDRA field comprises a first group of bits and a second group of bits.

[0231] In a seventeenth aspect, alone or in combination with one or more of the above aspects, the network node further determines resource allocation information based on a timeslot type for the transmission or a transmission type of the transmission. For example, the network node may identify the type of SBFD or how many subbands are present and where they are located.

[0232] In an eighteenth aspect, alone or in combination with one or more of the above aspects, the resource allocation information corresponds to at least a portion of the FDRA field, and the network node further determines a first group of bits of the FDRA field based on a timeslot type or a transmission type, wherein the first group of bits indicates FDRA information, and the FDRA field includes a second group of bits indicating non-FDRA information.

[0233] In a nineteenth aspect, alone or in combination with one or more of the above aspects, the network node further: receives time slot type information; and determines a transmission bandwidth for transmission based on a valid bit of the FDRA field, wherein the valid bit of the FDRA field indicates the FDRA information and is based on the time slot type information, and wherein the resource allocation information includes or corresponds to the valid bit.

[0234] In a twentieth aspect, alone or in combination with one or more of the above aspects, to determine a transmission bandwidth based on valid bits of the FDRA field, the network node determines a transmission bandwidth for transmission based on the number of valid bits.

[0235] In a twenty-first aspect, alone or in combination with one or more of the above aspects, the resource allocation information corresponds to a bitmap of resource element information for an active bandwidth part (BWP), and wherein the BWP is a downlink (DL) BWP, an uplink (UL) BWP, or a UL / DL BWP. The UL / DL BWP may include or correspond to a joint BWP, which may be assigned or used for uplink only or downlink only. Alternatively, the active BWP may be a full-duplex BWP to which uplink and downlink resources may be assigned in a single time slot.

[0236] In a twenty-second aspect, either alone or in combination with one or more of the above aspects, each bit of the bitmap corresponds to a corresponding resource block group (RBG) of an active BWP, wherein a specific RBG used for a specific bit of the bitmap partially overlaps with a transmission band used for transmission, and wherein the specific RBG is not allocated or transmitted.

[0237] In a twenty-third aspect, alone or in combination with one or more of the above aspects, each bit of the bitmap corresponds to a corresponding RBG of an active BWP, wherein a particular RBG for a particular bit of the bitmap partially overlaps a transmit band for transmission, wherein a first portion of the corresponding RBG is allocated and transmitted and a second portion of the corresponding RBG is not allocated or transmitted, and wherein the first portion corresponds to a resource block of the particular RBG that completely overlaps the transmit band. In some such aspects, the FDRA field is 9 or 18 bits long.

[0238] In a twenty-fourth aspect, either alone or in combination with one or more of the above aspects, the number of bits corresponds to the total number of bits of a frequency domain resource allocation (FDRA) field, wherein the total number of bits is based on: the number of resource block groups that overlap with one or more corresponding subbands of a transmitted time slot, and the RBG size.

[0239] In a twenty-fifth aspect, alone or in combination with one or more of the above aspects, the RBG size indicates the number of RBs in each RBG, and wherein the total number of bits in the FDRA field is the number of RBGs that at least partially overlap with any of the subbands divided by the number of RBs in each RBG. In some such aspects, the FDRA field is not 9 or 18 bits, such as longer than 18 bits or shorter than 9 bits.

[0240] In a twenty-sixth aspect, alone or in combination with one or more of the above aspects, a frequency band corresponding to transmission has two subbands for a specific transmission mode such as uplink or downlink.

[0241] In a twenty-seventh aspect, either alone or in combination with one or more of the above aspects, a frequency band corresponding to transmission has multiple subbands, and wherein a first subband of the multiple subbands has a first RBG size and a second subband of the multiple subbands has a second RBG size different from the first RBG size.

[0242] In a twenty-eighth aspect, either alone or in combination with one or more of the above aspects, the total number of bits transmitted is the sum of a first number of bits corresponding to RBGs in the BWP that overlap with the first subband divided by a first number of bits of the first RBG size of the first subband and a second number of bits corresponding to a second number of RBGs in the BWP that overlap with the second subband divided by a second RBG size of the second subband.

[0243] In a twenty-ninth aspect, alone or in combination with one or more of the above aspects, the network node further: receives time slot type information and resource element size information; determines a length of a FDRA field based on the time slot type information and the resource element size information, wherein the resource allocation information corresponds to the FDRA field; and determines a transmission bandwidth for transmission based on the length of the FDRA field. The resource element size information may include RB size information or RBG size information.

[0244] In a thirtieth aspect, alone or in combination with one or more of the above aspects, to determine a transmission bandwidth based on a length of the FDRA field, the network node determines a transmission bandwidth for transmission based on a number of bits of the FDRA field having a specific value.

[0245] In a thirty-first aspect, alone or in combination with one or more of the above aspects, the resource allocation information corresponds to a bitmap of resource element information for an active BWP, and wherein the bitmap corresponds to an entirety of the bandwidth of the BWP.

[0246] In a thirty-second aspect, alone or in combination with one or more of the above aspects, the resource allocation information corresponds to a bitmap of resource element information for an active BWP, wherein the bitmap corresponds to a portion of the bandwidth of the active BWP that overlaps with one or more subbands of a time slot in which transmission occurs. The subband corresponding to the BWP or in which transmission occurs may be a DL subband for a DL BWP or a DL / UL BWP, or may be a UL subband for a UL BWP or a DL / UL BWP.

[0247] In another aspect, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive resource allocation information; wherein the resource allocation information is indicated by a field including a first set of bits having FDRA information and a second set of bits having non-FDRA information, and wherein the number of bits of the first set of bits having the FDRA information corresponds to a transmission bandwidth for transmission; and communicate with a second network node using the transmission bandwidth for transmission.

[0248] In another aspect, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive resource allocation information having a number of bits corresponding to a transmission bandwidth for transmission, wherein the resource allocation information is included in a variable length field; and communicate with a second network node using the transmission bandwidth for transmission.

[0249] Therefore, the wireless communication device can perform an improved frequency domain resource allocation operation for the wireless communication device. By performing the improved frequency domain resource allocation, the throughput can be increased and the delay can be reduced.

[0250] Fig.11 1 is a flow chart illustrating example blocks executed by a wireless communication device (eg, a UE or a network entity such as a base station) configured according to aspects of the present disclosure. These example blocks will also be described with respect to Fig.13 The illustrated base station 105 is used for description. Fig.13 1 is a block diagram illustrating a base station 105 configured according to one aspect of the present disclosure. The base station 105 includes Figure 2 and / or Figure 41. The base station 105 of FIG. 105 is illustrative of the structure, hardware, and components of the base station 105 of FIG. 105. For example, the base station 105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and controls components of the base station 105 that provide the features and functionality of the base station 105. The base station 105 transmits and receives signals via wireless radios 1301a-t and antennas 234a-t under the control of the controller / processor 240. The wireless radios 1301a-t include, for example, Figure 2 Various components and hardware for base station 105 are illustrated, including modulator / demodulators 232a-r, MIMO detector 236, receive processor 238, transmit processor 220, and TX MIMO processor 230. Fig.13 As illustrated in the example of , the memory 242 stores resource allocation logic 1302, resource element mapping logic 1303, broadcast logic 1304, resource allocation information data 1305, timing information data 1306, time slot configuration data 1307, and setting data 1308. The data (1302-1308) stored in the memory 242 may include or correspond to data stored in Figure 4 data (406, 408, 442 and / or 444) in memory 432.

[0251] At block 1100, a wireless communication device, such as a network device (e.g., base station 105), sends resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission. For example, base station 105 may send resource allocation information 454 to one or more UEs (e.g., UE 115 and / or second UE 403). As described above, the resource allocation information may include or correspond to a bitmap indicating FDRA information.

[0252] Resource allocation information can be found in Figure 4 Configuration sends 450, Figure 4 Configuration message 452, Figure 4 Signaling messages, Figure 5 DCI or Figure 6 The RRC is sent or sent in a message, or includes or corresponds to Figure 4 Configuration sends 450, Figure 4 Configuration message 452, Figure 4 Signaling messages, Figure 5 DCI or Figure 6 For illustration, a transmitter of the base station 105 (e.g., the transmit processor 220 / TX MIMO processor 230 or the transmitter 434) transmits the resource allocation information 454 via the wireless radio 1301a-t and the antenna 234a-t. As another example, the resource allocation information 454 may be included in a reference Figures 4 to 6The configuration sending and / or signaling sending is sent or sent in a message, or includes or corresponds to the configuration sending and / or signaling sending.

[0253] At block 1101, the wireless communication device communicates with a second network node using a transmission bandwidth for transmission based on the number of bits. For example, base station 105 may send or receive at least one of transmissions 456 to one or more UEs (e.g., UE 115 and / or second UE 403). The first transmission may include or correspond to Figure 4 One or more of the transmissions 456, or one or more of the uplink or downlink transmissions, as referenced Figure 5 and Figure 6 described.

[0254] When the base station 105 receives the first transmission, the base station 105 may receive the downlink transmission or the sidelink transmission based on the resource allocation information. For illustration, the receiver of the base station 105 (e.g., the receiver processor 238 or the receiver 436) receives the first transmission 456 via the wireless radio 1301a-t and the antenna 234a-t using the transmission bandwidth for the transmission.

[0255] When the base station 105 sends the first transmission, the base station 105 may send an uplink transmission or a sidelink transmission based on the resource allocation information. For illustration, a transmitter of the base station 105 (e.g., the transmit processor 220 / TX MIMO processor 230 or the transmitter 434) sends the first transmission 456 via the wireless radio 1301a-t and the antenna 234a-t using the transmit bandwidth for transmission.

[0256] In other specific implementations, a wireless communication device (e.g., such as a UE or a base station) may perform additional blocks (or the wireless communication device may be configured to further perform additional operations). For example, the wireless communication device may perform as described in reference Figure 4 To one or more operations described in FIG. 7. For another example, the wireless communication device may perform the above reference Fig.12 One or more aspects described.

[0257] Therefore, the wireless communication device can perform an improved frequency domain resource allocation operation for the wireless communication device. By performing the improved frequency domain resource allocation, the throughput can be increased and the delay can be reduced.

[0258] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example in which a UE is configured to receive information from a base station and it is also disclosed that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first group of one or more components, a first processing entity, etc.; and a second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second group of one or more components, a second processing entity, etc.

[0259] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0260] It should be understood by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0261] This article is relative to Figures 1 to 13 The components, functional blocks and modules include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software codes, firmware codes, etc., or any combination thereof. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, etc., whether they are referred to as software, firmware, middleware, microcode, hardware description language or other terms. In addition, the features discussed herein may be implemented via dedicated processor circuits, via executable instructions, or a combination thereof.

[0262] The technician will further understand that the various exemplary logic boxes, modules, circuits and algorithm steps described in conjunction with the disclosure of this article can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, blocks, modules, circuits and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing departure from the scope of the present disclosure. The technician will also easily recognize that the order or combination of components, methods or interactions described herein are only examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner other than the manner illustrated and described herein.

[0263] The various illustrative logical components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. The interchangeability of hardware and software has been generally described in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0264] The hardware and data processing apparatus for implementing the various exemplary logic components, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. In some specific implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some specific implementations, specific processes and methods may be performed by circuits specific to a given function.

[0265] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Specific implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on computer storage media for execution by data processing apparatus or for controlling the operation of data processing apparatus.

[0266] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any media that can be implemented to transfer a computer program from one place to another. The storage medium may be any available medium accessible to a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and blue-ray disks, wherein disks generally reproduce data magnetically, and optical disks reproduce data optically with lasers. The above combination should also be included in the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0267] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to some other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0268] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positioning corresponding to the orientation of the drawings on a properly oriented page, and may not reflect the proper orientation of any device as implemented.

[0269] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, either individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to subcombinations or variations of subcombinations.

[0270] Similarly, although the operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all the illustrated operations to achieve the desired result. Further, the accompanying drawings can schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted can be combined in the schematically illustrated example process. For example, one or more additional operations can be performed before, after, at the same time or between any illustrated operations. In some environments, multitasking and parallel processing can be advantageous. In addition, the separation of various system components in the specific implementation described above should not be understood as requiring such separation in all specific implementations, and it should be understood that the program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other specific implementations also fall within the scope of the appended claims. In some cases, the actions described in the claims can be performed in different orders and still achieve the desired result.

[0271] As used herein, the term "or" is an inclusive "or" unless restrictive language is used with respect to the listed alternatives. For example, references to "X is based on A or B" should be interpreted as including within its scope X based on A, X based on B, and X based on A and B. In this regard, references to "X is based on A or B" refer to "at least one of A or B" or "one or more of A or B" because "or" is inclusive. Similarly, references to "X is based on A, B, or C" should be interpreted as including within its scope X based on A, X based on B, X based on C, X based on A and B, X based on A and C, X based on B and C, and X based on A, B, and C. In this regard, references to "X is based on A, B, or C" refer to "at least one of A, B, or C" or "one or more of A, B, or C" because "or" is inclusive. As an example of restrictive language, a reference to "X is based only on one of A or B" should be interpreted to include within its scope X being based on A and X being based on B, but not including X being based on both A and B. Additionally, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A," unless specifically stated differently. Additionally, as used herein, the phrase "group" should be understood to include the possibility of a group having one member. That is, the phrase "group" should be understood in the same manner as "one or more" or "at least one."

[0272] As used herein, the term "substantially" is defined as to a large extent, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed implementation, the term "substantially" may be replaced with "within [percentage] of" what is specified, where percentages include 0.1%, 1%, 5%, or 10%.

[0273] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first network node for wireless communication, comprising: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: receiving resource allocation information including a number of bits corresponding to a transmission bandwidth for transmission; and Communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

2. The first network node according to claim 1, wherein the at least one processor is configured to: receiving time slot type information; and The resource allocation information is interpreted based on the slot type information, wherein the transmission bandwidth used for the transmission is based on the interpretation of the resource allocation information.

3. The first network node according to claim 2, wherein the resource allocation information corresponds to a bitmap of resource element information for an active bandwidth part (BWP). 4 . The first network node according to claim 3 , wherein the interpretation indicates which resource elements of the active BWP are active or assigned for the transmission.

5. The first network node of claim 3, wherein the interpretation indicates which bits of the bitmap of the active BWP are assignable for the sending.

6. The first network node of claim 2, wherein the at least one processor is configured to: receiving timing information; and A time slot is determined based on the timing information, wherein: To interpret the resource allocation information, the at least one processor is configured to: The resource allocation information is interpreted based on a slot configuration for the slot, wherein the slot configuration is based on the slot type information and the timing information.

7. The first network node according to claim 6, wherein the at least one processor is configured to: determining, for each of the first subband, the second subband, and the third subband based on the time slot configuration, a respective position, a respective size, a respective type, and a respective RBG size; determining whether an active bandwidth part (BWP) overlaps at least a portion of each of the first sub-band, the second sub-band, or the third sub-band; determining which resource block groups of the active BWP overlap with at least the portion of the first subband, the second subband, or the third subband based on the determination of whether the active BWP overlaps with at least the portion of each of the first subband, the second subband, or the third subband; as well as A decoding bitmap is determined based on the determination of which of the resource block groups of the active BWP overlap with at least the portion of the first subband, the second subband, or the third subband, wherein the resource allocation information is interpreted based on the decoding bitmap for identifying the number of bits.

8. The first network node of claim 7 , wherein the total number of bits of the decoding bitmap corresponds to the total number of RBGs of the active BWP, and wherein the number and positions of the decoding bits of the decoding bitmap correspond to the number of overlapping RBGs between the active BWP and the first subband, the second subband, or the third subband, wherein the resource allocation information corresponds to a bitmap of RBGs for the active BWP, and wherein the decoding bits of the decoding bitmap are used to identify bits corresponding to the number of the transmission bandwidth used for the transmission.

9. The first network node of claim 6, wherein the at least one processor is configured to: determining, for each of the first subband, the second subband, and the third subband based on the time slot configuration, a respective position, a respective size, a respective type, and a respective RBG size; determining whether an active bandwidth part (BWP) overlaps at least a portion of each of the first sub-band, the second sub-band, or the third sub-band; determining which resource block groups of the active BWP overlap with at least the portion of the first subband, the second subband, or the third subband based on the determination of whether the active BWP overlaps with at least the portion of each of the first subband, the second subband, or the third subband; as well as A length of a variable length field comprising the resource allocation information is determined based on the determination of which of the resource block groups of the active BWP overlap with at least the portion of the first subband, the second subband, or the third subband, wherein the length of the variable length field corresponds to the number of overlapping RBGs between the active BWP and the first subband and the third subband, and wherein the length of the variable length field corresponds to the number of bits.

10. The first network node according to claim 1, wherein: To communicate with the second network node, the at least one processor is configured to: sending said sending; or The transmission is received.

11. The first network node according to claim 1, wherein: To communicate with the second network node, the at least one processor is configured to communicate with the second network node in a full-duplex manner.

12. The first network node according to claim 11, wherein: In order to communicate with the second network node in the full-duplex manner, the at least one processor is configured to: The transmission is transmitted in sub-band full-duplex mode and a second transmission is received.

13. The first network node of claim 1, wherein the transmitting occurs in a time slot having a sub-band full-duplex configuration.

14. The first network node of claim 1, wherein the number of bits corresponds to valid bits of a frequency domain resource allocation (FDRA) field.

15. The first network node of claim 1, wherein the number of bits corresponds to a total number of bits of a FDRA field.

16. The first network node of claim 1, wherein the resource allocation information comprises a first set of bits indicating FDRA information and a second set of bits indicating non-FDRA information.

17. The first network node of claim 16, wherein the resource allocation information comprises a FDRA field, wherein the FDRA field comprises the first set of bits and the second set of bits.

18. The first network node of claim 1, wherein the at least one processor is configured to: The resource allocation information is determined based on a timeslot type for the transmission or a transmission type of the transmission.

19. The first network node of claim 18, wherein the resource allocation information corresponds to at least a portion of a FDRA field, and wherein the at least one processor is configured to: A first set of bits of the FDRA field is determined based on the slot type or the transmission type, wherein the first set of bits indicates FDRA information, and wherein the FDRA field includes a second set of bits indicating non-FDRA information.

20. The first network node of claim 1, wherein the at least one processor is configured to: receiving time slot type information; and The transmission bandwidth for the transmission is determined based on a valid bit of a FDRA field, wherein the valid bit of the FDRA field indicates FDRA information and is based on the slot type information, and wherein the resource allocation information includes or corresponds to the valid bit.

21. The first network node according to claim 20, wherein: To determine the transmission bandwidth based on the valid bits of the FDRA field, the at least one processor is configured to: The transmission bandwidth used for the transmission is determined based on the number of significant bits.

22. The first network node of claim 1, wherein the resource allocation information corresponds to a bitmap of resource element information for an active bandwidth part (BWP), and wherein the BWP is a downlink (DL) BWP, an uplink (UL) BWP, or a UL / DL BWP.

23. The first network node of claim 22, wherein each bit of the bitmap corresponds to a respective resource block group (RBG) of the active BWP, wherein a specific RBG for a specific bit of the bitmap partially overlaps with a transmission band used for the transmission, and wherein the specific RBG is not allocated or transmitted.

24. The first network node of claim 22, wherein each bit of the bitmap corresponds to a corresponding RBG of the active BWP, wherein a specific RBG for a specific bit of the bitmap partially overlaps with a transmission band for the transmission, wherein a first portion of the corresponding RBG is allocated and transmitted and a second portion of the corresponding RBG is not allocated or transmitted, and wherein the first portion corresponds to a resource block of the specific RBG that completely overlaps with the transmission band.

25. The first network node of claim 1 , wherein the number of bits corresponds to a total number of bits of a frequency domain resource allocation (FDRA) field, wherein the total number of bits is based on: the number of resource block groups overlapping with one or more corresponding subbands of the transmitted time slot, and RBG size.

26. The first network node of claim 25, wherein the RBG size indicates the number of RBs in each RBG, and wherein the total number of bits in the FDRA field is the number of RBGs that at least partially overlap with any one of the subbands divided by the number of RBs in each RBG.

27. The first network node of claim 1, wherein a frequency band corresponding to the transmission has two sub-bands for a specific transmission mode.

28. The first network node of claim 1, wherein a frequency band corresponding to the transmission has a plurality of subbands, and wherein a first subband of the plurality of subbands has a first RBG size, and a second subband of the plurality of subbands has a second RBG size different from the first RBG size.

29. The first network node of claim 28, wherein the total number of bits sent is the sum of a first number of bits corresponding to RBGs in the BWP that overlap with the first subband divided by a first number of bits of the first RBG size of the first subband and a second number of bits corresponding to RBGs in the BWP that overlap with the second subband divided by the second RBG size of the second subband.

30. The first network node of claim 1, wherein the at least one processor is configured to: receiving time slot type information and resource element size information; and determining a length of a FDRA field based on the slot type information and the resource element size information, wherein the resource allocation information corresponds to the FDRA field; and The transmission bandwidth for the transmission is determined based on the length of the FDRA field.

31. The first network node according to claim 30, wherein: To determine the transmission bandwidth based on the length of the FDRA field, the at least one processor is configured to: The transmission bandwidth for the transmission is determined based on the number of bits of the FDRA field having a specific value.

32. The first network node of claim 1, wherein the resource allocation information corresponds to a bitmap of resource element information for an active BWP, and wherein the bitmap corresponds to an entirety of a bandwidth of the BWP.

33. The first network node of claim 1, wherein the resource allocation information corresponds to a bitmap of resource element information for an active BWP, wherein the bitmap corresponds to a portion of a bandwidth of the active BWP that overlaps with one or more subbands of a time slot in which the transmission occurs.

34. A first network node for wireless communication, comprising: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: transmit resource allocation information, the resource allocation information comprising a number of bits corresponding to a transmission bandwidth for transmission; and Communicating with a second network node using the transmission bandwidth for the transmission based on the number of bits.

Images