Sub-band full duplex resource allocation

Abstract

Aspects relate to sub-band full duplex (SBFD) resource allocation. In one aspect, a network entity configures SBFD frequency resources for one or more subbands based on a size of the subbands and a size of a bandwidth portion (BWP) associated with a user equipment (UE), and provides scheduling information to the UE, where the scheduling information includes a configuration of the SBFD frequency resources based on the size of the subbands and the size of the BWP associated with the UE. In another aspect, a UE receives scheduling information including a configuration of SBFD frequency resources for one or more sub-bands, where the configuration is based on a size of the sub-band and a size of a BWP associated with the UE. The UE then communicates with a network via the SBFD frequency resource based on the scheduling information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Non-Provisional Patent Application No. 18 / 354,408, filed on July 18, 2023, and U.S. Provisional Patent Application No. 63 / 399,642, filed on August 19, 2022, which patent applications are assigned to the assignee of this application and are hereby expressly incorporated herein by reference in their entirety as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communications, and more particularly to sub-band full-duplex (SBFD) resource allocation. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems. These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. Summary of the invention

[0005] An overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. 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 is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description presented later.

[0006] According to a first example, a user equipment (UE) is disclosed that includes a transceiver, a memory, and a processor coupled to the transceiver and the memory. The processor is configured to receive scheduling information, the scheduling information including a configuration of sub-band full-duplex (SBFD) frequency resources for one or more sub-bands, wherein the configuration is based on a size of the one or more sub-bands and a size of a bandwidth part (BWP) associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more sub-bands. The processor is also configured to communicate with a network via the SBFD frequency resources based on the scheduling information.

[0007] In other examples, a method for wireless communication in a UE is disclosed. The method includes receiving scheduling information, the scheduling information including a configuration of SBFD frequency resources for one or more subbands, wherein the configuration is based on a size of the one or more subbands and a size of a BWP associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands. The method also includes communicating with a network via the SBFD frequency resources based on the scheduling information.

[0008] Another example provides a network entity configured for wireless communication. The network entity includes a memory and a processor coupled to the memory. The processor is configured to configure SBFD frequency resources for one or more subbands based on the size of the one or more subbands and the size of the BWP associated with the UE, wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands. The processor is also configured to provide scheduling information to the UE, wherein the scheduling information includes the configuration of the SBFD frequency resources based on the size of the one or more subbands and the size of the BWP associated with the UE.

[0009] According to yet another example, a method for wireless communication in a network entity is disclosed. The method includes configuring SBFD frequency resources for one or more subbands based on a size of the one or more subbands and a size of a BWP associated with a UE, wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands, and further includes providing scheduling information to the UE, wherein the scheduling information includes configuration of the SBFD frequency resources based on the size of the one or more subbands and the size of the BWP associated with the UE.

[0010] After studying the specific embodiments below, these and other aspects of the present disclosure will become more fully understood. After studying the description of the specific examples of the present disclosure below in conjunction with the accompanying drawings, other aspects, features and examples of the present disclosure will be apparent to those of ordinary skill in the art. Although the features of the present disclosure may be discussed below with respect to certain examples and accompanying drawings, all examples of the present disclosure may include one or more advantageous features of the advantageous features discussed herein. In other words, although one or more examples may be discussed to have certain advantageous features, one or more of such features may also be used according to the various examples of the present disclosure discussed herein. In a similar manner, although each example may be discussed below as an example of a device, system or method, it should be understood that such examples can be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 is a schematic illustration of a wireless communication system according to some aspects.

[0012] Figure 2 is a conceptual illustration of an example radio access network in accordance with some aspects.

[0013] Figure 3 is a diagram providing a high-level illustration of one example of a configuration of a decomposed base station in accordance with some aspects.

[0014] Figure 4 is a schematic illustration of wireless resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) in accordance with some aspects.

[0015] FIG. 5A to FIG. 5C An example of full-duplex communication in an unpaired spectrum is illustrated.

[0016] Fig. 6A is a schematic diagram of network entities configured for full-duplex communications according to some aspects.

[0017] Figure 6B Based on some aspects of use Fig. 6A Schematic diagram of an exemplary sub-band full-duplex wireless communication using a multi-panel antenna array as shown in FIG.

[0018] Figure 7 An exemplary sub-band full-duplex (SBFD) resource allocation without partial resource block groups (RBGs) is illustrated.

[0019] Figure 8

[0046] Example SBFD resource allocation with fractional RBGs in accordance with some aspects is illustrated.

[0020] Fig. 9 A first exemplary valid downlink (DL) subband in accordance with some aspects is illustrated.

[0021] Fig.10 A second exemplary valid DL subband according to some aspects is illustrated.

[0022] Fig.11 A first exemplary valid uplink (UL) subband in accordance with some aspects is illustrated.

[0023] Fig.12 A second exemplary valid UL subband in accordance with some aspects is illustrated.

[0024] Fig.13 Example valid UL subbands and example valid DL subbands according to some aspects are illustrated.

[0025] Fig.14 Example SBFD resource allocations in accordance with some aspects are illustrated.

[0026] Fig.15 is a block diagram illustrating an example of a hardware implementation of a user equipment (UE) employing a processing system according to some aspects.

[0027] Fig.16 is a flow chart illustrating an example of a method for communicating in a UE according to some aspects.

[0028] Fig.17 is a block diagram illustrating an example of a hardware implementation of a network entity, such as a base station, employing a processing system according to some aspects.

[0029] Fig.18 is a flow chart illustrating a method for communicating among network entities according to some aspects. DETAILED DESCRIPTION

[0030] The specific embodiments described below in conjunction with the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configurations with which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0031] Aspects disclosed herein are directed to enhancements to resource allocation in symbols having subbands that the network will use for subband full-duplex (SBFD) operation. In a specific aspect, a network entity (e.g., a gNB) schedules SBFD resources for subbands based on the size of the subbands. In some examples, such scheduling advantageously facilitates utilizing partial resource block groups (RBGs) and partial precoding resource groups (PRGs) during SBFD operation. In further examples, such scheduling also desirably facilitates utilizing finer granularity frequency domain resource allocation (FDRA) bit widths during SBFD operation while maintaining the same DCI overhead as a TDD slot, or reducing DCI overhead in a SBFD slot while maintaining the same scheduling granularity as in a TDD slot.

[0032] Although various aspects and examples are described in this application by illustrating 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 innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each example and / or use may be generated via an integrated chip example and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, artificial intelligence-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. Specific implementations may range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some actual settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and implementation of the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) It is expected that the innovations described herein can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations.

[0033] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1, various aspects of the present disclosure are illustrated with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as (but not limited to) the Internet.

[0034] The RAN 104 may implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate according to a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as Long Term Evolution (LTE). 3GPP refers to such a hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0035] As illustrated, RAN 104 includes multiple base stations 108. In a broad sense, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP) or some other suitable terminology by those skilled in the art. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies in the same or different frequency bands. In an example where RAN 104 operates according to both the LTE standard and the 5G NR standard, one of the base stations may be an LTE base station, and the other base station may be a 5G NR base station. In addition, one or more base stations in the base station may have a decomposed configuration.

[0036] RAN 104 is also illustrated as supporting wireless communications for multiple mobile devices. In the 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also refer to it as a mobile station (MS), a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology. A UE may be a device (e.g., a mobile device) that provides access to network services to a user.

[0037] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, but may be stationary. The term mobile device or mobile equipment refers broadly to a wide variety of devices and technologies. A UE may include a number of hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide range of embedded systems, for example, corresponding to the "Internet of Things" (IoT).

[0038] The mobile device may also be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. The mobile device may also be a digital home or smart home device (such as home audio, video and / or multimedia equipment), an appliance, a vending machine, a smart lighting device, a home security system, a smart meter Etc. The mobile device may also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device that controls electrical power (e.g., a smart grid), lighting, water supply, etc., an industrial automation and enterprise device, a logistics controller, and / or agricultural equipment, etc. In addition, the mobile device may provide connected medical or telemedicine support, such as health care at a distance. Telemedicine devices may include telemedicine monitoring devices and telemedicine management devices, whose communications may be given priority or access priority over other types of information, for example, in terms of priority access for the transmission of critical service data and / or associated QoS for the transmission of critical service data.

[0039] The wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term "downlink" can refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe this scheme can be to use the term "broadcast channel multiplexing". Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term "uplink" can refer to point-to-point transmissions originating at a UE (e.g., UE 106).

[0040] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities (e.g., UEs 106). That is, for scheduled communications, multiple UEs 106 (which may be scheduled entities) may utilize resources allocated by the scheduling entity 108.

[0041] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0042] like Figure 1 , the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities (e.g., one or more UEs 106). Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112, and in some examples, uplink traffic 116 from one or more scheduled entities (e.g., one or more UEs 106) to the scheduling entity 108. On the other hand, the scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grant), synchronization or timing information, or other control information) from another entity in the wireless communication network (such as the scheduling entity 108). The scheduled entity 106 may also send uplink control information 118 (including but not limited to scheduling request or feedback information or other control information) to the scheduling entity 108.

[0043] In addition, uplink and / or downlink control information 114 and / or 118 and / or business 112 and / or 116 information may be sent on a waveform that may be divided into frames, subframes, time slots and / or symbols by time. As used herein, a symbol may refer to a time unit that carries one resource element (RE) per subcarrier in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. In the present disclosure, a frame may refer to a predetermined duration (e.g., 10 ms) for wireless transmission, wherein each frame is composed of, for example, 10 subframes of 1 ms each. Of course, these definitions are not required, and any suitable scheme for organizing waveforms may be utilized, and the various time divisions of waveforms may have any suitable duration.

[0044] Generally speaking, base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of wireless communication system 100. Backhaul portion 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0045] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other appropriate standard or configuration.

[0046] See now Figure 2 , by way of illustrative example and not limitation, a schematic diagram of a radio access network (RAN) 200 according to some aspects of the present disclosure is provided. In some examples, the RAN 200 may be similar to the RAN described above and in Figure 1 is the same as the RAN 104 illustrated in .

[0047] The geographic area covered by the RAN 200 may be divided into a number of cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station within the geographic area. Figure 2Cells 202, 204, 206, and 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by multiple groups of antennas, each of which is responsible for communicating with a UE in a portion of the cell.

[0048] Various base station arrangements can be used. Figure 2 , two base stations (base station 210 and base station 212) are shown in cells 202 and 204. A third base station (base station 214) is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, the base station may have an integrated antenna, or may be connected to an antenna or RRH 216 by a feeder cable. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. In addition, base station 218 is shown in cell 208, which may overlap with one or more macro cells. In this example, cell 208 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNode B, etc.) because base station 218 supports a cell with a relatively small range. The cell size setting may be performed according to the system design and component constraints.

[0049] It should be appreciated that the RAN 200 may include any number of wireless base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The scheduling entity 108 illustrated in FIG. 1 is the same as or similar to that in FIG.

[0050] Figure 2 Also included is an unmanned aerial vehicle (UAV) 220, which may be a drone or a quadcopter. UAV 220 may be configured to act as a base station, or more specifically, a mobile base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of a mobile base station (such as UAV 220).

[0051] Within the RAN 200, cells may include UEs that may communicate with one or more sectors of each cell. In addition, each base station 210, 212, 214, 218, and 220 may be configured to provide access to the core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may communicate with the base stations described above and Figure 1 202. In some examples, UAV 220 (e.g., a quadcopter) may be a mobile network node and may be configured to act as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0052] In another aspect of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. Sidelink communications can be utilized in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UE 238, 240, and 242) can communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UE 238, 240, and 242 can each act as a scheduling entity or a sender sidelink device and / or a scheduled entity or a receiver sidelink device to schedule resources and communicate sidelink signals 237 between them without relying on scheduling or control information from a base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also communicate sidelink signals 227 via a direct link (sidelink) without routing the communication through base station 212. In this example, base station 212 may allocate resources to UEs 226 and 228 for sidelink communication.

[0053] In some examples, a D2D relay framework may be included within a cellular network to facilitate relaying of communications to / from base station 212 via a D2D link (e.g., side link 227 or 237). For example, one or more UEs (e.g., UE 228) within the coverage area of ​​base station 212 may operate as relay UEs to expand the coverage of base station 212, improve transmission reliability to one or more UEs (e.g., UE 226), and / or allow the base station to recover from a failed UE link due to, for example, blocking or fading.

[0054] In order to obtain a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel coding may be used. That is, wireless communications may typically utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., a codec) at the sender device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message may improve the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0055] Data decoding can be implemented in a variety of ways. In early 5G NR specifications, user data is decoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and physical broadcast channel (PBCH) are decoded based on nested sequences using polar decoding. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0056] Aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of base stations and UEs may include appropriate hardware and capabilities (eg, encoders, decoders, and / or codecs) to utilize one or more of these channel codes for wireless communications.

[0057] In the RAN 200, the ability of a UE to communicate while moving (independent of its location) is called mobility. The various physical channels between the UE and the RAN 200 are generally established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include: a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may manage security contexts for both control plane functionality and user plane functionality in whole or in part.

[0058] In various aspects of the present disclosure, the RAN 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity or at any other time, the UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, the UE 224 may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 for a given amount of time, the UE 224 may send a report message indicating this to its serving base station 210. In response, UE 224 may receive the handover command, and the UE may proceed with the handover to cell 206 .

[0059] In a network configured for UL-based mobility, the network can select a serving cell for each UE using a UL reference signal from each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive unified synchronization signals, derive carrier frequency and slot timing from these synchronization signals, and send uplink pilots or reference signals in response to the derived opportunities. The uplink pilot signal sent by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within RAN 200. Each of the cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214 / 216 and / or a central node within the core network) may determine a serving cell for the UE 224. As the UE 224 moves through the RAN 200, the RAN 200 may continue to monitor the uplink pilot signals sent by the UE 224. When the signal strength or quality of the pilot signal measured by the neighboring cell exceeds the signal strength or quality measured by the serving cell, the RAN 200 may hand over the UE 224 from the serving cell to the neighboring cell with or without notifying the UE 224.

[0060] Although the synchronization signals transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone of multiple cells operating on the same frequency and / or using the same timing. Using zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network, because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0061] In various specific implementations, the air interface in the radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive use of a portion of the spectrum with the help of a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-authorized license. Although it is still generally necessary to comply with some technical rules to access the unlicensed spectrum, access is generally available to any operator or device. Shared spectrum can fall between licensed spectrum and unlicensed spectrum, where some technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of a licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0062] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to the base station 210, and multiplexing of DL transmissions from the base station 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other suitable multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0063] The equipment in the radio access network 200 may also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which two endpoints can communicate with each other in two directions. Full-duplex means that two endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can transmit information to the other endpoint at a time. Half-duplex simulation is often implemented for wireless links using time division duplex (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, in some scenarios, a channel is dedicated to transmission in one direction, while at other times, the channel is dedicated to transmission in another direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation of transmitters and receivers and suitable interference cancellation techniques. Full-duplex simulation is often implemented for wireless links by utilizing frequency division duplex (FDD) or space division duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication may be implemented within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplex.

[0064] 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) that perform 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.

[0065] 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).

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

[0067] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more distributed units (DUs) 330 via respective midhaul links, such as an F1 interface. The DU 330 may communicate with one or more radio units (RUs) 340 via respective fronthaul links. The RU 340 may communicate with respective UEs 350 via one or more radio frequency (RF) access links. In some implementations, a UE 350 may be served simultaneously by multiple RUs 340.

[0068] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

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

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

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

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

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

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

[0075] Reference will be made to the OFDM waveform (an example of which is given in Figure 4 Various aspects of the present disclosure are described in detail with reference to Figure 1 (illustrated schematically in Figure 2). It should be understood by those skilled in the art that various aspects of the present disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described herein below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0076] Reference now Figure 4 , illustrates an expanded view of an example subframe 402 showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the physical (PHY) layer transmission structure for any particular application may differ from the examples described herein, depending on any number of factors. Here, time is in units of OFDM symbols in the horizontal direction; and frequency is in units of subcarriers of a carrier in the vertical direction.

[0077] Resource grid 404 can be used to schematically represent the time-frequency resources for a given antenna port. In some examples, an antenna port is a logical entity for mapping a data stream to one or more antennas. Each antenna port can be associated with a reference signal (e.g., this can allow a receiver to distinguish data streams associated with different antenna ports in a received transmission). Antenna ports can be defined so that the channel on which a symbol on the antenna port is transmitted can be inferred from the channel on which another symbol on the same antenna port is transmitted. Therefore, a given antenna port can represent a specific channel model associated with a specific reference signal. In some examples, a given antenna port and a subcarrier spacing (SCS) can be associated with a corresponding resource grid (including REs as discussed above). Here, modulated data symbols from a multiple-input multiple-output (MIMO) layer can be combined and redistributed to each antenna port in the antenna port, and then pre-decoding is applied, and the pre-decoded data symbols are applied to the corresponding REs for generating and transmitting OFDM signals via one or more physical antenna elements. In some examples, the mapping of antenna ports to physical antennas can be based on beamforming (e.g., signals can be sent on certain antenna ports to form a desired beam). Thus, a given antenna port may correspond to a particular set of beamforming parameters (eg, signal phase and / or amplitude).

[0078] In a MIMO implementation with multiple available antenna ports, a corresponding number of resource grids 404 may be available for communication. Resource grid 404 is divided into multiple resource elements (REs) 406. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply a resource block (RB) 408, which may contain any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0079] A collection of contiguous or discontinuous resource blocks may be referred to herein as a resource block group (RBG), a subband, or a bandwidth part (BWP). A collection of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 406 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 404. In some examples, an RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE. The RBs may be scheduled by a scheduling entity such as a base station (e.g., a gNB, an eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

[0080] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, although this is only one possible example.

[0081] Each 1 ms subframe 402 may consist of one or more adjacent time slots. Figure 4 In the example shown, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., one to three OFDM symbols). These micro-slots or shortened transmission time intervals (TTIs) may be transmitted in some cases by occupying resources that are scheduled for ongoing time slot transmissions for the same UE or different UEs. Any number of resource blocks may be utilized within a subframe or time slot.

[0082] An expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. In general, the control region 412 may carry control channels, and the data region 414 may carry data channels. Of course, a time slot may contain full DL, full UL, or at least one DL portion and at least one UL portion. Figure 4 The structure illustrated in is merely an example, and different time slot structures may be utilized and may include one or more of each of the control region and the data region.

[0083] Although in Figure 4Although not illustrated in the figure, each RE 406 within the RB 408 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within the RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of control channels and / or data channels within the RB 408.

[0084] In some examples, time slot 410 may be utilized for broadcast, multicast, groupcast, or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast or groupcast communications are delivered to multiple intended receiving devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0085] In an example of cellular communication on a cellular carrier via a Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to one or more scheduled entities (e.g., UEs) to carry DL control information including one or more DL control channels (such as a physical downlink control channel (PDCCH)). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​transmission and UL transmission. The PDCCH may further carry a hybrid automatic repeat request (HARQ) feedback transmission, such as an acknowledgement (ACK) or a negative acknowledgement (NACK). HARQ is a technique well known to those of ordinary skill in the art, wherein the integrity of a packet transmission may be checked for accuracy at the receiving side, for example, using any appropriate integrity check mechanism, such as a checksum or a cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be sent, and if it is not confirmed, a NACK may be sent. In response to the NACK, the sending device may transmit a HARQ retransmission, which may implement trace combining, incremental redundancy, and the like.

[0086] The base station may also allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5ms, 10ms, 20ms, 30ms, 80ms, or 130ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, to identify the center of the channel (system) bandwidth in the frequency domain, and to identify the physical cell identity (PCI) of the cell.

[0087] The PBCH in the SSB may also include a master information block (MIB) containing various system information and parameters for decoding a system information block (SIB). The SIB may be, for example, SystemInformationType 1 (SIB1), which may include various additional (remaining) system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information sent in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, grid offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) sent in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also send other system information (OSI).

[0088] In UL transmission, the UE may utilize one or more REs 406 to carry UL control information (UCI) to the scheduling entity, and the UL control information (UCI) includes one or more UL control channels, such as a physical uplink control channel (PUCCH). The UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmission. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., requesting the scheduling entity to schedule uplink transmission. In this article, in response to the SR sent on the UCI, the scheduling entity may send downlink control information (DCI), which may schedule resources for uplink packet transmission. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other appropriate UCI.

[0089] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for data traffic. Such data traffic may be carried on one or more traffic channels, such as for DL ​​transmissions, on a physical downlink shared channel (PDSCH); or for UL transmissions, on a physical uplink shared channel (PUSCH). In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0090] In an example of sidelink communication on a sidelink carrier via a proximity service (ProSe) PC5 interface, a control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH) including sidelink control information (SCI) sent by an initiating (transmitting) sidelink device (e.g., a transmitting (Tx) V2X device or other Tx UE) toward a set of one or more other receiving sidelink devices (e.g., a receiving (Rx) V2X device or some other Rx UE). A data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH) including sidelink data traffic sent by the initiating (transmitting) sidelink device within resources reserved by the transmitting sidelink device on the sidelink carrier via the SCI. Other information may also be sent via various REs 406 within the time slot 410. For example, the HARQ feedback information may be sent from the receiving side link device to the transmitting side link device in a physical sidelink feedback channel (PSFCH) within time slot 410. Additionally, one or more reference signals may be sent within time slot 410, such as a sidelink SSB, a sidelink CSI-RS, a sidelink SRS, and / or a sidelink positioning reference signal (PRS).

[0091] These physical channels described above are typically multiplexed and mapped to transport channels for processing at the medium access control (MAC) layer. The transport channels carry information blocks called transport blocks (TBs). Based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission, the transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter.

[0092] References Figures 1 to 4 The channels or carriers described are not necessarily all channels or carriers that may be utilized between a scheduling entity and a scheduled entity, and one of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.

[0093] Transport blocks may be communicated between a scheduling entity (e.g., a base station such as a gNB) and a scheduled entity (e.g., a UE) via downlink resources or uplink resources allocated for the transport blocks in a time slot. When operating in full-duplex mode, both downlink and uplink resources may be allocated within symbols of the same time slot for transmission of both downlink and uplink transport blocks, respectively. In some examples, downlink and uplink resources may overlap in time (e.g., one or more symbols of a time slot may carry both downlink and uplink transport blocks). For example, simultaneous transmissions in different directions (uplink and downlink) may use frequency division duplexing (FDD) in a paired spectrum (e.g., carrying transmissions in different directions on different carrier frequencies) or in an unpaired spectrum (e.g., carrying transmissions in different directions on a single carrier bandwidth).

[0094] FIG. 5A to FIG. 5C An example of full-duplex communication in an unpaired spectrum is illustrated. FIG. 5A to FIG. 5C In the example shown, time is in the horizontal direction and frequency is in the vertical direction.Here, carrier bandwidth 502 (or a set of one or more active bandwidth parts (BWPs)) is illustrated along the frequency axis, and time slots 504 are illustrated along the time axis.

[0095] Figure 5A and Figure 5B In-band full-duplex (IBFD) communication is illustrated, while Figure 5C Sub-band FDD communication is illustrated. For IBFD communication, Figure 5A and Figure 5B As shown, downlink transmissions and uplink transmissions occur on the same time and frequency resources. For example, downlink resources 506 allocated for transmissions in the downlink direction overlap in both time and frequency with uplink resources 508 allocated for transmissions in the uplink direction. The overlap may be a complete overlap (e.g., Figure 5A as shown) or partially overlapped (as shown Figure 5B shown).

[0096] For sub-band FDD communication, such as Figure 5CAs shown, carrier bandwidth 502 (or active BWP) can be divided into sub-bands 510a and 510b. Each sub-band 510a and 510b can be allocated for communication in a single direction. For example, sub-band 510a can be allocated for downlink transmission, and sub-band 510b can be allocated for uplink transmission. Therefore, the downlink resource 506 allocated for the transmission in the downlink direction overlaps with the uplink resource 508 allocated for the transmission in the uplink direction in time, but does not overlap in frequency. Downlink resource 506 can also be separated from uplink resource 508 in the frequency domain by guard band 512 to isolate uplink and downlink transmission in frequency.

[0097] Fig. 6A A network entity 602 (eg, such as a Figures 1 to 3 600 is a schematic diagram of an antenna array 600 (shown in any one of the figures). The antenna array 600 is divided into two panels (panel 1 604, panel 2 606) with a physical separation 608 between the two panels. Each of the two panels can be a subarray of the antenna. A given panel can transmit and / or receive a beam or beam group. In one example, the panels can be physically separated from each other by a distance selected to provide improved isolation between simultaneous transmit (Tx) and receive (Rx) operations in full-duplex mode, thereby mitigating at least a portion of the self-interference caused by the simultaneously transmitted / received signals. Fig. 6A The multi-panel antenna configuration shown may also be applicable to a UE to achieve full-duplex communication at the UE.

[0098] Figure 6B Based on some aspects of use Fig. 6A Schematic diagram of an example of sub-band full-duplex wireless communication 610 for a multi-panel antenna array 600 shown in FIG. Figure 6B In the example shown, time is in the horizontal direction, in units of time slots 612a-612d, each of which includes multiple OFDM symbols; and frequency is in the vertical direction. Here, the carrier bandwidth 614 (or a set of one or more active BWPs) is illustrated along the frequency axis. The carrier bandwidth 614 (or active BWP) can be divided into multiple sub-bands 650a-650c for sub-band FDD full-duplex operation.

[0099] exist Figure 6BIn the example shown, in time slot 612a, antenna array 600 is first configured for downlink (DL) communication (e.g., DL burst 616 and DL data portion 618). DL burst 616 may include DL control sent in the first few symbols of time slot 612a. DL control 616 may include, for example, a physical downlink control channel (PDCCH) carrying DCI that may be related to time slot 612a or a previous time slot or a subsequent time slot. In one example, DCI may include common DCI or UE-specific DCI. Common DCI may include, for example, public control information broadcast to a group of UEs or all UEs in a cell. UE-specific DCI may include, for example, HARQ feedback information (e.g., ACK / NACK), scheduling information for downlink data transmission and / or uplink transmission in scheduling time slot 612a or a subsequent time slot (e.g., time slots 612b, 612c, and / or 612d), and other suitable information. DL burst 616 may also include various DL reference signals (e.g., SSB and / or CSI-RS). In this example, both panel 1 604 and panel 2 606 may be configured for DL ​​transmission. The DL data portion 618 may include, for example, DL data carried within a PDSCH. In addition to the DL data, the DL data portion 618 may also include a DL reference signal (eg, DMRS) for demodulating and decoding the DL data.

[0100] The time slot 612a may also include a common uplink (UL) burst 622 at the end of the time slot 612a. The common UL burst 622 may include, for example, a PUCCH carrying UCI and other UL signals. Figure 6B , the end of the DL data portion 618 may be separated in time from the beginning of the UL burst 622. This time separation 620 may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. Such separation may provide time for network entities and UEs to perform switching between transmission and reception, or vice versa. In this example, both panel 1 604 and panel 2 606 may be configured for UL transmission during the UL burst 622.

[0101] In time slots 612b and 612c, antenna array 600 is configured for both DL communication and UL communication. For example, in time slots 612b and 612c, carrier bandwidth 614 (or active BWP) is shown as divided between uplink transmission and downlink transmission. Subbands 650a and 650b are allocated for downlink transmission, while subband 650c is allocated for uplink transmission. In the example operation of the subband full-duplex configuration shown in Figure 6, panel 1 604 can be configured for DL ​​transmission at two edges (e.g., subbands 650a and 650b) of carrier bandwidth 614 (or active BWP), and panel 2 606 can be configured for UL reception at the middle (e.g., subband 650c) of carrier bandwidth 614 (or active BWP).

[0102] In each of the sub-band FDD time slots 612b and 612c, the DL sub-bands 650a and 650b include DL bursts 624 and 634, respectively, which may include a PDCCH carrying DCI and / or DL ​​reference signals in the initial portion of the time slots 612b and 612c. After the DL bursts 624 and 634, the time slots 612b and 612c each include a DL data portion 626 and 636 for sending DL data in the sub-bands 650a and 650b, respectively. For example, the DL data may be sent in the PDSCH. In addition to the DL data, the DL data portions 626 and 636 may also include a DL reference signal (e.g., DMRS) for demodulating and decoding the DL data.

[0103] In the uplink (UL) subband 650c, time slots 612b and 612c each include a UL data portion 628 and 638, respectively, for transmitting UL data. For example, the UL data may be transmitted within a PUSCH. After the UL data portions 628 and 638, the UL subband 650c of time slots 612b and 612c include UL bursts 630 and 640, respectively. The UL bursts 630 and 640 may include, for example, a PUCCH including UCI and / or other UL signals. A guard band 632 is also provided between the UL subband 650c and the DL subbands 650a and 650b to mitigate self-interference between simultaneous DL transmissions in the DL subbands 650a and 650b and UL transmissions in the UL subband 650c.

[0104] Slots 612b and 612c are sub-band full-duplex FDD time slots that multiplex uplink and downlink transmissions in frequency using FDM. The sub-band full-duplex time slot configuration shown in FIG. 6 is exemplary only, and other configurations of sub-band full-duplex time slots may be utilized in various aspects of the present disclosure. For example, in various aspects, other configurations including UL and DL sub-bands may be employed (e.g., Figure 4C or other suitable sub-band configurations).

[0105] In time slot 612d, antenna array 600 is configured for UL communication. For example, time slot 612d includes UL data portion 642, followed by UL burst 644. UL data portion 642 and UL burst 644 may include UL control information and / or UL data, as described above. In this example, panel 1 604 and panel 2 606 may both be configured for UL reception. Time slots 612a and 612d are half-duplex TDD time slots that utilize TDM to time-multiplex DL transmission and UL transmission.

[0106] For frequency domain resource allocation (FDRA), it should be noted that FDRA in NR is similar to FDRA in LTE, except that NR frequency resources are allocated per BWP, while LTE frequency resources are allocated over the entire carrier bandwidth. It should also be noted that NR supports two types of resource allocation schemes (Type 0 or Type 1), where the specific resource allocation type is implicitly determined by the DCI format or RRC layer message.

[0107] In type 0 resource allocation, a bitmap-based resource allocation scheme is used, where the RB allocation information includes a bitmap indicating the resource block groups (RBGs) allocated to the scheduled UE, where the resources are allocated in multiple RBGs. The number of RBs within an RBG varies depending on the BWP size and configuration type, as shown in Table 1 below, where the configuration type is determined by the rbg size field in the PDSCH-Config included in the RRC message.

[0108] Bandwidth portion size Configuration 1 Configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0109] Table 1

[0110] In Type 1 resource allocation, only contiguous allocation of virtual resource blocks (VRBs) is supported. Here, the network provides the UE with a coded resource indicator value (RIV), which corresponds to the starting virtual resource block number RB. start and the length of the consecutively allocated VRBs (L RB ). For example, RIV can be calculated according to the following equation:

[0111] if but

[0112]

[0113] otherwise

[0114]

[0115] (Equation 1)

[0116] Next reference Figure 7 , an exemplary sub-band full-duplex (SBFD) resource allocation without partial resource block groups (RBGs) is shown. For this example, each of the DL sub-band 720, the guard band 730, the UL sub-band 740, the guard band 750, and the DL sub-band 760 is aligned with the RBGs 700-717, as shown. Here, for a type 0 resource allocation across two DL sub-bands 720 and 760, the frequency resources mapped to the UL sub-band 740 and the guard bands 730 and 750 are not used for allocation. However, this may cause various problems. For example, there may be limited DL / UL sub-band configurations to accommodate the resolution of the RBGs (each including 2, 4, 8, or 16 RBs) to align the RBGs 700-717 with the sub-band sizes of the UL sub-band 740 and the guard bands 730 and 750. This problem is even more significant for large DL bandwidth parts (BWPs) (e.g., where the BWP>145 RBs and the RBG size is 16 RBs). Additionally, this results in limited scheduling flexibility when the DL subbands are not aligned with the RBGs, where the RBGs at the edges of the DL subbands cannot be used.

[0117] In one example, to facilitate more flexibility in scheduling of UL and DL subbands while maintaining the same DCI overhead, SBFD-aware UEs may be configured to allow partial RBGs to exist at the edge of DL subbands. For example, the first and last RBGs in each subband may be partial RBGs, whereby the network (e.g., gNB) may provide a bitmap to the UE indicating the use of corresponding PRBs within the partial RBGs for DL ​​or UL communications. This enhancement may be based on, for example, the UE's ability to support partial RBGs in SBFD communications.

[0118] Next reference Figure 8 According to some aspects, an exemplary SBFD resource allocation with partial RBGs is provided. For this example, each of DL subband 820, guard band 830, UL subband 840, guard band 850, and DL subband 860 is aligned with RBGs 800-817, as shown. Here, it is assumed that the RBG size is 16 RBs, where the size of DL subband 820 is 90 RBs and the size of DL subband 860 is 106 RBs. As shown, DL subband 820 only uses some RBs in RBG 805 (i.e., 10 of the 16 RBs), while DL subband 860 only uses some RBs in RBG 810 (i.e., 7 of the 16 RBs) and some RBs in RBG 817 (i.e., 3 of the 16 RBs). To accommodate such partial RBGs, SBFD scheduling of RBGs can be based on the size of DL subband 820 and / or DL ​​subband 860, rather than the size of the corresponding DL bandwidth part (BWP).

[0119] In the specific example, the size is The total number of RBGs of downlink subband i of PRBs (N RBG ) is given by the following equation:

[0120]

[0121] in

[0122] The size of the first RBG in a subband is

[0123] The size of the last RBG in a subband is The condition is Otherwise, P, and

[0124] All other RBGs are of size P.

[0125] In the case where the network schedules DL transmissions (or UL transmissions) across more than one DL (or UL subband), the size is and The total number of RBGs of downlink subband i and subband j (N RBG ) are given by the following equations:

[0126]

[0127] in

[0128] The size of the first RBG in subband i is

[0129] The size of the first RBG in subband j is

[0130] The size of the last RBG in subband i is The condition is Otherwise, all other RBGs are of size P, and

[0131] The size of the last RBG in subband j is The condition is Otherwise, it is P, and all other RBGs have size P.

[0132] In another exemplary solution disclosed herein, a new table with higher resolution RBG size (ie, smaller RBG size) is introduced specifically for SBFD timeslots. For example, Table 2 below can be used for SBFD timeslots, while Table 1 can be used for non-SBFD timeslots.

[0133] Bandwidth portion size Configuration 1 Configuration 2 1-36 2 2 37-72 2 4 73-144 4 8 145-275 8 8

[0134] Table 2

[0135] Alternatively, rather than using multiple tables, Table 1 may be modified to include an additional column specifically for SBFD time slots. For example, Table 1 may be modified to include a third configuration, as illustrated in Table 3 below, where Configuration 3 is used to schedule SBFD time slots, while Configurations 1 and 2 are used to schedule non-SBFD time slots.

[0136] Bandwidth portion size Configuration 1 Configuration 2 Configuration 3 1-36 2 4 1 37-72 4 8 2 73-144 8 16 4 145-275 16 16 8

[0137] Table 3

[0138] Similarly, partial PRGs may also be utilized, where the size of the first and last PRGs of a subband are not necessarily equal to each other or to other PRGs within the subband. As background, it is important to note that the precoding granularity P′ for non-SBFD slots is BWP,i It is usually defined as 2 RBs or 4 RBs, where it should be understood that PRG uses P′ BWP,i The bandwidth part i is divided into consecutive PRBs, and the actual number of consecutive PRBs in each PRG can be one or more. In addition, when determining the size of the first and last PRGs of a non-SBFD time slot, it should be noted that such size is generally based on the starting RB of bandwidth part i. and the length of bandwidth part i For example, the size of the first and last PRG of a non-SBFD timeslot can be determined as follows:

[0139] and

[0140] The condition is

[0141] Otherwise, the last PRG consists of P′ BWP,i Given.

[0142] (Equation 4)

[0143] However, for SBFD slots, this method for determining the PRG size is undesirable because the size of the first and last PRGs within each scheduled subband is not necessarily equal to the indicated P′. BWP,i To overcome this limitation, aspects disclosed herein include examples where the size of the first and last PRG within each scheduled subband is based on the effective available resources of each subband, which is defined as the overlap of a particular subband with the corresponding BWP portion of the UE. In a specific example, the size of the first and last PRG within each scheduled subband can therefore be based on the starting RB of the effective subband. and the length of the effective subband Instead of the starting RB of bandwidth part I and the length of bandwidth part i For example, the size of the first and last PRG of a SBFD slot can be determined as follows:

[0144] and

[0145] The condition is

[0146] Otherwise, the last PRG consists of P′ BWP,i Given.

[0147] (Equation 5)

[0148] Back to Reference About Figure 8 The example described now provides an exemplary calculation of the PRG size for the first and last PRG of each of DL subband 820 and DL subband 860. Here, again, an RBG size of 16 RBs is assumed, where the size of DL subband 820 is 90 RBs and the size of DL subband 860 is 106 RBs. For calculating the PRG size of the first and last PRG of DL subband 820, it is therefore important to note that P′ BWP,i =4, and This results in the size of the first PRG being 4 RBs and the size of the last PRG being 2 RBs. For calculating the PRG size of the first and last PRGs of DL subband 860, it should be noted that P′ BWP,i =4, and This results in the first PRG having a size of 4 RBs and the last PRG having a size of 2 RBs.

[0149] In another example, it is noted that the PRG size for each subband within the UE BWP can be further optimized. For example, for static bundling (i.e., where prb-BundlingType is set to "staticBundling"), the gNB can configure the RRC parameter "bundleSize" to indicate a set of PRG size values Where P′ BWP,i The value of is mapped to the PRG size in the TDD time slot, and and The value of is mapped to the corresponding PRG size for each subband.

[0150] Next reference Figures 9 to 13 , various illustrations of exemplary valid DL / UL subbands are provided according to some aspects. For example, Fig. 9A first example is illustrated, wherein a first valid DL subband 920 is determined by an overlap of a DL subband 910 and a corresponding DL BWP 900, and wherein a second valid DL subband 922 is determined by an overlap of a DL subband 912 and a corresponding DL BWP 900. Fig.10 , an example is provided where each of the DL subbands 1010 and 1012 completely overlaps with the DL BWP 1000, which results in effective DL subbands 1020 and 1022 as shown.

[0151] exist Fig.11 and Fig.12 In some aspects, examples of valid UL subbands are provided. For example, Fig.11 A first example is illustrated, in which the effective UL subband 1110 is determined by the overlap of the UL subband 1120 and the corresponding UL BWP 1100. Fig.12 , an example is provided where the UL sub-band 1210 completely overlaps with the UL BWP 1200, which results in an effective UL sub-band 1220 as shown.

[0152] Fig.13 Example valid UL subbands and example valid DL subbands according to some aspects are illustrated. In this example, the UE is configured with DL / UL BWP pairs 1310 and 1315 having the same center frequency, and wherein the configuration of DL subband 1300 and UL subband 1305 is provided by the gNB. As shown, valid DL subband 1320 is based on available frequency resources that overlap between DL subband 1300 and active DL-BWP 1310. Similarly, valid UL subband 1325 is based on available frequency resources that overlap between UL subband 1305 and active UL BWP 1315.

[0153] In further examples, the SBFD scheduling aspects disclosed herein are also expected to facilitate utilizing finer granularity frequency domain resource allocation (FDRA) bit widths during SBFD operation while maintaining the same DCI overhead as the corresponding TDD time slot, or reducing the DCI overhead in the SBFD time slot while maintaining the same scheduling granularity in the TDD time slot. Figure 8In the example provided, where it is assumed that the size of DL subband 820 is 90 RBs and the size of DL subband 860 is 106 RBs, it should also be assumed that the size of UL subband 840 is 62 RBs, and each of guard band 830 and guard band 850 is 6 RBs. For this particular SBFD configuration, the size of the UL / DL BWP is therefore 270 RBs, which includes two DL subbands (i.e., DL subbands 820 and 860) and one UL subband (i.e., UL subband 840). For type 0 resource allocation, the nominal RBG size P of each of the BWP, DL subbands 820 and 860, and UL subband 840 can then be determined with reference to Table 1. For example, assuming that the parameter rbg size is 18 bits, the nominal RBG size P of the BWP is 16 RBs for both configurations 1 and 2, because the size of the BWP is 270 RBs. For DL ​​subbands 820 and 860, assuming that the parameter rbg size is 18 bits (i.e., configuration 1), the nominal RBG size P for each of DL subbands 820 and 860 is 8 RBs (i.e., because their respective lengths are 90 RBs and 106 RBs), while a value of 9 bits for the parameter rbg size (i.e., configuration 2) results in a nominal RBG size P of 16 RBs for each of DL subbands 820 and 860. For UL subband 840, assuming that the parameter rbg size is 18 bits (i.e., configuration 1), the nominal RBG size P is 4 RBs (i.e., because the length of UL subband 840 is 62 RBs), while a value of 9 bits for the parameter rbg size (i.e., configuration 2) results in a nominal RBG size P of 8 RBs. From these examples, it should therefore be noted that configuration 1 allows for better resolution, while configuration 2 is able to compress the DCI by half and potentially achieve better resolution, as shown in the UL subband 840 example.

[0154] In some aspects disclosed herein, when the gNB schedules PxSCH in one subband, the FDRA bit field in the DCI may be interpreted based on the subband size instead of the BWP size. For example, for type 0 resource allocation, the UE may utilize a new table (such as Table 4 below) to determine the nominal RBG size based on the indicated subband size.

[0155] The indicated subband size Configuration 1 Configuration 2 1-36 2 2 37-72 2 4 73-144 4 8 145-275 8 8

[0156] Table 4

[0157] In further aspects disclosed herein, type 1 resource allocation (i.e., RIV-based resource allocation) may also be based on subband size. For example, the number of starting RBs and VRBs may be based on subband size as shown below:

[0158] but

[0159]

[0160] otherwise

[0161]

[0162] Among them RB start is the first RB in the scheduled subband;

[0163] Where L RBs ≥1; and

[0164] Among them RB start Should not exceed L RBs .

[0165] (Equation 6)

[0166] In other aspects disclosed herein, two DCI bit fields may be added to improve scheduling flexibility, while FDRA is still based on BWP size. For example, DCI may include a bit field for indicating one or more subbands for scheduling. For example, when there are two subbands, the "subband indicator" bit field may be two bits, where the indicated value "10" may indicate scheduling in the first subband; the indicated value "01" may indicate scheduling in the second subband; and the indicated value "11" may indicate scheduling in both subbands.

[0167] In addition, to improve flexibility, dynamic switching between configuration 1 and configuration 2 can be indicated by a DCI bit field. For example, the values ​​of the "subband indicator" and the "RBG configuration indicator" can be included in a new DCI bit field, or jointly encoded with the FRDA bit field (e.g., by utilizing unused bit fields of other subbands or by utilizing the least significant bit (LSB) or the most significant bit (MSB)).

[0168] In another example, when the gNB is scheduled in two or more subbands, the FRDA bit field can be based on the effective available frequency resources in the SBFD slot. For Type 1 resource allocation, for example, It can refer to the number of available RBs in the DL BWP excluding the guard band RBs and UL subband RBs, or equal to That is, the number of combined DL RBs across valid DL subbands. It can refer to the number of available RBs in the UL BWP excluding the guard band RBs and DL subband RBs, or equal to That is, the number of combined UL RBs across the valid UL subband.

[0169] For type 0 resource allocation, Can refer to Fig.1414. The size of the effective DL (or UL) subbands combined in the DL (or UL) BWP is shown. As shown, for this particular example, each of the DL subband 1420, guard band 1430, UL subband 1440, guard band 1450, and DL subband 1460 is aligned with RBGs 1400-1417. Here, it is assumed that the RBG size is 16 RBs and the BWP is 272 RBs, where the size of DL subband 1420 is 90 RBs and the size of DL subband 1460 is 106 RBs. The size of the total DL subband 1470 is therefore 196 RBs, where the total DL subband 1470 uses only some of the RBGs 1412 (i.e., only 4 of the 16 RBs).

[0170] Fig.15 1 is a block diagram conceptually illustrating an example of a hardware implementation of a user equipment (UE) 1500 employing a processing system 1514 in accordance with some aspects of the present disclosure. According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1514, which includes one or more processors 1504. In some implementations, the UE 1500 may correspond to any of the UEs or scheduled entities shown in any of the figures included herein.

[0171] UE 1500 may be implemented using a processing system 1514 that includes one or more processors 1504. Examples of processors 1504 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. In various examples, UE 1500 may be configured to perform any one or more of the functions described herein. That is, the processor 1504 as utilized in UE 1500 may be used to implement any one or more of the processes and procedures described below.

[0172] In this example, the processing system 1514 may be implemented using a bus architecture, which is generally represented by bus 1502. Bus 1502 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1514 and the overall design constraints. Bus 1502 communicatively couples various circuits including one or more processors (which are generally represented by processor 1504), memory 1505, and computer readable media (which are generally represented by computer readable media 1506). Bus 1502 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1508 provides an interface between bus 1502 and transceiver 1510 and between bus 1502 and interface 1530. Transceiver 1510 provides a communication interface or component for communicating with various other devices through a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1510, each transceiver being configured to communicate with a corresponding network type (e.g., terrestrial or non-terrestrial). At least one interface 1530 (e.g., a network interface and / or a user interface) provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices housed in the same device as UE 1500 or external devices) through an internal bus or via an external transmission medium (such as an Ethernet cable).

[0173] The processor 1504 is responsible for managing the bus 1502 and general processing, including executing software stored on the computer-readable medium 1506. The software, when executed by the processor 1504, causes the processing system 1514 to perform the various functions described below for any particular device. The computer-readable medium 1506 and the memory 1505 may also be used to store data that is manipulated by the processor 1504 when executing the software.

[0174] One or more processors 1504 in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer readable medium 1506.

[0175] Computer readable medium 1506 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1506 may reside in processing system 1514, be located outside processing system 1514, or be distributed across multiple entities including processing system 1514. Computer readable medium 1506 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.

[0176] UE 1500 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 7 to 14 As described and as follows Fig.16 In some aspects of the present disclosure, the processor 1504 as utilized in the UE 1500 may include circuits configured for various functions.

[0177] In one aspect, the processor 1504 may include a communication and processing circuit 1541. The communication and processing circuit 1541 may include one or more hardware components that provide a physical structure that performs various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1541 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuit 1541 may include two or more transmit / receive chains. The communication and processing circuit 1541 may be further configured to execute communication and processing software 1551 included on the computer-readable medium 1506 to implement one or more functions described herein.

[0178] The processor 1504 also includes an SBFD circuit 1542 configured to implement various aspects disclosed herein. For example, the SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 and configured to receive scheduling information, the scheduling information including a configuration of SBFD frequency resources for one or more subbands, wherein the configuration is based on the size of the one or more subbands and the size of the BWP associated with the UE 1500 (e.g., wherein the BWP associated with the UE 1500 has a BWP size of at least 145 resource blocks), and wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands. The SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 and further configured to communicate with the network via the SBFD frequency resources based on the scheduling information. The SBFD circuit 1542 may also be configured to execute the SBFD instructions 1552 included on the computer-readable medium 1506 to implement one or more functions described herein.

[0179] In further aspects, the configuration of the SBFD frequency resources may include at least two RBGs having different RBG sizes within each of the one or more subbands. In such an example, the SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 to configure the UE 1500 to communicate with the network via at least two RBGs. For example, the at least two RBGs within each of the one or more subbands may include a first subband RBG and a last subband RBG, and wherein the RBG size of the RBGs between the first subband RBG and the last subband RBG each has a different RBG size from the first subband RBG and the last subband RBG. In another example, the configuration of the SBFD frequency resources includes making the RBG size of the SBFD symbol different from the RBG size of the non-SBFD symbol.

[0180] In another example, the configuration of the SBFD frequency resources may include at least two PRGs with different PRG sizes within each of the one or more subbands. In such an example, the SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 to configure the UE 1500 to communicate with the network via the at least two PRGs. For example, the at least two PRGs within each of the one or more subbands may include a first subband PRG and a last subband PRG, and wherein the PRG size of the first subband PRG is different from the PRG size of the last subband PRG.

[0181] In another example, the SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 to configure the UE 1500 to refer to a first table for determining the RBG size of the SBFD time slot, and to refer to a second table for determining the RBG size of the non-SBFD time slot. Alternatively, the SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 to configure the UE 1500 to refer to the same table for determining the RBG size of the SBFD time slot and the RBG size of the non-SBFD time slot.

[0182] In yet another example, the scheduling information may further include an indication of static bundling of PRG sizes, wherein the SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 to configure the UE 1500 to determine the PRG size based on a static bundling algorithm. Alternatively, the scheduling information may further include an indication of dynamic bundling of PRG sizes, wherein the SBFD circuit 1542 may be combined with the communication and processing circuit 1541 and / or the transceiver 1510 to configure the UE 1500 to determine the PRG size based on a dynamic bundling algorithm.

[0183] In another example, the configuration of the SBFD frequency resources may include the number of bits allocated for the FDRA in the SBFD time slot based on the available resources in the SBFD time slot, wherein the available resources in the SBFD time slot are determined by the overlap of the corresponding subband in the one or more subbands and the BWP associated with the UE. In such an example, the configuration of the SBFD frequency resources may also include a configuration across multiple non-contiguous subbands, wherein the available resources in the SBFD time slot are determined by the overlap of the multiple non-contiguous subbands and the BWP associated with the UE 1500. Alternatively, the configuration of the SBFD frequency resources may include a configuration across a single subband, wherein the available resources in the SBFD time slot are determined by the overlap of the single subband and the BWP associated with the UE 1500.

[0184] In yet another example, it is contemplated that the scheduling information may include a downlink control information (DCI) bit field.For example, the scheduling information may include at least one DCI bit field indicating one or more subbands for data scheduling in the SBFD time slot.

[0185] Fig.16 1 is a flow chart illustrating an example wireless communication method 1600 implemented by a UE according to some aspects of the present disclosure. As described herein, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for implementation of all examples. In some examples, method 1600 may be implemented by Fig.15In some examples, the method 1600 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0186] At block 1602, the UE may receive scheduling information including a configuration of SBFD frequency resources for one or more subbands, wherein the configuration is based on a size of the one or more subbands and a size of a BWP associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands. In one aspect, the process of block 1602 may be implemented by a component for receiving scheduling information, which in a specific aspect may be implemented by the processor 1504, the communication and processing circuit 1541, and / or the transceiver 1510, or an equivalent thereof.

[0187] In addition, at block 1604, the UE may configure the UE to communicate with the network via the SBFD frequency resources based on the scheduling information. In one aspect, the process of block 1604 may be implemented by a component for communicating with the network, and in a specific aspect, the component may be implemented by the processor 1504, the communication and processing circuit 1541, and / or the SBFD circuit 1542, or an equivalent thereof.

[0188] Fig.17 1700 is a block diagram conceptually illustrating an example of a hardware implementation of a network node or entity 1700 employing a processing system 1714 according to some aspects of the present disclosure. According to various aspects of the present disclosure, an element or any portion of an element or any combination of elements may be implemented using a processing system 1714, which includes one or more processors 1704. In some implementations, the network entity 1700 may correspond to any of the BSs (e.g., gNBs, eNBs, etc.) or scheduling entities shown in any of the figures included herein. In further aspects, the network entity 1700 may be configured as a base station operable in an open RAN (O-RAN) environment, wherein the base station (e.g., 1700) is decomposed and includes different parts, including a distributed unit (DU), a centralized unit (CU), and a radio unit (RU). In yet other aspects, the disclosed and illustrated processing portions of the network entity 1700 may be implemented within a RU, a DU, and / or a CU, or within a portion of each. In addition, the network entity 1600 may be a stationary network entity or a mobile network entity.

[0189] The network entity 1700 may be implemented using a processing system 1714 that includes one or more processors 1704. Examples of processors 1704 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. In various examples, the network entity 1700 may be configured to perform any one or more of the functions described herein. That is, the processor 1704 as utilized in the network entity 1700 may be used to implement any one or more of the processes and procedures described herein.

[0190] In this example, the processing system 1714 may be implemented using a bus architecture, which is generally represented by bus 1702. Bus 1702 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1714 and the overall design constraints. Bus 1702 communicatively couples various circuits including one or more processors (which are generally represented by processor 1704), memory 1705, and computer readable media (which are generally represented by computer readable media 1706). Bus 1702 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. Bus interface 1708 provides an interface between bus 1702 and transceiver 1710 and between bus 1702 and interface 1730. Transceiver 1710 provides a communication interface or component for communicating with various other devices over a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1710, each transceiver being configured to communicate with a corresponding network type (e.g., terrestrial or non-terrestrial). At least one interface 1730 (e.g., a network interface and / or a user interface) provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices housed in the same device as the network entity 1700 or an external device) through an internal bus or an external transmission medium (such as an Ethernet cable).

[0191] The processor 1704 is responsible for managing the bus 1702 and general processing, including executing software stored on the computer-readable medium 1706. The software, when executed by the processor 1704, causes the processing system 1714 to perform the various functions described below for any particular device. The computer-readable medium 1706 and the memory 1705 may also be used to store data that is manipulated by the processor 1704 when executing the software.

[0192] One or more processors 1704 in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer readable medium 1706.

[0193] Computer readable medium 1706 may be a non-transitory computer readable medium. Non-transitory computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., cards, sticks or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer readable medium 1706 may reside in processing system 1714, be located outside processing system 1714, or be distributed across multiple entities including processing system 1714. Computer readable medium 1706 may be embodied in a computer program product. For example, a computer program product may include a computer readable medium in a packaging material. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure, depending on the specific application and the overall design constraints imposed on the overall system.

[0194] The network node 1700 may be configured to perform any one or more of the operations described herein (e.g., as described above in conjunction with Figures 7 to 14 Described and combined as follows Fig.18 In some aspects of the present disclosure, the processor 1704 as utilized in the network entity 1700 may include circuits configured for various functions.

[0195] Processor 1704 may be configured to generate, schedule, and modify resource assignments or grants of time-frequency resources (e.g., a set of one or more resource elements). For example, processor 1704 may schedule time-frequency resources within multiple time division duplex (TDD) and / or frequency division duplex (FDD) subframes, time slots, and / or mini-slots to carry user data traffic and / or control information to and / or from multiple UEs.

[0196] Processor 1704 may be configured to schedule resources for transmission of downlink reference signals (e.g., SSB or CSI-RS) or DCI (or SRS triggering) on ​​multiple downlink beams for downlink beam scanning according to the selected downlink beam scanning type and the selected number of downlink reference signal resources indicated in the request for uplink beam refinement received from the UE. Processor 1704 may also be configured to schedule resources for uplink transmission of uplink reference signals (e.g., SRS) on multiple uplink beams for uplink beam scanning according to the selected beam scanning type and the selected number of uplink reference signal resources indicated in the request. Processor 1704 may further be configured to schedule resources that the UE may use to send the request. For example, the uplink beam refinement request resources may include resources scheduled for transmission of PUCCH, PUSCH, PRACH opportunities, or RRC messages. In some examples, processor 1704 may be configured to schedule PUSCH resources for an uplink beam refinement request in response to receiving a scheduling request from a UE.

[0197] Processor 1704 may also be configured to schedule resources for transmission of uplink signals. In some examples, based on an indication of an uplink signal associated with one or more uplink transmit beams included in the request, resources may be associated with one or more uplink transmit beams and one or more corresponding receive beams applied to the uplink signal (e.g., based on an uplink BPL). In some examples, resources may be associated with an uplink transmission scheme that indicates the number of uplink transmit beams to be used for the uplink signal, the number of repetitions per uplink transmit beam of the uplink signal, and a multiplexing scheme when more than one uplink transmit beam is used to transmit the uplink signal.

[0198] The processor 1704 may include a communication and processing circuit 1741. The communication and processing circuit 1741 may include one or more hardware components that provide a physical structure that performs various processes related to wireless communication (e.g., signal reception and / or signal transmission) as described herein. The communication and processing circuit 1741 may also include one or more hardware components that provide a physical structure that performs various processes related to signal processing (e.g., processing received signals and / or processing signals for transmission) as described herein. In some examples, the communication and processing circuit 1741 may include two or more transmit / receive chains. In another example, the communication and processing circuit 1741 may be configured to convey higher layer information, such as RRC configuration information, to the UE. The communication and processing circuit 1741 may be further configured to execute communication and processing software 1751 included on the computer-readable medium 1706 to implement one or more functions described herein.

[0199] The processor 1704 also includes an SBFD configuration circuit 1742 configured to implement various aspects disclosed herein. For example, the SBFD configuration circuit 1742 can be combined with the communication and processing circuit 1741 and / or the transceiver 1710 to initiate or cause the network entity 1700 to configure SBFD frequency resources for one or more subbands based on the size of the one or more subbands and the size of the BWP associated with the UE (e.g., where the BWP associated with the UE has a BWP size of at least 145 resource blocks), wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands. The SBFD configuration circuit 1742 can also be combined with the communication and processing circuit 1741 and / or the transceiver 1710 to initiate or cause the network entity 1700 to provide scheduling information to the UE, wherein the scheduling information includes the configuration of the SBFD frequency resources based on the size of the one or more subbands and the size of the BWP associated with the UE. The SBFD configuration circuit 1742 can also be configured to execute the SBFD configuration instructions 1752 included on the computer-readable medium 1706 to implement one or more functions described herein.

[0200] In further aspects, the SBFD frequency resources configured for one or more subbands may include at least two RBGs having different RBG sizes within each of the one or more subbands. In such an example, the at least two RBGs within each of the one or more subbands may include a first subband RBG and a last subband RBG, and wherein the RBG sizes of the RBGs between the first subband RBG and the last subband RBG each have a different RBG size than the first subband RBG and the last subband RBG. The processor 1704 may also be configured to configure the SBFD frequency resources such that the RBG size of the SBFD symbol is different from the RBG size of the non-SBFD symbol.

[0201] In another example, the SBFD frequency resources configured for one or more subbands may include at least two PRGs having different PRG sizes within each of the one or more subbands. In such an example, the at least two PRGs within each of the one or more subbands may include a first subband PRG and a last subband PRG, wherein the PRG size of the first subband PRG is different from the PRG size of the last subband PRG.

[0202] In another example, the SBFD configuration circuit 1742 may be combined with the communication and processing circuit 1741 and / or the transceiver 1710 to initiate or cause the network entity 1700 to provide a configuration of the SBFD frequency resources, the configuration comprising reference to a first table for determining the RBG size of the SBFD time slot, and reference to a second table for determining the RBG size of the non-SBFD time slot. Alternatively, the SBFD configuration circuit 1742 may be combined with the communication and processing circuit 1741 and / or the transceiver 1710 to initiate or cause the network entity 1700 to provide a configuration of the SBFD frequency resources, the configuration comprising reference to the same table for determining the RBG size of the SBFD time slot and the RBG size of the non-SBFD time slot.

[0203] In yet another example, the scheduling information further includes an indication of static bundling of PRG sizes to facilitate the UE to determine the PRG size based on a static bundling algorithm. Alternatively, the scheduling information further includes an indication of dynamic bundling of PRG sizes to facilitate the UE to determine the PRG size based on a dynamic bundling algorithm.

[0204] In another example, the SBFD frequency resources configured for one or more subbands may include a number of bits allocated for the FDRA in the SBFD time slot based on available resources in the SBFD time slot, wherein the available resources in the SBFD time slot are determined by an overlap of a corresponding subband in the one or more subbands and a BWP associated with the UE. In such an example, the SBFD frequency resources configured for one or more subbands include a configuration across multiple non-contiguous subbands, wherein the available resources in the SBFD time slot are determined by an overlap of multiple non-contiguous subbands and a BWP associated with the UE. Alternatively, the SBFD frequency resources configured for one or more subbands may include a configuration across a single subband, wherein the available resources in the SBFD time slot are determined by an overlap of the single subband and a BWP associated with the UE.

[0205] In another example, the scheduling information may further include at least one DCI bit field indicating one or more subbands for data scheduling in the SBFD timeslot.In yet another example, the scheduling information may include at least one DCI bit field indicating dynamic switching between different configurations of RBG granularity of SBFD frequency resources.

[0206] Fig.18 1800 is a flowchart illustrating an example process 1800 for wireless communication according to some aspects of the present disclosure. As described herein, in certain implementations within the scope of the present disclosure, some or all of the illustrated features may be omitted, and some of the illustrated features may not be necessary for implementation of all examples. In some examples, the method 1800 may be performed by Fig.17 The method 1800 may be performed by the network entity 1700 (e.g., a gNB or a base station, including a base station that can operate in an O-RAN environment) illustrated in the example. In some examples, the method 1800 may be performed by any suitable device or component for performing the functions or algorithms described below.

[0207] At block 1802, method 1800 includes configuring SBFD frequency resources for one or more subbands based on a size of the one or more subbands and a size of a BWP associated with a UE, wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands. In one aspect, the process of block 1802 may be implemented by means for configuring SBFD frequency resources, which in a specific aspect may be implemented by processor 1704 and SBFD configuration circuit 1742 or an equivalent thereof.

[0208] In addition, in block 1804, the method 1800 includes providing scheduling information to the UE, wherein the scheduling information includes a configuration of SBFD frequency resources based on the size of one or more subbands and the size of the BWP associated with the UE. In one aspect, the process of block 1804 can be implemented by a component for providing scheduling information, which can be implemented by the processor 1704, the communication and processing circuit 1741, and the transceiver 1710 or their equivalents.

[0209] It is further noteworthy that the present disclosure may include the following further aspects of the present disclosure.

[0210] Aspect 1: A network entity configured for wireless communication, comprising: a memory; and a processor, the processor being coupled to the memory, the processor being configured to: configure SBFD frequency resources for the one or more subbands based on the size of the one or more subbands and the size of the BWP associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands; and provide scheduling information to the UE, wherein the scheduling information includes the configuration of the SBFD frequency resources based on the size of the one or more subbands and the size of the BWP associated with the UE.

[0211] Aspect 2: The network entity according to aspect 1, wherein the SBFD frequency resources configured for the one or more subbands include at least two RBGs having different RBG sizes within each of the one or more subbands.

[0212] Aspect 3: The network entity according to Aspect 2, wherein the at least two RBGs within each of the one or more subbands include a first subband RBG and a last subband RBG, and wherein the RBG sizes of the RBGs between the first subband RBG and the last subband RBG each have a different RBG size from the first subband RBG and the last subband RBG.

[0213] Aspect 4: The network entity according to any one of aspects 1 to 3, wherein the processor is configured to configure the SBFD frequency resources so that the RBG size of the SBFD symbol is different from the RBG size of the non-SBFD symbol.

[0214] Aspect 5: The network entity according to any one of aspects 1 to 4, wherein the SBFD frequency resources configured for the one or more subbands include at least two PRGs with different PRG sizes within each of the one or more subbands.

[0215] Aspect 6: The network entity according to Aspect 5, wherein the at least two PRGs within each of the one or more subbands include a first subband PRG and a last subband PRG, and wherein the PRG size of the first subband PRG is different from the PRG size of the last subband PRG.

[0216] Aspect 7: A network entity according to any one of Aspects 1 to 6, wherein the SBFD frequency resources configured for the one or more subbands include the number of bits allocated for the FDRA in the SBFD time slot based on available resources in the SBFD time slot, and wherein the available resources in the SBFD time slot are determined by the overlap of the corresponding subbands in the one or more subbands and the BWP associated with the UE.

[0217] Aspect 8: The network entity according to Aspect 7, wherein the SBFD frequency resources configured for the one or more subbands include a configuration across a single subband, and wherein the available resources in the SBFD time slot are determined by an overlap of the single subband and the BWP associated with the UE.

[0218] Aspect 9: A network entity according to Aspect 7, wherein the SBFD frequency resources configured for the one or more subbands include a configuration across multiple non-contiguous subbands, and wherein the available resources in the SBFD time slot are determined by an overlap of the multiple non-contiguous subbands and the BWP associated with the UE.

[0219] Aspect 10: The network entity according to any one of aspects 1 to 9, wherein the scheduling information comprises at least one DCI bit field indicating one or more subbands used for data scheduling in the SBFD timeslot.

[0220] Aspect 11: A method for wireless communication in a network entity, comprising: configuring SBFD frequency resources for one or more subbands based on the size of the one or more subbands and the size of a BWP associated with a UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands; and providing scheduling information to the UE, wherein the scheduling information includes the configuration of the SBFD frequency resources based on the size of the one or more subbands and the size of the BWP associated with the UE.

[0221] Aspect 12: The method according to aspect 11, wherein the configuration of the SBFD frequency resources comprises: referring to a first table for determining an RBG size of an SBFD time slot; and referring to a second table for determining an RBG size of a non-SBFD time slot.

[0222] Aspect 13: The method according to aspect 11, wherein the configuration of the SBFD frequency resources includes referring to the same table for determining the RBG size of the SBFD time slot and the RBG size of the non-SBFD time slot.

[0223] Aspect 14: The method according to any one of aspects 11 to 13, wherein the scheduling information further comprises an indication of a static bundling of PRG sizes.

[0224] Aspect 15: The method according to any one of aspects 11 to 14, wherein the scheduling information further comprises an indication of dynamic bundling of PRG sizes.

[0225] Aspect 16: A UE, comprising: a transceiver; a memory; and a processor, the processor being coupled to the transceiver and the memory, wherein the processor is configured to: receive scheduling information, the scheduling information comprising a configuration of SBFD frequency resources for one or more subbands, wherein the configuration is based on the size of the one or more subbands and the size of a BWP associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands; and communicate with a network via the SBFD frequency resources based on the scheduling information.

[0226] Aspect 17: A UE according to Aspect 16, wherein the configuration of SBFD frequency resources includes at least two RBGs with different RBG sizes within each of the one or more subbands, and wherein the processor is also configured to configure the UE to communicate with the network via the at least two RBGs.

[0227] Aspect 18: The UE according to Aspect 17, wherein the at least two RBGs within each of the one or more subbands include a first subband RBG and a last subband RBG, and wherein the RBG sizes of the RBGs between the first subband RBG and the last subband RBG each have a different RBG size from the first subband RBG and the last subband RBG.

[0228] Aspect 19: A UE according to any one of Aspects 16 to 18, wherein the configuration of SBFD frequency resources includes at least two PRGs with different PRG sizes within each of the one or more subbands, and wherein the processor is also configured to configure the UE to communicate with the network via the at least two PRGs.

[0229] Aspect 20: The UE according to Aspect 19, wherein the at least two PRGs within each of the one or more subbands include a first subband PRG and a last subband PRG, and wherein the PRG size of the first subband PRG is different from the PRG size of the last subband PRG.

[0230] Aspect 21: A UE according to any one of Aspects 16 to 20, wherein the configuration of the SBFD frequency resources includes the number of bits allocated to the FDRA in the SBFD time slot based on the available resources in the SBFD time slot, and wherein the available resources in the SBFD time slot are determined by the overlap of the corresponding subbands in the one or more subbands and the BWP associated with the UE.

[0231] Aspect 22: The UE according to Aspect 21, wherein the configuration of SBFD frequency resources includes a configuration across a single subband, and wherein the available resources in the SBFD time slot are determined by an overlap of the single subband and the BWP associated with the UE.

[0232] Aspect 23: The UE according to Aspect 21, wherein the configuration of SBFD frequency resources includes a configuration across multiple non-contiguous subbands, and wherein the available resources in the SBFD time slot are determined by the overlap of the multiple non-contiguous subbands and the BWP associated with the UE.

[0233] Aspect 24: A UE according to any one of aspects 16 to 23, wherein the scheduling information comprises at least one downlink control information (DCI) bit field indicating one or more subbands used for data scheduling in the SBFD time slot.

[0234] Aspect 25: A method for wireless communication in a UE, comprising: receiving scheduling information, the scheduling information including a configuration of SBFD frequency resources for one or more subbands, wherein the configuration is based on the size of the one or more subbands and the size of a BWP associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more subbands; and communicating with a network via the SBFD frequency resources based on the scheduling information.

[0235] Aspect 26: The method according to Aspect 25, wherein the configuration of SBFD frequency resources includes making the RBG size of SBFD symbols different from the RBG size of non-SBFD symbols.

[0236] Aspect 27: The method according to any one of aspects 25 to 26, wherein the configuring comprises: referring to a first table for determining the RBG size of the SBFD time slot; and referring to a second table for determining the RBG size of the non-SBFD time slot.

[0237] Aspect 28: The method according to any one of aspects 25 to 26, wherein the configuring comprises referring to the same table for determining the RBG size of the SBFD time slot and the RBG size of the non-SBFD time slot.

[0238] Aspect 29: The method according to any one of aspects 25 to 28, wherein the scheduling information further includes an indication of static bundling of PRG sizes, and wherein the configuring includes determining the PRG size based on a static bundling algorithm.

[0239] Aspect 30: The method according to any one of aspects 25 to 29, wherein the scheduling information further comprises an indication of dynamic bundling of PRG sizes, and wherein the configuring comprises determining the PRG size based on a dynamic bundling algorithm.

[0240] Several aspects of wireless communication networks have been presented with reference to example implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0241] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing Institute of Electrical and Electronics Engineers (IEEE) standards IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0242] Within the present disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration". Any specific implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other, even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object has never been in direct physical contact with the second object. The terms "circuit" are used broadly, and they are intended to include both hardware implementations of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, implement the execution of the functions described in the present disclosure, without limitation on the type of electronic circuits) and software implementations of information and instructions (where these information and instructions, when executed by a processor, implement the execution of the functions described in the present disclosure). As used herein, the term "determine" may include a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining, resolving, selecting, choosing, establishing, receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like.

[0243] Figures 1 to 18 One or more of the components, steps, features, and / or functions illustrated in the present invention may be rearranged and / or combined into a single component, step, feature, or function, or may be implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 18The illustrated apparatus, devices and / or components may be configured to perform one or more of the methods, features or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0244] It should be understood that the specific order or hierarchy of steps in the methods disclosed herein is illustrative of example processes. It should be understood that the specific order or hierarchy of steps in these methods can be rearranged based on design preferences. The attached method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically stated herein.

[0245] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the text of the claims, wherein unless explicitly stated otherwise, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specified, the term "some" refers to one or more. The phrase "at least one" of a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims.

Claims

1. A network entity configured for wireless communication, comprising: Memory; and a processor coupled to the memory, the processor being configured to: configuring sub-band full-duplex (SBFD) frequency resources for the one or more sub-bands based on a size of the one or more sub-bands and a size of a bandwidth part (BWP) associated with a user equipment (UE), and wherein at least one of the SBFD frequency resources is not aligned with the one or more sub-bands; as well as Scheduling information is provided to the UE, wherein the scheduling information includes a configuration of the SBFD frequency resources based on the size of the one or more subbands and the size of the BWP associated with the UE.

2. The network entity of claim 1, wherein the SBFD frequency resources configured for the one or more subbands include at least two resource block groups (RBGs) having different RBG sizes within each of the one or more subbands.

3. The network entity of claim 2 , wherein the at least two RBGs within each of the one or more subbands include a first subband RBG and a last subband RBG, and wherein RBG sizes of RBGs between the first subband RBG and the last subband RBG each have a different RBG size from the first subband RBG and the last subband RBG. 4 . The network entity of claim 1 , wherein the processor is configured to configure the SBFD frequency resources such that a resource block group (RBG) size of a SBFD symbol is different from a RBG size of a non-SBFD symbol.

5. The network entity of claim 1, wherein the SBFD frequency resources configured for the one or more subbands include at least two precoded resource block groups (PRGs) having different PRG sizes within each of the one or more subbands.

6. The network entity of claim 5, wherein the at least two PRGs within each of the one or more subbands include a first subband PRG and a last subband PRG, and wherein the PRG size of the first subband PRG is different from the PRG size of the last subband PRG.

7. The network entity of claim 1 , wherein the SBFD frequency resources configured for the one or more subbands comprise a number of bits allocated for a frequency domain resource allocation (FDRA) in the SBFD time slot based on available resources in the SBFD time slot, and wherein the available resources in the SBFD time slot are determined by an overlap of a corresponding subband in the one or more subbands and the BWP associated with the UE.

8. The network entity of claim 7, wherein the SBFD frequency resources configured for the one or more subbands comprise a configuration across a single subband, and wherein the available resources in the SBFD time slot are determined by an overlap of the single subband and the BWP associated with the UE.

9. The network entity of claim 7, wherein the SBFD frequency resources configured for the one or more subbands comprise a configuration across a plurality of non-contiguous subbands, and wherein the available resources in the SBFD time slot are determined by an overlap of the plurality of non-contiguous subbands and the BWP associated with the UE.

10. The network entity of claim 1, wherein the scheduling information comprises at least one downlink control information (DCI) bit field indicating one or more subbands for data scheduling in a SBFD timeslot.

11. A method for wireless communication in a network entity, comprising: configuring sub-band full-duplex (SBFD) frequency resources for the one or more sub-bands based on a size of the one or more sub-bands and a size of a bandwidth part (BWP) associated with a user equipment (UE), and wherein at least one of the SBFD frequency resources is not aligned with the one or more sub-bands; as well as Scheduling information is provided to the UE, wherein the scheduling information includes a configuration of the SBFD frequency resources based on the size of the one or more subbands and the size of the BWP associated with the UE.

12. The method according to claim 11, wherein the configuration of the SBFD resources comprises: referring to a first table for determining a resource block group (RBG) size for a SBFD time slot; as well as Reference is made to the second table for determining the RBG size for the non-SBFD time slot.

13. The method of claim 11, wherein the configuration of the SBFD resources comprises referencing a same table for determining a resource block group (RBG) size for a SBFD timeslot and a RBG size for a non-SBFD timeslot.

14. The method of claim 11, wherein the scheduling information further comprises an indication of static bundling of precoding resource block group (PRG) sizes.

15. The method of claim 11, wherein the scheduling information further comprises an indication of dynamic bundling of precoding resource block group (PRG) sizes.

16. A user equipment (UE), comprising: Transceiver; Memory; and a processor coupled to the transceiver and the memory, wherein the processor is configured to: receiving scheduling information comprising a configuration of sub-band full-duplex (SBFD) frequency resources for one or more sub-bands, wherein the configuration is based on a size of the one or more sub-bands and a size of a bandwidth part (BWP) associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more sub-bands; as well as Communicate with a network via the SBFD frequency resources based on the scheduling information.

17. The UE of claim 16, wherein the configuration of SBFD frequency resources comprises at least two resource block groups (RBGs) having different RBG sizes within each of the one or more subbands, and wherein the processor is further configured to configure the UE to communicate with the network via the at least two RBGs.

18. The UE of claim 17, wherein the at least two RBGs within each of the one or more subbands include a first subband RBG and a last subband RBG, and wherein RBG sizes of RBGs between the first subband RBG and the last subband RBG each have a different RBG size from the first subband RBG and the last subband RBG.

19. The UE of claim 16, wherein the configuration of SBFD frequency resources comprises at least two pre-coded resource block groups (PRGs) having different PRG sizes within each of the one or more subbands, and wherein the processor is further configured to configure the UE to communicate with the network via the at least two PRGs.

20. The UE of claim 19, wherein the at least two PRGs within each of the one or more subbands include a first subband PRG and a last subband PRG, and wherein the PRG size of the first subband PRG is different from the PRG size of the last subband PRG.

21. The UE of claim 16, wherein the configuration of SBFD frequency resources comprises a number of bits allocated for a frequency domain resource allocation (FDRA) in the SBFD time slot based on available resources in the SBFD time slot, and wherein the available resources in the SBFD time slot are determined by an overlap of a corresponding subband in the one or more subbands and the BWP associated with the UE.

22. The UE of claim 21, wherein the configuration of SBFD frequency resources comprises a configuration across a single subband, and wherein the available resources in the SBFD time slot are determined by an overlap of the single subband and the BWP associated with the UE.

23. The UE of claim 21, wherein the configuration of SBFD frequency resources comprises a configuration across a plurality of non-contiguous subbands, and wherein the available resources in the SBFD time slot are determined by an overlap of the plurality of non-contiguous subbands and the BWP associated with the UE.

24. The UE of claim 16, wherein the scheduling information comprises at least one downlink control information (DCI) bit field indicating one or more subbands for data scheduling in a SBFD time slot.

25. A method for wireless communication in a user equipment (UE), comprising: receiving scheduling information comprising a configuration of sub-band full-duplex (SBFD) frequency resources for one or more sub-bands, wherein the configuration is based on a size of the one or more sub-bands and a size of a bandwidth part (BWP) associated with the UE, and wherein at least one of the SBFD frequency resources is not aligned with the one or more sub-bands; as well as Communicate with a network via the SBFD frequency resources based on the scheduling information.

26. The method of claim 25, wherein the configuration of SBFD frequency resources comprises making a resource block group (RBG) size of SBFD symbols different from a RBG size of non-SBFD symbols.

27. The method of claim 25, wherein the configuring comprises: referring to a first table for determining a resource block group (RBG) size for a SBFD time slot; as well as A second table is referenced for determining the RBG size of the non-SBFD time slot.

28. The method of claim 25, wherein the configuring comprises referencing a same table for determining a resource block group (RBG) size for a SBFD timeslot and a RBG size for a non-SBFD timeslot.

29. The method of claim 25, wherein the scheduling information further includes an indication of static bundling of a precoding resource block group (PRG) size, and wherein the configuring includes determining the PRG size based on a static bundling algorithm.

30. The method of claim 25, wherein the scheduling information further includes an indication of dynamic bundling of a precoding resource block group (PRG) size, and wherein the configuring includes determining the PRG size based on a dynamic bundling algorithm.

Images