Sub-band specific channel and signal configuration

Abstract

Methods and apparatus related to a network entity and user equipment are described. The network entity is configured to receive an indication that the user equipment is aware of sub-band full duplex operation, and transmit at least one of a downlink sub-band full duplex specific channel and signal configuration or an uplink sub-band full duplex specific channel and signal configuration in response to receiving the indication. The user equipment is configured to send an indication that the user equipment is aware of sub-band full duplex operation, and receive scheduling information from a network entity in response to sending the indication, the scheduling information indicates that the user equipment is scheduled to transmit an uplink or receive a downlink in at least one of: a sub-band full duplex (SBFD) slot or a flexible symbol.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to and the benefit of pending non-provisional patent application No. 18 / 184,628 filed in the U.S. Patent and Trademark Office on March 15, 2023, and provisional patent application No. 63 / 397,334 filed in the U.S. Patent and Trademark Office on August 11, 2022, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication devices in a wireless communication network, and more particularly to network-determined sub-band specific channel and signal configurations. Background Art

[0004] As communication networks evolve, ways to improve latency and optimize the amount of data transmitted on frequency resources have been studied, and these ways can be incorporated into the standards used by wireless communication networks. For example, using time division duplex (TDD), each time slot is scheduled for uplink or downlink, but not both. Self-contained time slots have been introduced so that a single time slot can be scheduled using non-overlapping time resources for uplink and downlink. Therefore, the use of self-contained time slots in a time division duplex (TDD) system can improve latency. Another type of duplex that can improve latency and other communication characteristics outside the self-contained time slots in a TDD system can be referred to as sub-band full-duplex (SBFD). According to SBFD, a given time slot can be configured for simultaneous uplink communication and downlink communication. 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] In one example, a network access node is disclosed. The network node includes a memory and a processor coupled to the memory. In this example, the processor is configured to: receive an indication that a user equipment is aware of sub-band full-duplex operation based at least in part on information stored in the memory; and in response to receiving the indication, utilize radio resource control (RRC) signaling to send at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration.

[0007] In another example, a method operating at a network access node is disclosed. The method includes: receiving an indication that a user equipment is aware of sub-band full-duplex operation; and in response to receiving the indication, transmitting at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration using radio resource control (RRC) signaling.

[0008] In another example, an apparatus is disclosed. In this example, the apparatus includes: means for receiving an indication that a user equipment is aware of sub-band full-duplex operation; and means for transmitting at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration using radio resource control (RRC) signaling in response to receiving the indication.

[0009] In one example, a computer-readable medium storing computer-executable code is disclosed. In this example, the computer-executable code stored on the computer-readable medium includes instructions for performing the following operations: receiving an indication that a user equipment is aware of sub-band full-duplex operation; and in response to receiving the indication, transmitting at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration using radio resource control (RRC) signaling.

[0010] In yet another example, a user equipment (UE) is disclosed, including a memory and a processor coupled to the memory. In this example, the processor is configured to receive scheduling information from a network access node based at least in part on information stored in the memory, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full duplex (SBFD) time slot, or a flexible symbol or time slot.

[0011] In another example, a method operating at a user equipment is disclosed. In this example, the method includes receiving scheduling information from a network access node with sub-band full-duplex capability, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full-duplex (SBFD) time slot, or a flexible symbol or time slot.

[0012] In yet another example, an apparatus is disclosed. In this example, the apparatus includes means for receiving scheduling information from a network access node with sub-band full-duplex capability, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full-duplex (SBFD) time slot, or a flexible symbol or time slot.

[0013] In yet another example, a computer-readable medium storing computer-executable code is disclosed. In this example, the computer-executable code stored on the computer-readable medium includes instructions for the following operations: receiving scheduling information from a network access node with sub-band full-duplex capability, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full-duplex (SBFD) time slot, or a flexible symbol or time slot.

[0014] These and other aspects will be more fully understood after reading the following specific embodiments. After reading the description of specific exemplary aspects below in conjunction with the accompanying drawings, other aspects, features and examples will be obvious to those of ordinary skill in the art. Although each feature may be discussed below with respect to certain examples and drawings, all examples may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used according to the various examples discussed herein. Similarly, although each example may be discussed below as an example of a device, system or method, it should be understood that such examples may be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a schematic diagram of a wireless communication system according to some aspects of the present disclosure.

[0016] Figure 2 is a schematic diagram of an example of a radio access network (RAN) according to some aspects of the present disclosure.

[0017] Figure 3 is an expanded view of an example subframe showing an orthogonal frequency division multiplexing (OFDM) resource grid according to some aspects of the present disclosure.

[0018] Figure 4 is a textual representation of portions of downlink (DL) and uplink (UL) bandwidth part (BWP) configurations according to some aspects of the present disclosure.

[0019] Figure 5A and Figure 5B is a diagram of first and second examples of multiple time slots utilizing various duplex modes according to some aspects of the present disclosure.

[0020] Figure 6 is a schematic diagram of multiple full-duplex gNBs, half-duplex UEs, and full-duplex UEs and corresponding graphical depictions of time-frequency resources for uplink and downlink transmissions according to some aspects of the present disclosure.

[0021] Figure 7is an illustration of a plurality of time slots including time slots scheduled for sub-band full-duplex communication according to some aspects of the present disclosure.

[0022] Figure 8 is an illustration of first and second time slots and parameter data that may be used to configure the first and second time slots according to some aspects of the present invention.

[0023] Fig. 9 is an illustration of first and second time slots and parameter data that may be used to configure the first and second time slots according to some aspects of the present invention.

[0024] Fig.10 is a block diagram illustrating an example of a hardware implementation of a network access node employing a processing system according to some aspects of the present disclosure.

[0025] Fig.11 is a flow chart illustrating an exemplary process at a network access node according to some aspects of the present disclosure.

[0026] Fig.12 is a block diagram illustrating an example of a hardware implementation of user equipment employing a processing system according to some aspects of the present disclosure.

[0027] Fig.13 is a flow chart illustrating an exemplary process at a network access node according to some aspects of the present disclosure.

[0028] Fig.14 is a schematic diagram of an example decomposed base station architecture according to some aspects of the present disclosure. DETAILED DESCRIPTION

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

[0030] 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 can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or use can be generated via integrated chip examples 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, AI-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 can range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some actual settings, the device 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, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices of different sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, disaggregated arrangements (e.g., base stations and / or user equipment (UE)), end-user devices, etc.

[0031] Described herein are methods and apparatus for bandwidth part (BWP), cell common and user equipment (UE) specific channel and signal configurations. According to some aspects, the channel and signal configurations may be sub-band full-duplex specific channel and signal configurations, referred to herein as sub-band specific channel and signal configurations.

[0032] Downlink (DL) and uplink (UL) BWP configurations may be divided into BWP common parameters and BWP dedicated parameters. BWP common parameters may be cell-specific, meaning that the network may use to ensure that BWP common parameters (i.e., parameters corresponding to BWP common parameters) may be aligned across UEs served by a network access node (e.g., scheduling entity, gNB) that schedules communications within the relevant cell. BWP dedicated parameters may be UE-specific.

[0033] The BWP common parameters for a DL BWP with a non-zero index may include basic cell-specific BWP parameters (e.g., frequency domain position, bandwidth, subcarrier spacing (SCS), and cyclic prefix associated with a given cell-specific BWP) and additional cell-specific BWP parameters for the physical downlink control channel (PDCCH) and physical downlink shared channel (PDSCH) associated with a given DL BWP.

[0034] The BWP-specific parameters for a DL BWP with a non-zero index may include UE-specific parameters for PDCCH and PDSCH, UE-specific parameters for semi-persistent scheduling, and UE-specific parameters for radio link monitoring configuration associated with a given DL BWP.

[0035] The BWP common parameters for a UL BWP with a non-zero index may include basic BWP parameters (e.g., frequency domain position, bandwidth, subcarrier spacing (SCS), and cyclic prefix associated with a given cell-specific BWP) as well as cell-specific parameters for random access, physical uplink control channel (PUCCH), and physical uplink shared channel (PUSCH) associated with a given UL BWP.

[0036] The BWP-specific parameters for a UL BWP with a non-zero index may include UE-specific parameters for PUCCH, PUSCH, sounding reference signal (SRS), configuration grant, and beam failure recovery configuration associated with a given UL BWP.

[0037] For unpaired spectrum (e.g., spectrum that can accommodate time division duplex (TDD) operation), in examples where the indices of the DL BPW and UL BWP are the same, the DL BWP can be linked to the UL BWP. In such examples, the DL BWP and UL BWP can share the same center frequency; however, according to some aspects, the DL BWP and UL BWP can have different bandwidths.

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

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

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

[0041] The 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 subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber 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.

[0042] Within the present disclosure, a "mobile" device does not necessarily need to have the ability to move, but it can be stationary. The term "mobile device" or "mobile device" refers to a wide variety of devices and technologies. A UE may include a plurality 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, tablets, personal digital assistants (PDAs), and a wide variety of embedded systems (e.g., corresponding to the "Internet of Things" (IoT)).

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

[0044] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmission from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) over an air interface can be referred to as downlink (DL) transmission. According to certain aspects of the present disclosure, the term "downlink" can refer to point-to-multipoint transmission 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". Transmission from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmission. According to further aspects of the present disclosure, the term "uplink" can refer to point-to-point transmission originating at a UE (e.g., UE 106).

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

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

[0047] 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., grants), 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 requests or feedback information or other control information) to the scheduling entity 108.

[0048] In addition, uplink control information 118 and / or downlink control information 114 and / or uplink traffic 116 and / or downlink traffic 112 can be sent on a waveform, and the waveform can be divided into frames, subframes, time slots and / or symbols by time. As used herein, a symbol may refer to a time unit in which each subcarrier carries one resource element (RE) 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.

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

[0050] 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, such as 5G Core (5GC). In other examples, the core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

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

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

[0053] 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 small cell, 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 size. The cell size setting may be performed according to the system design and component constraints.

[0054] It should be appreciated that 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.

[0055] 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 function as a base station, or more specifically as 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).

[0056] 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 be in communication with base station 210, UEs 226 and 228 may be in communication with base station 212, UEs 230 and 232 may be in communication with base station 214 via RRH 216, UE 234 may be in communication with base station 218, and UE 236 may be in communication with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be in communication with the base stations described above and in 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.

[0057] In another aspect of RAN 200, sidelink signals may be used between UEs without having to rely on scheduling or control information from a base station. Sidelink communications may be utilized in a device-to-device (D2D) network, a peer-to-peer (P2P) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, and / or other suitable sidelink networks. For example, two or more UEs (e.g., UEs 238, 240, and 242) may communicate with each other using sidelink signals 237 without relaying the communication through a base station. In some examples, UEs 238, 240, and 242 may 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.

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

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

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

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

[0062] 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 UE's connection is transferred 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 .

[0063] In a network configured for UL-based mobility, the network may 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.

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

[0065] In various 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-granted license. Although some technical rules generally still need to be followed to access the unlicensed spectrum, generally any operator or device can obtain access. 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 licensed spectrum can provide licensed shared access (LSA) to share the spectrum with other parties (e.g., with appropriate licensee-determined conditions to obtain access).

[0066] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

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

[0068] In view of the above aspects, unless otherwise specifically stated, it should be understood that if used in this article, the term "below 6 GHz" or the like can broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used in this article, the term can broadly represent frequencies that can be within FR2, FR4, FR4-a or FR4-1 and / or FR5 or can be within the EHF band.

[0069] Devices communicating in the radio access network 200 may utilize one or more multiplexing techniques and multiple access algorithms to achieve 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.

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

[0071] Reference Figure 3 Various aspects of the present disclosure are described with reference to the OFDM waveforms schematically illustrated in . 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 below herein. 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.

[0072] Reference now Figure 3 , illustrates an expanded view of an exemplary subframe 302 showing an OFDM resource grid according to some aspects of the present disclosure. However, as will be readily appreciated by those skilled in the art, the physical (PHY) 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.

[0073] Resource grid 304 may be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple available antenna ports, a corresponding plurality of resource grids 304 may be available for communication. Resource grid 304 is divided into a plurality of resource elements (REs) 306. RE (which is 1 subcarrier x 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) 308, 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 308) corresponds entirely to communication in a single direction (transmission or reception for a given device).

[0074] 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 306 within one or more subbands or bandwidth parts (BWPs). Thus, a UE typically utilizes only a subset of a resource grid 304. 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, eNB, etc.), or may be self-scheduled by a UE implementing D2D sidelink communication.

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

[0076] Each 1 ms subframe 302 may consist of one or more adjacent time slots. Figure 3In the example shown, as an illustrative example, a subframe 302 includes four time slots 310. 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.

[0077] An expanded view of one of the time slots 310 illustrates that the time slot 310 includes a control region 312 and a data region 314. In general, the control region 312 may carry control channels, and the data region 314 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 3 The structures illustrated in are merely exemplary in nature, and different slot structures may be utilized and may include one or more regions in each of the control region and the data region.

[0078] Although in Figure 3 Although not illustrated in the figure, each RE 306 within the RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within the RB 308 may also carry pilot 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 the control channel and / or data channel within the RB 308.

[0079] In some examples, time slot 310 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.

[0080] In an example of cellular communication over a cellular carrier via a Uu interface, for DL ​​transmissions, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within a control region 312) 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 ​​transmissions and UL transmissions. The PDCCH may further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked for accuracy at the receiving side, for example, using any suitable 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.

[0081] The base station may also allocate one or more REs 306 (e.g., in the control region 312 or the data region 314) 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, 40ms, 80ms, or 160ms). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may use the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

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

[0083] In an UL transmission, a scheduled entity (e.g., a UE) may utilize one or more REs 306 to a scheduling entity to carry UL control information (UCI) including 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 transmissions. Examples of uplink reference signals may include a sounding reference signal (SRS) and an uplink DMRS. In some examples, the UCI may include a scheduling request (SR), i.e., a request to a scheduling entity to schedule an uplink transmission. In this document, 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 transmissions. The UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other suitable UCI.

[0084] In addition to control information, one or more REs 306 (e.g., within the data region 314) may also be allocated for data. Such data 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 306 within the data region 314 may be configured to carry other signals, such as one or more SIBs and DMRS. In some examples, the PDSCH may carry multiple SIBs, not limited to the SIB1 discussed above. For example, OSI may be provided in these SIBs (e.g., SIB2 and above SIBs).

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

[0086] 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 blocks of information 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 bits of information (e.g., the amount of bits of information), may be a controlled parameter.

[0087] Figure 1 , Figure 2 and Figure 3 The channels or carriers illustrated are not necessarily all channels or carriers that may be utilized between devices, 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.

[0088] According to various aspects described herein, uplink communications and downlink communications may be defined based on time and frequency resources and may also be defined based on channel-specific configurations. Examples of channel-specific configurations include uplink configurations and downlink configurations utilized with time slots scheduled as sub-band full-duplex (SBFD) time slots. According to some aspects of the present disclosure, utilization of channel-specific sub-band configurations (e.g., configurations of sub-band-specific uplink parameters and sub-band-specific downlink parameters) may optimize transmit / receive characteristics of UL / DL SBFD time slots and may reduce any effects of self-interference and / or cross-link interference in SBFD communications exchanged between full-duplex gNBs and half-duplex UEs.

[0089] Figure 4 is a representation of a portion of a downlink (DL) and uplink (UL) bandwidth part (BWP) configuration according to some aspects of the present disclosure. As shown, the DL / UL BWP configuration can be divided into common parameters and dedicated parameters. The BWP common parameters can be cell-specific. Since these parameters are cell-specific, the network can ensure that the BWP common parameters are distributed to all user equipment (UE) in the cell (e.g., aligned across all UEs in the cell). The BWP dedicated parameters can be UE-specific.

[0090] like Figure 4 As depicted, the BWP-Downlink 402 parameters may be used to specify, for example, a BWP identity (i.e., BWP-Id 404), BWP common parameters (i.e., BWP-DownlinkCommon 406), and BWP dedicated parameters (i.e., BWP-DownlinkDedicated 408). The BWP-DownlinkCommon 406 parameters may include, for example, common parameters 409, such as those described and illustrated below in conjunction with BWP 410. The BWP-DownlinkCommon 406 parameters may also include, for example, PDCCH-ConfigCommon parameters and PDSCH-ConfigCommon parameters, which may generally provide parameter information for the establishment and release of PDCCH and PDSCH. The BWP-DownlinkDedicated 408 parameters may include, for example, PDCCH-Config parameters, PDSCH-Config parameters, semi-persistent scheduling (SPS)-Config parameters, and radioLinkMonitoring-Config parameters, which may all provide parameter information for the establishment and release of PDCCH, PDSCH, as well as provide SPS information and generally information related to radio link monitoring. Figure 4Other parameters not exemplified in conjunction with the BWP-DownlinkCommon 406 parameter and the BWP-DownlinkDedicated 408 parameter are within the scope of the present disclosure.

[0091] In addition, if Figure 4 As depicted, BWP-Uplink 412 may be used to specify, for example, a BWP identity (i.e., BWP-Id 404 as shown and described in conjunction with BWP-Downlink 402), BWP common parameters (i.e., BWP-UplinkCommon 414), and BWP dedicated parameters (i.e., BWP-UplinkDedicated 416). BWP-UplinkCommon 414 parameters may include, for example, common parameters 411, such as those described and shown below in conjunction with BWP 410. BWP-UplinkCommon 414 parameters may also include, for example, RACH-ConfigCommon parameters, PUSCH-ConfigCommon parameters, and PUCCH-ConfigCommon parameters, which may provide parameter information utilized during a random access procedure and are generally used for the establishment and release of PUSCH and PUCCH. The BWP-UplinkDedicated 416 parameters may include, for example, PUCCH-Config parameters, PUSCH-Config parameters, Configuration Grant (CG)-Config parameters, Sounding Reference Signal (SRS)-Config parameters, and beamFailureRecovery-Config parameters, which may variously provide parameter information for setup and release of PUSCH, PUCCH, and provide SRS information, information related to configuration grants, and generally related to beam failure recovery. Figure 4 Other parameters not exemplified in conjunction with the BWP-UplinkCommon 414 parameter and the BWP-UplinkDedicated 416 parameter are within the scope of the present disclosure.

[0092] In addition, if Figure 4 As depicted, common information applicable to both public and private BWP configurations may be provided in the BWP 410 parameters, such as Figure 4. The generic BWP 410 parameters may include, for example, frequency domain location and bandwidth information for a given BWP, where an integer ranging from 0 to 37949 represents one of 37950 possible combinations of location and bandwidth for a given BWP. The generic BWP 410 parameters may also include a subcarrier spacing parameter that indicates the subcarrier spacing utilized in conjunction with a given BWP. The generic BWP 410 parameters may also include a value indicating a cyclic prefix associated with a given BWP. The foregoing list is exemplary and non-limiting.

[0093] Figure 5A and Figure 5B are first and second examples of a plurality of time slots 500 utilizing various duplex modes according to some aspects of the present disclosure. Figure 5A The above keywords 501 are suitable for Figure 5A and Figure 5B For ease of reference, keyword 501 identifies a filling pattern corresponding to the DL 503 , UL 505 , PDSCH 507 , PUSCH 509 , ACK / NACK 511 , and guard band / period 513 locations within the plurality of slots 500 . Figure 5A and Figure 5B It can be illustrated how a duplex mode known as sub-band full duplex (SBFD) is enabled and how SBFD provides benefits over time division duplex (TDD) modes in which time slots are configured for either uplink or downlink (but not both) and over TDD versions that utilize self-contained time slots in which non-temporally overlapping portions of time slots are allocated for either uplink or downlink. Figure 5A and Figure 5B In both, five time slots are depicted for convenience. The time slots are only depicted aligned in time to facilitate the use of self-contained time slots (in Figure 5A The delay obtained by using SBFD time slots (in Figure 5B Middle) Visual comparison of the obtained delays.

[0094] exist Figure 5A, the first time slot 502, the second time slot 504, the third time slot 506 and the fifth time slot 510 are TDD time slots. The first time slot 502, the second time slot 504 and the third time slot 506 are each scheduled for downlink communication (identified by the letter "D"). The fourth time slot is a self-contained time slot (identified by the letter "S") and is referred to as a self-contained time slot 508 hereinafter. The self-contained time slot 508 can be a time slot including a downlink portion 512, an uplink portion 514 and a protection period 516 therebetween. The self-contained time slot 508 is a feature introduced in 5G-NR and is not available in long term evolution (LTE). The self-contained time slot 508 can provide flexibility by providing, for example, lower latency when compared to, for example, LTE. The fifth time slot 510 can be a TDD time slot and is scheduled for uplink communication (identified by the letter "U").

[0095] exist Figure 5A In the example of FIG. 5 , a downlink message conveyed in a PDSCH 518 in a first time slot 502 may be transmitted from a network access node (not shown) to a UE (not shown). In the uplink portion 514 of the self-contained time slot 508, the UE conveys an ACK / NACK 520 indication to the network access node, thereby informing the network access node of the successful or unsuccessful reception of the message conveyed in the PDSCH 518 three time slots ago. If the fourth time slot had not been scheduled as the self-contained time slot 508, the uplink transmission of the ACK / NACK 520 would be delayed until the fifth time slot 510 (which is scheduled for uplink). Thus, compared to the case where the entire fourth time slot may have been scheduled as a downlink time slot, the uplink transmission of the ACK / NACK 520 may be delayed until the fifth time slot 510 (which is scheduled for uplink). Figure 5A The latency is improved by using self-contained time slots 508.

[0096] exist Figure 5B In the example of , the first time slot 522 and the fifth time slot 530 are TDD time slots. The first time slot 522 is scheduled for downlink communication (indicated by "D"). Figure 5B In the example of FIG. 5 , the second time slot 524, the third time slot 526, and the fourth time slot 528 are scheduled for sub-band full-duplex (SBFD) communication (identified by the letters "SBFD"). Each of the second time slot 524, the third time slot 526, and the fourth time slot 528 may be referred to as a SBFD time slot hereinafter. The fifth time slot 530 is identified as an uplink time slot (identified by the letter "U").

[0097] By utilizing SBFD, Figure 5BPortions of the associated BWP 532 in the second time slot 524, the third time slot 526, and the fourth time slot 528 (e.g., along the vertical axis (frequency axis)) can be used for the downlink, while another portion of the BWP 532 can be used for the uplink. Thus, SBFD can be described as a duplex mode that favors simultaneous non-overlapping uplink and downlink portions within a BWP in a given time slot. In the second time slot 524, the third time slot 526, and the fourth time slot 528, the guard band is visible above and below the uplink portion of the BWP 532. The guard period is visible between the first time slot 522 and the second time slot 524 (adjacent to the portion of the BWP 532 that changes from downlink to uplink) and between the fourth time slot 528 and the fifth time slot 530 (adjacent to the portion of the BWP 532 that changes from downlink to uplink).

[0098] exist Figure 5B In the example of , a downlink message conveyed in a PDSCH 534 in a first time slot 522 may be transmitted from a network access node (not shown) to a UE (not shown). In the uplink portion 536 of the SBFD time slot (the second time slot 522), the UE conveys an ACK / NACK 538 indication to the network access node, thereby notifying the network access node of the message conveyed in the PDSCH 534 in the immediately preceding time slot (the first time slot 524). If the second time slot 524 had not been scheduled as a SBFD time slot, the uplink transmission of the ACK / NACK 538 would be delayed until the fifth time slot 530 (which is scheduled for uplink). Thus, compared to the case where the entire second time slot 524, the third time slot 526, and the fourth time slot 528 may have been scheduled for downlink, and in combination with Figure 5A Compared to the use of the self-contained time slot 508 shown and described, Figure 5B The delay is improved by using the SBFD time slot (ie, the second time slot 524).

[0099] Thus, utilizing SBFD can reduce latency, for example, by enabling faster delivery of channel state information (CSI) or faster hybrid automatic repeat request (HARQ) feedback, and, for example, by enabling improved UL duty cycle and latency reduction (e.g., compared to a system using TDD with or without self-contained slots but without SBFD). The improved UL duty cycle and latency reduction may be particularly significant for small packets (interchangeable with Universal Personal Telecommunications (UPT)). For example, sub-band full-duplex can provide greater UL coverage and capacity due to coverage gains for cell edges with duplication. Further, sub-band full-duplex can also enable flexible UL / DL resource allocation by providing a multiplexing pattern that can be robustly adapted to different services.

[0100] Figure 6is a schematic diagram of multiple full-duplex gNBs, half-duplex UEs, and full-duplex UEs and corresponding graphical depictions of time-frequency resources for uplink and downlink transmissions according to some aspects of the present disclosure. Figure 6 , non-overlapping uplink and downlink sub-bands 651 (eg, SBFD), partially overlapping uplink and downlink 652 bands, and fully overlapping uplink and downlink 653 bands (also referred to as single frequency full duplex (SFFD)) are illustrated.

[0101] In a first example 601, a first full-duplex (FD) gNB 604, a second FD gNB 606, a first half-duplex (HD) UE 608, and a second HD UE 610 are depicted according to some aspects of the present disclosure. Non-overlapping uplink and downlink subbands 651 (i.e., as combined Figure 5B The described and illustrated SBFD) is used for uplink (UL) communications from a first HD UE 608 to a first FD gNB 604 and for downlink (DL) communications from the first FD gNB 604 to a second HD UE 610. A first example of cross-link interference (CLI) 612 exists between the first FD gNB 604 and the second FD gNB 606. A second example of CLI 614 exists between the first HD UE 608 and the second HD UE 610. Additionally, due to the full-duplex nature of the first FD gNB 604, self-interference (SI) 616 is shown as existing in conjunction with the first FD gNB 604.

[0102] In a second example 602, a first full-duplex (FD) gNB 618, a second FD gNB 620, a first full-duplex (FD) UE 622, and a second FD UE 624 are depicted in accordance with some aspects of the present disclosure. Partially overlapping uplink and downlink 652 frequency bands and fully overlapping 653 frequency bands (i.e., SFPD) may be used for uplink (UL) communications from the first FD UE 622 to the first FD gNB 618 and downlink (DL) communications from the first FD gNB 618 to the first FD UE 622 and the second FD UE 624. A first example of cross-link interference (CLI) 626 exists between the first FD gNB 618 and the second FD gNB 620. A second example of CLI 628 exists between the first FD UE 622 and the second FD UE 624. In addition, due to the full-duplex nature of the first FD gNB 618, a first self-interference (SI) 630 is shown as existing in conjunction with the first FD gNB 618. In addition, due to the partial or full overlapping duplex mode of the first FD UE 622, a second self-interference (SI) 632 is shown as existing in conjunction with the first FD UE 622.

[0103] In a third example 603, a first full-duplex (FD) gNB 634 (acting as a first transmit-receive point (TRP) of a multi-TRP (M-TRP) configuration of the gNB), a second FD gNB 636 (acting as a second TRP of the gNB's M-TRP configuration), a first FD UE 638, and a second FD UE 640 are depicted in accordance with some aspects of the present disclosure. Partially overlapping uplink and downlink 652 frequency bands or fully overlapping 653 frequency bands (i.e., SFFD) may be used for uplink (UL) communications from the first FD UE 638 to the first FD gNB 634 (first M-TRP node) and downlink (DL) communications from the second FD gNB 636 (second M-TRP node) to the first FD UE 638 and the second FD UE 640. A first example of cross-link interference (CLI) 642 exists between the first FD gNB 634 and the second FD gNB 636 (i.e., between the two TRPs of the M-TRP configuration). A second example of CLI 644 exists between the first FD UE 638 and the second FD UE 640. Additionally, self-interference (SI) 646 is shown as existing in conjunction with the first FD UE 638 due to the partial or complete overlapping duplex mode of the first FD UE 638.

[0104] A duplex mode with non-overlapping uplink and downlink subbands 651 (i.e., SBFD) may be utilized in 5G communications, for example, according to Release 18 of certain 3GPP standards. A duplex mode with partially overlapping uplink and downlink 652 frequency bands or fully overlapping 653 frequency bands (i.e., SFPD) may be used in 5G communications, for example, starting with Release 19 of certain 3GPP standards.

[0105] Figure 7 is an example of a plurality of time slots including time slots scheduled for sub-band full-duplex communication according to some aspects of the present disclosure. Figure 7, the first time slot 702 is identified as a downlink time slot, the second time slot 704 is identified as a SBFD time slot, the third time slot 706 is identified as a SBFD time slot, and the fourth time slot 708 is also identified as a SBFD time slot. The fifth time slot 710 is identified as an uplink time slot. In the second to fourth time slots 704 to 708, using SBFD, a portion of the BWP 712 in the second time slot 704, the third time slot 706, and the fourth time slot 708 can be used for the downlink, while another portion of the BWP 712 can be used for the uplink. Therefore, SBFD can be described as a duplex mode that favors non-overlapping uplink and downlink portions within the BWP 712 in a given time slot. In the second time slot 704, the third time slot 706, and the fourth time slot 708, the guard band is visible above and below the uplink portion of the BWP 712. The guard period is visible between the first time slot 702 and the second time slot 704 (adjacent to the portion of the BWP 712 changing from downlink to uplink) and between the fourth time slot 708 and the fifth time slot 710 (adjacent to the portion of the BWP 712 changing from downlink to uplink).

[0106] In addition, Figure 7 It should be noted that the first time slot 702 may be configured according to DL-BWP specific configuration parameters, for example, such as in combination with Figure 4 Note that the fifth time slot 710 may be configured according to UL-BWP specific configuration parameters, such as, for example, in conjunction with Figure 4 BWP-Uplink 412 parameters shown and described.

[0107] Further in Figure 7 In the example, it is noted that the DL portion of the second time slot 704 (and the third time slot 706 and the fourth time slot 708) can be configured according to the DL subband specific 718 configuration parameters, and the UL portion of the second time slot 704 (and the third time slot 706 and the fourth time slot 708) can be configured according to the UL subband specific 720 configuration parameters. Figure 8 and Fig. 9 To describe subband specific parameters (related to DL and UL).

[0108] exist Figure 6 In the example of Figure 6 614), the use of SBFD in conjunction with FD gNBs and HD UEs may result in, for example, a difference in DL QoS between a DL TDD timeslot (i.e., a one-way timeslot) and a DL-SBFD timeslot. As another example, due to gNB self-interference (e.g., Figure 6 SI 616) and gNB CLI (e.g. Figure 6Due to the presence of CLI 612), there may be a difference in UL QoS between UL TDD time slots (ie, unidirectional time slots) and UL SBFD time slots.

[0109] To accommodate differences in link quality, it may be beneficial and / or useful to define SBFD-specific uplink (referred to herein as sub-band specific uplink) and SBFD-specific downlink (referred to herein as sub-band specific downlink) channel and / or signal configurations. These configurations may be separate from those defined within the BWP, such as in conjunction with Figure 4 Those configurations described.

[0110] According to some examples, these configurations (which may include unique channel configurations and / or reference signal configurations) may be used when the FD gNB and HD UE communicate using sub-band full-duplex.

[0111] According to various aspects described herein, UL and DL may be defined in terms of time and frequency, and may also be defined in terms of channel-specific configurations (e.g., subband-specific uplink parameters and subband-specific downlink parameters). By using channel-specific subband configurations (e.g., subband-specific uplink parameters and subband-specific downlink parameters), transmission / reception in UL / DL SBFD may be optimized to handle the frequency resources of UL / DL SBFD, and may also be optimized based on link requirements (e.g., power, timing, transceiver control interface (TCI) etc.), thereby being optimized to reduce the impact of self-interference and / or cross-link interference at both nodes (i.e., at the FD gNB and the HD UE). In combination Figure 7 Examples are given of slot portions to which DL subband specific parameters and UL subband specific parameters may be applied.

[0112] Figure 7 7 is an example of five time slots, where the first time slot 702 is scheduled as a downlink (D) time slot (using TDD). The second time slot 704, the third time slot 706, and the fourth time slot 708 are scheduled as sub-band full duplex (SBFD) time slots. The fifth time slot 710 is scheduled as an uplink (U) time slot (using TDD). In the first time slot 702, DL-BWP specific 714 parameters may be configured by the gNB (not shown) to the UE (not shown). In the second time slot 704, the third time slot 706, and the fourth time slot 708, in the downlink portion of those time slots, DL sub-band specific 718 parameters may be configured to the UE, and in the uplink portion, UL sub-band specific 720 parameters may be configured to the UE. In the fifth time slot 710, UL-BWP specific 716 parameters may be configured by the gNB to the UE.

[0113] Described herein may be UL / DL subband specific configurations, wherein according to some aspects of the present disclosure, subband specific parameters may be conveyed via radio resource connection (RRC) signaling. Various UL / DL subband specific configuration options may be configured by a full-duplex network access node (e.g., gNB, scheduling entity) to one or more half-duplex user equipment. Separate RRC parameters may be configured for each downlink and uplink subband.

[0114] In one example, the gNB may configure the UE with subband-specific RRC parameters for transmission / reception of channels and / or signals for the subband. In one aspect, there may be separate RRC parameters for each DL and UL subband.

[0115] According to some examples, there may be at least three options for the RRC parameters. For example, the first option may entail using cell-specific subband common parameters (e.g., common to all UEs in a given cell). In this example, the network (e.g., network access node, gNB, scheduling entity) may be implied to ensure that the subband common parameters are aligned across UEs within a given cell.

[0116] A second option may require that subband-specific parameters may be dedicated (which may be referred to herein as subband-specific parameters) (eg, subband-specific parameters may be specific to a given UE, also described as UE-specific configuration).

[0117] A third option may entail that both common sub-band specific configuration and dedicated sub-band specific configuration may be used.

[0118] For DL ​​subband: RRC parameters may include, for example, PDSCH, PDCCH and SPS configuration + DL-SB time and frequency (T / F) indication.

[0119] For UL subband: RRC parameters may include, for example, PUSCH, PUCCH, CG, SRS and PRACH configuration + UL-SB T / F indication.

[0120] The RRC parameters may indicate a SB specific configuration dedicated to a specific channel and / or signal.

[0121] For example, in one example of a UL subband, the gNB may configure a SBFD-specific PUCCH resource set (or multiple resources) configured with a specific hopping pattern, repetition factor, frequency allocation, and open-loop power control parameters.

[0122] In one example of a DL subband, the gNB may configure SBFD specific CSI-RS for non-continuous channel measurement, or may configure CLI specific resources for calculating CLI metrics at SBFD timeslots.

[0123] According to one aspect, the RRC parameters may be indicated as sub-band specific parameters (eg, timing advance or common TCI (also referred to as unfired TCI state)) for all signals and channels.

[0124] FD gNB (e.g., as combined with Figure 6 The first FD gNB 604 shown and described may have various ways to provide HD UEs (e.g., such as in conjunction with Figure 6 The first HD UE 608 is shown and described as indicating a UL / DL subband specific configuration.

[0125] Figure 8 804 and parameter data that can be used to configure the first time slot 802 (configured as a downlink time slot) and the second time slot 804 (configured as a SBFD time slot) according to some aspects of the present disclosure. For ease of reference, keyword 801 identifies a fill pattern corresponding to the DL 803, UL 805, PUSCH 807, and guard band / period 809 positions within the first time slot 802 and the second time slot 804.

[0126] In a first time slot 802, DL-BWP specific 806 parameters may be configured by a gNB (not shown) to a UE (not shown). In a second time slot 804, in the downlink portion of the time slot, DL subband specific 808a, 808b parameters may be configured to the UE, and in the uplink portion of the time slot, UL subband specific 810 parameters may be configured to the UE.

[0127] According to some aspects, when the gNB configures the downlink, the DL-BWP specific configuration (e.g., BWP-Downlink 812) can be associated with the UL subband specific configuration (e.g., subband-uplink 822). The BWP-Downlink 812 parameters can include a BWP identity (BWP-Id 814), BWP common parameters (BWP-DownlinkCommon 816), BWP dedicated parameters (BWP-DownlinkDedicated 818), and an uplink subband identifier (subband-Id 820). The subband-uplink 822 parameters can include an identifier for the UL subband specific parameters (ul-subband-Id 819 indicated as subband-Id 820). The subband-uplink 822 parameters may include, for example, subband-Id 820 , subband-locationAndBW 824 , subband-subcarrierSpacing 826 , subband-Common 828 , subband-Dedicated 830 , and tci-info 832 .

[0128] Similarly, when the gNB configures the uplink, the UL-BWP specific configuration (not shown) can be associated with the DL subband specific configuration (not shown). In the former case, the association can be by making the ul-subband-Id 819 as a parameter within the BWP-Downlink 812 configuration, or by making all UL subband specific configurations under the DL BWP (i.e., within the BWP-Downlink 812).

[0129] Fig. 9 902 and a second time slot 904 and parameter data that may be used to configure the first time slot 902 (configured as a downlink time slot) with DLBWP-specific 906 parameters and the second time slot 904 (configured as a SBFD time slot) with DL subband-specific 908a, 908b parameters and UL subband-specific 910 parameters in accordance with some aspects of the present disclosure. In an example where the gNB configures a DL BWP (e.g., BWP-Downlink 912), the BWP-Downlink 912 may be associated with the UL subband-specific 910 configuration and the DL subband-specific 908a, 908b configuration pair. In one example, the association may be made by having a subband-Id 920 as a parameter within the BWP-Downlink 912, where the subband-Id 920 indicates both the UL subband-specific 910 configuration and the DL subband-specific 908a, 908b configuration. Keyword 901 identifies the padding pattern corresponding to the DL 903 , UL 905 , PUSCH 907 , and guard band / period 909 locations.

[0130] The BWP-Downlink 912 parameters may include, for example, BWP-Id 914, BWP-DownlinkCommon 916, and BWP-DownlinkDedicated 918. The BWP-Downlink 912 parameters may also include identifiers for both the UL subband-specific 910 parameters and the DL subband-specific 908a, 908b parameters (e.g., ul-dl-subband-Id 919 (i.e., subband identifier) ​​indicated as subband-Id 920). The ul-dl-subband-Id 919 associates both the UL subband-specific 910 parameters (e.g., subband-uplink 922 parameters) and the DL subband-specific parameters (e.g., subband-downlink 923 parameters). Thus, the identifier subband-Id 920 may correspond to the subband-uplink 922 parameters and the subband-downlink 923 parameters.

[0131] The subband-uplink 922 parameters may include, for example, subband-Id 920, subband-locationAndBW 924, subband-subcarrierSpacing 926, subband-Common 928, subband-Dedicated 930, and tci-info 932. The subband-downlink 923 parameters may include, for example, subband-Id 920, subband-locationAndBW 925, subband-subcarrierSpacing 927, subband-Common 929, subband-Dedicated 931, and tci-info 933.

[0132] The UE behavior with respect to subband and BWP channel and signal configurations is now described. When the UE is scheduled (DCI, higher layer, or MAC-CE) for UL transmission in a SBFD timeslot, the UE may use the channels / signals configured under the UL subband-specific 910 configuration parameters (if configured); otherwise, the UE may use the UL channel / signal configuration under the UL BWP-specific configuration. By way of example, the UE may receive a UL DCI (e.g., format 0_1 ​​or 0_2) that schedules PUSCH repeatedly across SBFD timeslots. The UE may then use the PUSCH configuration under the UL subband-specific 910 configuration parameters for PUSCH-related configurations (where examples of PUSCH-related configurations may include, for example, TDRA, frequency hopping, power control, MCS tables, etc.).

[0133] In another example, in response to being scheduled (e.g., in DCI or higher layers, or MAC-CE) for DL ​​reception in SBFD, the UE may use a channel / signal configured under the DL subband specific 908a, 908b configuration parameters (if configured). Otherwise, the UE may use a DL channel / signal configured under the DL BWP specific 906 configuration. By way of example, the UE may receive a DL DCI (e.g., format 1_1 or 1_2) that schedules PUSCH repeatedly across SBFD time slots. The UE may use PDSCH-config under the DL subband specific 908a, 908b configuration parameters for PDSCH related configurations (e.g., TDRA, frequency hopping, MCS table, etc.).

[0134] For UEs that can use TDD but not SBFD, the TDD DL and UL time slots / symbols may be indicated to the UE via a dedicated / common RRC configuration (eg, TDD mode). The UE may use DL / UL signals / channels within the DL / UL BWP configuration.

[0135] For flexible symbols / slots, the UE may use the BWP configuration unless the DCI includes a bit indicating the use of SBFD mode (then the UE may use the UL / DL SB configuration).

[0136] NOTE: SBFD symbols / slots are from the perspective of the gNB and are indicated to the UE via SBFD RRC signaling. The slots / symbols are configured as DL / UL or flexible (UL-DL TDD mode).

[0137] For other periodic (P) or semi-persistent (SP), UL or DL ​​channel or reference signal configurations (e.g., SPS, CG, SRS, CSI-RS, etc.) configured within the UL / DL subband, when an instance occurs in a non-SBFD timeslot, it is discarded or canceled for the non-SBFD timeslot.

[0138] For dynamic grants (DG) (based on DCI) including aperiodic (AP) reference signals (RS), such as aperiodic-SRS (A-SRS) and aperiodic CSI-RS (A-CSI-RS), the gNB may transmit DCI targeting the appropriate configuration of the time slot and corresponding signal / channel.

[0139] Fig.10 1 is a block diagram illustrating an example of a hardware implementation of a network access node 1000 (e.g., a gNB, a base station, a TRP, a scheduling entity) employing a processing system 1002 according to some aspects of the present disclosure. The network access node 1000 may be similar to the one in Figure 1 , Figure 2 and / or Figure 6 Any one or more of the network access nodes illustrated and described in .

[0140] 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 1002 including one or more processors, such as a processor 1004. Examples of processor 1004 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 the present disclosure. In various examples, the network access node 1000 may be configured to perform any one or more of the functions described herein. That is, the processor 1004 as utilized in the network access node 1000 may be used to implement, for example, the functions described in FIG. 5, Figure 6 , Figure 7 , Figure 8 and / or Fig. 9Any one or more of the methods or processes described and / or illustrated in.

[0141] In some examples, the processor 1004 may be implemented via a baseband or modem chip, and in other implementations, the processor 1004 may include several devices distinct and other than a baseband or modem chip (e.g., in scenarios such as those that may work together to implement the examples discussed herein). And as mentioned above, various hardware arrangements and components outside of a baseband modem processor may be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc.

[0142] In this example, the processing system 1002 may be implemented using a bus architecture, which is generally represented by bus 1006. The bus 1006 may include any number of interconnecting buses and bridges, depending on the specific application of the processing system 1002 and the overall design constraints. The bus 1006 couples together (e.g., communicatively couples) various circuits including one or more processors, which are generally represented by processor 1004, memory 1008, and computer-readable media, which are generally represented by computer-readable media 1010. The bus 1006 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.

[0143] The bus interface 1012 provides an interface between the bus 1006 and one or more transceivers (generally represented by transceiver 1014). The transceiver 1014 can be a wireless transceiver. The transceiver 1014 can provide components for communicating with various other devices through a transmission medium (e.g., an air interface). The transceiver 1014 can also be coupled to an antenna array 1016.

[0144] The bus interface 1012 further provides an interface between the bus 1006 and a user interface 1028 (e.g., a keypad, a display, a touch screen, a speaker, a microphone, control features, etc.). Of course, such a user interface 1028 is optional and may be omitted in some examples. In addition, the bus interface 1012 further provides an interface between the bus 1006 of the network access node 1000 and a power supply 1022.

[0145] The processor 1004 is responsible for managing the bus 1006 and general processing, including executing software stored on the computer-readable medium 1010. The software, when executed by the processor 1004, causes the processing system 1002 to perform the various functions described below for any particular device. The computer-readable medium 1010 and the memory 1008 may also be used to store data that is manipulated by the processor 1004 when executing the software.

[0146] Software should be construed broadly to mean instructions, instruction sets, codes, code segments, program code, 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 1010. The software, when executed by the processor 1004, may cause the processing system 1002 to perform the various processes and functions described herein for any particular apparatus.

[0147] Computer readable medium 1010 may be a non-transient computer readable medium, and may be referred to as a computer readable storage medium or a non-transient computer readable medium. Non-transient computer readable medium may store computer executable code (e.g., processor executable code). Computer executable code may include code for causing a computer (e.g., a processor) to implement one or more of the functions described herein. Non-transient computer readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact discs (CDs) or digital versatile discs (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 1010 may reside in processing system 1002, be located outside processing system 1002, or be distributed across multiple entities including processing system 1002. The computer readable medium 1010 may be embodied in a computer program product or article of manufacture. By way of example, a computer program product or article of manufacture may include a computer readable medium in packaging materials. In some examples, the computer readable medium 1010 may be part of the memory 1008. 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.

[0148] In some aspects of the present disclosure, processor 1004 may include communication and processing circuitry 1041 configured for various functions, including, for example, communicating with user equipment (e.g., a wireless communication device, a mobile device, a scheduled entity), a network core (e.g., a 5G core network), or any other entity (such as, for example, an entity (such as a network provider) that communicates with network access node 1000 via the Internet). In some examples, communication and processing circuitry 1041 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). For example, communication and processing circuitry 1041 may include one or more transmit / receive chains.

[0149] In some implementations where communication involves receiving information, the communication and processing circuit system 1041 may obtain or identify information from a component of the network access node 1000 (e.g., from a transceiver 1014 that receives information via radio frequency signaling or some other type of signaling suitable for an applicable communication medium), process (e.g., decode) the information, and output the processed information. For example, the communication and processing circuit 1041 may output the information to another component of the processor 1004, to the memory 1008, or to the bus interface 1012. In some examples, the communication and processing circuit 1041 may receive one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuit 1041 may receive information via one or more channels. In some examples, the communication and processing circuit 1041 may include functionality for components for receiving. In some examples, the communication and processing circuit 1041 may include functionality for components for processing, including components for demodulation, components for decoding, and the like.

[0150] In some implementations where communication involves transmitting (e.g., sending) information, the communication and processing circuitry 1041 may obtain or identify information (e.g., from another component of the processor 1004, the memory 1008, or the bus interface 1012), process (e.g., modulate, encode, etc.) the information, and output the processed information. For example, according to some aspects of the present disclosure, the communication and processing circuitry 1041 may obtain data stored in the memory 1008 and may process the obtained data.

[0151] In some examples, the communication and processing circuitry 1041 may obtain information and output the information to the transceiver 1014 (e.g., sending the information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, the communication and processing circuitry 1041 may transmit one or more of a signal, a message, other information, or any combination thereof. In some examples, the communication and processing circuitry 1041 may transmit the information via one or more channels. In some examples, the communication and processing circuitry 1041 may include functionality for components for transmitting (e.g., components for sending).

[0152] In some examples, the communication and processing circuit 1041 may include functionality for components for generating (including components for modulating, components for encoding, etc.). In some examples, the communication and processing circuit 1041 may be configured to receive and process uplink traffic and uplink control messages (e.g., similar to Figure 1 uplink traffic 116 and uplink control information 118) and processing and sending downlink traffic and downlink control messages (e.g., similar to Figure 1 downlink traffic 112 and downlink control information 114).

[0153] The communication and processing circuit 1041 may be further configured to execute communication and processing instructions 1051 (eg, software) stored on the computer-readable medium 1010 to implement one or more functions described herein.

[0154] In some aspects of the present disclosure, the processor 1004 may include a sub-band full-duplex aware circuit 1042. The sub-band full-duplex aware circuit 1042 may be configured for various functions, including, for example, receiving an indication that the user equipment is aware of the sub-band full-duplex operation of the network access node 1000. The sub-band full-duplex aware circuit 1042 may be configured to execute sub-band full-duplex aware instructions 1052 (e.g., software), for example, stored on the computer-readable medium 1010, to implement one or more functions described herein.

[0155] In some aspects of the present disclosure, the processor 1004 may include a channel and signal configuration circuit 1043. The channel and signal configuration circuit 1043 may be configured for various functions including, for example, utilizing radio resource control (RRC) signaling to send at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration in response to receiving an indication of sub-band full-duplex awareness from the UE.

[0156] According to some aspects, the downlink subband specific channel and signal configuration includes at least one of the following: a cell-specific subband common parameter, a user equipment-specific subband dedicated parameter, or a combination of a subband common parameter and a subband dedicated parameter. In some examples, the cell-specific subband common parameter or the user equipment-specific subband common parameter may be configured per cell or per bandwidth part (BWP), respectively. In some examples, multiple subband configurations may be configured, and each subband configuration may be marked with an identifier (ID).

[0157] In some examples, RRC signaling associated with downlink subband-specific channel and signal configuration may include at least one of the following: physical downlink shared channel configuration parameters, physical downlink control channel configuration parameters, semi-persistent scheduling configuration parameters, or downlink subband timing and frequency indication parameters; and RRC signaling associated with uplink subband-specific channel and signal configuration may include at least one of the following: physical uplink shared channel configuration parameters, physical uplink control channel configuration parameters, uplink configuration grant configuration parameters, sounding reference signal configuration parameters, physical random access channel (PRACH) configuration parameters, or uplink subband timing and frequency indication parameters.

[0158] According to some aspects, the RRC signaling may include a parameter indicating that the downlink subband specific channel and signal configuration or the uplink subband specific channel and signal configuration is dedicated to a specific channel or a specific signal. In some examples, the processor 1004 or the channel and signal configuration circuit 1043 may be further configured to: send RRC signaling, the RRC signaling includes a parameter indicating a subband full-duplex specification common to all signals and channels. In some examples, the subband full-duplex specification is at least one of a timing advance parameter or a unified transmission configuration indicator state.

[0159] In some examples, the processor 1004 or the channel and signal configuration circuit 1043 may be further configured to perform at least one of the following: sending a downlink bandwidth portion configuration associated with an uplink subband specific channel and signal configuration, or sending an uplink bandwidth portion configuration associated with a downlink subband specific channel and signal configuration. According to some aspects, the association may be established by including a subband identifier (e.g., ul-subband-Id, ul-dl-subband-Id) in at least one of the following: a downlink bandwidth portion configuration for associating a downlink bandwidth portion configuration with an uplink SBFD specific channel and signal configuration, or an uplink bandwidth portion configuration for associating an uplink bandwidth portion configuration with a downlink SBFD specific channel and signal configuration.

[0160] In some examples, the downlink subband-specific channel and signal configuration and the uplink subband-specific channel and signal configuration together may include a downlink-uplink subband-specific pair, and the processor 1004 or the channel and signal configuration circuit 1043 may be further configured to: send a downlink bandwidth portion configuration in association with the downlink-uplink subband-specific pair.

[0161] In some examples, the downlink subband specific channel and signal configuration is different from both the bandwidth portion downlink common configuration and the bandwidth portion downlink dedicated configuration, and the uplink subband specific channel and signal configuration is different from both the bandwidth portion uplink common configuration and the bandwidth portion uplink dedicated configuration.

[0162] The channel and signal configuration circuitry 1043 may be configured to execute channel and signal configuration instructions 1053 (eg, software), stored, for example, on the computer-readable medium 1010 , to implement one or more functions described herein.

[0163] Fig.11 is a flow chart illustrating an exemplary process 1100 (e.g., a method of wireless communication) at a network access node (e.g., a gNB, a base station, a TRP, a scheduling entity) according to some aspects of the present disclosure. For example, the process 1100 may occur in a wireless communication network (such as Figure 1 , Figure 2 and / or Figure 6 As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required in all implementations. In some examples, process 1100 may be performed in conjunction with Fig.10 The process 1100 is performed by the network access node 1000 described and illustrated. In some examples, the process 1100 can be performed by any suitable device or component for performing the functions or algorithms described herein.

[0164] At block 1102, the network access node may receive an indication that the user equipment is aware of sub-band full-duplex operation. For example, the sub-band full-duplex aware circuit 1042 in conjunction with, for example, the transceiver 1014 and the antenna array 1016 (all in conjunction with Fig.10 ) as shown and described may provide means for receiving an indication that the user equipment is aware of sub-band full-duplex operation.

[0165] At block 1104, the network access node may utilize radio resource control (RRC) signaling to send at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration in response to receiving the indication. Fig.10The illustrated and described channel and signal configuration circuit 1043 may provide means for transmitting at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration utilizing radio resource control (RRC) signaling in response to receiving the indication.

[0166] According to some aspects, the downlink subband specific channel and signal configuration may include at least one of the following: a cell-specific subband common parameter, a user equipment-specific subband dedicated parameter, or a combination of a subband common parameter and a subband dedicated parameter. In some examples, these parameters may be configured per bandwidth part (BWP) or per cell. In some examples, multiple subband configurations may be configured, and each subband configuration may be marked with an identifier (ID). According to some aspects, the RRC signaling associated with the downlink subband specific channel and signal configuration may include at least one of the following: a physical downlink shared channel configuration parameter, a physical downlink control channel configuration parameter, a semi-persistent scheduling configuration parameter, or a downlink subband timing and frequency indication parameter; and the RRC signaling associated with the uplink subband specific channel and signal configuration may include at least one of the following: a physical uplink shared channel configuration parameter, a physical uplink control channel configuration parameter, an uplink configuration grant configuration parameter, a sounding reference signal configuration parameter, a physical random access channel (PRACH) configuration parameter, or an uplink subband timing and frequency indication parameter. In some examples, the RRC signaling may include a parameter indicating that a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration may be dedicated to a specific channel or a specific signal.

[0167] In some examples, the channel and signal configuration circuit 1043 in conjunction with the transceiver 1014 and the antenna array 1016 can be configured to send RRC signaling that includes parameters indicating a sub-band full-duplex specification common to all signals and channels. According to some aspects, the sub-band full-duplex specification can be at least one of a timing advance parameter or a unified transmission configuration indicator state.

[0168] In some examples, the channel and signal configuration circuit 1043 in conjunction with the transceiver 1014 and the antenna array 1016 may be configured to perform at least one of the following: sending a downlink bandwidth portion configuration associated with an uplink subband-specific channel and signal configuration, or sending an uplink bandwidth portion configuration associated with a downlink subband-specific channel and signal configuration. According to some aspects, the association may be established by including an uplink subband full-duplex identifier (e.g., ul-subband-Id, ul-dl-subband-Id) in at least one of the following: a downlink bandwidth portion configuration for associating a downlink bandwidth portion configuration with an uplink SBFD-specific channel and signal configuration, or an uplink bandwidth portion configuration for associating an uplink bandwidth portion configuration with a downlink SBFD-specific channel and signal configuration. .

[0169] In some aspects, the downlink subband specific channel and signal configuration and the uplink subband specific channel and signal configuration together may include a downlink-uplink subband specific pair, and the processor 1004 or the channel and signal configuration circuit 1043 in combination with the transceiver 1014 and the antenna array 1016 may be further configured to: send a downlink bandwidth portion configuration in association with the downlink-uplink subband specific pair.

[0170] In accordance with some aspects, the downlink subband specific channel and signal configuration may be different from both the bandwidth portion downlink common configuration and the bandwidth portion downlink dedicated configuration, and the uplink subband specific channel and signal configuration may be different from both the bandwidth portion uplink common configuration and the bandwidth portion uplink dedicated configuration.

[0171] Fig.12 1 is a block diagram illustrating an example of a hardware implementation of a user equipment 1200 (eg, a wireless communication device, a mobile device, a scheduling entity) employing a processing system 1202 according to some aspects of the present disclosure. For example, the user equipment 1200 may be similar to the one in Figure 1 , Figure 2 and / or Figure 6 Any one or more of the user equipments illustrated and described in .

[0172] 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 1202 including one or more processors 1204. The processing system 1202 may be combined with Fig.10The processing system 1002 illustrated and described is substantially the same, including a bus interface 1212, a bus 1206, a memory 1208, a processor 1204, and a computer-readable medium 1210. In addition, the user equipment 1200 may include a user interface 1228, a transceiver 1214, an antenna array 1216, and a power supply 1222, which are substantially similar to the above combined Fig.10 The processor 1204 as utilized in the user equipment 1200 may be used to implement any one or more of the processes described below.

[0173] Processor 1204 may include communication and processing circuitry 1241 configured to communicate with a network access node, similar to that described in conjunction with Figure 1 , Figure 2 , Figure 6 and / or Fig.10 Any network access node shown and described. In some examples, the communication and processing circuit 1241 may include one or more hardware components that provide a physical structure that performs processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). The communication and processing circuit 1241 may be further configured to execute communication and processing instructions 1251 (e.g., software) stored on the computer-readable medium 1210 to implement one or more functions described herein. The communication and processing circuit 1241 and the communication and processing instructions 1251 may be similar to the combination of Fig.10 The communication and processing circuitry 1041 and the communication and processing instructions 1051 are shown and described. Therefore, for the sake of brevity, a detailed description of the communication and processing circuitry 1241 and the communication and processing instructions 1251 is omitted.

[0174] In some aspects of the present disclosure, the processor 1204 may include a sub-band full-duplex aware circuit 1242. The sub-band full-duplex aware circuit 1242 may be configured for various functions, including, for example, to communicate with the user equipment 1200 in conjunction with a network access node such as Figure 1 , Figure 2 , Figure 6 and / or Fig.10 The sub-band full-duplex aware circuit 1242 may be configured to execute, for example, sub-band full-duplex aware instructions 1252 (e.g., software) stored on the computer-readable medium 1210 to implement one or more functions described herein.

[0175] In some aspects of the present disclosure, the processor 1204 may include a channel and signal configuration circuit 1243. The channel and signal configuration circuit 1243 may be configured for various functions, including, for example, receiving from a network access node an indication that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full-duplex (SBFD) time slot, or a flexible symbol or time slot. For example, the received scheduling information and / or configuration information may be received via RRC signaling. The reception may be in response to an indication of a sub-band full-duplex awareness being sent from the UE. The scheduling (and / or configuration) information may include configuration parameters associated with at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration. The scheduling (and / or configuration) information may be conveyed via, for example, radio resource control (RRC) signaling.

[0176] The channel and signal configuration circuit 1243 can be configured for various other functions, including, for example, in an SBFD time slot: sending uplink traffic or uplink control data, or receiving downlink traffic or downlink control data, respectively, according to sub-band specific channel and signal configuration parameters configured to the UE in response to the duplex mode of the UE including SBFD, or according to bandwidth portion configuration parameters configured to the UE in response to the UE being a time division duplex UE, and receiving downlink control information including a bit indicating the use of the SBFD mode.

[0177] The channel and signal configuration circuit 1243 may be configured for various other functions, including, for example, in response to the UE's duplex mode (including SBFD) and receipt of a periodic or semi-persistent uplink or downlink channel or reference signal configuration, the processor 1204 or the channel and signal configuration circuit 1243 of the processor 1204 may be further configured to: maintain the periodic or semi-persistent repetition of the uplink or downlink channel or reference signal associated with the uplink or downlink channel or reference signal configuration in response to the uplink or downlink channel or reference signal appearing in the SBFD time slot; and discard the periodic or semi-persistent repetition of the uplink or downlink channel or reference signal in response to the uplink or downlink channel or reference signal appearing in the non-SBFD time slot.

[0178] Fig.13 1 is a flow chart illustrating an exemplary process 1300 (e.g., a method of wireless communication) at a user equipment (e.g., a wireless communication device, a mobile device, a scheduled entity) according to some aspects of the present disclosure. For example, process 1300 may occur in a wireless communication network (such as Figure 1 , Figure 2 and / or Figure 6As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required in all implementations. In some examples, process 1300 may be performed by combining Fig.12 The process 1300 is performed by the user equipment 1200 described and illustrated. In some examples, the process 1300 can be performed by any suitable device or component for performing the functions or algorithms described herein.

[0179] At block 1302, the user equipment or its processor may send an indication that the user equipment is aware of sub-band full-duplex operation. For example, the sub-band full-duplex aware circuit 1242 in conjunction with, for example, the transceiver 1214 and the antenna array 1216 (all as combined) Fig.12 ) shown and described may provide means for sending an indication that the user equipment is aware of sub-band full-duplex operation.

[0180] At box 1304, the user equipment or its processor may receive scheduling information from the network access node (e.g., in response to sending an indication at 1302) indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of a sub-band full-duplex (SBFD) time slot or a flexible symbol or time slot.

[0181] According to some aspects, the user equipment or its processor may be further configured to: in the SBFD time slot: send uplink traffic or uplink control signals, or receive downlink traffic or downlink control signals, respectively, according to the subband specific channels and signal configuration parameters configured to the UE in response to the UE being aware of the SBFD, or according to bandwidth portion configuration parameters configured to the UE in response to the UE being a time division duplex UE.

[0182] In some examples, in response to knowing SBFD and receiving a periodic or semi-persistent uplink or downlink channel or reference signal configuration, the UE or its processor is further configured to: in response to the uplink or downlink channel or reference signal appearing in a SBFD time slot, maintain the periodic or semi-persistent repetition of the uplink or downlink channel or reference signal associated with the uplink or downlink channel or reference signal configuration; and in response to the uplink or downlink channel or reference signal appearing in a non-SBFD time slot, discard the periodic or semi-persistent repetition of the uplink or downlink channel or reference signal.

[0183] 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 entity, a mobility element of the network, a radio access network (RAN) node, a core network entity, a network element or 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 architecture or a decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, a network access node, 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.

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

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

[0186] Fig.141 is a schematic diagram of an example disaggregated base station architecture 1400 according to some aspects of the present disclosure. The disaggregated base station 1400 architecture may include one or more central units (CUs) 1410 that may communicate directly with a core network 1420 via a backhaul link, or indirectly with the core network 1420 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 1425 via an E2 link, or a non-real-time (non-RT) RIC 1415 associated with a service management and orchestration (SMO) framework 1405, or both. The CU 1410 may communicate with one or more distributed units (DUs) 1430 via respective midhaul links, such as an F1 interface. The DU 1430 may communicate with one or more radio units (RUs) 1440 via respective fronthaul links. The RU 1440 may communicate with respective UEs 1442 via one or more radio frequency (RF) access links. In some implementations, a UE 1442 may be served by multiple RUs 1440 simultaneously. Figure 1 and Figure 2 Any of the UEs or scheduled entities illustrated and described are the same or similar.

[0187] Each of these units (i.e., CU 1410, DU 1430, RU 1440, and near-RT RIC 1425, non-RTRIC 1415, and SMO framework 1405) may include one or more interfaces, or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) that is configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0188] In some aspects, CU 1410 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 that is configured to communicate signals with other control functions hosted by CU 1410. CU1410 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 1410 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 1410 may be implemented to communicate with DU 1430 for network control and signaling.

[0189] DU 1430 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 1440. In some aspects, DU 1430 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 partitioning such as that defined by the 14th Generation Partnership Project (3GPP). In some aspects, DU 1430 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 DU 1430 or with control functions hosted by CU 1410.

[0190] The lower layer functionality may be implemented by one or more RUs 1440. In some deployments, a RU 1440 controlled by a DU 1430 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 a functional split (such as a lower layer functional split). In such an architecture, the RU 1440 may be implemented to handle over-the-air (OTA) communications with one or more UEs 1442. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 1440 may be controlled by the corresponding DU 1430. In some scenarios, this configuration may enable the DU 1430 and CU 1410 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0191] The SMO framework 1405 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 1405 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 1405 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 1490) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 1410, DU 1430, RU 1440, and near-RT RIC 1425. In some specific implementations, the SMO framework 1405 may communicate with hardware aspects of the 14G RAN (such as an open eNB (O-eNB) 1411) via the O1 interface. Additionally, in some implementations, the SMO framework 1405 can communicate directly with one or more RUs 1440 via the O1 interface. The SMO framework 1405 can also include a non-RTRIC 1415 configured to support the functionality of the SMO framework 1405.

[0192] The non-RT RIC 1415 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 1425. The non-RT RIC 1415 may be coupled to or in communication with the near-RT RIC 1425 (such as via an A1 interface). The near-RT RIC 1425 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 1410, one or more DUs 1430, or both, and the O-eNB with the near-RT RIC 1425.

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

[0194] Of course, in the above example, Fig.10 The processor 1004 and / or Fig.12 The circuits included in the processor 1204 are provided as examples only. Other components for performing the described processes or functions may be included in various aspects of the present disclosure, including but not limited to storage in Fig.10 Computer readable medium 1010 and / or Fig.12 Computer readable medium 1210 or Figure 1 , Figure 2 , Figure 6 , Fig.10 , Fig.12 and / or Fig.14 In any other suitable device or component described in any of the foregoing and utilizing, for example, Figure 4 Figure 5 Figure 6 , Figure 7 , Figure 8 , Fig. 9 , Fig.11 and / or Fig.13 Instructions of the described processes and / or algorithms.

[0195] The following provides an overview of various aspects of the disclosure:

[0196] Aspect 1: A network access node, comprising: a memory; and a processor, the processor being coupled to the memory, wherein the processor is configured to: receive an indication that a user equipment is aware of sub-band full-duplex operation based at least in part on information stored in the memory; and in response to receiving the indication, utilize radio resource control (RRC) signaling to send at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration.

[0197] Aspect 2: The network access node according to Aspect 1, wherein the downlink subband specific channel and signal configuration comprises at least one of the following: a cell-specific subband common parameter, a user equipment-specific subband dedicated parameter, or a combination of the subband common parameter and the subband dedicated parameter.

[0198] Aspect 3: The network access node according to aspect 2, wherein the cell-specific sub-band common parameters or the user equipment-specific sub-band common parameters are configured per cell or per bandwidth part (BWP), respectively.

[0199] Aspect 4: The network access node according to any one of aspects 1 to 3, wherein a plurality of subband configurations are configured, and each subband configuration is marked with an identifier (ID).

[0200] Aspect 5: A network access node according to any one of Aspects 1 to 4, wherein the RRC signaling associated with the downlink subband specific channel and signal configuration includes at least one of the following items: physical downlink shared channel configuration parameters, physical downlink control channel configuration parameters, semi-persistent scheduling configuration parameters, or downlink subband timing and frequency indication parameters; and the RRC signaling associated with the uplink subband specific channel and signal configuration includes at least one of the following items: physical uplink shared channel configuration parameters, physical uplink control channel configuration parameters, uplink configuration grant configuration parameters, sounding reference signal configuration parameters, physical random access channel (PRACH) configuration parameters, or uplink subband timing and frequency indication parameters.

[0201] Aspect 6: A network access node according to any one of aspects 1 to 5, wherein the RRC signaling includes a parameter indicating that the downlink subband specific channel and signal configuration or the uplink subband specific channel and signal configuration is dedicated to a specific channel or a specific signal.

[0202] Aspect 7: The network access node according to any one of aspects 1 to 6, wherein the processor is further configured to: send RRC signaling, the RRC signaling including parameters indicating a sub-band full-duplex specification common to all signals and channels.

[0203] Aspect 8: The network access node according to aspect 7, wherein the sub-band full-duplex specification is at least one of a timing advance parameter or a unified transmission configuration indicator state.

[0204] Aspect 9: A network access node according to any one of Aspects 1 to 8, wherein the processor is further configured to perform at least one of the following: sending a downlink bandwidth portion configuration associated with the uplink subband specific channel and signal configuration, or sending an uplink bandwidth portion configuration associated with the downlink subband specific channel and signal configuration.

[0205] Aspect 10: A network access node according to Aspect 9, wherein an association is established by including an uplink subband identifier (e.g., ul-subband-Id, ul-dl-subband-id) in at least one of the following items: the downlink bandwidth portion configuration for associating the downlink bandwidth portion configuration with the uplink subband specific channel and signal configuration, or the uplink bandwidth portion configuration for associating the uplink bandwidth portion configuration with the downlink subband specific channel and signal configuration.

[0206] Aspect 11: A network access node according to any one of Aspects 1 to 10, wherein the downlink subband specific channel and signal configuration and the uplink subband specific channel and signal configuration together include a downlink-uplink subband specific pair, and the processor is further configured to: send a downlink bandwidth portion configuration in association with the downlink-uplink subband specific pair.

[0207] Aspect 12: A network access node according to any one of Aspects 1 to 11, wherein the downlink sub-band specific channel and signal configuration is different from both the bandwidth portion downlink common configuration and the bandwidth portion downlink dedicated configuration, and the uplink sub-band specific channel and signal configuration is different from both the bandwidth portion uplink common configuration and the bandwidth portion uplink dedicated configuration.

[0208] Aspect 13. A method operating at a network access node, the method comprising: receiving an indication that a user equipment is aware of sub-band full-duplex operation; and in response to receiving the indication, utilizing radio resource control (RRC) signaling to send at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration.

[0209] Aspect 14: An apparatus comprising: a component for receiving an indication that a user equipment is aware of sub-band full-duplex operation; and a component for using radio resource control (RRC) signaling to send at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration in response to receiving the indication.

[0210] Aspect 15: A computer-readable medium storing computer executable code, the computer executable code comprising instructions for performing the following operations: receiving an indication that a user equipment is aware of sub-band full-duplex operation; and in response to receiving the indication, utilizing radio resource control (RRC) signaling to send at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration.

[0211] Aspect 16: A user equipment (UE), comprising: a memory; and a processor, the processor being coupled to the memory, wherein the processor is configured to: receive scheduling information from a network access node based at least in part on information stored in the memory, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full-duplex (SBFD) time slot, or a flexible symbol or time slot.

[0212] Aspect 17: The user equipment according to Aspect 16, wherein the processor is further configured to: in the SBFD time slot: send uplink traffic or uplink control signals, or receive downlink traffic or downlink control signals, respectively, according to a subband specific channel and a signal configuration parameter configured to the UE in response to the UE knowing SBFD, or according to a bandwidth portion configuration parameter configured to the UE in response to the UE being a time division duplex UE.

[0213] Aspect 18: A user equipment according to Aspect 16 or 17, wherein the processor is further configured to: in the flexible symbol or time slot: send uplink traffic or uplink control data, or receive downlink traffic or downlink control data, respectively, according to the sub-band specific channel and signal configuration parameters configured to the UE in response to the duplex mode of the UE including SBFD, or according to the bandwidth portion configuration parameters configured to the UE in response to the UE being a time division duplex UE, and receive downlink control information including a bit indicating the use of the SBFD mode.

[0214] Aspect 19: A user equipment according to any one of Aspects 16 to 18, wherein in response to the UE being aware of SBFD and receiving a periodic or semi-persistent uplink or downlink channel or reference signal configuration, the processor is further configured to: in response to the uplink or downlink channel or reference signal appearing in an SBFD time slot, maintain the periodic or semi-persistent repetition of the uplink or downlink channel or reference signal associated with the uplink or downlink channel or reference signal configuration; and in response to the uplink or downlink channel or reference signal appearing in a non-SBFD time slot, discard the periodic or semi-persistent repetition of the uplink or downlink channel or reference signal.

[0215] Aspect 20. A method operating at a user equipment, the method comprising: receiving scheduling information from a network access node with sub-band full-duplex capability, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full-duplex (SBFD) time slot, or a flexible symbol or time slot.

[0216] Aspect 21: An apparatus comprising: a component for receiving scheduling information from a network access node with subband full-duplex capability, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a subband full-duplex (SBFD) time slot, or a flexible symbol or time slot.

[0217] Aspect 22: A computer-readable medium storing computer executable code, the computer executable code comprising instructions for performing the following operations: receiving scheduling information from a network access node with sub-band full-duplex capability, the scheduling information indicating that the UE is scheduled to send an uplink or receive a downlink in at least one of the following: a sub-band full-duplex (SBFD) time slot, or a flexible symbol or time slot.

[0218] Aspect 23: A method of wireless communication at a network access node in a wireless network, the method being operable to implement any of the features described in the accompanying description in any configuration, alone or in combination with any other features.

[0219] Aspect 24: A network access node configured for wireless communication, the network access node comprising: a processor; a memory communicatively coupled to the processor; and a transceiver communicatively coupled to the processor, wherein the processor is configured to implement any feature described in the attached specification in any configuration, alone or in combination with any other feature, based at least in part on information stored in the memory.

[0220] Aspect 25: A network access node for wireless communications, the network access node comprising: means for implementing any of the features described in the accompanying specification in any configuration, alone or in combination with any other features.

[0221] Aspect 26: A computer readable medium storing computer executable code comprising instructions for implementing any of the features described in the accompanying specification in any configuration, alone or in combination with any other features.

[0222] Aspect 27: A method of wireless communication at a wireless communication device within a wireless network, the method being operable to implement any of the features described in the accompanying specification in any configuration, alone or in combination with any other features.

[0223] Aspect 28: A wireless communication device configured for wireless communication, the network access node comprising: a processor; a memory, the memory being communicatively coupled to the processor; and a transceiver, the transceiver being communicatively coupled to the processor, wherein the processor is configured to implement any feature described in the attached specification in any configuration, alone or in combination with any other feature, based at least in part on information stored in the memory.

[0224] Aspect 29: A wireless communication device for wireless communication, the network access node comprising: means for implementing any feature described in the attached specification in any configuration, alone or in combination with any other feature.

[0225] Aspect 30: A computer readable medium storing computer executable code comprising instructions for implementing any of the features described in the accompanying specification in any configuration, alone or in combination with any other features.

[0226] Several aspects of wireless communication networks have been presented with reference to exemplary 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.

[0227] For 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 3rd Generation Partnership Project 2 (3GPP2), such as CDMA 2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing 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.

[0228] 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 discussed features, advantages, or modes of operation. 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).

[0229] Figures 1 to 14 One or more of the illustrated components, steps, features and / or functions may be rearranged and / or combined into a single component, step, feature or function, or may be embodied 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 14 The 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.

[0230] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. 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 the 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. Although some of the examples illustrated herein only depict the time domain and the frequency domain, additional domains such as the spatial domain are also contemplated in the present disclosure.

[0231] 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" referring to 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. Structures A and / or B are intended to cover: A; B; and A and B. As used herein, the word "obtain" may mean, for example, obtaining, calculating, constructing, deriving, determining, receiving, and / or retrieving. The foregoing list is exemplary and non-restrictive. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are or later become 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 disclosed to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element should be interpreted under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase “means for…” or, in the case of a method claim, the phrase “step for…” is used to recite the element.

Claims

1. A network access node, the network access node comprising: Memory; and a processor coupled to the memory, wherein the processor is configured to: receiving an indication that the user equipment is aware of sub-band full-duplex operation; as well as At least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration is sent utilizing radio resource control (RRC) signaling in response to receiving the indication.

2. The network access node according to claim 1, wherein the downlink sub-band specific channel and signal configuration comprises at least one of the following: Cell-specific subband common parameters, User equipment specific sub-band dedicated parameters, or A combination of the sub-band common parameters and the sub-band specific parameters.

3. The network access node according to claim 2, wherein the cell-specific sub-band common parameters or the user equipment-specific sub-band dedicated parameters are configured per cell or per bandwidth part (BWP), respectively.

4. The network access node according to claim 2, wherein a plurality of sub-band configurations are configured and each sub-band configuration is marked with an identifier (ID).

5. The network access node of claim 1 , wherein the processor is further configured to: transmitting, using the RRC signaling associated with the downlink subband specific channel and signal configuration, at least one of: a physical downlink shared channel configuration parameter, a physical downlink control channel configuration parameter, a semi-persistent scheduling configuration parameter, or a downlink subband timing and frequency indication parameter; and The RRC signaling associated with the uplink subband specific channel and signal configuration is used to send at least one of the following: physical uplink shared channel configuration parameters, physical uplink control channel configuration parameters, uplink configuration grant configuration parameters, sounding reference signal configuration parameters, physical random access channel (PRACH) configuration parameters, or uplink subband timing and frequency indication parameters.

6. The network access node according to claim 1, wherein the processor is further configured to: The RRC signaling is used to transmit a parameter indicating that the downlink sub-band specific channel and signal configuration or the uplink sub-band specific channel and signal configuration is dedicated to a specific channel or a specific signal.

7. The network access node of claim 1, wherein the processor is further configured to: The RRC signaling is sent including parameters indicating a sub-band full-duplex specification common to all signals and channels.

8. The network access node of claim 7, wherein the sub-band full-duplex specification is at least one of a timing advance parameter or a unified transmission configuration indicator state.

9. The network access node of claim 1 , wherein the processor is further configured to perform at least one of the following operations based at least in part on the information stored in the memory: sending a downlink bandwidth portion configuration associated with the uplink sub-band specific channel and signal configuration; or An uplink bandwidth portion configuration associated with the downlink sub-band specific channel and signal configuration is transmitted.

10. The network access node according to claim 9, wherein the processor is further configured to: The subband identifiers are respectively sent in at least one of the following: the downlink bandwidth portion configuration for associating the downlink bandwidth portion configuration with the uplink sub-band specific channel and signal configuration; or The uplink bandwidth portion configuration is used to associate the uplink bandwidth portion configuration with the downlink sub-band specific channel and signal configuration.

11. The network access node of claim 1 , wherein the downlink sub-band specific channel and signal configuration and the uplink sub-band specific channel and signal configuration together comprise a downlink-uplink sub-band specific pair, and the processor is further configured to: A downlink bandwidth portion configuration is sent in association with the downlink-uplink subband specific pair.

12. The network access node according to claim 1, wherein The downlink sub-band specific channel and signal configuration is different from both the bandwidth portion downlink common configuration and the bandwidth portion downlink dedicated configuration; and The uplink sub-band specific channel and signal configuration is different from both the bandwidth portion uplink common configuration and the bandwidth portion uplink dedicated configuration.

13. A method operating at a network access node, the method comprising: receiving an indication that the user equipment is aware of sub-band full-duplex operation; as well as At least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration is sent utilizing radio resource control (RRC) signaling in response to receiving the indication.

14. The method of claim 13, wherein the downlink sub-band specific channel and signal configuration comprises at least one of: Cell-specific subband common parameters, User equipment specific sub-band dedicated parameters, or A combination of the sub-band common parameters and the sub-band specific parameters.

15. The method according to claim 14, wherein the cell-specific subband common parameters or the user equipment-specific subband dedicated parameters are configured per cell or per bandwidth part (BWP), respectively.

16. The method of claim 14, wherein a plurality of sub-band configurations are configured and each sub-band configuration is marked with an identifier (ID).

17. The method according to claim 13, further comprising: transmitting, using the RRC signaling associated with the downlink subband specific channel and signal configuration, at least one of: a physical downlink shared channel configuration parameter, a physical downlink control channel configuration parameter, a semi-persistent scheduling configuration parameter, or a downlink subband timing and frequency indication parameter; and The RRC signaling associated with the uplink subband specific channel and signal configuration is used to send at least one of the following: physical uplink shared channel configuration parameters, physical uplink control channel configuration parameters, uplink configuration grant configuration parameters, sounding reference signal configuration parameters, physical random access channel (PRACH) configuration parameters, or uplink subband timing and frequency indication parameters.

18. The method according to claim 13, further comprising: The RRC signaling is used to transmit a parameter indicating that the downlink sub-band specific channel and signal configuration or the uplink sub-band specific channel and signal configuration is dedicated to a specific channel or a specific signal.

19. The method according to claim 13, further comprising: The RRC signaling is sent including parameters indicating a sub-band full-duplex specification common to all signals and channels.

20. The method of claim 19, wherein the sub-band full-duplex specification is at least one of a timing advance parameter or a unified transmission configuration indicator state.

21. The method according to claim 13, further comprising at least one of the following operations: sending a downlink bandwidth portion configuration associated with the uplink sub-band specific channel and signal configuration; or An uplink bandwidth portion configuration associated with the downlink sub-band specific channel and signal configuration is transmitted.

22. The method according to claim 21, further comprising: The subband identifiers are respectively sent in at least one of the following: the downlink bandwidth portion configuration for associating the downlink bandwidth portion configuration with the uplink sub-band specific channel and signal configuration; or The uplink bandwidth portion configuration is used to associate the uplink bandwidth portion configuration with the downlink sub-band specific channel and signal configuration.

23. The method of claim 13, wherein the downlink sub-band specific channel and signal configuration and the uplink sub-band specific channel and signal configuration together comprise a downlink-uplink sub-band specific pair, the method further comprising: A downlink bandwidth portion configuration is sent in association with the downlink-uplink subband specific pair.

24. The method of claim 13, wherein The downlink sub-band specific channel and signal configuration is different from both the bandwidth portion downlink common configuration and the bandwidth portion downlink dedicated configuration; and The uplink sub-band specific channel and signal configuration is different from both the bandwidth portion uplink common configuration and the bandwidth portion uplink dedicated configuration.

25. An apparatus, comprising: means for receiving an indication that the user equipment is aware of sub-band full-duplex operation; and Means for transmitting at least one of a downlink sub-band specific channel and signal configuration or an uplink sub-band specific channel and signal configuration utilizing radio resource control (RRC) signaling in response to receiving the indication.

26. The apparatus according to claim 25, further comprising: means for transmitting, using said RRC signaling associated with said downlink sub-band specific channel and signal configuration, at least one of: a physical downlink shared channel configuration parameter, a physical downlink control channel configuration parameter, a semi-persistent scheduling configuration parameter, or a downlink sub-band timing and frequency indication parameter; and Means for transmitting at least one of: a physical uplink shared channel configuration parameter, a physical uplink control channel configuration parameter, an uplink configuration grant configuration parameter, a sounding reference signal configuration parameter, a physical random access channel (PRACH) configuration parameter, or an uplink subband timing and frequency indication parameter using the RRC signaling associated with the uplink subband specific channel and signal configuration.

27. The apparatus according to claim 25, further comprising: The RRC signaling is used to transmit a parameter indicating that the downlink sub-band specific channel and signal configuration or the uplink sub-band specific channel and signal configuration is dedicated to a specific channel or a specific signal.

28. The apparatus of claim 25, further comprising at least one of: means for transmitting a downlink bandwidth portion configuration associated with said uplink sub-band specific channel and signal configuration; or Means for transmitting an uplink bandwidth portion configuration associated with said downlink sub-band specific channel and signal configuration.

29. The apparatus according to claim 28, further comprising: Means for respectively transmitting a subband identifier in at least one of: the downlink bandwidth portion configuration for associating the downlink bandwidth portion configuration with the uplink sub-band specific channel and signal configuration; or The uplink bandwidth portion configuration is used to associate the uplink bandwidth portion configuration with the downlink sub-band specific channel and signal configuration.

30. The apparatus of claim 25, wherein the downlink sub-band specific channel and signal configuration and the uplink sub-band specific channel and signal configuration together comprise a downlink-uplink sub-band specific pair, the apparatus further comprising: Means for transmitting a downlink bandwidth portion configuration in association with the downlink-uplink subband specific pair.

Images